[jira] Updated: (GERONIMO-4902) need license file modifications for imported plexus code in osgi sandbox modules/geronimo-plugin
[ https://issues.apache.org/jira/browse/GERONIMO-4902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4902: --- Component/s: osgi need license file modifications for imported plexus code in osgi sandbox modules/geronimo-plugin Key: GERONIMO-4902 URL: https://issues.apache.org/jira/browse/GERONIMO-4902 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: osgi, Plugins Affects Versions: 3.0 Reporter: David Jencks Assignee: Kevan Miller Fix For: 3.0 In order to avoid giant problems with plexus invasiveness I copied the plexus code we need to build archives into geronimo-plugin and modified it to not pull in all of the plexus infrastructure. We need to find a way to eliminate this code or fix the legal files. rev 821961, https://svn.apache.org/repos/asf/geronimo/sandbox/djencks/osgi/framework Kevan, if you don't want to do this unassign it -- I thought you might be the best at figuring out what we need. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4902) need license file modifications for imported plexus code in osgi sandbox modules/geronimo-plugin
[ https://issues.apache.org/jira/browse/GERONIMO-4902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4902: --- Issue Type: Sub-task (was: Bug) Parent: GERONIMO-5087 need license file modifications for imported plexus code in osgi sandbox modules/geronimo-plugin Key: GERONIMO-4902 URL: https://issues.apache.org/jira/browse/GERONIMO-4902 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: osgi, Plugins Affects Versions: 3.0 Reporter: David Jencks Assignee: Kevan Miller Fix For: 3.0 In order to avoid giant problems with plexus invasiveness I copied the plexus code we need to build archives into geronimo-plugin and modified it to not pull in all of the plexus infrastructure. We need to find a way to eliminate this code or fix the legal files. rev 821961, https://svn.apache.org/repos/asf/geronimo/sandbox/djencks/osgi/framework Kevan, if you don't want to do this unassign it -- I thought you might be the best at figuring out what we need. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4921) Figure out how to handle OSGI cache in Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4921: --- Issue Type: Sub-task (was: Improvement) Parent: GERONIMO-5087 Figure out how to handle OSGI cache in Geronimo --- Key: GERONIMO-4921 URL: https://issues.apache.org/jira/browse/GERONIMO-4921 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: osgi Affects Versions: 3.0 Reporter: Ivan Fix For: 3.0 Some install/uninstall action should be done via OSGI API or Karaf functions more easily. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5041) Use Aries InitialContextFactoryBuilder
[ https://issues.apache.org/jira/browse/GERONIMO-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-5041: --- Issue Type: Sub-task (was: New Feature) Parent: GERONIMO-5086 Use Aries InitialContextFactoryBuilder -- Key: GERONIMO-5041 URL: https://issues.apache.org/jira/browse/GERONIMO-5041 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: naming, osgi Affects Versions: 3.0 Reporter: David Jencks Assignee: David Jencks Fix For: 3.0 Aries has a partial implementation of the osgi frc 142 jndi stuff. We should integrate it. One of the bits is an InitaliContextFactoryBuilder that uses the service registry to find appropriate url context factories rather than the unfortunate scheme envisaged by the jndi spec. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5016) Enable cxf in Geronimo 3.0
[ https://issues.apache.org/jira/browse/GERONIMO-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-5016: --- Issue Type: Sub-task (was: Task) Parent: GERONIMO-5082 Enable cxf in Geronimo 3.0 -- Key: GERONIMO-5016 URL: https://issues.apache.org/jira/browse/GERONIMO-5016 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Affects Versions: 3.0 Environment: Enable cxf in Geronimo 3.0 Reporter: Rex Wang Assignee: Rex Wang Fix For: 3.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4992) Tomcat StandardContext use of Class.forName(className) doesn't work well in osgi
[ https://issues.apache.org/jira/browse/GERONIMO-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4992: --- Issue Type: Sub-task (was: Bug) Parent: GERONIMO-5087 Tomcat StandardContext use of Class.forName(className) doesn't work well in osgi Key: GERONIMO-4992 URL: https://issues.apache.org/jira/browse/GERONIMO-4992 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: osgi, Tomcat Affects Versions: 3.0 Reporter: David Jencks Assignee: David Jencks Fix For: 3.0 Tomcat 7's StandardContext.createWrapper() method uses a lot of Class.forName(fooName). This doesn't work for us since some of the listeners are in the geronimo-tomcat7 bundle, not tomcat itself. Using the InstanceManager works fine for us. I've overridden the method in GeronimoStandardContext. We should talk to tomcat about fixing this in tomcat itslef. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5016) Enable cxf in Geronimo 3.0
[ https://issues.apache.org/jira/browse/GERONIMO-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-5016: --- Component/s: webservices javaee6 Enable cxf in Geronimo 3.0 -- Key: GERONIMO-5016 URL: https://issues.apache.org/jira/browse/GERONIMO-5016 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: javaee6, webservices Affects Versions: 3.0 Environment: Enable cxf in Geronimo 3.0 Reporter: Rex Wang Assignee: Rex Wang Fix For: 3.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5008) Create util methods for all the Geronimo components
[ https://issues.apache.org/jira/browse/GERONIMO-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-5008: --- Issue Type: Sub-task (was: Improvement) Parent: GERONIMO-5087 Create util methods for all the Geronimo components --- Key: GERONIMO-5008 URL: https://issues.apache.org/jira/browse/GERONIMO-5008 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Affects Versions: 3.0 Reporter: Ivan Assignee: Ivan Priority: Minor Fix For: 3.0 Create util methods for all the Geronimo components -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4919) The @WebListener annotation needs to be able to accept a value as the description
[ https://issues.apache.org/jira/browse/GERONIMO-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4919: --- Issue Type: Sub-task (was: Bug) Parent: GERONIMO-5061 The @WebListener annotation needs to be able to accept a value as the description - Key: GERONIMO-4919 URL: https://issues.apache.org/jira/browse/GERONIMO-4919 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: javaee6, specs, web, Web Profile Affects Versions: 3.0 Reporter: Robert Goff Assignee: David Jencks Priority: Minor Fix For: 3.0 The @WebListener annotation needs to be able to accept a value as the description i.e. @WebListener(The description of the listener) See: http://javadoc.glassfish.org/javaee6/apidoc/javax/servlet/annotation/WebListener.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4680) Create a plugin in for OpenJPA 2.0.
[ https://issues.apache.org/jira/browse/GERONIMO-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12828643#action_12828643 ] Rick McGuire commented on GERONIMO-4680: I opened this some time ago, so this could be redundant. Right now, I'm just trying to get all of the 3.0 Jiras organized into different categories and classified better so we can have automated status snapshots more easily created to see what work needs to be done for 3.0 and see who is working on what. Create a plugin in for OpenJPA 2.0. Key: GERONIMO-4680 URL: https://issues.apache.org/jira/browse/GERONIMO-4680 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: javaee6, persistence, Web Profile Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Now that the JEE6 specifications are getting closer to reality and OpenJPA is getting closer to supporting the JPA 2.0 specification, we should have a plugin that allows OpenJPA 2.0 to replace the 1.x version so people can start kicking the tires on the new version. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5098) Create Servlet 3.0 version of the spec jar.
Create Servlet 3.0 version of the spec jar. Key: GERONIMO-5098 URL: https://issues.apache.org/jira/browse/GERONIMO-5098 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Reporter: Rick McGuire -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5098) Create Servlet 3.0 version of the spec jar.
[ https://issues.apache.org/jira/browse/GERONIMO-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire closed GERONIMO-5098. -- Resolution: Fixed Fix Version/s: 3.0 Already created and available in specs project. Create Servlet 3.0 version of the spec jar. Key: GERONIMO-5098 URL: https://issues.apache.org/jira/browse/GERONIMO-5098 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Rick McGuire Fix For: 3.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5099) Create JSP 2.2 spec jar
[ https://issues.apache.org/jira/browse/GERONIMO-5099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire closed GERONIMO-5099. -- Resolution: Fixed Spec jar created and available. Create JSP 2.2 spec jar Key: GERONIMO-5099 URL: https://issues.apache.org/jira/browse/GERONIMO-5099 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: javaee6, specs, Web Profile Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Create a JSP 2.2 spec jar in the specs project. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5099) Create JSP 2.2 spec jar
Create JSP 2.2 spec jar Key: GERONIMO-5099 URL: https://issues.apache.org/jira/browse/GERONIMO-5099 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Components: javaee6, specs, Web Profile Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Create a JSP 2.2 spec jar in the specs project. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5031) Implement EL spec 2.2
[ https://issues.apache.org/jira/browse/GERONIMO-5031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12828648#action_12828648 ] Rick McGuire commented on GERONIMO-5031: Is this work item complete now? Implement EL spec 2.2 -- Key: GERONIMO-5031 URL: https://issues.apache.org/jira/browse/GERONIMO-5031 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: javaee6, specs, Web Profile Affects Versions: 3.0 Reporter: Ivan Assignee: Ivan Fix For: 3.0 Attachments: GERONIMO-5031.patch Implement EL spec 2.2, a new brach is created and some first steps are committed, including : 1. Implement newInstance in ExpressionFactory 2. Add new class ValueReference. 3. Add invoke methods to ELResolver Next step, will implement those invoke methods. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5100) Create connector 1.6 spec jar
[ https://issues.apache.org/jira/browse/GERONIMO-5100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire closed GERONIMO-5100. -- Resolution: Fixed Spec jar is available in the specs project. Create connector 1.6 spec jar - Key: GERONIMO-5100 URL: https://issues.apache.org/jira/browse/GERONIMO-5100 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: javaee6 Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5100) Create connector 1.6 spec jar
Create connector 1.6 spec jar - Key: GERONIMO-5100 URL: https://issues.apache.org/jira/browse/GERONIMO-5100 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Components: javaee6 Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5061) Servlet 3.0 enhancements
Servlet 3.0 enhancements Key: GERONIMO-5061 URL: https://issues.apache.org/jira/browse/GERONIMO-5061 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: Web Profile Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Upgrade Geronimo to support the servlet 3.0 (JSR 315) specification. This item includes both Tomcat and Jetty subtasks. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5062) JSP 2.2 Enhancements
JSP 2.2 Enhancements Key: GERONIMO-5062 URL: https://issues.apache.org/jira/browse/GERONIMO-5062 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: javaee6, Web Profile Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Upgrade Geronimo to support JSP 2.2 (JSR 245) for both Tomcat and Jetty web containers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5063) Expression Language 2.2 enhancements
Expression Language 2.2 enhancements Key: GERONIMO-5063 URL: https://issues.apache.org/jira/browse/GERONIMO-5063 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: javaee6, Web Profile Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Upgrade to expression language 2.2 (JSR 245) for both Tomcat and Jetty. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5064) Java Server Faces 2.0 enhancement
Java Server Faces 2.0 enhancement - Key: GERONIMO-5064 URL: https://issues.apache.org/jira/browse/GERONIMO-5064 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: javaee6, Web Profile Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Upgrade the Geronimo JSF level to 2.0 (JSR 314) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5065) EJBs in WAR files enhancement
EJBs in WAR files enhancement - Key: GERONIMO-5065 URL: https://issues.apache.org/jira/browse/GERONIMO-5065 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: javaee6 Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 JSR 316 includes new support to allow EJBs to be package inside of WAR files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5066) Java EE 6 Global JNDI enhancments
Java EE 6 Global JNDI enhancments - Key: GERONIMO-5066 URL: https://issues.apache.org/jira/browse/GERONIMO-5066 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: javaee6, Web Profile Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Enhancements for the java ee 6 global JNDI additions specified by JSR 316, -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5067) Java ee 6 datasource resource definition enhancements.
Java ee 6 datasource resource definition enhancements. --- Key: GERONIMO-5067 URL: https://issues.apache.org/jira/browse/GERONIMO-5067 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: javaee6 Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Implement the data source resource additions specified in JSR 316. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5068) JPA 2.0 enhancements
JPA 2.0 enhancements Key: GERONIMO-5068 URL: https://issues.apache.org/jira/browse/GERONIMO-5068 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: javaee6, Web Profile Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Upgrade the persistence support to JPA 2.0 (JSR 317) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5069) Java Connector Architecture 1.6 enhancements
Java Connector Architecture 1.6 enhancements Key: GERONIMO-5069 URL: https://issues.apache.org/jira/browse/GERONIMO-5069 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: javaee6 Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Upgrade to JCA 1.6 (JSR 322) specification level. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5070) JACC 1.4 enhancements
JACC 1.4 enhancements - Key: GERONIMO-5070 URL: https://issues.apache.org/jira/browse/GERONIMO-5070 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: javaee6 Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Upgrade to JACC 1.4 (JSR 115) specification level. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5071) JASPIC 1.0 Enhancement
JASPIC 1.0 Enhancement --- Key: GERONIMO-5071 URL: https://issues.apache.org/jira/browse/GERONIMO-5071 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: javaee6 Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Implement JASPIC 1.0 (JSR 196) for Geronimo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5072) Common Annotations 1.1 enhancements
Common Annotations 1.1 enhancements --- Key: GERONIMO-5072 URL: https://issues.apache.org/jira/browse/GERONIMO-5072 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: javaee6, Web Profile Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Upgrade to the Common Annotations 1.1 level (JSR 250) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5073) EJB 3.1 Enhancements
EJB 3.1 Enhancements Key: GERONIMO-5073 URL: https://issues.apache.org/jira/browse/GERONIMO-5073 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: javaee6 Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Upgrade to the EJB 3.1 specification level (JSR 3.1.) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5074) EJB 3.1 Lite enhancements
EJB 3.1 Lite enhancements - Key: GERONIMO-5074 URL: https://issues.apache.org/jira/browse/GERONIMO-5074 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: javaee6, Web Profile Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Add a plugin version for the EJB 3.1 Lite specification level that can be used for the web profile assembly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5075) Convert the minimal assembly into a Java EE 6 Web Profile assembly
Convert the minimal assembly into a Java EE 6 Web Profile assembly -- Key: GERONIMO-5075 URL: https://issues.apache.org/jira/browse/GERONIMO-5075 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: javaee6, Web Profile Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Create the necessary configurations and plugins for a Web Profile assembly and convert the minimal assembly into the Web Profile version. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5076) Interceptor 1.1 enhancements
Interceptor 1.1 enhancements Key: GERONIMO-5076 URL: https://issues.apache.org/jira/browse/GERONIMO-5076 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: javaee6, Web Profile Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Upgrade to the Interceptor 1.1 specification level (JSR 318) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5078) Managed Bean 1.0 enhancements
Managed Bean 1.0 enhancements - Key: GERONIMO-5078 URL: https://issues.apache.org/jira/browse/GERONIMO-5078 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: javaee6, Web Profile Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Add support for Managed Beans 1.0 (JSR 318) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5077) Bean Validation 1.0 enhancements
Bean Validation 1.0 enhancements Key: GERONIMO-5077 URL: https://issues.apache.org/jira/browse/GERONIMO-5077 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: javaee6, Web Profile Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Add support for the Bean Validation 1.0 specification (JSR 302) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5079) Dependency Injection 1.0 enhancements
Dependency Injection 1.0 enhancements - Key: GERONIMO-5079 URL: https://issues.apache.org/jira/browse/GERONIMO-5079 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: javaee6, Web Profile Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Add support for the DI 1.0 specification (JSR 330) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5080) Contexts and Dependency Injection 1.0 enhancements
Contexts and Dependency Injection 1.0 enhancements -- Key: GERONIMO-5080 URL: https://issues.apache.org/jira/browse/GERONIMO-5080 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: javaee6, Web Profile Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Add support for the CDI 1.0 specification (JSR 299) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5081) Web Services for EE 1.3-MR2 enhancements
Web Services for EE 1.3-MR2 enhancements Key: GERONIMO-5081 URL: https://issues.apache.org/jira/browse/GERONIMO-5081 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: javaee6 Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Implement the enhancements in the WSEE 1.3-MR2 released (JSR 109) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5082) JAX-WS 2.2 enhancements
JAX-WS 2.2 enhancements --- Key: GERONIMO-5082 URL: https://issues.apache.org/jira/browse/GERONIMO-5082 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Reporter: Rick McGuire Additions for the JAX-WS 2.2 enhancements. This includes work for both Axis2 and CXF imtegration. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5083) JAX-RS 1.1 enhancements
JAX-RS 1.1 enhancements --- Key: GERONIMO-5083 URL: https://issues.apache.org/jira/browse/GERONIMO-5083 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: javaee6 Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Addition of JAX-RX to the javaee 6 stack (JSR 311) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5084) JAXB 2.2 enhancements
JAXB 2.2 enhancements - Key: GERONIMO-5084 URL: https://issues.apache.org/jira/browse/GERONIMO-5084 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: javaee6 Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Upgrade to the JAXB 2.2 specification level (JSR 222) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5085) CORBA/Yoko OSGi enhancements
CORBA/Yoko OSGi enhancements Key: GERONIMO-5085 URL: https://issues.apache.org/jira/browse/GERONIMO-5085 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: javaee6, osgi Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Get CORBA/Yoko working in an OSGi environment. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5086) Apache Aries enhancements
Apache Aries enhancements - Key: GERONIMO-5086 URL: https://issues.apache.org/jira/browse/GERONIMO-5086 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: Aries, osgi Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Support for hosting Apache Aries applications on Geronimo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4976) rfc 66 support for jetty and tomcat
[ https://issues.apache.org/jira/browse/GERONIMO-4976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4976: --- Issue Type: Sub-task (was: Bug) Parent: GERONIMO-5086 rfc 66 support for jetty and tomcat --- Key: GERONIMO-4976 URL: https://issues.apache.org/jira/browse/GERONIMO-4976 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: Jetty, osgi, Tomcat Affects Versions: 3.0 Reporter: David Jencks Fix For: 3.0 We probably want to support osgi rfc 66. One thing it has is access to the BundleContext through the ServletContext as an attribute: BundleContext webAppBundleContext = servletContext.getAttribute(osgi-bundlecontext); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5087) Use OSGi for the Geronimo classloading model.
Use OSGi for the Geronimo classloading model. -- Key: GERONIMO-5087 URL: https://issues.apache.org/jira/browse/GERONIMO-5087 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: osgi Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4996) myfaces 2 osgi integration
[ https://issues.apache.org/jira/browse/GERONIMO-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4996: --- Issue Type: Sub-task (was: Bug) Parent: GERONIMO-5087 myfaces 2 osgi integration -- Key: GERONIMO-4996 URL: https://issues.apache.org/jira/browse/GERONIMO-4996 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: osgi Affects Versions: 3.0 Reporter: David Jencks Fix For: 3.0 Tracking of integrating myfaces 2 integration into geronimo under osgi. first problem is to get myfaces to fix their osgi metadata to allow use of servlet 3 api jars and other javaee6 spec bundles. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4972) Nested child configurations from ears don't work well with osgi
[ https://issues.apache.org/jira/browse/GERONIMO-4972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4972: --- Issue Type: Sub-task (was: Bug) Parent: GERONIMO-5087 Nested child configurations from ears don't work well with osgi --- Key: GERONIMO-4972 URL: https://issues.apache.org/jira/browse/GERONIMO-4972 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: deployment, osgi Affects Versions: 3.0 Reporter: David Jencks Assignee: David Jencks Fix For: 3.0 Right now we are generating nested bundles inside plugins for ear files with web modules. These don't quite work. One code problem is that the SimpleConifgurationManager tries to start the child bundles before the configuration for the parent/containing bundle is registered, so a getConfiguration call to find the parent config fails. This is probably easy to fix. However a bigger issue is that there's no way to tell the osgi framework about the nested bundle. Three possible solutions: 1. stop having nested bundles, just use one bundle per ear. This is a 1-line change in AbstractWebModuleBuilder so I expect to use this until we can actually solve the problem 2. modify the pax mvn url handler to deal with urls to nested bundles inside the car. 3. modify the ear deployer to create more than one bundle from an ear. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4924) Reenable the client container in Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4924: --- Issue Type: Sub-task (was: Task) Parent: GERONIMO-5087 Reenable the client container in Geronimo - Key: GERONIMO-4924 URL: https://issues.apache.org/jira/browse/GERONIMO-4924 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Affects Versions: 3.0 Reporter: Ivan Fix For: 3.0 Please refer to http://www.nabble.com/connector_1.6-td25997828s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5045) geronimo-maven-plugin needs to be updated for karaf
[ https://issues.apache.org/jira/browse/GERONIMO-5045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-5045: --- Issue Type: Sub-task (was: Bug) Parent: GERONIMO-5087 geronimo-maven-plugin needs to be updated for karaf --- Key: GERONIMO-5045 URL: https://issues.apache.org/jira/browse/GERONIMO-5045 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: buildsystem, osgi Affects Versions: 3.0 Reporter: David Jencks Assignee: David Jencks Fix For: 3.0 geronimo-maven-plugin needs to be updated for karaf. This should start letting it's work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4920) Convert Tomcat plugin to bundlized version.
[ https://issues.apache.org/jira/browse/GERONIMO-4920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4920: --- Issue Type: Sub-task (was: Task) Parent: GERONIMO-5087 Convert Tomcat plugin to bundlized version. Key: GERONIMO-4920 URL: https://issues.apache.org/jira/browse/GERONIMO-4920 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: osgi Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Placeholder for the Tomcat cleanup work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5047) Create javaee 6 Tomcat assemblies and plugin groups.
[ https://issues.apache.org/jira/browse/GERONIMO-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-5047: --- Summary: Create javaee 6 Tomcat assemblies and plugin groups. (was: Create javaee5 Tomcat assemblies and plugin groups. ) Create javaee 6 Tomcat assemblies and plugin groups. - Key: GERONIMO-5047 URL: https://issues.apache.org/jira/browse/GERONIMO-5047 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: Tomcat Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 javaee6 versions of the assemblies and plugin groups have been created for jetty in trunk, but the similar changes have not been made for Tomcat. I suspect this ends up just being a series of renames, since we're already building with Tomcat 7 versions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5047) Create javaee 6 Tomcat assemblies and plugin groups.
[ https://issues.apache.org/jira/browse/GERONIMO-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-5047: --- Issue Type: Sub-task (was: Task) Parent: GERONIMO-5061 Create javaee 6 Tomcat assemblies and plugin groups. - Key: GERONIMO-5047 URL: https://issues.apache.org/jira/browse/GERONIMO-5047 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: Tomcat Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 javaee6 versions of the assemblies and plugin groups have been created for jetty in trunk, but the similar changes have not been made for Tomcat. I suspect this ends up just being a series of renames, since we're already building with Tomcat 7 versions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4974) ee apps or other plugins can't contain gbeans
[ https://issues.apache.org/jira/browse/GERONIMO-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4974: --- Issue Type: Sub-task (was: Bug) Parent: GERONIMO-5087 ee apps or other plugins can't contain gbeans - Key: GERONIMO-4974 URL: https://issues.apache.org/jira/browse/GERONIMO-4974 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: deployment, osgi Affects Versions: 3.0 Reporter: David Jencks Fix For: 3.0 right now the deployer adds packages it can detect as used in a gbean to the Import-Packages. However it never populares Export-Package. This causes problems if the class is actually in the plugin/bundle we are constructing. If a bundle contains a class, if it lists the package in Import-Package, it won't satisfy the constraint itself unless the package is also listed in Export-Package. So, we need to make the deployer list all the packages contained in the bundle in Export-Package. This might be a challenge in case there are embedded jars and a complicated Bundle-Classpath. For now the workaround appears to be to move any classes used in gbeans to another bundle rather than packing them in a javaee app. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4931) Enable ActiveMQ plugin in the OSGI environment
[ https://issues.apache.org/jira/browse/GERONIMO-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4931: --- Issue Type: Sub-task (was: Task) Parent: GERONIMO-5087 Enable ActiveMQ plugin in the OSGI environment -- Key: GERONIMO-4931 URL: https://issues.apache.org/jira/browse/GERONIMO-4931 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: ActiveMQ, osgi Affects Versions: 3.0 Reporter: Ivan Fix For: 3.0 Enable ActiveMQ plugin in the OSGI environment -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5019) geronimo-cdi-1.0 spec needs to be using the JEE6 dependencies, not the JEE5 versions.
[ https://issues.apache.org/jira/browse/GERONIMO-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-5019: --- Issue Type: Sub-task (was: New Feature) Parent: GERONIMO-5080 geronimo-cdi-1.0 spec needs to be using the JEE6 dependencies, not the JEE5 versions. -- Key: GERONIMO-5019 URL: https://issues.apache.org/jira/browse/GERONIMO-5019 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 The geronimo-cdi-1.0 spec jar is using the JEE5 versions of the interceptor and expression language spec jars rather than the JEE6 versions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4934) Make application client container work under osgi
[ https://issues.apache.org/jira/browse/GERONIMO-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4934: --- Issue Type: Sub-task (was: Improvement) Parent: GERONIMO-5087 Make application client container work under osgi - Key: GERONIMO-4934 URL: https://issues.apache.org/jira/browse/GERONIMO-4934 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: osgi Affects Versions: 3.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4815) Update myfaces' version to 2.0
[ https://issues.apache.org/jira/browse/GERONIMO-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4815: --- Issue Type: Sub-task (was: New Feature) Parent: GERONIMO-5064 Update myfaces' version to 2.0 -- Key: GERONIMO-4815 URL: https://issues.apache.org/jira/browse/GERONIMO-4815 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: dependencies Affects Versions: 3.0 Reporter: Ivan Assignee: Ivan Fix For: 3.0 Update the myfaces' version to 2.0-SNAPSHOT in the trunk. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4980) Use Tomcat 7 in Geronimo 3.0
[ https://issues.apache.org/jira/browse/GERONIMO-4980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4980: --- Issue Type: Sub-task (was: Task) Parent: GERONIMO-5061 Use Tomcat 7 in Geronimo 3.0 Key: GERONIMO-4980 URL: https://issues.apache.org/jira/browse/GERONIMO-4980 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: Tomcat Affects Versions: 3.0 Reporter: Ivan Fix For: 3.0 Use Tomcat 7 in Geronimo 3.0. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4908) RMIClassLoader is not compatible with osgi
[ https://issues.apache.org/jira/browse/GERONIMO-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4908: --- Issue Type: Sub-task (was: Bug) Parent: GERONIMO-5087 RMIClassLoader is not compatible with osgi -- Key: GERONIMO-4908 URL: https://issues.apache.org/jira/browse/GERONIMO-4908 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: osgi Affects Versions: 3.0 Reporter: David Jencks Fix For: 3.0 We have RMIClassLoaderSpiImpl in geronimo-kernel. However, RMIClassLoader loads the spi impl using the system classloader. (http://java.sun.com/javase/6/docs/api/java/rmi/server/RMIClassLoader.html) So we'd have to get our impl into the system classloader unless osgi provides an additional level of delegation in the system classloader. For now I'm going to try not setting java.rmi.server.RMIClassLoaderSpi in RMIRegistryService -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4909) How should we shut down plugin under osgi?
[ https://issues.apache.org/jira/browse/GERONIMO-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4909: --- Issue Type: Sub-task (was: Bug) Parent: GERONIMO-5087 How should we shut down plugin under osgi? -- Key: GERONIMO-4909 URL: https://issues.apache.org/jira/browse/GERONIMO-4909 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: osgi Affects Versions: 3.0 Reporter: David Jencks Fix For: 3.0 ConfigurationActivator needs it's stop method to shut down the plugin. Calling configurationManager.unload(id) is symmetrical with start and should leave the configuration model in a consistent state, but resets the load attribute in config.xml to false, which prevents restarting the server. Just stopping and unloading the configuration gbean works fine but may leave the configuration model (in the configuration manager) in an inconsistent state. This needs further investigation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4936) OpenJPA2 plugin needs to replace use of Configuration.getConfigurationClassLoader()
[
https://issues.apache.org/jira/browse/GERONIMO-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire updated GERONIMO-4936:
---
Issue Type: Sub-task (was: Bug)
Parent: GERONIMO-5068
OpenJPA2 plugin needs to replace use of
Configuration.getConfigurationClassLoader()
---
Key: GERONIMO-4936
URL: https://issues.apache.org/jira/browse/GERONIMO-4936
Project: Geronimo
Issue Type: Sub-task
Security Level: public(Regular issues)
Components: osgi
Affects Versions: 3.0
Reporter: Donald Woods
Fix For: 3.0
As pointed out by the TODO added in r830529 by Rick McGuire -
plugins/openjpa2/geronimo-openjpa2/src/main/java/org/apache/geronimo/openjpa/ConfigurationMonitorGBean.java
{code}
private void configurationRunning(AbstractName name) {
try {
Configuration config = (Configuration)kernel.getGBean(name);
-classLoaderMap.put(name, config.getConfigurationClassLoader());
+// TODO: This needs to be resolved as to what class loader should be
registered
+// classLoaderMap.put(name, config.getConfigurationClassLoader());
} catch (GBeanNotFoundException gnfe) {
log.warn(Could not retrieve GBean for artifact: +
name.toString(), gnfe);
}
}
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4914) gogo commands for manipulating g. plugins
[ https://issues.apache.org/jira/browse/GERONIMO-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4914: --- Issue Type: Sub-task (was: New Feature) Parent: GERONIMO-5088 gogo commands for manipulating g. plugins - Key: GERONIMO-4914 URL: https://issues.apache.org/jira/browse/GERONIMO-4914 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: osgi Affects Versions: 3.0 Reporter: David Jencks Fix For: 3.0 We need some simple gogo commands for manipulating geronimo plugins - listing, starting gbeans, stopping gbeans, etc. I started on this in a geronimo-shell-base module. we might be able to adapt the gshell commands, although I don't think groovy is necessary or appropriate here. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5088) Support OSGi as a Geronimo programming model
Support OSGi as a Geronimo programming model Key: GERONIMO-5088 URL: https://issues.apache.org/jira/browse/GERONIMO-5088 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: osgi Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 This is for enhancements to the Geronimo deployment and management models for supporting OSGi bundles as application bundles. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4911) osgi manifest for plugins is created in the car-maven-plugin, not the deployer
[ https://issues.apache.org/jira/browse/GERONIMO-4911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4911: --- Issue Type: Sub-task (was: Bug) Parent: GERONIMO-5087 osgi manifest for plugins is created in the car-maven-plugin, not the deployer -- Key: GERONIMO-4911 URL: https://issues.apache.org/jira/browse/GERONIMO-4911 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: osgi Affects Versions: 3.0 Reporter: David Jencks Assignee: David Jencks Fix For: 3.0 Currently the deployer doesn't generate osgi metadata, the car-maven-plugin does. This needs to be fixed so that its possible to deploy stuff directly to geronimo without building a plugin with maven first. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4913) Use pax mvn urls everywhere possible.
[ https://issues.apache.org/jira/browse/GERONIMO-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4913: --- Issue Type: Sub-task (was: Improvement) Parent: GERONIMO-5087 Use pax mvn urls everywhere possible. - Key: GERONIMO-4913 URL: https://issues.apache.org/jira/browse/GERONIMO-4913 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: osgi Affects Versions: 3.0 Reporter: David Jencks Fix For: 3.0 While running the server, we use pax mvn urls for bundle locations, but not always while running tests and otherwise during the build. We should clean this up to use mvn urls except for temporary bundles in the DeploymentContext. The code that creates the non mvn: urls is in locateBundle methods in SimpleConfigurationManager and DeploymentManager. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5089) Reorganize the Geronimo console and rebase on Pluto 2.
Reorganize the Geronimo console and rebase on Pluto 2. --- Key: GERONIMO-5089 URL: https://issues.apache.org/jira/browse/GERONIMO-5089 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: console Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 This new release is a good opportunity to redo the console and convert to a Pluto 2 portal version. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4982) ccpp (jsr 188) spec bundle
[ https://issues.apache.org/jira/browse/GERONIMO-4982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4982: --- Issue Type: Sub-task (was: Bug) Parent: GERONIMO-5089 ccpp (jsr 188) spec bundle -- Key: GERONIMO-4982 URL: https://issues.apache.org/jira/browse/GERONIMO-4982 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: console, osgi-bundles, specs Affects Versions: 3.0 Reporter: David Jencks Assignee: David Jencks Fix For: 3.0 Pluto 2 requires a ccpp spec jar. They are using the sun one in the build. I'm not sure if we can redistribute that or distribute a bundlized version of it so I wrote a new implementation from the javadoc while we figure this out. Sun download page: http://jcp.org/aboutJava/communityprocess/final/jsr188/index.html license page: https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_JCP-Site/en_US/-/USD/ViewLicense-Start -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5009) Enable Java EE package deployment in Geronimo 3.0
[ https://issues.apache.org/jira/browse/GERONIMO-5009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-5009: --- Issue Type: Sub-task (was: Bug) Parent: GERONIMO-5087 Enable Java EE package deployment in Geronimo 3.0 - Key: GERONIMO-5009 URL: https://issues.apache.org/jira/browse/GERONIMO-5009 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: deployment Affects Versions: 3.0 Reporter: Ivan Fix For: 3.0 Attachments: Geronimo-5009-2.patch Figure out how to deploy Java EE packages in the new OSGI environment -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4926) Fix ConfigurationMonitorGBean management of PCRegistry class.
[ https://issues.apache.org/jira/browse/GERONIMO-4926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4926: --- Fix Version/s: 3.0 Fix ConfigurationMonitorGBean management of PCRegistry class. -- Key: GERONIMO-4926 URL: https://issues.apache.org/jira/browse/GERONIMO-4926 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: osgi Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 The ConfigurationMonitorGBean maintains a cache of active configuration class loaders and when a configuration is shutdown, it tells the openjpa PCRegistry to remove any cached classes associated with that class loader. This won't work any more because there is no such thing as a configuration class loader. It might be possible to get the bundle for the class loader, then request the list of managed classes and iterate through the classes looking for any class that might be defined using a BundleReference class loader for that bundle. If one is found, then that classloader can be used for the deregister() operation. For now, the insertion of the map entries is disabled. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4920) Convert Tomcat plugin to bundlized version.
[ https://issues.apache.org/jira/browse/GERONIMO-4920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4920: --- Fix Version/s: 3.0 Assignee: (was: Rick McGuire) Convert Tomcat plugin to bundlized version. Key: GERONIMO-4920 URL: https://issues.apache.org/jira/browse/GERONIMO-4920 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: osgi Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Placeholder for the Tomcat cleanup work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4934) Make application client container work under osgi
[ https://issues.apache.org/jira/browse/GERONIMO-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4934: --- Fix Version/s: 3.0 Make application client container work under osgi - Key: GERONIMO-4934 URL: https://issues.apache.org/jira/browse/GERONIMO-4934 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: osgi Affects Versions: 3.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4971) Recognize Aries applications in Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4971: --- Fix Version/s: 3.0 Recognize Aries applications in Geronimo Key: GERONIMO-4971 URL: https://issues.apache.org/jira/browse/GERONIMO-4971 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: osgi Affects Versions: 3.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4973) Classpath entrys in karaf-client.jar is ../system/ instead of ../repository/
[ https://issues.apache.org/jira/browse/GERONIMO-4973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4973: --- Fix Version/s: 3.0 Classpath entrys in karaf-client.jar is ../system/ instead of ../repository/ - Key: GERONIMO-4973 URL: https://issues.apache.org/jira/browse/GERONIMO-4973 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: osgi Affects Versions: 3.0 Reporter: Shawn Jiang Assignee: Shawn Jiang Fix For: 3.0 Classpath entrys in karaf-client.jar is ../system/ instead of ../repository/ so that it does not work in geronimo. We need to repackage it with the correct classpath. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5034) Integrate JMX (RFC 142) implementation from Apache Aries
[ https://issues.apache.org/jira/browse/GERONIMO-5034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-5034: --- Fix Version/s: 3.0 Integrate JMX (RFC 142) implementation from Apache Aries Key: GERONIMO-5034 URL: https://issues.apache.org/jira/browse/GERONIMO-5034 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: osgi Affects Versions: 3.0 Reporter: Jarek Gawor Fix For: 3.0 Integrate JMX (RFC 142) implementation from Apache Aries into Geronimo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5030) Implement web container extender (RFC 66)
[ https://issues.apache.org/jira/browse/GERONIMO-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-5030: --- Fix Version/s: 3.0 Implement web container extender (RFC 66) - Key: GERONIMO-5030 URL: https://issues.apache.org/jira/browse/GERONIMO-5030 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: osgi Affects Versions: 3.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5026) Class and resource discovery in OSGi
[ https://issues.apache.org/jira/browse/GERONIMO-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-5026: --- Fix Version/s: 3.0 Class and resource discovery in OSGi Key: GERONIMO-5026 URL: https://issues.apache.org/jira/browse/GERONIMO-5026 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: osgi Affects Versions: 3.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0 For servlets 3.0, EJBs, and web services we need a way to find all classes loadable by the bundle so that we can discover additional servlets, ejbs or web services dynamically (by checking annotations) that are not explicitly referenced in the given deployment descriptor. For resources, we might need a way to discover all resources with a given extension and prefix. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4938) Move geronimo-schema-j2ee and geronimo-schema-jee_5
[ https://issues.apache.org/jira/browse/GERONIMO-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4938: --- Affects Version/s: 3.0 Move geronimo-schema-j2ee and geronimo-schema-jee_5 --- Key: GERONIMO-4938 URL: https://issues.apache.org/jira/browse/GERONIMO-4938 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Affects Versions: 3.0 Reporter: Kevan Miller Fix For: 3.0 With the properly CDDL licensed xsd/dtd's. We should move the xmlbean schema svn into geronimo/components or geronimo/schema... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Tracking Geronimo 3.0 work.
I've been trying to map the existing Jiras against the tentative Geronomo 3.0 roadmap we have and with the existing set of Jiras we have, it's proved to be fairly difficult to get a clear picture of where we are, what work still needs to be done, and who's actually working on what items. The OpenEJB project has done an excellent job of setting up Jiras using major issues for specific enhancement areas and subtask issues for individual pieces of work necessary to complete the task. A simple wiki script makes it easy to get a good picture of the work progress and the Jiras allow them to see who's working on what task. Here's the web page with the consolidated information: http://openejb.apache.org/ejb-31-roadmap.html I'd like to start doing something similar for the Geronimo 3.0 release. A good starting point would be to have a major Jira issue for each of the Java EE 6 items that need to be updated. In other words, for each spec item identified here: http://cwiki.apache.org/confluence/display/GMOxDEV/Road+map+for+Java+EE6+Web+Profile there would be a major Jira issue plus additional subtasks that would be required to implement the item. For example, the Servlet 3.0 task might have the initial set of of Jiras: Add Servlet 3.0 support Implement servlet 3.0 spec jar Upgrade geronimo to use servlet 3.0 spec jar Upgrade tomcat plugin to Tomcat 7 Upgrade jetty plugin to Jetty 8 etc. Additional subtasks can be added as additional work items are identified. This table on the roadmap page gives a nice starting set of major tasks, but there are obviously other major tasks related to the OSGi work. These can be handled in a similar way, but I suspect we should gather an initial starting set here in the dev list so they can be coordinated a little and the tracking page can be set up accordingly. Does this sound like a reasonable plan? I'll volunteer to open the initial set of Jiras and try to migrate the existing Jiras to subtasks of the major categories if we have a consensus here. Rick
Re: Tracking Geronimo 3.0 work.
On 1/29/2010 1:26 PM, David Jencks wrote: Any work you are willing to do along these lines would be great! I wish we'd added an ee6 category a long time ago so we could have associated all the work already done with it. It may be difficult to find all the existing closed jiras that relate to already-implemented ee6 features. Do you think its appropriate to create new jiras for work that has been done without benefit of a jira? The related commits won't have the jira number in the commit message unless you go back and edit the commit message. I personally don't think there is much to be gained for this, I would only create jiras for work that has not yet been done. So for your example of servlet 3.0... we've already done the steps you list :-) Just from the standpoint of being able to keep track of things, it would be nice to have Jiras to keep track of items that are already completed. In the case of OpenEJB, it sounded like they dealt with the situation by linking the tracking Jira to ones that implemented the actual work. I ran into this a lot while trying to put together the wiki page on the jee6 work. Just trying to keep straight all of the individual specs jars was an interesting exercise. It would be nice to use the same mechanism to keep track of all of these, even if it means having Jiras that don't have commits necessarily associated with them. thanks david jencks On Jan 29, 2010, at 7:24 AM, Rick McGuire wrote: I've been trying to map the existing Jiras against the tentative Geronomo 3.0 roadmap we have and with the existing set of Jiras we have, it's proved to be fairly difficult to get a clear picture of where we are, what work still needs to be done, and who's actually working on what items. The OpenEJB project has done an excellent job of setting up Jiras using major issues for specific enhancement areas and subtask issues for individual pieces of work necessary to complete the task. A simple wiki script makes it easy to get a good picture of the work progress and the Jiras allow them to see who's working on what task. Here's the web page with the consolidated information: http://openejb.apache.org/ejb-31-roadmap.html I'd like to start doing something similar for the Geronimo 3.0 release. A good starting point would be to have a major Jira issue for each of the Java EE 6 items that need to be updated. In other words, for each spec item identified here: http://cwiki.apache.org/confluence/display/GMOxDEV/Road+map+for+Java+EE6+Web+Profile there would be a major Jira issue plus additional subtasks that would be required to implement the item. For example, the Servlet 3.0 task might have the initial set of of Jiras: Add Servlet 3.0 support Implement servlet 3.0 spec jar Upgrade geronimo to use servlet 3.0 spec jar Upgrade tomcat plugin to Tomcat 7 Upgrade jetty plugin to Jetty 8 etc. Additional subtasks can be added as additional work items are identified. This table on the roadmap page gives a nice starting set of major tasks, but there are obviously other major tasks related to the OSGi work. These can be handled in a similar way, but I suspect we should gather an initial starting set here in the dev list so they can be coordinated a little and the tracking page can be set up accordingly. Does this sound like a reasonable plan? I'll volunteer to open the initial set of Jiras and try to migrate the existing Jiras to subtasks of the major categories if we have a consensus here. Rick
Re: [VOTE] Release geronimo-validation_1.0_spec-1.0
+1 On 1/25/2010 12:52 PM, Donald Woods wrote: Hi, I'd like to release v1.0 of the Bean Validation Spec API, now that we have it passing the Bean Validation 1.0 TCK signature tests. Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-065/ The svn location is here: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-validation_1.0_spec-1.0/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Donald
[jira] Resolved: (GERONIMO-5023) jaxws spec jar has wrong version number for its package exports.
[ https://issues.apache.org/jira/browse/GERONIMO-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire resolved GERONIMO-5023. Resolution: Fixed Assignee: Rick McGuire Committed revision 903751. New geronimo-jaxws_2.1.2_spec project created. jaxws spec jar has wrong version number for its package exports. -- Key: GERONIMO-5023 URL: https://issues.apache.org/jira/browse/GERONIMO-5023 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: Rick McGuire Assignee: Rick McGuire Priority: Critical The current version of the geronimo-jaxws_2.1_spec jar implements the 2.1.1 version of the APIs but the package exports are for the 2.1 release. This is causing a problems for OSGi projects that wish to use this API (e.g., the OSGi RFC 66 reference implementation). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: rfc66 update
On 1/25/2010 8:06 AM, Delos wrote: It's really great news! But I have some questions about current implementation.Just want to learn more from it. 1) I found only active and starting bundles are taken into account in current implementation. What about resolved bundles? That's the requirement of the RFC66 specification. Resolution is a requirement for a bundle to transition to the active or starting states, but the extender is not supposed to take action until one of those states is seen. It's the same way with Blueprint. 2) For lazy activiated bundles, only starting bundles will be deployed.But in RFC 66, it said A bundle that has a lazy activation policy should not be transitioned to the STARTING state by the web extender unless a request is made that requires a class to be loaded. Does the implementation violate the document? This is a statement that the extender should not explicitly force the bundle into a started state, but rather should leave that transition to one triggered by a class load. If the processing the extender needs to perform in processing the bundle results in a triggering class load, that's ok. 3) In RFC 66, static content can be requested without starting a WAB. It's not in the TODO file. Do you have any idea for it? I'm not sure if configuration of WAB can become accessible before actually it's started. The note about static content is marked as an optional feature. For a lot of processing, it would not be possible to achieve deployment without performing a classload. Thanks! 2010/1/24 David Jencks david_jen...@yahoo.com mailto:david_jen...@yahoo.com great news! congratulations! david jencks On Jan 23, 2010, at 6:55 PM, Jarek Gawor wrote: Hi all, Today I checked in an initial version of the rfc66 extender that can actually deploy WABs with simple servlets and jsps. There is still much work to be done (for example updating the Jasper module builder to work with Bundles) but simple stuff seems to be working. In fact with David's recent JNDI (rfc142) integration work I was able to deploy the Aries blog sample in Geronimo. Here are the steps I took to run the sample: 1) Build latest blog sample in Aries 2) Build latest Geronimo trunk 3) cd plugins/wab/web-tomcat-server/target/assembly (or web-jetty-server if you prefer) 4) Create database for blog sample using blogDB.sql from blog sample: java -cp repository/org/apache/geronimo/bundles/derby-all/10.4.2.0-SNAPSHOT/derby-all-10.4.2.0-SNAPSHOT.jar org.apache.derby.tools.ij aries/samples/blog-sample/blog-assembly/target/blogDB.sql 5) Move created blogDB directory to plugins/wab/web-tomcat-server/target/assembly/var/derby 6) Start server: ./bin/geronimo -l 7) Install and start all the blog sample bundles (blog-api-1.0.0.jar, blog-persistence-1.0.0.jar, blog-1.0.0.jar, blog-servlet-1.0.0.jar) using the karaf console. 8) Once you start the blog-servlet-1.0.0.jar bundle, the WAB will be deployed and you should be able to access http://localhost:8080/blog. And if everything is running right you should be able to add new blog entries, etc. Enjoy, Jarek -- Best Regards, Delos
How to handle the Web Profile subset
We should be putting some thought on what the Geronimo deliverables are in the web profile world. I think for the most part, this should be just a different assembly that assembles a smaller set of components. The one additional configuration that is probably going to be needed is an EJB Lite configuration that would be used by the Web Profile assembly. This should not be a big delta over what we have, but it does increase the number of assemblies that we end up releasing. Are there other options we should be working at? Rick
[jira] Created: (GERONIMO-5047) Create javaee5 Tomcat assemblies and plugin groups.
Create javaee5 Tomcat assemblies and plugin groups. Key: GERONIMO-5047 URL: https://issues.apache.org/jira/browse/GERONIMO-5047 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: Tomcat Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 javaee6 versions of the assemblies and plugin groups have been created for jetty in trunk, but the similar changes have not been made for Tomcat. I suspect this ends up just being a series of renames, since we're already building with Tomcat 7 versions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5048) Create an EJB Lite plugin for 3.0 Web Profile usage.
Create an EJB Lite plugin for 3.0 Web Profile usage. - Key: GERONIMO-5048 URL: https://issues.apache.org/jira/browse/GERONIMO-5048 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 Currently, the Geronimo OpenEJB plugin is an all or nothing configuration that brings in all of OpenEJB. There should also be a plugin that only pulls in the features required for the Java EE6 web profile. It might also be nice if additional EJB features could be added to the profile via custom assemblies, but that might require a larger refactoring of the openejb plugin. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-5018) Remove -EA- versioning from the JEE6 spec versions.
[ https://issues.apache.org/jira/browse/GERONIMO-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire resolved GERONIMO-5018. Resolution: Fixed Remove -EA- versioning from the JEE6 spec versions. Key: GERONIMO-5018 URL: https://issues.apache.org/jira/browse/GERONIMO-5018 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: specs Affects Versions: 3.0 Reporter: Rick McGuire Assignee: Rick McGuire Fix For: 3.0 Now that the JEE6 specs have gone final, the -EA- version identifiers used in the early spec versions should be removed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5049) Add bean validation (JSR 302) to Geronimo 3.0
Add bean validation (JSR 302) to Geronimo 3.0 - Key: GERONIMO-5049 URL: https://issues.apache.org/jira/browse/GERONIMO-5049 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5050) Integrate OpenWebBeans into Geronimo 3.0.
Integrate OpenWebBeans into Geronimo 3.0. -- Key: GERONIMO-5050 URL: https://issues.apache.org/jira/browse/GERONIMO-5050 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 A JSR 299 and 330 implementation is required for Java EE6 and the Java EE 6 web profile. OpenWebBeans is the most feasible candidate for providing these features. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
OpenJPA2 build breakage in trunk
There's a nasty build breakage in trunk caused by switching to the latest jpa 2.0 spec jar from the one used for the OpenJPA milestone release. This change requires some code changes to the Geronimo code because some methods were removed and some classes were moved to different package locations. I've got the code compiling cleanly with the new spec jar, but that just moved things on to another problem. The next problem to arise came from the mismatch between the OpenJPA 2.0.0-M3 release and this spec jar. The M3 OpenJPA code still had references to classes in the old package locations, so we ended up with ClassNotFoundExceptions while trying to build. Ok, this should be a simple fix...it just requires changing the OpenJPA version to the 2.0.0-SNAPSHOT level. And here is where things start to get nasty. The current trunk code for OpenJPA no longer builds the OpenJPA jars as bundles. This issue was already noticed by the Aries folks and a Jira was opened on it: https://issues.apache.org/jira/browse/OPENJPA-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel Donald fixed this today, but it does not appear that he's pushed new snapshots to the repo yet, so I haven't been able to test against the new jars. I did make an attempt at creating a geronimo bundle from these jars, but ran into some resource loading issues between the openjpa jar and the openjpa-persistence-jdbc jars that I was never able to work out. I tried building openjpa locally, but ran into a couple of dependency issues I haven't had the chance to chase down. So, the build is sort of broken in its current state. The Geronimo code won't compile against the current spec jar without changes and the openjpa2 plugin can't build with the current openjpa snapshot because of the missing bundle information. Should I 1) back off the spec change 2) check in the changes to fix the compile errors and use the new openjpa snapshot and wait for the new snapshot of openjpa to show up Rick
Re: OpenJPA2 build breakage in trunk
On 1/22/2010 2:11 PM, David Jencks wrote: Judging from some activity on the openjpa mailing list I think donald would be available to push some snapshots later today so I'd suggest waiting an hour or two to see if (2) is possible. If that doesn't work out then (1) would be better. Is there a rev # or two that people could revert locally to get a buildable trunck? It looks like the problem was introduced with rev 902033, which made a number of changes besides the one causing the problem. Rick thanks david jencks On Jan 22, 2010, at 10:14 AM, Rick McGuire wrote: There's a nasty build breakage in trunk caused by switching to the latest jpa 2.0 spec jar from the one used for the OpenJPA milestone release. This change requires some code changes to the Geronimo code because some methods were removed and some classes were moved to different package locations. I've got the code compiling cleanly with the new spec jar, but that just moved things on to another problem. The next problem to arise came from the mismatch between the OpenJPA 2.0.0-M3 release and this spec jar. The M3 OpenJPA code still had references to classes in the old package locations, so we ended up with ClassNotFoundExceptions while trying to build. Ok, this should be a simple fix...it just requires changing the OpenJPA version to the 2.0.0-SNAPSHOT level. And here is where things start to get nasty. The current trunk code for OpenJPA no longer builds the OpenJPA jars as bundles. This issue was already noticed by the Aries folks and a Jira was opened on it: https://issues.apache.org/jira/browse/OPENJPA-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel Donald fixed this today, but it does not appear that he's pushed new snapshots to the repo yet, so I haven't been able to test against the new jars. I did make an attempt at creating a geronimo bundle from these jars, but ran into some resource loading issues between the openjpa jar and the openjpa-persistence-jdbc jars that I was never able to work out. I tried building openjpa locally, but ran into a couple of dependency issues I haven't had the chance to chase down. So, the build is sort of broken in its current state. The Geronimo code won't compile against the current spec jar without changes and the openjpa2 plugin can't build with the current openjpa snapshot because of the missing bundle information. Should I 1) back off the spec change 2) check in the changes to fix the compile errors and use the new openjpa snapshot and wait for the new snapshot of openjpa to show up Rick
Re: rfc66 fun
On 1/20/2010 2:38 PM, Jarek Gawor wrote: Hey, For last few days I've been looking into getting the rfc66 extender going in Geronimo but I ran into a problem. As previously mentioned on this list, the idea for the extender was to call the Tomcat/Jetty ModuleBuilders with a bundle as an input and once the deployment process was done start the generated configuration. All without creating any additional temporary or permanent bundles. Because we don't have a single classloader that can load all the gbeans within the configuration, David Jencks added a special classSource attribute to GBeanData which can be used to figure out the right Bundle to load the gbean class. Now, since we use Java serialization to save and load gbeans, we actually need to set the right classloader when we deserialize the gbean. That is, during deserialization as soon as we read the classSource we need to lookup and set the right classloader and then read the rest of the gbean data. This should (and seems to) work when all the attributes of the gbean are accessible from the same classloader. But what about if the gbean has some attribute with some values from different classloaders? For example, the Map object we build for jndi context can contain objects from different classloaders. I'm not exactly sure what to do about it. Although maybe having a custom ObjectOutputStream with annotateClass() method that saves classSource type of info for each unique class might work. Ideas? Also, I'm dealing with lots of classloader issues since there is no single classloader that load all the gbean classes and module classes. A lot of Geronimo and other code assumes a single classloader and resolving these problems is time consuming and not very fun (although probably good in long term). So I'm wondering if we can still somehow assemble a single classloader in the extender. For example, the http://www.osgi.org/blog/2008/08/classy-solutions-to-tricky-proxies.html post shows a classloader that delegates a number of different bundles. Maybe we could use that in Geronimo especially since we can figure out the bundles needed from the configuration environment information. There have been a number of situations while during the conversion that I've suspected we were going to need a classloader that could delegate to more than one bundle instance as we developed more complex dependency situations. I suspect it's finally time to bit that particular bullet. Rick Thoughts? Jarek
Re: Errors when building JAXWS :: EJB Deployer
On 1/19/2010 2:20 AM, Ivan wrote: Hi, Rex Some suggestions for your information 1. Always add clean option while compiling the plugins, there is some problems if the Felix cache folder exists. 2. Add -X to find the reason why those bundles contained unresolved packages are not started. using dependencies:tree in the failing project can also give some clues as to whether the dependencies have been properly set up. Rick 2010/1/19 Rex Wang rwo...@gmail.com mailto:rwo...@gmail.com could anyone give me any tips? Thanks! ... ... [INFO] Packaging module configuration: D:\_g\trunk\plugins\jaxws\jaxws-ejb-deployer\target\work\plan.xml ERROR: Error creating archive. (java.io.FileNotFoundException: D:\_g\trunk\plugins\jaxws\jaxws-ejb-deployer\target\bundle-cache\bundle130\version0.-1\revision.location (???)) ERROR: Error creating archive. (java.io.FileNotFoundException: D:\_g\trunk\plugins\jaxws\jaxws-ejb-deployer\target\bundle-cache\bundle131\version0.-1\revision.location (???)) ERROR: Error creating archive. (java.io.IOException: Referenced file does not exist: D:\_g\trunk\plugins\jaxws\jaxws-ejb-deployer\target\repository\org\apache\geronimo\configs\jaxws-ejb-deployer\3.0-SNAPSHOT\jaxws-ejb-deployer-3.0-SNAPSHOT.car) ERROR: Error creating archive. (java.io.FileNotFoundException: D:\_g\trunk\plugins\jaxws\jaxws-ejb-deployer\target\bundle-cache\bundle52\version0.-1\revision.location (???)) [org.apache.geronimo.system.configuration.DependencyManager] : found geronimo-plugin.xml for bundle org.apache.geronimo.framework.geronimo-gbean-deployer [1] ... ... [FelixDispatchQueue] DEBUG org.apache.geronimo.configs.jaxws-deployer - BundleEvent STARTED [org.apache.geronimo.system.configuration.DependencyManager] : Could not start bundle: org.apache.geronimo.configs.openejb-deployer [90] org.osgi.framework.BundleException: Unresolved constraint in bundle org.apache.geronimo.modules.geronimo-openejb [113]: package; (package=org.apache.geronimo.persistence) at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3291) at org.apache.felix.framework.Felix.startBundle(Felix.java:1653) at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:890) at org.apache.geronimo.system.configuration.DependencyManager.starting(DependencyManager.java:163) at org.apache.geronimo.system.configuration.DependencyManager.bundleChanged(DependencyManager.java:78) at org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:800) at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:728) at org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:610) at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:3604) at org.apache.felix.framework.Felix.activateBundle(Felix.java:1746) at org.apache.felix.framework.Felix.startBundle(Felix.java:1678) at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:890) at org.apache.geronimo.deployment.DeploymentContext.createTempConfiguration(DeploymentContext.java:213) at org.apache.geronimo.deployment.DeploymentContext.initializeConfiguration(DeploymentContext.java:177) at org.apache.geronimo.deployment.service.ServiceConfigBuilder.buildConfiguration(ServiceConfigBuilder.java:251) at org.apache.geronimo.deployment.service.ServiceConfigBuilder.buildConfiguration(ServiceConfigBuilder.java:211) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:250) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:856) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.mavenplugins.car.PackageMojo.invokeDeployer(PackageMojo.java:519) at org.apache.geronimo.mavenplugins.car.PackageMojo.buildPackage(PackageMojo.java:337) at org.apache.geronimo.mavenplugins.car.PackageMojo.execute(PackageMojo.java:234) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at
Re: Implementing rfc66 in Geronimo
Rex Wang wrote: 2010/1/14 Jarek Gawor jga...@gmail.com mailto:jga...@gmail.com Hey all, I've been looking into implementing rfc66 support in Geronimo a little bit more. Here are some things that we need to do and my thoughts/impressions about them: 1. WAR to WAB converter. Installs webbundle: url handler that converts standard WAR files into Web Application Bundles (WAB). The converter code was contributed by IBM to Apache Aries but so far it has not been moved to trunk yet. This code will probably need some updates but I think we could just mostly use it as it is in Geronimo. 2. WAB extender. Watches for WABs to be started in the framework and performs the necessary steps to deploy the applications. a. In Geronimo we will need a custom extender that effectively invokes Tomcat/JettyWebModuleBuilders to deploy the application. There might be an extender implementation donated to Aries at some point but I don't think we will be able to use since it most likely will use the Tomcat or Jetty API directly to deploy the application. In Geronimo we build the GBeans which then use Tomcat/Jetty API to set everything up. b. The biggest issue that I see with Geronimo WAB extender is updating the WebModuleBuilders (or actually the whole deployment process) to work with Bundle objects. Right now the deployment process for the most part assumes it is working with JarFiles. So, what is the standard method to install/deploy a WAB into Geronimo 3.0? From the osgi perspective, that should be the same with installing a normal bundle to framework, and then the extender will track this and help deploy it to geronimo by instantiating some gbeans. Should we support the geronimo deployment process such as deploy a WAB with a external plan? One key point with WABs is to remember that a WAB is an OSGi programming construct and even though it is running under Geronimo, it should function under OSGi rules. One key point here is any application may install and start a WAB bundle using a BundleContext without ever knowing anything about the hosting Geronimo server. That's the key purpose of the extender...it processes any bundle that has the manifest entries that identify this as a WAB and take the steps necessary to deploy this. The bundle in question might not have gone through the Geronimo deployment process first. c. Rick has some initial extender code in the sandbox that we should be able to reuse (or at least parts of it) in Geronimo. d. Things to keep in mind: 1. The specification talks about support for lazy bundles. More specifically, that a request on static resource of a lazy activated bundle should not cause the bundle to become fully activated. This might be tricky to implement in Geronimo and would require changes to existing code. However, support for lazy bundles seems to be optional in the specification. 2. The specification says that “it should be possible for a Web application bundle to remain installed when its Web Container is dynamically replaced”. Which I think it means what happens if somebody deploys WAB, then stops Tomcat container and starts Jetty container all at runtime. Does the application continue to work? Should Geronimo support this case? It is an optional feature. Does that indicate each WAB will contain several plans for different containers? That might require a way to distinguish the plans. 3. The extender might need to track somehow which WABs were already deployed to prevent double start problems. Once some WAB is deployed and the Geronimo server is restarted, Geronimo will attempt to start the generated configuration/plugin for the WAB. Starting of the plugin will also start the actual WAB and then the extender will see the starting bundle and attempt to deploy the WAB again. Yes, I think the other RFC66 implementation also need to take care of it. Thanks -Rex 3. Annotation and resource discovery. a. The specification does not describe an exact way of discovering annotations or resources in a WAB. For example, if WAB imports some package from another bundle, are all classes in that package scanned for annotations? What about resources in META-INF directory? Are the bundles wired to the WAB checked for META-INF resources? These are some unanswered questions that we need to keep track of. b. In certain cases (e.g. servlets 3.0, EJBs, etc.) we will need to discover all accessible classes in bundle class space that have a given annotation. For that we will need annotation discovery code that might need to know how to scan bundles based on Bundle-Classpath and possibly on Import-Packages, DynamicImport-Package, Require-Bundle, etc. depending on what the specification will say. The annotation scanning code might get even more
Re: [VOTE] Release geronimo-jpa_2.0_spec-1.0 (2nd try)
+1 Donald Woods wrote: Hi, I'd like to release v1.0 of the JPA 2.0 Spec API, now that we have OpenJPA trunk and our API passing the JPA2 TCK. Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-036/ The svn location is here: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jpa_2.0_spec-1.0/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Donald
[jira] Created: (GERONIMO-5023) jaxws spec jar has wrong version number for its package exports.
jaxws spec jar has wrong version number for its package exports. -- Key: GERONIMO-5023 URL: https://issues.apache.org/jira/browse/GERONIMO-5023 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Reporter: Rick McGuire Priority: Critical The current version of the geronimo-jaxws_2.1_spec jar implements the 2.1.1 version of the APIs but the package exports are for the 2.1 release. This is causing a problems for OSGi projects that wish to use this API (e.g., the OSGi RFC 66 reference implementation). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5023) jaxws spec jar has wrong version number for its package exports.
[ https://issues.apache.org/jira/browse/GERONIMO-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12799165#action_12799165 ] Rick McGuire commented on GERONIMO-5023: I have a few questions on how this should be fixed. The current released version of this spec jar is geronimo-jaxws_2.1_spec-1.0. This actually implements the 2.1.1 version of the jaxws spec, but the OSGi manifest is incorrect. Fixing the manifest is easy, but should this new version be released as geronimo-jaxws_2.1_spec-1.1 or geronimo-jaxws_2.1.1_spec-1.0? I suspect this really should be the latter to more clearly identify what level of the spec is contained in the jar. jaxws spec jar has wrong version number for its package exports. -- Key: GERONIMO-5023 URL: https://issues.apache.org/jira/browse/GERONIMO-5023 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: Rick McGuire Priority: Critical The current version of the geronimo-jaxws_2.1_spec jar implements the 2.1.1 version of the APIs but the package exports are for the 2.1 release. This is causing a problems for OSGi projects that wish to use this API (e.g., the OSGi RFC 66 reference implementation). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5023) jaxws spec jar has wrong version number for its package exports.
[ https://issues.apache.org/jira/browse/GERONIMO-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12799196#action_12799196 ] Rick McGuire commented on GERONIMO-5023: There already is a geronimo-jaxws-2.2_spec branch in trunk for Java EE 6. This Jira issue is intended to fix a problem with the currently released 2.1 version. jaxws spec jar has wrong version number for its package exports. -- Key: GERONIMO-5023 URL: https://issues.apache.org/jira/browse/GERONIMO-5023 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: Rick McGuire Priority: Critical The current version of the geronimo-jaxws_2.1_spec jar implements the 2.1.1 version of the APIs but the package exports are for the 2.1 release. This is causing a problems for OSGi projects that wish to use this API (e.g., the OSGi RFC 66 reference implementation). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5023) jaxws spec jar has wrong version number for its package exports.
[ https://issues.apache.org/jira/browse/GERONIMO-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12799204#action_12799204 ] Rick McGuire commented on GERONIMO-5023: The OSGi Alliance wishes to use the Geronimo spec jars for the RFC 66 reference implementation, but they are running into a constrain violation because the Geronimo version is exporting the wrong version of the packages. This Jira is just to correct this problem and get a new version of the spec jar released for their benefit. jaxws spec jar has wrong version number for its package exports. -- Key: GERONIMO-5023 URL: https://issues.apache.org/jira/browse/GERONIMO-5023 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: Rick McGuire Priority: Critical The current version of the geronimo-jaxws_2.1_spec jar implements the 2.1.1 version of the APIs but the package exports are for the 2.1 release. This is causing a problems for OSGi projects that wish to use this API (e.g., the OSGi RFC 66 reference implementation). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5022) Sending mails fail with german umlauts (ä, ö, ü, ß ) in description (not in emailaddress itse lf) e.g. Müste Mö yourmai...@mail.com
[ https://issues.apache.org/jira/browse/GERONIMO-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12799244#action_12799244 ] Rick McGuire commented on GERONIMO-5022: According to the RFC822 specification, the part before the in an internet address is defined as a phrase. A phrase is defined as a sequence of one or more words, and a word is defined as being an ATOM or a Quoted String. Since the characters allowed in an ATOM are restriced to being in the range 0-127 decimal (0--0xff) minus the special characters. Thus, according to the RFC822 syntax rules, this is an invalid address. Making the personal part into a quoted string should fix the problem. Sending mails fail with german umlauts (ä, ö, ü, ß) in description (not in emailaddress itself) e.g. Müste Mö yourmai...@mail.com -- Key: GERONIMO-5022 URL: https://issues.apache.org/jira/browse/GERONIMO-5022 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: mail Affects Versions: 2.1.4 Environment: Windows XP IBM SDK 1.6 SR5 Reporter: Ashok Poralu Sending mails fail with german umlauts (ä, ö, ü, ß) in description (not in emailaddress itself) e.g. Müste Mö yourmai...@mail.com. Sending mails without german umlauts (ä, ö, ü, ß) works, e. g, Muste Mo yourmai...@mail.com. Below the exception --- 2010-01-12 15:24:12,156 ERROR [[jsp]] Servlet.service() for servlet jsp threw exception javax.mail.internet.AddressException: Illegal character in address (Maxü Müstermann mm730...@gmail.com,3) at javax.mail.internet.AddressParser.syntaxError(AddressParser.java:1114) at javax.mail.internet.AddressParser.tokenizeAddress(AddressParser.java:735) at javax.mail.internet.AddressParser.parseAddress(AddressParser.java:113) at javax.mail.internet.InternetAddress.init(InternetAddress.java:78) at javax.mail.internet.InternetAddress.init(InternetAddress.java:69) at org.apache.jsp.index_jsp._jspService(index_jsp.java:100) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:406) at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:568) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:735) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: What is correct version for EL 2.2
Ivan wrote: From the final Java EE 6 spec, it indicates that both JSP and EL is of version 2.2. So I would suggest to rename JSP 2.1-MR2 to 2.2, and use 2.2 for the new EL package version. Any comment ? To further confuse things, the latest JSP spec is named jsp-2_2-mrel-spec.pdf and says inside both Version 2.2 and Maintenace[SIC} Release 2, while the EL spec is expression_language-2_2-mrel-spec.pdf and the internal title is Version 2.2 Maintenance Release. The EL spec also contains the subtitle A component of the JavaServer Pages Specification Version 2.2. They've not been terribly consistent with the usage, but I think 2.2 is probably the correct naming. Rick 2010/1/11 Ivan xhh...@gmail.com mailto:xhh...@gmail.com By the way, I found that last version of EL is 1.0, it does not keep consistent with JSP version. 2010/1/11 Ivan xhh...@gmail.com mailto:xhh...@gmail.com Hi, While compiling the latest Tomcat 7, I got some errors with our el spec 1.0. It seems that we need to create a new EL package, currently, the EL is distributed within the JSP spec, so what is the proper version for it, 2.2 or 2.1-MR2 ? Thanks ! -- Ivan -- Ivan -- Ivan
