With WAS 6.1, it's no longer possible to remove
JSF-related jar files to bypass the JSF RI. All those
jars are now an integral part of WAS's web container.
I've raised the issue with IBM. They suggest to remove
myfaces-api.jar and myfaces-impl.jar out of the web
app. Instead, the user should create a shared lib that
contains paths to myfaces jars, and then have the
webapp references to that shared lib. It helps to
resolve some issues, but I'm still having a lot of
other problems with it. It still uses LifeCycle,
Application, etc from JSF RI. I haven't tried
classloader's PARENTLAST option yet. It's something I
want to try next.

--- phtan <[EMAIL PROTECTED]> wrote:

> 
> 
> Shinpei Ohtani <shinpei.ohtani <at> gmail.com>
> writes:
> 
> > 
> > Hi,
> > 
> > I'm having the same problem with WebSphere6.1.
> > With some debugging, I assume the problem is
> > Sun JSF RI is incluede in WebSphere webcontainer
> runtime
> > jar(com.ibm.ws.webcontainer_2.0.0.jar)
> > so I can not remove RI jar.
> > When with WebSphere6, it is easy to remove Sun RI
> jar because I can
> > find the jar easily.
> > 
> > 2006/8/29, pds <pdsahoo <at> gmail.com>:
> > >
> > > Hi,
> > >
> > >  I am using myfaces1.1.3 in websphere6.1 .When
> deploying no exception is
> > > occuring after I made the class-loader value as
> PARENTLAST.But the problem
> > > is non of the jsf elements are rendering html
> content.Thats why my screen is
> > > remaining blank.But my log statements are
> showing that its going through all
> > > the phases of lifecycle.In websphere 6.0 this
> problem was not occuring.
> > >
> > > Can anybody tell me what can be the problem  ?
> > > --
> > > View this message in context:
>
http://www.nabble.com/problem-with-myfaces1.1.3--websphere6.1-tf2182105.html#a6034684
> > > Sent from the MyFaces - Users forum at
> Nabble.com.
> > >
> > >
> > 
> 
> 
> We had the same problem.  Besides setting to
> application class loader first, we
> found that we have to  remove jars like jsp-api.jar,
> xml-api, xercesImpl. 
> Otherwise websphere will load classes from our own
> version and somehow trigger
> its Sun RI JSF classes to be loaded, even if we set
> to application class loader
> first.
> 
> After doing the above, from class loader trace we
> can see myfaces classes loaded
> and pages show up ok and an 'generally' work. 
> However, we still have one
> problem -- myfaces javascript such as calendar does
> not work. 
> 
> Somehow the javascript in myfaces1.1.3.jar is not
> showing up.  Have checked the
> MyfacesExtensions filter settings and still no
> resolution.  Any pointers anyone?
> 
> ph
> 
> 
> 
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Reply via email to