We have no realistic plans to update Crowd's support for Resin, so I'm going to close this issue.

We recommend using Tomcat.

Obviously not fixed... thanks Dieter for the detective work

add_directoryconnector.jsp, same problem, same workaround.

add_directorydelegated.jsp has the same problem. Uploading a package with the tabs split out into separate included jsp files as a workaround.

Confirmed to work.

Split the tabs out into separate files, to avoid the compiler limitation on Resin (and probably Websphere).

Tested and confirmed as a viable workaround.

David:

I have been trying now to cover as much of the pages possible to make sure it really works (apart from the authentication mechanism).

Unfortunately I have found at least one (so far; still working on this) that runs into the Caucho Compiler Limit Issue:
com.caucho.java.JavaCompileException: /console/secure/principal/view_principal.jsp:547: code too large for try statement } catch (java.lang.Throwable jsp_e) { ^ /opt/resin-3.1.9/webapps/crowd/WEB-INF/work/_jsp/_console/_secure/_principal/_view_0principaljsp.java:93: code too large for try statement try { ^ /opt/resin-3.1.9/webapps/crowd/WEB-INF/work/_jsp/_console/_secure/_principal/_view_0principal_jsp.java:16: code too large _jspService(javax.servlet.http.HttpServletRequest request, ^ 3 errors

This seems to be related to:
http://bugs.caucho.com/view.php?id=1530

May require more work to get it running, but this limit may also hit you on Websphere, so it may be a good idea to fix it.

Regards,
Dieter

Dieter,

Thanks heaps for providing the workaround. It's much appreciated & will save people a bunch of heartache.
Cheers,
Dave.
Crowd Product Manager.

JAXP can be a pain when it comes to containers. That's actually why I would suggest you to use OSGi and do it through a Factory providing Service

Now, to make Crowd work on Resin 3.1.9 (I am using Crod 2.0.2), what it really needs is to set all required parser factories using corresponding system properties. Now, Crowd uses XFire, XFire works best with WoodStox, and voila

      <web-app id="/crowd" root-directory="webapps/crowd" >
         <!-- xml -->
         <system-property javax.xml.parsers.DocumentBuilderFactory=
             "org.apache.xerces.jaxp.DocumentBuilderFactoryImpl"/>
         <system-property javax.xml.parsers.SAXParserFactory=
             "org.apache.xerces.jaxp.SAXParserFactoryImpl"/>
         <!--  xslt -->
         <system-property javax.xml.transform.TransformerFactory=
             "org.apache.xalan.processor.TransformerFactoryImpl"/>
        
         <!-- StAX for XFire! -->
         <system-property javax.xml.stream.XMLInputFactory="com.ctc.wstx.stax.WstxInputFactory" />
         <system-property javax.xml.stream.XMLOutputFactory="com.ctc.wstx.stax.WstxOutputFactory" />
         <system-property javax.xml.stream.XMLEventFactory="com.ctc.wstx.stax.WstxEventFactory" />
      
      </web-app>

Setting these properties on the web application itself, will isolate (not apply them for all, which may cause conflicts with other apps e.g. Solr).

Enjoy, and I guess somebody can close this one.

What is the current progress of this issue? This issue is a major blocker for our project of integrating JIRA and Confluence under common user authentication system on Resin 3.1.7a.