Hi "phtan",
Your problem with the calendar might be similar to my
<t:popup> problem. There is a bug in WAS 6.1 that
fails to locate javascript referenced by MyFaces. In
my case, the server log exception under the ffdc
folder shows something like this:
Exception = java.io.FileNotFoundException
Source =
com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest
probeid = 573
Stack Dump = java.io.FileNotFoundException:
/faces/myFacesExtensionResource/org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader/11532427/popup.HtmlPopupRenderer/JSPopup.js
at
com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:355)
at
com.ibm.ws.wswebcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:111)
at
com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3107)
at
com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:238)
at
com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:811)
at
com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1425)
at
com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:92)
at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:465)
at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:394)
at
com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:102)
at
com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:152)
at
com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:213)
at
com.ibm.io.async.AbstractAsyncFuture.fireCompletionActions(AbstractAsyncFuture.java:195)
at
com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at
com.ibm.io.async.ResultHandler.complete(ResultHandler.java:193)
at
com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:725)
at
com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:847)
at
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1498)
The problem is still not fixed with FixPack1, but IBM
is working on it.
--- phtan <[EMAIL PROTECTED]> wrote:
>
>
>
> There are actually a few places in Websphere 6.1 to
> set class loader order,
> which can be quite confusing. The one which we
> tried and works (except the
> calendar problem mentioned above) is via this path:
>
> Enterprise Applications > <war-file name> > Manage
> Modules >
>
> Change class loader to "Classes loaded with
> application class loader firstâ. If
> you are seeing those PARENT_LAST options, that is
> not the right page.
>
> ph
>
>
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
