Codehaus XFire

Documentation

Quicklinks

Developers

Sponsors

If you are trying to deploy XFire on IBM WebSphere 6.x and it's not working, you maybe should try following these instructions to make sure it's not an issue from XFire distribution.

  1. Due to default WAS policy, a custom was.policy file must be deployed in (either EAR or WAR archive) with the following content:
    META-INF/was.policy 
    grant codeBase "file:${application}" {
      permission java.security.AllPermission;
    };

    Obs: you can see SecurityPermission errors in WAS logs trying to deploy without this set up.

  2. Due to default WAS class loader configuration, you must change some properties of your deployed application before starts it.
    Go to the Administration Console > Applications > [ Your Application ]
    In the Application Configuration page, look for the field Class Loading and File Upload Detection
    Change these fields as follows:
    • Class loader mode: Parent Last
      * This change is required
    • WAR class loader policy: Application
      * Change this property if you deployed your XFire webapp inside an EAR.

Obs: you can see ClassCastExcecptions in WAS logs trying to run without these changes due to XFire distro and WebSphere jars incompatibilities (i.e.: JDOM)

Cheers!
--
Bruno Borges (at) GMail

As mentioned above, there are incompatibility issues with Websphere 6.x and the XFire distro.  The main issue is with the version of the jdom.jar, that ships with Websphere 6.x.  This jar was deprecated in Websphere 5.1, but still ships with 6.x.  If you simply remove the jdom.jar from the Websphere / Appserver / lib directory, XFire will deploy without fault.  So if the above method does not work or more likely not allowed, try simply removing the jdom.jar.