You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Denis Cabasson (JIRA)" <ji...@apache.org> on 2009/02/17 22:25:46 UTC
[jira] Created: (WW-2999) Convention plugin and jar scanning
failing on Websphere
Convention plugin and jar scanning failing on Websphere
-------------------------------------------------------
Key: WW-2999
URL: https://issues.apache.org/struts/browse/WW-2999
Project: Struts 2
Issue Type: Bug
Components: Plugin - Convention
Affects Versions: 2.1.6
Environment: Websphere 6.1
Reporter: Denis Cabasson
Priority: Critical
Hi,
I am upgrading an existing project from struts 2.0.14 to 2.1.6. We are using the zero configuration approach, and the classpath scanning ability.
The application is running on Websphere 6.1, and I had a lot of trouble having it work. My 2 major issues were :
* Classes of the current project not being scanned : This url file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/classes/ was originally excluded by the filters in the convention plugin. I'll let you know exactly which one did that
* We had some action classes in a dependency jar, and it didn't get included because of the wsjar protocol. See http://jira.opensymphony.com/browse/XW-669 for more documentation on this protocol and its inclusion in Xwork. The url look like :
wsjar:file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/lib/axis-1.4.jar!/
And are not processed by com.opensymphony.xwork2.util.finder.ClassFinder.
I'll add more detail as I dig into this and let you know how I worked around it (except by moving to a real application server.... )
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WW-2999) Convention plugin and jar scanning
failing on Websphere
Posted by "Andrew Cooper (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45666#action_45666 ]
Andrew Cooper commented on WW-2999:
-----------------------------------
Do you not think it may be a good idea to have real cross compatibility and utilise the getResourceAsStream() method to resolve classes instead of getResource().
I have raise another JIRA in the xwork project (http://jira.opensymphony.com/browse/XW-678) to acknowledge this fact.
Overall surely it would probably be a better solution to make the software truly cross container compatible?
> Convention plugin and jar scanning failing on Websphere
> -------------------------------------------------------
>
> Key: WW-2999
> URL: https://issues.apache.org/struts/browse/WW-2999
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - Convention
> Affects Versions: 2.1.6
> Environment: Websphere 6.1
> Reporter: Denis Cabasson
> Priority: Critical
>
> Hi,
> I am upgrading an existing project from struts 2.0.14 to 2.1.6. We are using the zero configuration approach, and the classpath scanning ability.
> The application is running on Websphere 6.1, and I had a lot of trouble having it work. My 2 major issues were :
> * Classes of the current project not being scanned : This url file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/classes/ was originally excluded by the filters in the convention plugin. I'll let you know exactly which one did that
> * We had some action classes in a dependency jar, and it didn't get included because of the wsjar protocol. See http://jira.opensymphony.com/browse/XW-669 for more documentation on this protocol and its inclusion in Xwork. The url look like :
> wsjar:file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/lib/axis-1.4.jar!/
> And are not processed by com.opensymphony.xwork2.util.finder.ClassFinder.
> I'll add more detail as I dig into this and let you know how I worked around it (except by moving to a real application server.... )
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (WW-2999) Convention plugin and jar
scanning failing on Websphere
Posted by "Kobe Nys (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45696#action_45696 ]
Kobe Nys edited comment on WW-2999 at 3/10/09 6:02 AM:
-------------------------------------------------------
All my jars are inside my EAR project and I get:
wsjar:file:/C:/workspacePath/EarProject/struts2-core-2.1.7-SNAPSHOT.jar!/struts-default.xml
was (Author: 2fast2bcn):
All my jars are inside EarProject and I get:
wsjar:file:/C:/workspacePath/EarProject/struts2-core-2.1.7-SNAPSHOT.jar!/struts-default.xml
> Convention plugin and jar scanning failing on Websphere
> -------------------------------------------------------
>
> Key: WW-2999
> URL: https://issues.apache.org/struts/browse/WW-2999
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - Convention
> Affects Versions: 2.1.6
> Environment: Websphere 6.1
> Reporter: Denis Cabasson
> Priority: Critical
>
> Hi,
> I am upgrading an existing project from struts 2.0.14 to 2.1.6. We are using the zero configuration approach, and the classpath scanning ability.
> The application is running on Websphere 6.1, and I had a lot of trouble having it work. My 2 major issues were :
> * Classes of the current project not being scanned : This url file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/classes/ was originally excluded by the filters in the convention plugin. I'll let you know exactly which one did that
> * We had some action classes in a dependency jar, and it didn't get included because of the wsjar protocol. See http://jira.opensymphony.com/browse/XW-669 for more documentation on this protocol and its inclusion in Xwork. The url look like :
> wsjar:file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/lib/axis-1.4.jar!/
> And are not processed by com.opensymphony.xwork2.util.finder.ClassFinder.
> I'll add more detail as I dig into this and let you know how I worked around it (except by moving to a real application server.... )
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WW-2999) Convention plugin and jar scanning
failing on Websphere
Posted by "Kobe Nys (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45681#action_45681 ]
Kobe Nys commented on WW-2999:
------------------------------
When I run my code on rational 7.5.1 and I publish (to WAS 6.1) my application with resources within workspace (minimize application files copied to the server option on) rather then copy resources to server, I get this exception:
[9/03/09 13:56:47:250 CET] 0000002a WebApp E [Servlet Error]-[Filter [struts2]: could not be initialized]: Unable to load configuration. - Class: java.io.File
File: File.java
Method: <init>
Line: 362 - java/io/File.java:362:-1
at com.opensymphony.xwork2.config.ConfigurationManager.getConfiguration(ConfigurationManager.java:58)
at org.apache.struts2.dispatcher.Dispatcher.init_PreloadConfiguration(Dispatcher.java:360)
at org.apache.struts2.dispatcher.Dispatcher.init(Dispatcher.java:403)
at org.apache.struts2.dispatcher.ng.InitOperations.initDispatcher(InitOperations.java:69)
at org.apache.struts2.dispatcher.ng.filter.StrutsPrepareAndExecuteFilter.init(StrutsPrepareAndExecuteFilter.java:48)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.init(FilterInstanceWrapper.java:142)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager._loadFilter(WebAppFilterManager.java:471)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.loadFilter(WebAppFilterManager.java:385)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.getFilterInstanceWrapper(WebAppFilterManager.java:244)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.getFilterChain(WebAppFilterManager.java:302)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:792)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:742)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:695)
at com.ibm.ws.wswebcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:101)
at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.invokeFilters(DefaultExtensionProcessor.java:818)
at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:768)
at com.ibm.ws.wswebcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:113)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3440)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:267)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:815)
at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1461)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:118)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:387)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:267)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)
Caused by: Caught exception while loading file struts-default.xml - Class: java.io.File
File: File.java
Method: <init>
Line: 362 - java/io/File.java:362:-1
at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.loadConfigurationFiles(XmlConfigurationProvider.java:894)
at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.loadDocuments(XmlConfigurationProvider.java:144)
at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.init(XmlConfigurationProvider.java:111)
at com.opensymphony.xwork2.config.impl.DefaultConfiguration.reloadContainer(DefaultConfiguration.java:164)
at com.opensymphony.xwork2.config.ConfigurationManager.getConfiguration(ConfigurationManager.java:55)
... 34 more
Caused by: java.lang.IllegalArgumentException: URI is not hierarchical
at java.io.File.<init>(File.java:362)
at com.opensymphony.xwork2.util.FileManager$FileRevision.build(FileManager.java:191)
at com.opensymphony.xwork2.util.FileManager.loadFile(FileManager.java:126)
at com.opensymphony.xwork2.util.FileManager.loadFile(FileManager.java:89)
at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.loadConfigurationFiles(XmlConfigurationProvider.java:879)
... 38 more
> Convention plugin and jar scanning failing on Websphere
> -------------------------------------------------------
>
> Key: WW-2999
> URL: https://issues.apache.org/struts/browse/WW-2999
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - Convention
> Affects Versions: 2.1.6
> Environment: Websphere 6.1
> Reporter: Denis Cabasson
> Priority: Critical
>
> Hi,
> I am upgrading an existing project from struts 2.0.14 to 2.1.6. We are using the zero configuration approach, and the classpath scanning ability.
> The application is running on Websphere 6.1, and I had a lot of trouble having it work. My 2 major issues were :
> * Classes of the current project not being scanned : This url file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/classes/ was originally excluded by the filters in the convention plugin. I'll let you know exactly which one did that
> * We had some action classes in a dependency jar, and it didn't get included because of the wsjar protocol. See http://jira.opensymphony.com/browse/XW-669 for more documentation on this protocol and its inclusion in Xwork. The url look like :
> wsjar:file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/lib/axis-1.4.jar!/
> And are not processed by com.opensymphony.xwork2.util.finder.ClassFinder.
> I'll add more detail as I dig into this and let you know how I worked around it (except by moving to a real application server.... )
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (WW-2999) Convention plugin and jar
scanning failing on Websphere
Posted by "Musachy Barroso (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45618#action_45618 ]
musachy edited comment on WW-2999 at 2/17/09 1:56 PM:
--------------------------------------------------------------
This was fixed in XWork trunk. See: http://jira.opensymphony.com/browse/XW-675
was (Author: musachy):
This was also fixed in trunk.
> Convention plugin and jar scanning failing on Websphere
> -------------------------------------------------------
>
> Key: WW-2999
> URL: https://issues.apache.org/struts/browse/WW-2999
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - Convention
> Affects Versions: 2.1.6
> Environment: Websphere 6.1
> Reporter: Denis Cabasson
> Priority: Critical
>
> Hi,
> I am upgrading an existing project from struts 2.0.14 to 2.1.6. We are using the zero configuration approach, and the classpath scanning ability.
> The application is running on Websphere 6.1, and I had a lot of trouble having it work. My 2 major issues were :
> * Classes of the current project not being scanned : This url file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/classes/ was originally excluded by the filters in the convention plugin. I'll let you know exactly which one did that
> * We had some action classes in a dependency jar, and it didn't get included because of the wsjar protocol. See http://jira.opensymphony.com/browse/XW-669 for more documentation on this protocol and its inclusion in Xwork. The url look like :
> wsjar:file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/lib/axis-1.4.jar!/
> And are not processed by com.opensymphony.xwork2.util.finder.ClassFinder.
> I'll add more detail as I dig into this and let you know how I worked around it (except by moving to a real application server.... )
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WW-2999) Convention plugin and jar scanning
failing on Websphere
Posted by "Musachy Barroso (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45667#action_45667 ]
Musachy Barroso commented on WW-2999:
-------------------------------------
If you have a patch that makes it work, and you can share it, it would be great. thanks.
> Convention plugin and jar scanning failing on Websphere
> -------------------------------------------------------
>
> Key: WW-2999
> URL: https://issues.apache.org/struts/browse/WW-2999
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - Convention
> Affects Versions: 2.1.6
> Environment: Websphere 6.1
> Reporter: Denis Cabasson
> Priority: Critical
>
> Hi,
> I am upgrading an existing project from struts 2.0.14 to 2.1.6. We are using the zero configuration approach, and the classpath scanning ability.
> The application is running on Websphere 6.1, and I had a lot of trouble having it work. My 2 major issues were :
> * Classes of the current project not being scanned : This url file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/classes/ was originally excluded by the filters in the convention plugin. I'll let you know exactly which one did that
> * We had some action classes in a dependency jar, and it didn't get included because of the wsjar protocol. See http://jira.opensymphony.com/browse/XW-669 for more documentation on this protocol and its inclusion in Xwork. The url look like :
> wsjar:file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/lib/axis-1.4.jar!/
> And are not processed by com.opensymphony.xwork2.util.finder.ClassFinder.
> I'll add more detail as I dig into this and let you know how I worked around it (except by moving to a real application server.... )
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WW-2999) Convention plugin and jar scanning
failing on Websphere
Posted by "Denis Cabasson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45617#action_45617 ]
Denis Cabasson commented on WW-2999:
------------------------------------
So the thing breaking on the first point was the line :
{code}
urlSet = urlSet.excludeJavaEndorsedDirs();
{code}
The system variable was empty "", and that messed up the classpath. Commenting out this line re-established the expected behaviour.
> Convention plugin and jar scanning failing on Websphere
> -------------------------------------------------------
>
> Key: WW-2999
> URL: https://issues.apache.org/struts/browse/WW-2999
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - Convention
> Affects Versions: 2.1.6
> Environment: Websphere 6.1
> Reporter: Denis Cabasson
> Priority: Critical
>
> Hi,
> I am upgrading an existing project from struts 2.0.14 to 2.1.6. We are using the zero configuration approach, and the classpath scanning ability.
> The application is running on Websphere 6.1, and I had a lot of trouble having it work. My 2 major issues were :
> * Classes of the current project not being scanned : This url file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/classes/ was originally excluded by the filters in the convention plugin. I'll let you know exactly which one did that
> * We had some action classes in a dependency jar, and it didn't get included because of the wsjar protocol. See http://jira.opensymphony.com/browse/XW-669 for more documentation on this protocol and its inclusion in Xwork. The url look like :
> wsjar:file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/lib/axis-1.4.jar!/
> And are not processed by com.opensymphony.xwork2.util.finder.ClassFinder.
> I'll add more detail as I dig into this and let you know how I worked around it (except by moving to a real application server.... )
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WW-2999) Convention plugin and jar scanning
failing on Websphere
Posted by "Kobe Nys (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45696#action_45696 ]
Kobe Nys commented on WW-2999:
------------------------------
All my jars are inside EarProject and I get:
wsjar:file:/C:/workspacePath/EarProject/struts2-core-2.1.7-SNAPSHOT.jar!/struts-default.xml
> Convention plugin and jar scanning failing on Websphere
> -------------------------------------------------------
>
> Key: WW-2999
> URL: https://issues.apache.org/struts/browse/WW-2999
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - Convention
> Affects Versions: 2.1.6
> Environment: Websphere 6.1
> Reporter: Denis Cabasson
> Priority: Critical
>
> Hi,
> I am upgrading an existing project from struts 2.0.14 to 2.1.6. We are using the zero configuration approach, and the classpath scanning ability.
> The application is running on Websphere 6.1, and I had a lot of trouble having it work. My 2 major issues were :
> * Classes of the current project not being scanned : This url file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/classes/ was originally excluded by the filters in the convention plugin. I'll let you know exactly which one did that
> * We had some action classes in a dependency jar, and it didn't get included because of the wsjar protocol. See http://jira.opensymphony.com/browse/XW-669 for more documentation on this protocol and its inclusion in Xwork. The url look like :
> wsjar:file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/lib/axis-1.4.jar!/
> And are not processed by com.opensymphony.xwork2.util.finder.ClassFinder.
> I'll add more detail as I dig into this and let you know how I worked around it (except by moving to a real application server.... )
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WW-2999) Convention plugin and jar scanning
failing on Websphere
Posted by "Musachy Barroso (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Musachy Barroso resolved WW-2999.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.1.7
We are talking about 2 different problems here. The original problem is fixed in http://jira.opensymphony.com/browse/XW-675. That's why I am closing the ticket. The other problem is being tracked here: http://jira.opensymphony.com/browse/XW-678
> Convention plugin and jar scanning failing on Websphere
> -------------------------------------------------------
>
> Key: WW-2999
> URL: https://issues.apache.org/struts/browse/WW-2999
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - Convention
> Affects Versions: 2.1.6
> Environment: Websphere 6.1
> Reporter: Denis Cabasson
> Priority: Critical
> Fix For: 2.1.7
>
>
> Hi,
> I am upgrading an existing project from struts 2.0.14 to 2.1.6. We are using the zero configuration approach, and the classpath scanning ability.
> The application is running on Websphere 6.1, and I had a lot of trouble having it work. My 2 major issues were :
> * Classes of the current project not being scanned : This url file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/classes/ was originally excluded by the filters in the convention plugin. I'll let you know exactly which one did that
> * We had some action classes in a dependency jar, and it didn't get included because of the wsjar protocol. See http://jira.opensymphony.com/browse/XW-669 for more documentation on this protocol and its inclusion in Xwork. The url look like :
> wsjar:file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/lib/axis-1.4.jar!/
> And are not processed by com.opensymphony.xwork2.util.finder.ClassFinder.
> I'll add more detail as I dig into this and let you know how I worked around it (except by moving to a real application server.... )
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WW-2999) Convention plugin and jar scanning
failing on Websphere
Posted by "Musachy Barroso (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45616#action_45616 ]
Musachy Barroso commented on WW-2999:
-------------------------------------
You can also grab a snapshot: http://people.apache.org/builds/struts/nightlies/2.x/
> Convention plugin and jar scanning failing on Websphere
> -------------------------------------------------------
>
> Key: WW-2999
> URL: https://issues.apache.org/struts/browse/WW-2999
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - Convention
> Affects Versions: 2.1.6
> Environment: Websphere 6.1
> Reporter: Denis Cabasson
> Priority: Critical
>
> Hi,
> I am upgrading an existing project from struts 2.0.14 to 2.1.6. We are using the zero configuration approach, and the classpath scanning ability.
> The application is running on Websphere 6.1, and I had a lot of trouble having it work. My 2 major issues were :
> * Classes of the current project not being scanned : This url file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/classes/ was originally excluded by the filters in the convention plugin. I'll let you know exactly which one did that
> * We had some action classes in a dependency jar, and it didn't get included because of the wsjar protocol. See http://jira.opensymphony.com/browse/XW-669 for more documentation on this protocol and its inclusion in Xwork. The url look like :
> wsjar:file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/lib/axis-1.4.jar!/
> And are not processed by com.opensymphony.xwork2.util.finder.ClassFinder.
> I'll add more detail as I dig into this and let you know how I worked around it (except by moving to a real application server.... )
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WW-2999) Convention plugin and jar scanning
failing on Websphere
Posted by "Kobe Nys (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45683#action_45683 ]
Kobe Nys commented on WW-2999:
------------------------------
I used the version @ http://people.apache.org/builds/struts/nightlies/2.x/struts-2.1.7-SNAPSHOT-all-200903081615.zip
> Convention plugin and jar scanning failing on Websphere
> -------------------------------------------------------
>
> Key: WW-2999
> URL: https://issues.apache.org/struts/browse/WW-2999
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - Convention
> Affects Versions: 2.1.6
> Environment: Websphere 6.1
> Reporter: Denis Cabasson
> Priority: Critical
>
> Hi,
> I am upgrading an existing project from struts 2.0.14 to 2.1.6. We are using the zero configuration approach, and the classpath scanning ability.
> The application is running on Websphere 6.1, and I had a lot of trouble having it work. My 2 major issues were :
> * Classes of the current project not being scanned : This url file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/classes/ was originally excluded by the filters in the convention plugin. I'll let you know exactly which one did that
> * We had some action classes in a dependency jar, and it didn't get included because of the wsjar protocol. See http://jira.opensymphony.com/browse/XW-669 for more documentation on this protocol and its inclusion in Xwork. The url look like :
> wsjar:file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/lib/axis-1.4.jar!/
> And are not processed by com.opensymphony.xwork2.util.finder.ClassFinder.
> I'll add more detail as I dig into this and let you know how I worked around it (except by moving to a real application server.... )
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WW-2999) Convention plugin and jar scanning
failing on Websphere
Posted by "Musachy Barroso (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45615#action_45615 ]
Musachy Barroso commented on WW-2999:
-------------------------------------
A new setting was added to convention in trunk (you would have to build it yourself):
<constant name="struts.convention.action.fileProtocols" value="jar" />
you can add wsjar like:
<constant name="struts.convention.action.fileProtocols" value="jar,wsjar" />
to make Convention recognize those files, I haven't been able to test it in Websphere, could you please test it and report back?
> Convention plugin and jar scanning failing on Websphere
> -------------------------------------------------------
>
> Key: WW-2999
> URL: https://issues.apache.org/struts/browse/WW-2999
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - Convention
> Affects Versions: 2.1.6
> Environment: Websphere 6.1
> Reporter: Denis Cabasson
> Priority: Critical
>
> Hi,
> I am upgrading an existing project from struts 2.0.14 to 2.1.6. We are using the zero configuration approach, and the classpath scanning ability.
> The application is running on Websphere 6.1, and I had a lot of trouble having it work. My 2 major issues were :
> * Classes of the current project not being scanned : This url file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/classes/ was originally excluded by the filters in the convention plugin. I'll let you know exactly which one did that
> * We had some action classes in a dependency jar, and it didn't get included because of the wsjar protocol. See http://jira.opensymphony.com/browse/XW-669 for more documentation on this protocol and its inclusion in Xwork. The url look like :
> wsjar:file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/lib/axis-1.4.jar!/
> And are not processed by com.opensymphony.xwork2.util.finder.ClassFinder.
> I'll add more detail as I dig into this and let you know how I worked around it (except by moving to a real application server.... )
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WW-2999) Convention plugin and jar scanning
failing on Websphere
Posted by "Musachy Barroso (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45682#action_45682 ]
Musachy Barroso commented on WW-2999:
-------------------------------------
Kobe, can you try using a recent xwork snapshot, or building xwork by yourself?
> Convention plugin and jar scanning failing on Websphere
> -------------------------------------------------------
>
> Key: WW-2999
> URL: https://issues.apache.org/struts/browse/WW-2999
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - Convention
> Affects Versions: 2.1.6
> Environment: Websphere 6.1
> Reporter: Denis Cabasson
> Priority: Critical
>
> Hi,
> I am upgrading an existing project from struts 2.0.14 to 2.1.6. We are using the zero configuration approach, and the classpath scanning ability.
> The application is running on Websphere 6.1, and I had a lot of trouble having it work. My 2 major issues were :
> * Classes of the current project not being scanned : This url file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/classes/ was originally excluded by the filters in the convention plugin. I'll let you know exactly which one did that
> * We had some action classes in a dependency jar, and it didn't get included because of the wsjar protocol. See http://jira.opensymphony.com/browse/XW-669 for more documentation on this protocol and its inclusion in Xwork. The url look like :
> wsjar:file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/lib/axis-1.4.jar!/
> And are not processed by com.opensymphony.xwork2.util.finder.ClassFinder.
> I'll add more detail as I dig into this and let you know how I worked around it (except by moving to a real application server.... )
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WW-2999) Convention plugin and jar scanning
failing on Websphere
Posted by "Musachy Barroso (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45618#action_45618 ]
Musachy Barroso commented on WW-2999:
-------------------------------------
This was also fixed in trunk.
> Convention plugin and jar scanning failing on Websphere
> -------------------------------------------------------
>
> Key: WW-2999
> URL: https://issues.apache.org/struts/browse/WW-2999
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - Convention
> Affects Versions: 2.1.6
> Environment: Websphere 6.1
> Reporter: Denis Cabasson
> Priority: Critical
>
> Hi,
> I am upgrading an existing project from struts 2.0.14 to 2.1.6. We are using the zero configuration approach, and the classpath scanning ability.
> The application is running on Websphere 6.1, and I had a lot of trouble having it work. My 2 major issues were :
> * Classes of the current project not being scanned : This url file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/classes/ was originally excluded by the filters in the convention plugin. I'll let you know exactly which one did that
> * We had some action classes in a dependency jar, and it didn't get included because of the wsjar protocol. See http://jira.opensymphony.com/browse/XW-669 for more documentation on this protocol and its inclusion in Xwork. The url look like :
> wsjar:file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/lib/axis-1.4.jar!/
> And are not processed by com.opensymphony.xwork2.util.finder.ClassFinder.
> I'll add more detail as I dig into this and let you know how I worked around it (except by moving to a real application server.... )
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WW-2999) Convention plugin and jar scanning
failing on Websphere
Posted by "Musachy Barroso (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45684#action_45684 ]
Musachy Barroso commented on WW-2999:
-------------------------------------
Thanks Kobe. Can you debug the app at all? can you set a breakpoint at com.opensymphony.xwork2.util.FileManager$FileRevision.build(FileManager.java:191) and post what the fileUrl looks like?
> Convention plugin and jar scanning failing on Websphere
> -------------------------------------------------------
>
> Key: WW-2999
> URL: https://issues.apache.org/struts/browse/WW-2999
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - Convention
> Affects Versions: 2.1.6
> Environment: Websphere 6.1
> Reporter: Denis Cabasson
> Priority: Critical
>
> Hi,
> I am upgrading an existing project from struts 2.0.14 to 2.1.6. We are using the zero configuration approach, and the classpath scanning ability.
> The application is running on Websphere 6.1, and I had a lot of trouble having it work. My 2 major issues were :
> * Classes of the current project not being scanned : This url file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/classes/ was originally excluded by the filters in the convention plugin. I'll let you know exactly which one did that
> * We had some action classes in a dependency jar, and it didn't get included because of the wsjar protocol. See http://jira.opensymphony.com/browse/XW-669 for more documentation on this protocol and its inclusion in Xwork. The url look like :
> wsjar:file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/F6FMSWASTSTNode02Cell/fms-ear.ear/fms-web.war/WEB-INF/lib/axis-1.4.jar!/
> And are not processed by com.opensymphony.xwork2.util.finder.ClassFinder.
> I'll add more detail as I dig into this and let you know how I worked around it (except by moving to a real application server.... )
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.