Cool, we'll probably just end up creating a package type for Seam then..

Gavin King wrote: > You dont need to do anything special, just copy class files across to > the exploded dir. > > However, it is a special directory, WEB-INF/dev. > > On 3/9/07, *Marshall Culpepper * <marshall.culpepper(a)redhat.com > <mailto:marshall.culpepper@redhat.com>> wrote: > > Hey guys... > > Just wanted to start a thread about integrating our new packaging > tools > w/ Seam. IIRC, Gavin told me Monday that Seam has incremental > class/module deployment... is there anything special we need to do > to > trigger an update other than update/overwrite the code? Does the > incremental deployer only work with exploded deployments? > > -- > Marshall Culpepper > marshall.culpepper(a)jboss.com <mailto:marshall.culpepper@jboss.com> > JBossIDE Team Lead > JBoss, a division of Red Hat > > > > > -- > Gavin King > gavin.king(a)gmail.com <mailto:gavin.king@gmail.com> > http://hibernate.org > http://jboss.com/products/seam

What's the difference? > Yes, a "seam-gen" package type.

So help cure my ignorance here... How are "seam-gen" generated packages any different than the packages Seam normally accepts/deploys? Does Seam do special processing for "seam-gen" packages? (I'm guessing this is where WEB-INF/dev comes in?) Max Rydahl Andersen wrote: > >> What's the difference? >>> Yes, a "seam-gen" package type. > > seam-gen is a tool in Seam. Seam does not require the layout seam-gen > generates, thus it's a seam-gen layout/package. > > > ---- > Max Rydahl Andersen > callto://max.rydahl.andersen > > Hibernate > max(a)hibernate.org > http://hibernate.org > > JBoss a division of Red Hat > max.andersen(a)jboss.com

Fair enough, so if I understand correctly, Seam allows for a pretty flexible deployment similar to JBoss nested deployments? From the user's perspective, wouldn't it be better to call it a "Seam JAR" or some such rather than "seam-gen".. just to avoid confusion? The configuration only dictates a "default" packaging scenario anyway. Once the user is done setting up the JAR, they have full control of modifying it however they see fit. Max Rydahl Andersen wrote: > > seam-gen generates a specific structure that matches its build.xml > script and vice versa. > > It is single rooted opposed to e.g. WTP or netbeans projects which > can/is multirooted. > > Seam can be used in all of these scenarioes; it is seam-gen that > (currently) has this layout hence > it is a "seam-gen" related structure. > > WEB-INF/dev is the default location that Seam defines AFAIK. but the > rest is seam-gen specific. > > /max > >> So help cure my ignorance here... How are "seam-gen" generated >> packages any different than the packages Seam normally >> accepts/deploys? Does Seam do special processing for "seam-gen" >> packages? (I'm guessing this is where WEB-INF/dev comes in?) >> >> Max Rydahl Andersen wrote: >>> >>>> What's the difference? >>>>> Yes, a "seam-gen" package type. >>> >>> seam-gen is a tool in Seam. Seam does not require the layout seam-gen >>> generates, thus it's a seam-gen layout/package. >>> >>> >>> ---- >>> Max Rydahl Andersen >>> callto://max.rydahl.andersen >>> >>> Hibernate >>> max(a)hibernate.org >>> http://hibernate.org >>> >>> JBoss a division of Red Hat >>> max.andersen(a)jboss.com >> >> > > > > ---- > Max Rydahl Andersen > callto://max.rydahl.andersen > > Hibernate > max(a)hibernate.org > http://hibernate.org > > JBoss a division of Red Hat > max.andersen(a)jboss.com