Looks like it could be a JAXP config issue. Need to follow-up with the full stack-trace.

websphere 6.0.2 and 6.1 also don't work with facelets-enh

jetty 6.1 doesn't work with facelets-enh too

Update the ApplicationBuilder class in two ways:

• improved logging and exceptions if the JAXB schema and metaData files could not successfully be loaded
• updated how we load the metaData and schema data to avoid resolving the absolute path unless using websphere.

Though back over to QA for testing.

Mandeep;

I've updated the the enhanced version of showcase in the hope that it will resolve server specific issues. Could you please test again against the problematic servers.

Patrick says:

Looks like showcase is more or less running on weblogic 9.2. However it looks like there are some issues with push and/or the progress bar component or demo.

Mandeep wrote:

The new test results below are from weblogic 9.2

> > The component-showcase works except progress bar and file upload
> > components.
> > I see following errors on the server:
> >
> > INFO - Adapting to Thread Blocking environment -
> > com.icesoft.faces.webapp.http.servlet.EnvironmentAdaptingServlet
> > Exception in thread "Timer-4"
> > java.lang.ArrayIndexOutOfBoundsException: -1
> > at
> > com.icesoft.net.messaging.jms.JMSAdapter.lookUpTopic(JMSAdapter.java:533)
> > at
> > com.icesoft.net.messaging.jms.JMSAdapter.publish(JMSAdapter.java:246)
> > at
> > com.icesoft.net.messaging.MessagePipeline.publish(MessagePipeline.java:151)
> >
> > at com.icesoft.net.messaging.PublishTask.run(PublishTask.java:46)
> > at java.util.TimerThread.mainLoop(Timer.java:512)
> > at java.util.TimerThread.run(Timer.java:462)
> > INFO - core render service created:
> > core pool size : 10
> > max pool size : 15
> > keep alive time: 300000 - com.icesoft.faces.async.render.RenderHub
> > ERROR - Failed to notify listener:
> > com.icesoft.faces.context.View$3@197a82f - com.icesoft.faces.context.View
> > java.lang.IllegalStateException: Timer already cancelled.
> > at java.util.Timer.sched(Timer.java:354)
> > at java.util.Timer.schedule(Timer.java:170)
> > at
> > com.icesoft.net.messaging.MessageServiceClient.schedule(MessageServiceClient.java:825)
> >
> > at
> > com.icesoft.net.messaging.MessagePipeline.enqueue(MessagePipeline.java:129)
> >
> > at
> > com.icesoft.net.messaging.MessageServiceClient.publish(MessageServiceClient.java:922)
> >
> > at
> > com.icesoft.net.messaging.MessageServiceClient.publish(MessageServiceClient.java:493)
> >
> > at
> > com.icesoft.net.messaging.MessageServiceClient.publish(MessageServiceClient.java:604)
> >
> > at
> > com.icesoft.faces.async.server.AsyncHttpServerAdaptingServlet$1.run(AsyncHttpServerAdaptingServlet.java:110)
> >
> > at
> > com.icesoft.faces.webapp.http.core.ViewQueue.put(ViewQueue.java:17)
> > at com.icesoft.faces.context.View$3.run(View.java:76)
> > at com.icesoft.faces.context.View.broadcastTo(View.java:195)
> > at com.icesoft.faces.context.View.put(View.java:170)
> > at
> > com.icesoft.faces.context.PushModeSerializer.serialize(PushModeSerializer.java:72)
> >
> > at
> > com.icesoft.faces.context.DOMResponseWriter.endDocument(DOMResponseWriter.java:160)
> >
> > at
> > com.icesoft.faces.facelets.D2DFaceletViewHandler.renderResponse(D2DFaceletViewHandler.java:283)
> >
> > at
> > com.icesoft.faces.application.D2DViewHandler.renderView(D2DViewHandler.java:161)
> >
> > at
> > com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:107)
> >
> > at
> > com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:245)
> > at
> > com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:137)
> > at
> > com.icesoft.faces.webapp.xmlhttp.PersistentFacesState.render(PersistentFacesState.java:189)
> >
> > at
> > com.icesoft.faces.webapp.xmlhttp.PersistentFacesState.executeAndRender(PersistentFacesState.java:373)
> >
> > at
> > com.icesoft.faces.async.render.RunnableRender.run(RunnableRender.java:143)
> >
> > at
> > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
> >
> > at
> > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> >
> > at java.lang.Thread.run(Thread.java:595)

As I suspected, the exception is due to the fact that the auto-detection system is not finished yet for WebLogic (ICE-3162). Adding the following to the ICEfaces application's web.xml should fix this:

<context-param>
<param-name>com.icesoft.net.messaging.properties</param-name>
<param-value>weblogic.properties</param-value>
</context-param>

Assigning back to Mandeep for confirmation.

File upload and progress bar still not working:

INFO - Trying JMS Environment:
java.naming.provider.url = t3://localhost:7001
java.naming.factory.initial = weblogic.jndi.WLInitialContextFactory

• com.icesoft.net.messaging.jms.JMSAdapter
  ERROR - Failed JMS Environment: Unable to resolve 'ConnectionFactory'. Resolved '' - com.icesoft.net.messaging.jms.JMSAdapter
  ERROR - - com.icesoft.net.messaging.MessagePipeline
  com.icesoft.net.messaging.MessageServiceException: javax.naming.NameNotFoundException: Unable to resolve 'ConnectionFactory'. Resolved ''; remaining name 'ConnectionFactory'
  at com.icesoft.net.messaging.jms.JMSAdapter.publish(JMSAdapter.java:239)
  at com.icesoft.net.messaging.MessagePipeline.publish(MessagePipeline.java:151)
  at com.icesoft.net.messaging.PublishTask.run(PublishTask.java:46)
  at java.util.TimerThread.mainLoop(Timer.java:512)
  at java.util.TimerThread.run(Timer.java:462)
  Caused by: javax.naming.NameNotFoundException: Unable to resolve 'ConnectionFactory'. Resolved ''; remaining name 'ConnectionFactory'
  at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
  at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
  at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
  at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
  at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
  at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:362)
  at javax.naming.InitialContext.lookup(InitialContext.java:351)
  at com.icesoft.net.messaging.jms.JMSAdapter.initialize(JMSAdapter.java:508)
  at com.icesoft.net.messaging.jms.JMSAdapter.publish(JMSAdapter.java:237)
  ... 4 more
  INFO - Trying JMS Environment:
  java.naming.provider.url = t3://localhost:7001
  java.naming.factory.initial = weblogic.jndi.WLInitialContextFactory
• com.icesoft.net.messaging.jms.JMSAdapter

This seems to be working now on WebLogic 9.2. Marking this one as FIXED.