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
--
Marshall Culpepper
marshall.culpepper(a)jboss.com
JBossIDE Team Lead
JBoss, a division of Red Hat