On Wed, 19 Jul 2006 19:28:30 +0200, Marshall Culpepper
1) AFAIK the .components file describes different types of components
is not generic enough to simply describe arbitrary packaging
configurations.. It's main benefit is it carries a lot of metadata inside
the file, hence why i've allowed free-form "property" elements at any
in the tree of my .packages file..
mkay...what are free-form property elements usable/used for ?
2) I agree completely, and this is already something I've been
Copy-on-save/modify and Synchronize-on-delete are both supported (if not
100% fully functional yet) in my current implementation
cool - let me know when it hit the cvs (i'm currently working intensively
to create a usable seam project environment where this is an important
btw. one thing that I think is important is that when you change jsp's,
they should be synched instantly and jboss should detect them, but if you
then the autodeployment (which is done by auto-touch in jboss afaik)
should only be done
when explicitly asked for it...e.g. a short cut/action of some sort.
3) The MainDeployer MBean takes deployment URLs as a JMX attribute,
theoretically it would be as simple as running twiddle to add the user's
project deployment URL at runtime. I'm honestly not sure if the
supports changing the deploymentURLs attribute at runtime or if it's one
the few "static configurations" of JBoss. Of course the downside to this
would be no transparency and the IDE would have to manage persisting that
well it could be an option...
I'm not sure how WTP handles deployment, Rob can you shed some
auto-setting up the J2EE package for the adapter or is the adapter
to do it?
On 7/19/06, Max Rydahl Andersen <max.andersen(a)jboss.com> wrote:
> There are a couple of disturbing bugs about "delta-detection" in WTP:
> ...and the worst thing i see is that even if we could make our WTP
> adapter insanely quick ;), we will not be able to opt-out of those
> traversals that the WTP "bug" is doing.
> Great...Rob - is this something you have been looking into ?
> > Hi guys,
> > Been looking at various aspects of WTP deployment, our IDE and JBoss
> > deployement in context of easy Seam project deployment,
> > and out sprung some questions ;)
> > 1) Does anyone know about the file
> > .settings/org.eclipse.wst.common.component in WTP ?
> > This file looks to do *some* of the things Marshall is trying to
> > accomplish in context of
> > his xml file for describing packaging. Do you know how they relate and
> > if we use that
> > file (or some dependent API) for anything ?
> > 2) "copy-on-save" should be "synchronize-on-modify"
> > When we get around making it possible to listen to resources and copy
> > files according
> > to the packaging we will also need to be able to handle "delete" of
> > hence the name
> > of this bullet point ;)
> > 3) Exploded deployment on JBoss
> > Can we point a jboss to a specific directory without the user having
> > edit services.xml ?
> > Or does anyone know if WTP actually maintains a "deployed" structure
> > internally or is that
> > completely up to the WTP server plugins to handle ?
> Max Rydahl Andersen
> JBoss Inc
> jbosside-dev mailing list
Max Rydahl Andersen