You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Tony Dalbrekt (JIRA)" <ji...@apache.org> on 2008/02/12 15:03:09 UTC
[jira] Created: (CXF-1428) Another solution to setup WebSphere 6.1
to work with CXF.
Another solution to setup WebSphere 6.1 to work with CXF.
----------------------------------------------------------
Key: CXF-1428
URL: https://issues.apache.org/jira/browse/CXF-1428
Project: CXF
Issue Type: Task
Components: Resources
Environment: ttp://cwiki.apache.org/CXF20DOC/
Reporter: Tony Dalbrekt
Priority: Trivial
Improve documentation for WebSphere setup: http://cwiki.apache.org/CXF20DOC/appserverguide.html#AppServerGuide-Websphere
If you put your wsdl4j-1.6.1 jar in $WAS_HOME/java/jre/lib/endorsed as suggested in the wiki all your application will depend on your version of wsdl4j. Another solution is to create a new class loader in your server which loads before parent class loader, create a shared library with your version of wsdl4j and add this shared library to your new class loader. This version of wsdl4j will only be available for your specific server and not affect applications running in other servers.
Tested in WAS 6.1 only but should work in earlier versions as well.
Step by step
1. In the WAS console navigate to "Environment > Shared Libraries"
2. Select the scope you wish your library should be visible in
3. Click "New" and set values ex.: name=MYAPP_SHARED_LIB, classpath=PATH_TO/wsdl4j-1.6.1.jar and "Save"
4. Navigate to "Application servers > [your server name] > Java and Process Management > Class loader > New"
5. Select "Classes loaded with application class loader first" and "Save"
6. Select your new class loader and click " Shared library references"
7. Add your shared library (MYAPP_SHARED_LIB) save and restart your server.
This should do it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (CXF-1428) Another solution to setup WebSphere 6.1
to work with CXF.
Posted by "Tony Dalbrekt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tony Dalbrekt closed CXF-1428.
------------------------------
Resolution: Fixed
Ah, thanks! Never thought about that. Done by now.
Tony
> Another solution to setup WebSphere 6.1 to work with CXF.
> ----------------------------------------------------------
>
> Key: CXF-1428
> URL: https://issues.apache.org/jira/browse/CXF-1428
> Project: CXF
> Issue Type: Task
> Components: Resources
> Environment: ttp://cwiki.apache.org/CXF20DOC/
> Reporter: Tony Dalbrekt
> Priority: Trivial
> Original Estimate: 0.08h
> Remaining Estimate: 0.08h
>
> Improve documentation for WebSphere setup: http://cwiki.apache.org/CXF20DOC/appserverguide.html#AppServerGuide-Websphere
> If you put your wsdl4j-1.6.1 jar in $WAS_HOME/java/jre/lib/endorsed as suggested in the wiki all your application will depend on your version of wsdl4j. Another solution is to create a new class loader in your server which loads before parent class loader, create a shared library with your version of wsdl4j and add this shared library to your new class loader. This version of wsdl4j will only be available for your specific server and not affect applications running in other servers.
> Tested in WAS 6.1 only but should work in earlier versions as well.
> Step by step
> 1. In the WAS console navigate to "Environment > Shared Libraries"
> 2. Select the scope you wish your library should be visible in
> 3. Click "New" and set values ex.: name=MYAPP_SHARED_LIB, classpath=PATH_TO/wsdl4j-1.6.1.jar and "Save"
> 4. Navigate to "Application servers > [your server name] > Java and Process Management > Class loader > New"
> 5. Select "Classes loaded with application class loader first" and "Save"
> 6. Select your new class loader and click " Shared library references"
> 7. Add your shared library (MYAPP_SHARED_LIB) save and restart your server.
> This should do it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1428) Another solution to setup WebSphere
6.1 to work with CXF.
Posted by "willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568128#action_12568128 ]
willem Jiang commented on CXF-1428:
-----------------------------------
Hi Tony,
You do not need to create a JIRA for the wiki page update. It's wiki , you can edit it as you want :)
Willem
> Another solution to setup WebSphere 6.1 to work with CXF.
> ----------------------------------------------------------
>
> Key: CXF-1428
> URL: https://issues.apache.org/jira/browse/CXF-1428
> Project: CXF
> Issue Type: Task
> Components: Resources
> Environment: ttp://cwiki.apache.org/CXF20DOC/
> Reporter: Tony Dalbrekt
> Priority: Trivial
> Original Estimate: 0.08h
> Remaining Estimate: 0.08h
>
> Improve documentation for WebSphere setup: http://cwiki.apache.org/CXF20DOC/appserverguide.html#AppServerGuide-Websphere
> If you put your wsdl4j-1.6.1 jar in $WAS_HOME/java/jre/lib/endorsed as suggested in the wiki all your application will depend on your version of wsdl4j. Another solution is to create a new class loader in your server which loads before parent class loader, create a shared library with your version of wsdl4j and add this shared library to your new class loader. This version of wsdl4j will only be available for your specific server and not affect applications running in other servers.
> Tested in WAS 6.1 only but should work in earlier versions as well.
> Step by step
> 1. In the WAS console navigate to "Environment > Shared Libraries"
> 2. Select the scope you wish your library should be visible in
> 3. Click "New" and set values ex.: name=MYAPP_SHARED_LIB, classpath=PATH_TO/wsdl4j-1.6.1.jar and "Save"
> 4. Navigate to "Application servers > [your server name] > Java and Process Management > Class loader > New"
> 5. Select "Classes loaded with application class loader first" and "Save"
> 6. Select your new class loader and click " Shared library references"
> 7. Add your shared library (MYAPP_SHARED_LIB) save and restart your server.
> This should do it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.