I've committed a new patched eapseamgen.zip that includes our jboss-
seam.jar that has ejb-jar.xml in the META-INF folder (which lets
Webtools 2.0.2 actually deploy the
<module><ejb>jboss-seam.jar</ejb></
module> correctly).
Forcing a new (hopefully final build) that will take some smoke tests
later tonight, and hopefully I will get a chance to upload everything
to sourceforge so Max and I can announce CR1 tomorrow.
On May 4, 2008, at 7:02 PM, Rob Stryker wrote:
Max:
Because of this change, any old seam projects will need to use the
new jboss-seam.jar. I know this is shitty. I know this sucks. I know
this is pretty much unacceptable.
But it's all that was possible to ensure the jboss-seam file gets
published. The only alternative was to remove it from
application.xml, and I suspect strongly that would have other bad
affects. If that's not the case, Marshall can roll back the change
and we can just remove it from application.xml.
But my impression was that it's required to be in application.xml.
And because of that, it needs a descriptor file or wtp 2.0.2 will
puke on it.
So... tl;dr = old seam 1.2 projects will need to upgrade their jboss-
seam.jar file.
Sucks.
- RS
Rob Stryker wrote:
> The most recent problem was that wtp is still too restrictive. It
> did not like our seam 1.2 jboss-seam.jar file. It refused to parse
> it because it had no deployment descriptor.
>
> When given a deployment descriptor with proper ejb 3.0 tags in it,
> such as interceptors etc, it puked because it didn't understand them.
>
> THe solution is to patch jboss-seam.jar and give it a skeleton ejb
> 3.0 ejb-jar.xml file.
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev