> > accessed. That's the developer perspective in me.
> > > >
> > > > Now for the Architect/PM side. I very much
believe in
> > > > the seperation of duties, and auditability of
> > > > application/server/network ad
d have
> > > any chance at mashing up with generic code coming from
> > > my web developer or ejb/database developer! A
> > > template system that incorporated creation of the
> > > container specific configuration b
rated creation of the
> > container specific configuration based on the web.xml
> > and ejb-jar.xml would be a valuable tool within the
> > server administration tool set. I would expect a tool
>
> > like this t
this was I believe a
> component of the server jar deployment wizard.
>
> My two cents.
>
> Mark Aufdencamp
> [EMAIL PROTECTED]
>
>
>
he management console in direct proximity to
> the deploy application tool! Setting deployment specific environment values
> falls within this scope as well. In my early J2EE experiences with
> Websphere 3.5, this was I believe a component of the server jar
> deployment wizard.
&g
J2EE experiences with
Websphere 3.5, this was I believe a component of the server jar deployment
wizard.
My two cents.
Mark Aufdencamp
[EMAIL PROTECTED]
Original Message ----
Subject: How important is simplifying Creation/Updation of Geronimo
Deployment Plans?
From: "Shi
