struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Cooper (JIRA)" <j...@apache.org>
Subject [jira] Commented: (WW-2999) Convention plugin and jar scanning failing on Websphere
Date Tue, 03 Mar 2009 19:58:45 GMT

    [ 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.


Mime
View raw message