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.
 

Missing jar in CR3 distribution. Both were included in CR2
- ocpsoft-pretty-time.jar (Used by org.jboss.seam.examples.booking.booking.BookingAgent)
- prettyfaces-jsf2.jar. Not sure for this one, but there is a file name pretty-config.xml under WEB-INF...Maybe this is the later
file that should not be there.

If you want me to create JIRAs for those, I will

Yep, both are needed for the example.
 

And now I'm stuck with this exception at startup:

An error occured while initializing MyFaces: null
     java.util.NoSuchElementException
    at java.util.HashMap$AbstractMapIterator.makeNext(HashMap.java:124)
    at java.util.HashMap$KeyIterator.next(HashMap.java:195)
    at org.jboss.seam.faces.event.AbstractListener.getListeners(AbstractListener.java:27)
    at org.jboss.seam.faces.event.DelegatingSystemEventListener.getEventListeners(DelegatingSystemEventListener.java:48)
    at org.jboss.seam.faces.event.DelegatingSystemEventListener.processEvent(DelegatingSystemEventListener.java:36)
    at javax.faces.event.SystemEvent.processListener(SystemEvent.java:43)
    at org.apache.myfaces.application.ApplicationImpl._traverseListenerList(ApplicationImpl.java:2110)
    at org.apache.myfaces.application.ApplicationImpl.access$000(ApplicationImpl.java:118)
    at org.apache.myfaces.application.ApplicationImpl$SystemListenerEntry.publish(ApplicationImpl.java:2204)
    at org.apache.myfaces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:557)
    at org.apache.myfaces.webapp.AbstractFacesInitializer._dispatchApplicationEvent(AbstractFacesInitializer.java:251)
    at org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces(AbstractFacesInitializer.java:143)
    at org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:112)
    at com.ibm.ws.webcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:1635)

I will try to investigate why this occur

Ah, chances are Seam Faces is assuming that a class will in fact be a bean. However, it never checks to ensure this is the case. It should likely be more defensive. As to why the class is not a bean, that's another story.

Denis, would you be able to provide the steps to get websphere v8 running so that other people in the community (and team) can get up to speed testing on websphere? I'm looking for the download link, requirements to get the download and how to get to a running state ready to accept deployments.

Thanks,

-Dan

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

http://www.google.com/profiles/dan.j.allen#about
http://mojavelinux.com
http://mojavelinux.com/seaminaction