[jira] Created: (GERONIMO-2043) remove context-priority-classloader element, provide separate artifact and dependency elements
remove context-priority-classloader element, provide separate artifact and dependency elements -- Key: GERONIMO-2043 URL: http://issues.apache.org/jira/browse/GERONIMO-2043 Project: Geronimo Type: Bug Security: public (Regular issues) Components: deployment Versions: 1.1 Reporter: David Jencks Assigned to: David Jencks Fix For: 1.1 The context-priority-classloader flag in web plans is redundant and/or contradicts the inverse-classloading element in environment and should be removed. We need separate artifact and dependency elements in the environment element so you can't give a moduleId an import element, which doesn't make sense. As a side note, the securty-builder module needs an xmlbeans dependency on j2ee-schema to pull in xml.xsd which is used in a description element. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1784) SQL Login Modules logs null instead of the driver name
[ http://issues.apache.org/jira/browse/GERONIMO-1784?page=all ] David Jencks closed GERONIMO-1784: -- Fix Version: (was: 1.2) Resolution: Fixed Assign To: David Jencks Fixed in rev 407961 SQL Login Modules logs null instead of the driver name Key: GERONIMO-1784 URL: http://issues.apache.org/jira/browse/GERONIMO-1784 Project: Geronimo Type: Bug Security: public(Regular issues) Components: security Versions: 1.0, 1.2, 1.1 Reporter: Vamsavardhana Reddy Assignee: David Jencks Priority: Minor Fix For: 1.1 SQLLoginModule.java has the following line: throw new IllegalArgumentException(Driver class + driver + is not available. Perhaps you need to add it as a dependency in your deployment plan?) Change to throw new IllegalArgumentException(Driver class + options.get(DRIVER)+ is not available. Perhaps you need to add it as a dependency in your deployment plan?); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-2043) remove context-priority-classloader element, provide separate artifact and dependency elements
[ http://issues.apache.org/jira/browse/GERONIMO-2043?page=all ] David Jencks closed GERONIMO-2043: -- Resolution: Fixed Fixed in rev 407962. Also made the upgrader remove context-priority-classloader elements and put in a comment if you need to set the inverse-classloading element. It might be possible to make the upgrader add the inverse-classloading element but it would be a bit complicated. remove context-priority-classloader element, provide separate artifact and dependency elements -- Key: GERONIMO-2043 URL: http://issues.apache.org/jira/browse/GERONIMO-2043 Project: Geronimo Type: Bug Security: public(Regular issues) Components: deployment Versions: 1.1 Reporter: David Jencks Assignee: David Jencks Fix For: 1.1 The context-priority-classloader flag in web plans is redundant and/or contradicts the inverse-classloading element in environment and should be removed. We need separate artifact and dependency elements in the environment element so you can't give a moduleId an import element, which doesn't make sense. As a side note, the securty-builder module needs an xmlbeans dependency on j2ee-schema to pull in xml.xsd which is used in a description element. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1196) Keystore portlet: Viewing trusted certificate results in an error
[ http://issues.apache.org/jira/browse/GERONIMO-1196?page=comments#action_12412628 ] David Jencks commented on GERONIMO-1196: I couldn't get the portlet called keystore to work: it wouldn't create a new keystore for me. The old keystore portlet would not let me create a key pair with blank alias or validity, but did let me create a key pair with alias = (a single space). Keystore portlet: Viewing trusted certificate results in an error - Key: GERONIMO-1196 URL: http://issues.apache.org/jira/browse/GERONIMO-1196 Project: Geronimo Type: Bug Security: public(Regular issues) Components: console Versions: 1.0, 1.0-M5 Environment: Win XP, Sun JDK 1.4.2_08 Reporter: Vamsavardhana Reddy Assignee: Aaron Mulder Priority: Critical Fix For: 1.1 Attachments: GERONIMO-1196-2.patch, GERONIMO-1196.patch Viewing a trusted certificate results in an error. The following exception is logged to geronimo.log 12:04:01,806 ERROR [PortletInvokerImpl] PortletInvokerImpl.render() - Error while dispatching portlet. javax.portlet.PortletException at org.apache.geronimo.console.certmanager.actions.ViewKeyStoreEntryDetail.render(ViewKeyStoreEntryDetail.java:69) at org.apache.geronimo.console.certmanager.CertManagerPortlet.doView(CertManagerPortlet.java:134) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:250) ... Caused by: java.lang.NullPointerException at sun.security.provider.JavaKeyStore$JKS.convertAlias(JavaKeyStore.java:40) at sun.security.provider.JavaKeyStore.engineIsCertificateEntry(JavaKeyStore.java:409) at java.security.KeyStore.isCertificateEntry(KeyStore.java:567) at org.apache.geronimo.console.core.keystore.KeyStoreGBean.getKeyEntryInfo(KeyStoreGBean.java:179) ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1846) geronimo-config-1.1.xsd needs to be changed - import element is not valid as a child of the configId element in a plan
[ http://issues.apache.org/jira/browse/GERONIMO-1846?page=all ] John Sisson closed GERONIMO-1846: - Resolution: Duplicate Assign To: John Sisson Fixed as part of djencks changes in http://svn.apache.org/viewvc?rev=407962view=rev geronimo-config-1.1.xsd needs to be changed - import element is not valid as a child of the configId element in a plan -- Key: GERONIMO-1846 URL: http://issues.apache.org/jira/browse/GERONIMO-1846 Project: Geronimo Type: Bug Security: public(Regular issues) Components: deployment, kernel Versions: 1.1 Reporter: John Sisson Assignee: John Sisson Fix For: 1.1 In the geronimo-config-1.1.xsd schema the configId has a type of sys:artifactType. The last element in sys:artifactType is the import element, but the import element is not used when specifying a configId, it is only used when specifying dependencies. The import element should be moved out of the type sys:artifact type. Do we need to introduce a dependencyArtifactType type that has the import element? Here is what the schema currently looks like: xs:complexType name=environmentType xs:sequence xs:element name=configId type=sys:artifactType minOccurs=0/ xs:element name=dependencies type=sys:dependenciesType minOccurs=0/ xs:element name=hidden-classes type=sys:classFilterType minOccurs=0/ xs:element name=non-overridable-classes type=sys:classFilterType minOccurs=0/ xs:element name=inverse-classloading type=sys:emptyType minOccurs=0/ xs:element name=suppress-default-environment type=sys:emptyType minOccurs=0/ /xs:sequence /xs:complexType xs:complexType name=artifactType xs:sequence !-- TODO not sure if groupId can in fact be optional -- xs:element name=groupId type=xs:string minOccurs=0/ xs:element name=artifactId type=xs:string/ xs:element name=version type=xs:string minOccurs=0/ xs:element name=type type=xs:string minOccurs=0/ xs:element name=import type=sys:importType minOccurs=0/ /xs:sequence /xs:complexType xs:complexType name=dependenciesType xs:sequence xs:element name=dependency type=sys:artifactType minOccurs=0 maxOccurs=unbounded/ /xs:sequence /xs:complexType -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (XBEAN-11) JMX notification to SNMP converter
[ http://issues.apache.org/jira/browse/XBEAN-11?page=all ] Alan Cabrera reassigned XBEAN-11: - Assign To: Alan Cabrera JMX notification to SNMP converter -- Key: XBEAN-11 URL: http://issues.apache.org/jira/browse/XBEAN-11 Project: XBean Type: New Feature Reporter: Dan Diephouse Assignee: Alan Cabrera Attachments: snmp.diff This patch adds an xbean-snmp module which converts jmx notifications to snmp messages. Everything is configured via beans. Here is a short sample: SnmpEmitter em = new SnmpEmitter(); SnmpServer ss = new SnmpServer(); ss.setHost(127.0.0.1); ss.setPort(162); ss.setVarBindings(new ArrayList()); /* Bind the JMX notification type java.management.memory.threshold.exceeded * to the specified OID. The payload of the snmp message will be the usage * attribute. */ SnmpBinding binding = new SnmpBinding(); binding.setOid(1.3.6.1.2.1.1.3); binding.setPayload(usage); binding.setType(java.management.memory.threshold.exceeded); ss.getVarBindings().add(binding); Set servers = new HashSet(); servers.add(ss); em.setServers(servers); em.start(); Then all you need to do as add the SnmpEmitter as a NotificationListener for your JMX events. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2044) Compilation failure: java.nio.BufferOverflowException
Compilation failure: java.nio.BufferOverflowException
-
Key: GERONIMO-2044
URL: http://issues.apache.org/jira/browse/GERONIMO-2044
Project: Geronimo
Type: Bug
Security: public (Regular issues)
Components: buildsystem
Versions: 1.2
Environment: windows 2003 server,jdk 1.5.0_05,Celeren 64bit 2.6G
Reporter: chenjianghong
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Geronimo
[INFO] Geronimo Plugins
[INFO] Geronimo Modules
[INFO] Geronimo :: Activation
[INFO] Geronimo :: ActiveMQ Embedded RAR
[INFO] Geronimo :: Interceptor
[INFO] Geronimo :: Kernel
[INFO] Geronimo :: Common
[INFO] Geronimo :: Management API
[INFO] Geronimo :: Core
[INFO] Geronimo :: Util
[INFO] Geronimo :: System
[INFO] Geronimo :: J2EE
[INFO] Geronimo :: Security
[INFO] Geronimo :: Web Services
[INFO] Geronimo :: Axis
[INFO] Geronimo :: J2EE Schema
[INFO] Geronimo :: Naming
[INFO] Geronimo :: Deployment
[INFO] Geronimo :: Service :: Builder
[INFO] Geronimo :: Deploy :: Common Config
[INFO] Geronimo :: Security :: Builder
[INFO] Geronimo :: J2EE :: Builder
[INFO] Geronimo :: Naming :: Builder
[INFO] Geronimo :: Axis :: Builder
[INFO] Geronimo :: Transaction
[INFO] Geronimo :: Client
[INFO] Geronimo :: Test :: DDBeans
[INFO] Geronimo :: Connector
[INFO] Geronimo :: Connector :: Builder
[INFO] Geronimo :: Client Builder
[INFO] Geronimo :: Configuration Converter
[INFO] Geronimo :: Web :: Builder
[INFO] Geronimo :: Deploy :: JSR-88
[INFO] Geronimo :: Deploy :: CLI Tool
[INFO] Geronimo :: Derby
[INFO] Geronimo :: Directory
[INFO] Geronimo :: Deploy :: Hot Deployer
[INFO] Geronimo :: Installer :: Processing
[INFO] Geronimo :: Installer :: Support
[INFO] Geronimo :: Jetty
[INFO] Geronimo :: Jetty :: Builder
[INFO] Geronimo :: JavaMail Transport
[INFO] Geronimo :: JMX Remoting
[INFO] Geronimo :: Mail
[INFO] Geronimo :: Scripts
[INFO] Geronimo :: Session
[INFO] Geronimo :: Spring
[INFO] Geronimo :: Timer
[INFO] Geronimo :: Tomcat
[INFO] Geronimo :: Tomcat :: Builder
[INFO] Geronimo Configs
[INFO] Geronimo Applications
[INFO] Geronimo Demo Application
[INFO] Geronimo JMX Debug Application
[INFO] Geronimo LDAP Demo Application
[INFO] Geronimo :: The Magic G Ball
[INFO] Geronimo :: The Magic G Ball Sample :: EJB
[INFO] Geronimo :: The Magic G Ball Sample :: Client
[INFO] Geronimo :: The Magic G Ball Sample :: WAR
[INFO] Geronimo :: The Magic G Ball Sample Application
[INFO] Geronimo :: Remote Deploy GBean
[INFO] Geronimo Remote Deploy Application
[INFO] Geronimo UDDI Server Database
[INFO] Geronimo UDDI Server
[INFO] Geronimo Welcome Application
[INFO] Geronimo Assemblies
[INFO]
[INFO] Building Geronimo
[INFO]task-segment: [install]
[INFO]
[INFO] Skipping missing optional mojo:
org.apache.maven.plugins:maven-site-plugin:attach-descriptor
[INFO] [install:install]
[INFO] Installing F:\apache\src\Geronimo\pom.xml to
F:\usr\.m2\repository\org\apache\geronimo\geronimo-parent\1.2-SNAPSHOT\geronimo-parent-1.2-SNAPSHOT.pom
[INFO] [maven-one-plugin:install-maven-one-repository {execution: default}]
[INFO] Installing F:\apache\src\Geronimo\pom.xml to C:\Documents and
Settings\Administrator\.maven\repository\org.apache.geronimo\poms\geronimo-parent-1.2-SNAPSHOT.pom
[INFO]
[INFO] Building Geronimo Plugins
[INFO]task-segment: [install]
[INFO]
[INFO] Skipping missing optional mojo:
org.apache.maven.plugins:maven-site-plugin:attach-descriptor
[INFO] [install:install]
[INFO] Installing F:\apache\src\Geronimo\plugins\pom.xml to
F:\usr\.m2\repository\org\apache\geronimo\plugins\plugins-parent\1.2-SNAPSHOT\plugins-parent-1.2-SNAPSHOT.pom
[INFO] [maven-one-plugin:install-maven-one-repository {execution: default}]
[INFO] Installing F:\apache\src\Geronimo\plugins\pom.xml to C:\Documents and
Settings\Administrator\.maven\repository\org.apache.geronimo.plugins\poms\plugins-parent-1.2-SNAPSHOT.pom
[INFO]
[INFO] Building Geronimo Modules
[INFO]task-segment: [install]
[INFO]
[INFO] Skipping missing optional mojo:
org.apache.maven.plugins:maven-site-plugin:attach-descriptor
[INFO] [install:install]
[INFO] Installing F:\apache\src\Geronimo\modules\pom.xml to
F:\usr\.m2\repository\org\apache\geronimo\modules\modules-parent\1.2-SNAPSHOT\modules-parent-1.2-SNAPSHOT.pom
[INFO] [maven-one-plugin:install-maven-one-repository {execution: default}]
[jira] Closed: (XBEAN-11) JMX notification to SNMP converter
[ http://issues.apache.org/jira/browse/XBEAN-11?page=all ] Alan Cabrera closed XBEAN-11: - Fix Version: 2.4 Resolution: Fixed Nice. Many thanks! JMX notification to SNMP converter -- Key: XBEAN-11 URL: http://issues.apache.org/jira/browse/XBEAN-11 Project: XBean Type: New Feature Reporter: Dan Diephouse Assignee: Alan Cabrera Fix For: 2.4 Attachments: snmp.diff This patch adds an xbean-snmp module which converts jmx notifications to snmp messages. Everything is configured via beans. Here is a short sample: SnmpEmitter em = new SnmpEmitter(); SnmpServer ss = new SnmpServer(); ss.setHost(127.0.0.1); ss.setPort(162); ss.setVarBindings(new ArrayList()); /* Bind the JMX notification type java.management.memory.threshold.exceeded * to the specified OID. The payload of the snmp message will be the usage * attribute. */ SnmpBinding binding = new SnmpBinding(); binding.setOid(1.3.6.1.2.1.1.3); binding.setPayload(usage); binding.setType(java.management.memory.threshold.exceeded); ss.getVarBindings().add(binding); Set servers = new HashSet(); servers.add(ss); em.setServers(servers); em.start(); Then all you need to do as add the SnmpEmitter as a NotificationListener for your JMX events. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (XBEAN-11) JMX notification to SNMP converter
[ http://issues.apache.org/jira/browse/XBEAN-11?page=all ] Alan Cabrera updated XBEAN-11: -- Component: jmx JMX notification to SNMP converter -- Key: XBEAN-11 URL: http://issues.apache.org/jira/browse/XBEAN-11 Project: XBean Type: New Feature Components: jmx Reporter: Dan Diephouse Assignee: Alan Cabrera Fix For: 2.4 Attachments: snmp.diff This patch adds an xbean-snmp module which converts jmx notifications to snmp messages. Everything is configured via beans. Here is a short sample: SnmpEmitter em = new SnmpEmitter(); SnmpServer ss = new SnmpServer(); ss.setHost(127.0.0.1); ss.setPort(162); ss.setVarBindings(new ArrayList()); /* Bind the JMX notification type java.management.memory.threshold.exceeded * to the specified OID. The payload of the snmp message will be the usage * attribute. */ SnmpBinding binding = new SnmpBinding(); binding.setOid(1.3.6.1.2.1.1.3); binding.setPayload(usage); binding.setType(java.management.memory.threshold.exceeded); ss.getVarBindings().add(binding); Set servers = new HashSet(); servers.add(ss); em.setServers(servers); em.start(); Then all you need to do as add the SnmpEmitter as a NotificationListener for your JMX events. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (XBEAN-2) XBean should throw exceptions when a namespace can not be mapped or when an element / attribute can not be mapped
[ http://issues.apache.org/jira/browse/XBEAN-2?page=all ] Alan Cabrera closed XBEAN-2: XBean should throw exceptions when a namespace can not be mapped or when an element / attribute can not be mapped - Key: XBEAN-2 URL: http://issues.apache.org/jira/browse/XBEAN-2 Project: XBean Type: Improvement Components: spring Versions: 2.3 Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 2.3 Attachments: XBEAN-2.patch -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (XBEAN-4) Create a maven 2 plugin for spring mapping generation
[ http://issues.apache.org/jira/browse/XBEAN-4?page=all ] Alan Cabrera closed XBEAN-4: Create a maven 2 plugin for spring mapping generation - Key: XBEAN-4 URL: http://issues.apache.org/jira/browse/XBEAN-4 Project: XBean Type: New Feature Components: spring Versions: 2.3 Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 2.3 Attachments: XBEAN-4.patch -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (XBEAN-6) Fix dependencies scope
[ http://issues.apache.org/jira/browse/XBEAN-6?page=all ] Alan Cabrera closed XBEAN-6: Fix dependencies scope -- Key: XBEAN-6 URL: http://issues.apache.org/jira/browse/XBEAN-6 Project: XBean Type: Bug Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 2.3 Attachments: XBEAN-6.patch Some dependencies do not have the right scope and this can be annoying for end users -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (XBEAN-8) Support flat collections
[ http://issues.apache.org/jira/browse/XBEAN-8?page=all ] Alan Cabrera closed XBEAN-8: Support flat collections Key: XBEAN-8 URL: http://issues.apache.org/jira/browse/XBEAN-8 Project: XBean Type: New Feature Components: spring Versions: 2.2 Reporter: Dan Diephouse Assignee: Guillaume Nodet Fix For: 2.3 Attachments: flat.diff, xbean8.diff I would like to be able to do serviceoperation//service instead of serviceoperationsoperation//operations -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (XBEAN-7) Inconsistent use of classloader when using spring configurations for xbean-server
[ http://issues.apache.org/jira/browse/XBEAN-7?page=all ] Alan Cabrera closed XBEAN-7: Inconsistent use of classloader when using spring configurations for xbean-server - Key: XBEAN-7 URL: http://issues.apache.org/jira/browse/XBEAN-7 Project: XBean Type: Bug Components: server Versions: 2.2 Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 2.3 Attachments: XBEAN-7.patch The ClassLoaderXmlPreprocessor redefines the classloader used by spring / xbean when loading a spring configuration file. Unfortunately, the behavior is inconsistent when using the classpath / tag and when not. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (XBEAN-9) Support flat properties
[ http://issues.apache.org/jira/browse/XBEAN-9?page=all ] Alan Cabrera closed XBEAN-9: Support flat properties --- Key: XBEAN-9 URL: http://issues.apache.org/jira/browse/XBEAN-9 Project: XBean Type: New Feature Components: spring Versions: 2.2 Reporter: Dan Diephouse Assignee: Guillaume Nodet Fix For: 2.3 Right now in servicemix we have to do: eip:inListener eip:exchange-target service=test:trace1 / /eip:inListener It would be much better if we could do: eip:inListener service=test:trace1 / -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Created: (GERONIMO-2044) Compilation failure: java.nio.BufferOverflowException
chenjianghong,
The trunk (1.2) has become obsolete. Most of the work is being done
in branches/1.1. Geronimo does not build with M2 yet.
Thanks
Anita
--- chenjianghong (JIRA) dev@geronimo.apache.org wrote:
Compilation failure: java.nio.BufferOverflowException
-
Key: GERONIMO-2044
URL: http://issues.apache.org/jira/browse/GERONIMO-2044
Project: Geronimo
Type: Bug
Security: public (Regular issues)
Components: buildsystem
Versions: 1.2
Environment: windows 2003 server,jdk 1.5.0_05,Celeren 64bit 2.6G
Reporter: chenjianghong
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Geronimo
[INFO] Geronimo Plugins
[INFO] Geronimo Modules
[INFO] Geronimo :: Activation
[INFO] Geronimo :: ActiveMQ Embedded RAR
[INFO] Geronimo :: Interceptor
[INFO] Geronimo :: Kernel
[INFO] Geronimo :: Common
[INFO] Geronimo :: Management API
[INFO] Geronimo :: Core
[INFO] Geronimo :: Util
[INFO] Geronimo :: System
[INFO] Geronimo :: J2EE
[INFO] Geronimo :: Security
[INFO] Geronimo :: Web Services
[INFO] Geronimo :: Axis
[INFO] Geronimo :: J2EE Schema
[INFO] Geronimo :: Naming
[INFO] Geronimo :: Deployment
[INFO] Geronimo :: Service :: Builder
[INFO] Geronimo :: Deploy :: Common Config
[INFO] Geronimo :: Security :: Builder
[INFO] Geronimo :: J2EE :: Builder
[INFO] Geronimo :: Naming :: Builder
[INFO] Geronimo :: Axis :: Builder
[INFO] Geronimo :: Transaction
[INFO] Geronimo :: Client
[INFO] Geronimo :: Test :: DDBeans
[INFO] Geronimo :: Connector
[INFO] Geronimo :: Connector :: Builder
[INFO] Geronimo :: Client Builder
[INFO] Geronimo :: Configuration Converter
[INFO] Geronimo :: Web :: Builder
[INFO] Geronimo :: Deploy :: JSR-88
[INFO] Geronimo :: Deploy :: CLI Tool
[INFO] Geronimo :: Derby
[INFO] Geronimo :: Directory
[INFO] Geronimo :: Deploy :: Hot Deployer
[INFO] Geronimo :: Installer :: Processing
[INFO] Geronimo :: Installer :: Support
[INFO] Geronimo :: Jetty
[INFO] Geronimo :: Jetty :: Builder
[INFO] Geronimo :: JavaMail Transport
[INFO] Geronimo :: JMX Remoting
[INFO] Geronimo :: Mail
[INFO] Geronimo :: Scripts
[INFO] Geronimo :: Session
[INFO] Geronimo :: Spring
[INFO] Geronimo :: Timer
[INFO] Geronimo :: Tomcat
[INFO] Geronimo :: Tomcat :: Builder
[INFO] Geronimo Configs
[INFO] Geronimo Applications
[INFO] Geronimo Demo Application
[INFO] Geronimo JMX Debug Application
[INFO] Geronimo LDAP Demo Application
[INFO] Geronimo :: The Magic G Ball
[INFO] Geronimo :: The Magic G Ball Sample :: EJB
[INFO] Geronimo :: The Magic G Ball Sample :: Client
[INFO] Geronimo :: The Magic G Ball Sample :: WAR
[INFO] Geronimo :: The Magic G Ball Sample Application
[INFO] Geronimo :: Remote Deploy GBean
[INFO] Geronimo Remote Deploy Application
[INFO] Geronimo UDDI Server Database
[INFO] Geronimo UDDI Server
[INFO] Geronimo Welcome Application
[INFO] Geronimo Assemblies
[INFO]
[INFO] Building Geronimo
[INFO]task-segment: [install]
[INFO]
[INFO] Skipping missing optional mojo:
org.apache.maven.plugins:maven-site-plugin:attach-descriptor
[INFO] [install:install]
[INFO] Installing F:\apache\src\Geronimo\pom.xml to
F:\usr\.m2\repository\org\apache\geronimo\geronimo-parent\1.2-SNAPSHOT\geronimo-parent-1.2-SNAPSHOT.pom
[INFO] [maven-one-plugin:install-maven-one-repository {execution:
default}]
[INFO] Installing F:\apache\src\Geronimo\pom.xml to C:\Documents and
Settings\Administrator\.maven\repository\org.apache.geronimo\poms\geronimo-parent-1.2-SNAPSHOT.pom
[INFO]
[INFO] Building Geronimo Plugins
[INFO]task-segment: [install]
[INFO]
[INFO] Skipping missing optional mojo:
org.apache.maven.plugins:maven-site-plugin:attach-descriptor
[INFO] [install:install]
[INFO] Installing F:\apache\src\Geronimo\plugins\pom.xml to
F:\usr\.m2\repository\org\apache\geronimo\plugins\plugins-parent\1.2-SNAPSHOT\plugins-parent-1.2-SNAPSHOT.pom
[INFO] [maven-one-plugin:install-maven-one-repository {execution:
default}]
[INFO] Installing F:\apache\src\Geronimo\plugins\pom.xml to
C:\Documents and
Settings\Administrator\.maven\repository\org.apache.geronimo.plugins\poms\plugins-parent-1.2-SNAPSHOT.pom
[INFO]
[INFO] Building Geronimo Modules
[INFO]task-segment: [install]
[INFO]
[INFO] Skipping missing optional mojo:
[jira] Closed: (GERONIMO-1762) Create a derby network /embedded XA datasource via admin console fail
[ http://issues.apache.org/jira/browse/GERONIMO-1762?page=all ] David Jencks closed GERONIMO-1762: -- Resolution: Fixed Assign To: David Jencks I've applied the patch because with it you can in fact create derby xa pools. However, the portlet should know what additional jars are needed to go with these particular adapters, so the user doesn't need to. Also it looks like there are some hardcoded 1.1 versions in DatabaseInfo. Create a derby network /embedded XA datasource via admin console fail - Key: GERONIMO-1762 URL: http://issues.apache.org/jira/browse/GERONIMO-1762 Project: Geronimo Type: Bug Security: public(Regular issues) Components: console Versions: 1.0, 1.1 Environment: winXP Reporter: Lin Sun Assignee: David Jencks Fix For: 1.1 Attachments: G1762.patch Wehn tried to deploy a derby embedded or network XA datasource via console, got a class not found error and failed. This is caused by the plan generated by the console not declaring the dependency elements correctly (for example derbyclient.jar is needed as dependency for derby network XA). The fix adds a jar selection for XA resource adapters, thus the dependency URI element can be set correctly with user's selection. With the fix, I am able to create database connection pools using either derby embedded XA or network XA. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Notes from JavaOne
Just as a reminder, these notes are just a starting point for discussion. -David On May 19, 2006, at 2:01 PM, Aaron Mulder wrote: All, A great time was had at JavaOne, including a variety of Geronimo-related meetings, hacking time in the W and Moscone, a BOF, a party, etc. Here are some thoughts I put together based on the bits I was involved with, which I think we'd all like to run by everyone who couldn't be there. Also, here are the slides from the Geronimo BOF, that talk a bit about the various releases: http://people.apache.org/~ammulder/geronimo-javaone2006.pdf Thanks, Aaron Ebay announced in a BOF that they are deploying their site on WebSphere CE (Geronimo)!!! Yeah, let's talk about acalability... :) Vendor Support - Many vendors are supporting Geronimo, including: - 24x7 support - services - building applications on Geronimo - building/supporting software stacks including Geronimo 1.1/1.2 Merge - Major things changed in 1.2: OpenEJB refactoring, JavaMail providers, initial Maven 2 build script, ActiveMQ 3-4, dynamic EJB queries - Still, not that much compared to 1.1 - We plan for the process to be 1) move 1.2 to branches/1.2-pre 2) copy 1.1 to trunk 3) maintain 1.1 in current 1.1 branch 4) merge changes from branches/1.2-pre to trunk 5) eventually whack branches/1.2-pre perhaps Release Schedule - 1.0 took too long to arrive (since founding) and 1.1 took too long to arrive (since 1.0) - We need to avoid TCK breakage and do a better job of incremental change - Some people advocate time-based releases (2/3/4 months) - Some people would like to see XBean releases more often, outside the Geronimo release schedule - Vendors don't like the uncertainty about release dates; most are still targeting 1.0 because it's here and there's no guarantee when 1.1 will actually arrive - Overall, there seems to be interest in targeting a 3-month release schedule for 1.2 (2 months active development and 1 month stabilization) - Proposal to target 4 features releases per year with incremental features available via plugins Jira Process - lots of open Jiras - estimate we have closed 250 for 1.1, and have 500 currently open - may need to clean up some old/stale issues - Jira never reflects how close we are to a release - Many Jiras go unnoticed - There's not a good way to have a personal work/priority list separate from the project release/priority list - Might be good to have 3 Jira releases: current release, next release, everything else - Might be helpful to have someone take responsibility for evaluating all incoming Jiras for a period of time (1-4 weeks?) and rotate that responsibility - Maybe could add custom fiuelds to help us manage it Java SE 5 - We can develop on Java 5 and support 1.4.2 via Retrotranslator - It supports most of Java 5, with some caveats regarding Serialization and new classes added outside of Collections (some SSL-related stuff, etc.) - Running on 1.4 with Retrotranslator causes a startup penalty of ~20% (but shouldn't have much effect after startup, when all the classes are loaded) - Running on 1.5 speeds startup by 20% and should have benefits after startup too - Dain will try a more extensive test and make sure everything works for us - Yoko is making good progress. Some holes (e.g. SSL) but we can probably start integrating and may have this for 1.2 (Rick will work on this) Java EE 5 - OpenJPA code is only partially available; more expected soon - Should be able to implement a JPA factory that lets us give access to installed JPA implementations - Should be able to get web features from Jetty 6 - Should be able to get JAX-WS from XFire/Celtix - Don't have an immediate plan for EJB3 (outside of JPA), though Spring reportedly has working code we could leverage - Should be easy to get initial EE 5 features in 1.2, may not have full support, but this is enough for people to play with Candidate Features for Future Releases - Console portlets can be added at runtime - OpenEJB 2.x revisions - Initial XBean-style features - Don't require GBeanInfo for GBeans - Integrate XBean reflect to support factory beans, nested complex objects, etc. - Designate startup methods instead of requiring interface - Full XBean Integration - Monitoring / Statistics - DConfigBeans - Improved JMX+SNMP - Pluggable JACC (Acegi, LDAP, etc.) - Start Levels - ActiveIO - IBM AIO??? - Workflow via BeanFlow - Global JNDI - XDoclet - Startup Wrapper - Upgrade on the fly - Security Rewrite - 1-click to disable unused services - Separate App/Server ClassLoaders - Spring Deployment - Improve Hot Deployment - Integrate (plugins, etc.) - XFire - OpenJPA - OpenEJB 3 - Jetty 6 - Yoko - LiveTribe - JetSpeed - Clustering - DAG ClassLoader - Maven 2 - Parallel Startup - Windows/UNIX Service - Performance - No Proxies - Console manage multiple servers - Provisioning via agents - Lingo - Map apps to ports - Eliminate XML namespaces - Telnet / GShell - GShell - Purpose-built
[jira] Closed: (GERONIMO-2020) Relative symlinks to the shell scripts were not handled correctly
[ http://issues.apache.org/jira/browse/GERONIMO-2020?page=all ] John Sisson closed GERONIMO-2020: - Resolution: Fixed Relative symlinks to the shell scripts were not handled correctly - Key: GERONIMO-2020 URL: http://issues.apache.org/jira/browse/GERONIMO-2020 Project: Geronimo Type: Bug Security: public(Regular issues) Components: startup/shutdown Versions: 1.0 Environment: UNIX, Linux Reporter: John Sisson Assignee: John Sisson Priority: Minor Fix For: 1.1 Attachments: relative-symlinks.patch Geronimo's shell scripts originated from Tomcat and recently Tomcat had this fix applied to fix issues with relative symlinks. http://mail-archives.apache.org/mod_mbox/tomcat-dev/200603.mbox/[EMAIL PROTECTED] Attaching patch for someone to test on a unix box. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1638) Multiple servers sharing the same repo and config store
[ http://issues.apache.org/jira/browse/GERONIMO-1638?page=all ] John Sisson updated GERONIMO-1638: -- Fix Version: 1.1 (was: 1.2) Multiple servers sharing the same repo and config store --- Key: GERONIMO-1638 URL: http://issues.apache.org/jira/browse/GERONIMO-1638 Project: Geronimo Type: New Feature Security: public(Regular issues) Components: usability Versions: 1.0 Reporter: Gianny Damour Assignee: John Sisson Fix For: 1.1 David J. sent to the dev mailing list: Many people have talked on and off about how to set up multiple servers sharing the same repository and config-store, but we haven't arrived at an agreed on way to do it. We have a prospective customer for this feature (Vincent Massol with Cargo) so I'd like to move beyond thinking about it in my head, discuss it, and have someone implement it. I believe any implementation will be more or less trivial, the hard part is figuring out what to do. I've only thought of ways to extend what we have now, rather than restructure anything or add big new capabilities. If someone sees a better way, please speak up. So, we have a ServerInfo gbean that knows where geronimo is located and can resolve absolute locations for other components. Then we have things like the repository and config store gbeans that typically are located outside the var dir and things like the logging framework, local attribute manager, derby, and tomcat, that typically keep stuff in the var directory. All or most of these start with the first configuration loaded so they can't have any attributes overridden by config.xml: in fact this file is read by one of the gbeans that we need to relocate. I've thought of two related solutions. Both of them involve giving ServerInfo knowledge of another path and another resolve method. One would be something like resolveVar and would normally resolve to geronimo_home/var. This would involve all the gbeans currently looking inside var having the var trimmed off the front of their paths and using the new resolveVar method. In this case we'd have different servers represented as e.g. var1 var2 var3 ... The other would give ServerInfo something like resolveServer which would normally resolve to geronimo_home. The gbeans looking inside var would keep their current paths and just call the new resolve method instead of the old one. In this case we'd have servers like var server1/var server2/var ... In either case I think starting geronimo with a command line argument pointing to the var directory is the only way to specify which server you want to run; the default would presumably be as now var. Several people have suggested putting an additional config-store into var for private use by a particular server. At the moment I think that providing a different config-store class that uses the new resolve method on server info would be the best way to do this. I'm not attached to these ideas but this is as far as my thinking has gone. Please comment. thanks david jencks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
1.1 Status
All, We're still waiting for the Codehaus Repo to go writeable. I just checked their web site and there was no prognosis on the date yet. I have some uncommitted performance changes and I believe others have changes as well. Gianny was also completing some work on TranQL I believe. At this point I want to release a candidate early next week based on Codehaus' situation. Then release 1.1 by the end of May. Any questions / comments reply back to this note. Matt
[jira] Commented: (GERONIMO-2037) Build failing on some Windows boxes and Solaris x86
[ http://issues.apache.org/jira/browse/GERONIMO-2037?page=comments#action_12412661 ] John Sisson commented on GERONIMO-2037: --- On Solaris x86 (geronimo rev 408120), I narrowed the problem down a bit further.. to the call to getJarEntry(..) in the initializeVerifier() method of the JarFile class throwing a NullPointerException if getJarEntry(..) returns null. I placed a modified version of the JarFile class to debug the problem on my bootclasspath that dumps the name of the jar entry and the jar file name by doing a export MAVEN_OPTS='-Xmx512m -XX:MaxPermSize=128m -server -ea -Xbootclasspath/p:/home/sissonj/patch/' I am guessing that on windows, the native code called by java.util.zip.ZipFile.getEntry(..) maybe doesn't handle errors gracefully and causes an access violation instead of returning null. I found that repeated runs on Solaris x86 always had the problem with getting the same entry. Here is my debugging info for it that shows the entry being looked up, its index in the array, the jar file name, and the contents of the array: java.lang.NullPointerException: jarEntry(META-INF/LICENSE.txt) (names index 6) returned null for jar file: /home/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/geronimo-system-1.1-SNAPSHOT. jarNames array: [META-INF/,META-INF/MANIFEST.MF,META-INF/schema/,META-INF/product-versions.properties,META-INF/schema/local-attributes-1.1.xsd,META-INF/schema/plugins-1.1.xsd,META-INF/LICENSE.txt] at java.util.jar.JarFile.initializeVerifier(JarFile.java:307) at java.util.jar.JarFile.getInputStream(JarFile.java:381) at sun.misc.URLClassPath$5.getInputStream(URLClassPath.java:619) at sun.misc.Resource.getBytes(Resource.java:57) at java.net.URLClassLoader.defineClass(URLClassLoader.java:248) at java.net.URLClassLoader.access$100(URLClassLoader.java:55) at java.net.URLClassLoader$1.run(URLClassLoader.java:194) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:187) at java.lang.ClassLoader.loadClass(ClassLoader.java:289) at java.lang.ClassLoader.loadClass(ClassLoader.java:235) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) at org.apache.geronimo.deployment.PluginBootstrap.bootstrap(PluginBootstrap.java:73) It is interesting that it is the last entry in the array that it has problems with. Build failing on some Windows boxes and Solaris x86 --- Key: GERONIMO-2037 URL: http://issues.apache.org/jira/browse/GERONIMO-2037 Project: Geronimo Type: Bug Security: public(Regular issues) Components: buildsystem Environment: Windows XP - 1.4.2_11-b06 Solaris x86 - 1.4.2_10-b03 Reporter: John Sisson Priority: Blocker Fix For: 1.1 I can build geronimo on my windows notebook ok (with the GERONIMO-1434 openejb patch applied). But when I try to build on my windows desktop (tried latest 1.4.2_11-b06 jvm) it fails with a JVM crash. I found that whilst running with diagnostic code enabled (slowing the build down) the build worked on my windows desktop. I think Joe Bohn had also run into this crash on Windows. I didn't get a JVM crash on Solaris x86, but got a NoClassDefFoundError (see below) in the same part of the build that had the JVM crash. *Windows Output *** 13:12:30,732 INFO [ReactorTag] | configurations Geronimo Configuration for performing service deployments 13:12:30,732 INFO [ReactorTag] | Memory: 96M/103M build:start: multiproject:install-callback: [echo] Running car:install for Geronimo Configuration for performing service deployments # # An unexpected error has been detected by HotSpot Virtual Machine: # # EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x7c92ae22, pid=5240, tid=4788 # # Java VM: Java HotSpot(TM) Client VM (1.4.2_11-b06 mixed mode) # Problematic frame: # C [ntdll.dll+0x2ae22] # --- T H R E A D --- Current thread (0x000377a8): JavaThread main [_thread_in_native, id=4788] siginfo: ExceptionCode=0xc005, reading address 0xd1d7763b Registers: EAX=0x00048b77, EBX=0x, ECX=0xd1d7763b, EDX=0x00030608 ESP=0x0007d858, EBP=0x0007d914, ESI=0x030654d0, EDI=0x0003 EIP=0x7c92ae22, EFLAGS=0x00010213 Top of Stack: (sp=0x0007d858) 0x0007d858: 77c2c21b 030654f0 04ba4238 0356 0x0007d868: 04ba4238 0008 000e 7ffdd000 0x0007d878: 001e 7ffdd000 000377a8 0007d860 0x0007d888: 63617061 0007d8fc 7c8399f3 7c809bd8 0x0007d898: d1d7763b 77c2f941 00048b77 0x0007d8a8: 030654d0 001e 0007d8c4 0x0007d8b8: 77c62448 01d4 004d 001e 0x0007d8c8: 001e 77c2e556 02fa1bd8 0007d90c Instructions: (pc=0x7c92ae22) 0x7c92ae12: 75 cc
[jira] Updated: (GERONIMO-1740) Plugin migration to Maven 2: geronimo-packaging-plugin
[ http://issues.apache.org/jira/browse/GERONIMO-1740?page=all ] Anita Kulshreshtha updated GERONIMO-1740: - Attachment: modules.patch pom.patch These patches are for building all the modules in 1.1 : - modules.patch - pom.patch - created from the top directory Some more work is needed - 1. There are 2 fatal test failures, one in system and one in connector-builder. Hence the tests are being skipped in these two modules. 2. The j2ee-schema should be built online. This restriction will be removed as soon as newer version of xmlbeans plugin is available. 3. The jvm needed to be forked per test for the security module. 4. The geronimo-dependency.xml files will be checked in after the merge. 5. A separate patch will be submitted for the configs and the plugin. The packaging-plugin got changed again today! Plugin migration to Maven 2: geronimo-packaging-plugin -- Key: GERONIMO-1740 URL: http://issues.apache.org/jira/browse/GERONIMO-1740 Project: Geronimo Type: Sub-task Security: public(Regular issues) Components: buildsystem Versions: 1.x Reporter: Jacek Laskowski Assignee: Anita Kulshreshtha Attachments: configs.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, m2-plugins.patch, modules.patch, pom.patch It's a task to keep track of the progress of the plugin build migration to Maven2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-2039) typos in org.apache.geronimo.kernel.config.recursiveCopy(File srcDir, File destDir)
[ http://issues.apache.org/jira/browse/GERONIMO-2039?page=all ]
John Sisson closed GERONIMO-2039:
-
Resolution: Fixed
Fixed. Good eyes Anita :-)
typos in org.apache.geronimo.kernel.config.recursiveCopy(File srcDir, File
destDir)
---
Key: GERONIMO-2039
URL: http://issues.apache.org/jira/browse/GERONIMO-2039
Project: Geronimo
Type: Bug
Security: public(Regular issues)
Components: kernel
Versions: 1.1
Reporter: John Sisson
Assignee: John Sisson
Fix For: 1.1
Hi,
I came across some typos in o.a.g.k.config.IOUtil.recursiveCopy()-
...
if (srcDir == null) throw new NullPointerException(sourceDir is
null);
if (srcDir == null) throw new NullPointerException(destDir is
null);
.
if (destDir.equals(destDir)) {
throw new IllegalArgumentException(Source and destination
directory are the same + srcDir);
}
..
Thanks
Anita
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
