On Mon, Mar 21, 2011 at 19:55, Dan Allen <dan.j.allen@gmail.com> wrote:
On Mon, Mar 21, 2011 at 19:37, Denis Forveille <denis.forveille@gmail.com> wrote:

I'm trying to deploy the seam-booking app on WebSphere v8 beta (WAS).

It still fails to start. My discoveries:

Extension that have their constructor in scope "package" instead of "public" that makes the initialization to fail in WAS:
- org.jboss.seam.servlet.ServletExtension    --> Dan you wrote in a previous mail that it was solved in CR3, it is not
- org.jboss.seam.servlet.logging.TypedMessageBundleAndLoggerExtension
- org.jboss.seam.solder.logging.TypedMessageLoggerExtension
- org.jboss.seam.solder.messages.TypedMessageBundleExtension
- org.jboss.seam.solder.serviceHandler.ServiceHandlerExtension
They may be other but they have not been "seen" by the initialization process..

Dan, if you want to create JIRA for those, please let me know

Oops. I was looking at the class, not the constructor. I'll fix in HEAD. You can go ahead and file a JIRA for reference.


filed and fixed.


Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597