Re: WebSphere 5.0 and cocoon

2003-01-28 Thread Cameron McKenzie
Really think I've licked the WebSphere 5.0 problem now.

The trick is this.  Make sure the application server
classloader is set to MODULE visibility.  Then set the
classloader on the ear to PARENT_LAST and then again,
set the classloader on the war module to PARENT_LAST. 
Once you've made these changes, the cocoon war should
run without a hitch.

Good luck.

-Cameron McKenzie

-
Please check that your question  has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:   [EMAIL PROTECTED]




Re: WebSphere 5.0 and cocoon

2003-01-28 Thread dfeather

Just out of curiosity, are you running that on an AS/400 (e...
iSeries... sorry)?

Dan Feather






-
Please check that your question  has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:   [EMAIL PROTECTED]




Re: WebSphere 5.0 and cocoon

2003-01-28 Thread Cameron McKenzie
The fix worked on both the WSAD test environment, and
the WAS running on Windows 2000.  Sorry, I haven't
tested it on my AS/400 yet.

-Cameron McKenzie


On Tue, 28 Jan 2003, [EMAIL PROTECTED] wrote:

 
 
 Just out of curiosity, are you running that on an
 AS/400 (e...
 iSeries... sorry)?
 
 Dan Feather
 
 

-
Please check that your question  has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:   [EMAIL PROTECTED]