You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Vijay Pandey (JIRA)" <ji...@apache.org> on 2009/02/27 00:05:01 UTC
[jira] Created: (AXIS2-4258) Modules not getting loaded from
classpath in websphere 6.1
Modules not getting loaded from classpath in websphere 6.1
----------------------------------------------------------
Key: AXIS2-4258
URL: https://issues.apache.org/jira/browse/AXIS2-4258
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: deployment
Affects Versions: 1.4.1
Environment: JDK 5 , WebSphere application server 6.1
Reporter: Vijay Pandey
I tried to deploy the axis2 ver 1.4.1 in websphere 6.1 with jdk 1.5 and wanted to load the modules from the classpath., which did not work. In websphere a jar URL will be starting with "wsjar" instead of "jar" for eg. the addressing module xml file came up like wsjar:file:/opt/IBM/WebSphere/xyz/xyz.ear/addressing-1.4.1.jar!/META-NNF/module.xml.
To overcome this issue in the class org.apache.axis2.deployment.RepositoryListener, method name "loadClassPathModules()", i changed its implementation to also look for "wsjar" instead of just "jar" and "file". Also since the "wsjar" is not actually an instance of "java.net.JarURLConnection", we can't use directly this way of getting the URL of the jar
((java.net.JarURLConnection)url.openConnection()).getJarFileURL();
One more "else if" clause was added for "wsjar" and its file name was fetched directly by doing
else if (fileName.startsWith("wsjar")) {
fileName =fileName.substring("wsjar:".length());
fileName =fileName.substring(0, fileName.lastIndexOf("!/META-INF/module.xml"));
}
Thanks
Vijay
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (AXIS2-4258) Modules not getting loaded from
classpath in websphere 6.1
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen reassigned AXIS2-4258:
--------------------------------------
Assignee: Andreas Veithen
> Modules not getting loaded from classpath in websphere 6.1
> ----------------------------------------------------------
>
> Key: AXIS2-4258
> URL: https://issues.apache.org/jira/browse/AXIS2-4258
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: deployment
> Affects Versions: 1.4.1
> Environment: JDK 5 , WebSphere application server 6.1
> Reporter: Vijay Pandey
> Assignee: Andreas Veithen
>
> I tried to deploy the axis2 ver 1.4.1 in websphere 6.1 with jdk 1.5 and wanted to load the modules from the classpath., which did not work. In websphere a jar URL will be starting with "wsjar" instead of "jar" for eg. the addressing module xml file came up like wsjar:file:/opt/IBM/WebSphere/xyz/xyz.ear/addressing-1.4.1.jar!/META-NNF/module.xml.
> To overcome this issue in the class org.apache.axis2.deployment.RepositoryListener, method name "loadClassPathModules()", i changed its implementation to also look for "wsjar" instead of just "jar" and "file". Also since the "wsjar" is not actually an instance of "java.net.JarURLConnection", we can't use directly this way of getting the URL of the jar
> ((java.net.JarURLConnection)url.openConnection()).getJarFileURL();
> One more "else if" clause was added for "wsjar" and its file name was fetched directly by doing
> else if (fileName.startsWith("wsjar")) {
> fileName =fileName.substring("wsjar:".length());
> fileName =fileName.substring(0, fileName.lastIndexOf("!/META-INF/module.xml"));
> }
> Thanks
> Vijay
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AXIS2-4258) Modules not getting loaded from
classpath in websphere 6.1
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen resolved AXIS2-4258.
------------------------------------
Resolution: Fixed
Fix Version/s: post-1.5
Fixed in revision 748761 on trunk. The fix doesn't look for "wsjar" specifically, but supports any archive URL. If you want to see this change included in 1.5, please test and confirm that it works. Then I will merge it to the 1.5 branch.
> Modules not getting loaded from classpath in websphere 6.1
> ----------------------------------------------------------
>
> Key: AXIS2-4258
> URL: https://issues.apache.org/jira/browse/AXIS2-4258
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: deployment
> Affects Versions: 1.4.1
> Environment: JDK 5 , WebSphere application server 6.1
> Reporter: Vijay Pandey
> Assignee: Andreas Veithen
> Fix For: post-1.5
>
>
> I tried to deploy the axis2 ver 1.4.1 in websphere 6.1 with jdk 1.5 and wanted to load the modules from the classpath., which did not work. In websphere a jar URL will be starting with "wsjar" instead of "jar" for eg. the addressing module xml file came up like wsjar:file:/opt/IBM/WebSphere/xyz/xyz.ear/addressing-1.4.1.jar!/META-NNF/module.xml.
> To overcome this issue in the class org.apache.axis2.deployment.RepositoryListener, method name "loadClassPathModules()", i changed its implementation to also look for "wsjar" instead of just "jar" and "file". Also since the "wsjar" is not actually an instance of "java.net.JarURLConnection", we can't use directly this way of getting the URL of the jar
> ((java.net.JarURLConnection)url.openConnection()).getJarFileURL();
> One more "else if" clause was added for "wsjar" and its file name was fetched directly by doing
> else if (fileName.startsWith("wsjar")) {
> fileName =fileName.substring("wsjar:".length());
> fileName =fileName.substring(0, fileName.lastIndexOf("!/META-INF/module.xml"));
> }
> Thanks
> Vijay
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AXIS2-4258) Modules not getting loaded from
classpath in websphere 6.1
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen updated AXIS2-4258:
-----------------------------------
Fix Version/s: (was: post-1.5)
1.5
Merged the fix to the 1.5 branch. Thanks Vijay for testing.
> Modules not getting loaded from classpath in websphere 6.1
> ----------------------------------------------------------
>
> Key: AXIS2-4258
> URL: https://issues.apache.org/jira/browse/AXIS2-4258
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: deployment
> Affects Versions: 1.4.1
> Environment: JDK 5 , WebSphere application server 6.1
> Reporter: Vijay Pandey
> Assignee: Andreas Veithen
> Fix For: 1.5
>
>
> I tried to deploy the axis2 ver 1.4.1 in websphere 6.1 with jdk 1.5 and wanted to load the modules from the classpath., which did not work. In websphere a jar URL will be starting with "wsjar" instead of "jar" for eg. the addressing module xml file came up like wsjar:file:/opt/IBM/WebSphere/xyz/xyz.ear/addressing-1.4.1.jar!/META-NNF/module.xml.
> To overcome this issue in the class org.apache.axis2.deployment.RepositoryListener, method name "loadClassPathModules()", i changed its implementation to also look for "wsjar" instead of just "jar" and "file". Also since the "wsjar" is not actually an instance of "java.net.JarURLConnection", we can't use directly this way of getting the URL of the jar
> ((java.net.JarURLConnection)url.openConnection()).getJarFileURL();
> One more "else if" clause was added for "wsjar" and its file name was fetched directly by doing
> else if (fileName.startsWith("wsjar")) {
> fileName =fileName.substring("wsjar:".length());
> fileName =fileName.substring(0, fileName.lastIndexOf("!/META-INF/module.xml"));
> }
> Thanks
> Vijay
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (AXIS2-4258) Modules not getting loaded from
classpath in websphere 6.1
Posted by "Vijay Pandey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vijay Pandey closed AXIS2-4258.
-------------------------------
it works fine, tested the same.
Thanks
Vijay
> Modules not getting loaded from classpath in websphere 6.1
> ----------------------------------------------------------
>
> Key: AXIS2-4258
> URL: https://issues.apache.org/jira/browse/AXIS2-4258
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: deployment
> Affects Versions: 1.4.1
> Environment: JDK 5 , WebSphere application server 6.1
> Reporter: Vijay Pandey
> Assignee: Andreas Veithen
> Fix For: post-1.5
>
>
> I tried to deploy the axis2 ver 1.4.1 in websphere 6.1 with jdk 1.5 and wanted to load the modules from the classpath., which did not work. In websphere a jar URL will be starting with "wsjar" instead of "jar" for eg. the addressing module xml file came up like wsjar:file:/opt/IBM/WebSphere/xyz/xyz.ear/addressing-1.4.1.jar!/META-NNF/module.xml.
> To overcome this issue in the class org.apache.axis2.deployment.RepositoryListener, method name "loadClassPathModules()", i changed its implementation to also look for "wsjar" instead of just "jar" and "file". Also since the "wsjar" is not actually an instance of "java.net.JarURLConnection", we can't use directly this way of getting the URL of the jar
> ((java.net.JarURLConnection)url.openConnection()).getJarFileURL();
> One more "else if" clause was added for "wsjar" and its file name was fetched directly by doing
> else if (fileName.startsWith("wsjar")) {
> fileName =fileName.substring("wsjar:".length());
> fileName =fileName.substring(0, fileName.lastIndexOf("!/META-INF/module.xml"));
> }
> Thanks
> Vijay
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.