On 1/12/07, Wendy Smoak <wsmoak@(protected):
>
> On 1/12/07, Joe Germuska <joe@(protected):
> > (I sent the below to the cargo users list, but haven't gotten a response
> in
> > several days, so I'm going to be gauche and send it to struts; now that
> > Struts2 uses Maven2, some Struts folks must be dealing with this
> [*cough*
> > Wendy :-) ] If anyone has advice, it will be appreciated... )
>
> You must have learned the secret-- I can't read all the mail I get, so
> I search for my name occasionally to see if anyone is calling me. :)


duly noted!

I'm slightly confused about what's going on, since you mention both an
> exploded webapp and remote deployment. I don't see how that would
> work.


Maybe I'm confused; the combinations of values for <type> (container),
<type> (configuration) and <type> (deployer) are not manifestly clear to me,
which I think is a combination of unintuitive naming, overloading the
concept of "type", and my laziness in not wanting to spend time developing a
deep understanding of the Cargo architecture.

I thought "remote" was the way that you did things if you had an already
running Tomcat instance. That's how we used the Codeczar plugin, so I was
trying to maintain the analog. Perhaps I should switch to trying to have
the plugin start Tomcat. When we used Tomcat with Maven 1 this way it
resulted in a fat memory-hogging Maven process hanging around not achieving
much, so I steered away from that and wasn't enthusiastic


> Best bet would be to construct a simple example app, maybe start with
> the Struts blank archetype and add the Cargo config, and post back to
> the Cargo list with a link to it.


I'll probably give this a shot when time allows, which is not just right
now...

Thanks again
Joe


--
Joe Germuska
Joe@(protected)

"The truth is that we learned from João forever to be out of tune."
-- Caetano Veloso