[
https://issues.apache.org/jira/browse/WW-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christina Kaskoura updated WW-3958:
-----------------------------------
Attachment: 2.3.8-error.txt
As a temporary workaround I managed to deploy the sample application in
GlassFish by using the GlasssFish_Platform=Static option which starts GlassFish
without OSGi. However, when attempting to use Struts version 2.3.8 instead of
2.3.1 I get the attached errors, which seem to be due to the fact that the
XWork file manager is null. I get the same errors also when deploying in Tomcat
instead of GlassFish.
> Struts2 OSGi plugin does not work with GlassFish
> ------------------------------------------------
>
> Key: WW-3958
> URL: https://issues.apache.org/jira/browse/WW-3958
> Project: Struts 2
> Issue Type: Bug
> Components: Other
> Affects Versions: 2.3.1
> Environment: GlassFish 3.1.2.2
> Reporter: Christina Kaskoura
> Fix For: 2.3.9
>
> Attachments: 2.3.8-error.txt, Struts2OSGi.zip
>
>
> The OSGi plugin does not work with GlassFish where Felix is already included.
> When including in the Struts web application a bundle containing an activator
> class the following exception occurs:
> java.lang.ClassCastException: myosgi.Activator cannot be cast to
> org.osgi.framework.BundleActivator
> while when including a bundle with a class which implements
> BundleContextAware the following exception occurs:
> Exception starting filter struts2 java.lang.LinkageError: loader constraint
> violation: loader (instance of
> org/apache/felix/framework/searchpolicy/ContentClassLoader) previously
> initiated loading for a different type with name
> "org/osgi/framework/BundleContext"
> It also seems that the plugin uses an old version of Felix which could be (at
> least partly) responsible for the errors since GlassFish uses a newer one.
> More details on the errors also available in [this stackoverflow
> post|http://stackoverflow.com/questions/14200300/using-struts2-osgi-plugin-with-glassfish]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
