Hey Ryan, all: Following up with your last comment (really valuable one, thanks), I realized that the order of the classpath is correct. myfaces-xxx.jar's are at the top (then, should be loaded first).
Looking at the logs again, I am getting this: [3/22/07 9:56:03:295 EDT] 00000022 MyFacesResour E org.apache.commons.logging.impl.Jdk14Logger error Unable to find resource src/__package__.js for component dojo.DojoResourceLoader. Check that this file is available in the classpath in sub-directory /resource of the package-directory. [3/22/07 9:56:03:295 EDT] 00000022 SRTServletRes W WARNING: Cannot set status. Response already committed. [3/22/07 9:56:03:295 EDT] 00000022 SRTServletRes W WARNING: Cannot set header. Response already committed. [3/22/07 9:56:03:420 EDT] 00000022 MyFacesResour E org.apache.commons.logging.impl.Jdk14Logger error Unable to find resource __package__.js for component dojo.DojoResourceLoader. Check that this file is available in the classpath in sub-directory /resource of the package-directory. [3/22/07 9:56:03:420 EDT] 00000022 SRTServletRes W WARNING: Cannot set status. Response already committed. [3/22/07 9:56:03:436 EDT] 00000022 SRTServletRes W WARNING: Cannot set header. Response already committed. Some comments here: I am using: myfaces-impl-1.1.6-SNAPSHOT.jar myfaces-api-1.1.6-SNAPSHOT.jar tomahawk-1.1.5-SNAPSHOT.jar Here it seems a problem with the filter, that I am trying to dig into it. But the weird thing about it, is that in a previous version of WAS (6.0....) this exact same app works fine. Any help? "Ryan Wynn" <[EMAIL PROTECTED]> 03/21/2007 12:43 PM Please respond to "MyFaces Discussion" <[email protected]> To "MyFaces Discussion" <[email protected]> cc Subject Re: MyFaces on WAS 6.1.0.2 In the web based WAS Admin Console you can see exactly the order of the jars that websphere is loading for your application. You have to dig into the nested links for classloader after clicking on your app under Enterprise Apps. The end result is a tree view consisting of all the jars in the classpath in the order they will be loaded. You want to make sure myfaces-xxx.jar is at the top of the tree above the was jars. This helped us confirm that our PARENT_LAST classloader setting was indeed taking affect. It ended up working fine. Depending on whether you choose application or module for your classloader scope, make sure you are viewing the corresponding classloader details. On 3/21/07, [EMAIL PROTECTED] <[EMAIL PROTECTED] > wrote: Werner, I am trying to follow your suggestion. To double check, I am just removing these files: myfaces-api-1.1.6-SNAPSHOT.jar myfaces-impl-1.1.6-SNAPSHOT.jar and leaving: tomahawk-1.1.5-SNAPSHOT.jar Or what is the approach? Werner Punz <[EMAIL PROTECTED]> Sent by: news <[EMAIL PROTECTED]> 03/21/2007 11:07 AM Please respond to "MyFaces Discussion" < [email protected]> To [email protected] cc Subject Re: MyFaces on WAS 6.1.0.2 [EMAIL PROTECTED] schrieb: > > In fact according to the document I am making reference for installation > says > "/Unlike Websphere 6.0, in Websphere 6.1 the JSF Sun RI is bundled > together with several other WAS libraries in > com.ibm.ws.webcontainer_2.0.0.jar, so removing the webspheres JSF API > jars is not an option. /" > > That is why I proceed with the class loader orders. > > But the problem persists. > ok... following, can you try to shift your application towards Sun RI settings? Tomahawk should work with the RI. *************************** IMPORTANT NOTE ***************************** The opinions expressed in this message and/or any attachments are those of the author and not necessarily those of Brown Brothers Harriman & Co., its subsidiaries and affiliates BBH. There is no guarantee that this message is either private or confidential, and it may have been altered by unauthorized sources without your or our knowledge. Nothing in the message is capable or intended to create any legally binding obligations on either party and it is not intended to provide legal advice. BBH accepts no responsibility for loss or damage from its use, including damage from virus. ******************************************************************* *************************** IMPORTANT NOTE***************************** The opinions expressed in this message and/or any attachments are those of the author and not necessarily those of Brown Brothers Harriman & Co., its subsidiaries and affiliates ("BBH"). There is no guarantee that this message is either private or confidential, and it may have been altered by unauthorized sources without your or our knowledge. Nothing in the message is capable or intended to create any legally binding obligations on either party and it is not intended to provide legal advice. BBH accepts no responsibility for loss or damage from its use, including damage from virus. ************************************************************************
