This preview shows page 1. Sign up to view the full content.
Unformatted text preview: jb-class> <session-type>Stateless</session-type> <transaction-type>Container</transaction-type> </session> </enterprise-beans> <assembly-descriptor> <method-permission> <unchecked/> <method> <ejb-name>HelloBean</ejb-name> <method-name>*</method-name> </method> </method-permission> <container-transaction> <description>Transaction attributes for 'HelloBean' methods</description> <method> <ejb-name>HelloBean</ejb-name> <method-name>*</method-name> </method> <trans-attribute>Required</trans-attribute> </container-transaction> </assembly-descriptor> </ejb-jar> tomcat ejb ws login and authorization doesn't work Tomcat ejb ws security must use the jacc framework for logging in and must not check any user data or web resource permissions. I've written a subclass of TomcatGeronimoRealm that does this. HTTPS Connectors fail on IBM JDK HTTPS connectors for Jetty and Tomcat fail to load when starting the server using the IBM 1.4.2 JDK. This worked with M4, but was broken sometime in the last several weeks by changes in M5. The IBM JDK supplies its own HTTPS handler - com.ibm.net.ssl.www.protocol, which must be manually loaded in addition to the default sun.net.www.protocol. Also, the IBM JDK provides a different implementation of the X059 algorithm, which is IbmX509 instead of SunX509. The required code changes to recognize that an IBM JDK is being used and initialize the algorithm and protocol handler correctly, are confined to the Jetty and Tomcat HttpsConnector classes and the GeronimoURLFactory. The resolution of this bug will only allow a Geronimo server built with the Sun JDK to run on an IBM JDK - it does not resolve the other known build and Orb problems with using non-Sun JVMs. The deployer does not look for ConfigurationBuilder in other modules Just add <module>*</module> in the deployment plan for...
View Full Document
This document was uploaded on 10/12/2012.
- Spring '09