Re: svn commit: r685741 - in /geronimo/server/trunk: ./ framework/configs/jee-specs/ plugins/axis2/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/pojo/ plugins/cxf/geronimo-cxf-ejb/src/main/ja
On Thu, Aug 14, 2008 at 3:34 AM, [EMAIL PROTECTED] wrote:
Author: gawor
Date: Wed Aug 13 18:34:00 2008
New Revision: 685741
URL: http://svn.apache.org/viewvc?rev=685741view=rev
Log:
upgrade to jax-ws api 2.1 (GERONIMO-4242)
dependency
-groupIdorg.apache.axis2/groupId
-artifactIdaxis2-jaxws-api/artifactId
+groupIdorg.apache.geronimo.specs/groupId
+artifactIdgeronimo-jaxws_2.1_spec/artifactId
/dependency
Do they (Axis) use Geronimo jars from now on? I don't think there's a
value keeping two jars in different ASF projects.
Modified:
geronimo/server/trunk/plugins/cxf/geronimo-cxf-ejb/src/main/java/org/apache/geronimo/cxf/ejb/EJBEndpoint.java
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/plugins/cxf/geronimo-cxf-ejb/src/main/java/org/apache/geronimo/cxf/ejb/EJBEndpoint.java?rev=685741r1=685740r2=685741view=diff
==
---
geronimo/server/trunk/plugins/cxf/geronimo-cxf-ejb/src/main/java/org/apache/geronimo/cxf/ejb/EJBEndpoint.java
(original)
+++
geronimo/server/trunk/plugins/cxf/geronimo-cxf-ejb/src/main/java/org/apache/geronimo/cxf/ejb/EJBEndpoint.java
Wed Aug 13 18:34:00 2008
@@ -23,6 +23,7 @@
import javax.naming.InitialContext;
import javax.naming.NamingException;
+import javax.xml.ws.EndpointReference;
import javax.xml.ws.WebServiceContext;
import javax.xml.ws.WebServiceException;
@@ -42,6 +43,8 @@
import org.apache.geronimo.jaxws.JNDIResolver;
import org.apache.openejb.DeploymentInfo;
+import org.w3c.dom.Element;
+
public class EJBEndpoint extends CXFEndpoint {
public EJBEndpoint(Bus bus,
@@ -140,5 +143,14 @@
// shutdown server
super.stop();
}
+
+public EndpointReference getEndpointReference(Element...
referenceParameters) {
+throw new UnsupportedOperationException();
+}
+
+public T extends EndpointReference T getEndpointReference(ClassT
clazz,
+Element...
referenceParameters) {
+throw new UnsupportedOperationException();
+}
}
Modified:
geronimo/server/trunk/plugins/cxf/geronimo-cxf/src/main/java/org/apache/geronimo/cxf/pojo/POJOEndpoint.java
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/plugins/cxf/geronimo-cxf/src/main/java/org/apache/geronimo/cxf/pojo/POJOEndpoint.java?rev=685741r1=685740r2=685741view=diff
==
---
geronimo/server/trunk/plugins/cxf/geronimo-cxf/src/main/java/org/apache/geronimo/cxf/pojo/POJOEndpoint.java
(original)
+++
geronimo/server/trunk/plugins/cxf/geronimo-cxf/src/main/java/org/apache/geronimo/cxf/pojo/POJOEndpoint.java
Wed Aug 13 18:34:00 2008
@@ -21,6 +21,7 @@
import java.net.URL;
import javax.naming.Context;
+import javax.xml.ws.EndpointReference;
import javax.xml.ws.WebServiceException;
import org.slf4j.Logger;
@@ -36,6 +37,8 @@
import org.apache.geronimo.jaxws.JNDIResolver;
import org.apache.geronimo.jaxws.annotations.AnnotationHolder;
+import org.w3c.dom.Element;
+
public class POJOEndpoint extends CXFEndpoint {
private static final Logger LOG =
LoggerFactory.getLogger(POJOEndpoint.class);
@@ -112,4 +115,14 @@
// shutdown server
super.stop();
}
+
+public EndpointReference getEndpointReference(Element...
referenceParameters) {
+throw new UnsupportedOperationException();
+}
+
+public T extends EndpointReference T getEndpointReference(ClassT
clazz,
+Element...
referenceParameters) {
+throw new UnsupportedOperationException();
+}
+
}
Why is getEndpointReference not part of CXFEndpoint class?
Jacek
--
Jacek Laskowski
Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl
Re: Geronimo Futures
On Wed, Aug 13, 2008 at 5:25 PM, Donald Woods [EMAIL PROTECTED] wrote: This will help other community members know who to talk to if they have questions regarding those areas or would like to assist. This drew my attention - shouldn't all questions be asked on mailing lists so those who are not blessed with technology could become at some point? Jacek -- Jacek Laskowski Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl
[jira] Updated: (GERONIMODEVTOOLS-480) Support Web application test using the embeded browser in testsuite
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim McConnell updated GERONIMODEVTOOLS-480: --- Fix Version/s: 2.1.2 Yun Feng, this is just wonderful !! Now we can use Abbot and Selenium all within Eclipse. It's the coolest thing I've ever seen !! Thanks very much for getting this done for the GEP 2.1.2 release. Support Web application test using the embeded browser in testsuite --- Key: GERONIMODEVTOOLS-480 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-480 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 2.1.2 Reporter: YunFeng Ma Assignee: Tim McConnell Fix For: 2.1.2 Attachments: GERONIMODEVTOOLS-480.patch Integrate Selenium into the testsuite. Testcase can test the web application developed in testsuite via Selenium API. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMODEVTOOLS-444) 5 Minute tutorial web browser testcase
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim McConnell closed GERONIMODEVTOOLS-444. -- Resolution: Fixed Fix Version/s: 2.1.2 Closing as a result of the Selenium incorporation via GERONIMODEVTOOLS-480 5 Minute tutorial web browser testcase -- Key: GERONIMODEVTOOLS-444 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-444 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: B.J. Reed Fix For: 2.1.2 Attachments: GERONIMODEVTOOLS-444.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-461) Documentation updates
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12622473#action_12622473 ] Tim McConnell commented on GERONIMODEVTOOLS-461: Hi Ashish, this tutorial may also need some updating: http://cwiki.apache.org/GMOxDOC21/5-minute-tutorial-on-enterprise-application-development-with-eclipse-and-geronimo.html Documentation updates - Key: GERONIMODEVTOOLS-461 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-461 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.2 Reporter: Tim McConnell Assignee: Ashish Jain Fix For: 2.1.2 These tutorials below need to be updated once GEP 2.1.2 is released: (X) http://cwiki.apache.org/GMOxDOC21/web-application-for-ejb-access.html (X) http://cwiki.apache.org/GMOxDOC21/quick-start-fast-and-easy-development.html (X) http://cwiki.apache.org/GMOxDOC21/development-environment.html#Developmentenvironment-InstallingEclipse (X) http://geronimo.apache.org/developing-the-geronimo-eclipse-plugin-in-eclipse.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[VOTE] Release Geronimo Eclipse Plugin 2.1.2 (RC1)
Hi everyone, Please review and vote on the maintenance release of the Geronimo Eclipse Plugin 2.1.2 RC1. The deployable zip file is here: http://people.apache.org/~mcconne/releases/2.1.2/RC1/geronimo-eclipse-plugin-2.1.2-deployable.zip The update site zip file is here: http://people.apache.org/~mcconne/releases/2.1.2/RC1/geronimo-eclipse-plugin-2.1.2-updatesite.zip The current svn location is here (revision number 685795): https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.1.2 The future svn location will be here (when approved): https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.1.2 There is a rudimentary set of install instructions available at the URL below that will hopefully describe the necessary prereq(s) and steps required to install and run the GEP: http://people.apache.org/~mcconne/releases/2.1.2/RC1/Geronimo_Eclipse_Plugin_2.1.2_Instructions-RC1.txt In an effort to get more people to review and vote I'd recommend going through this quick but useful tutorial demonstrating some of the capabilities of the GEP: http://cwiki.apache.org/GMOxDOC21/5-minute-tutorial-on-enterprise-application-development-with-eclipse-and-geronimo.html Additionally, there is an ant build.xml file that can be used to download the prereq(s) for the GEP. It is documented in the instructions. Finally, I've created a Staging Site that can used to test the update manager functions (i.e., p2 in Ganymede) of Eclipse for downloading the GEP itself. This is also documented in the instructions. Please let me know if there are any questions and/or problems. The vote is open over the weekend and will conclude on Monday (8/18) at Noon ET. [ ] +1 Release Geronimo Eclipse Plugin 2.1.2 [ ] +0 No opinion [ ] -1 Don't release Geronimo Eclipse Plugin 2.1.2 -- Thanks, Tim McConnell
[DISCUSS] Release Geronimo Eclipse Plugin 2.1.2 (RC1)
-- Thanks, Tim McConnell
[jira] Resolved: (GERONIMODEVTOOLS-480) Support Web application test using the embeded browser in testsuite
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YunFeng Ma resolved GERONIMODEVTOOLS-480. - Resolution: Fixed Thanks a lot, Tim, for reviewing this patch. I've applied it to trunk (rev 685852). Support Web application test using the embeded browser in testsuite --- Key: GERONIMODEVTOOLS-480 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-480 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 2.1.2 Reporter: YunFeng Ma Assignee: Tim McConnell Fix For: 2.1.2 Attachments: GERONIMODEVTOOLS-480.patch Integrate Selenium into the testsuite. Testcase can test the web application developed in testsuite via Selenium API. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r685741 - in /geronimo/server/trunk: ./ framework/configs/jee-specs/ plugins/axis2/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/pojo/ plugins/cxf/geronimo-cxf-ejb/src/main/ja
On Thu, Aug 14, 2008 at 2:57 AM, Jacek Laskowski [EMAIL PROTECTED] wrote:
On Thu, Aug 14, 2008 at 3:34 AM, [EMAIL PROTECTED] wrote:
Author: gawor
Date: Wed Aug 13 18:34:00 2008
New Revision: 685741
URL: http://svn.apache.org/viewvc?rev=685741view=rev
Log:
upgrade to jax-ws api 2.1 (GERONIMO-4242)
dependency
-groupIdorg.apache.axis2/groupId
-artifactIdaxis2-jaxws-api/artifactId
+groupIdorg.apache.geronimo.specs/groupId
+artifactIdgeronimo-jaxws_2.1_spec/artifactId
/dependency
Do they (Axis) use Geronimo jars from now on? I don't think there's a
value keeping two jars in different ASF projects.
Yes, both Axis2 and CXF are using this Geronimo spec jar now.
Modified:
geronimo/server/trunk/plugins/cxf/geronimo-cxf-ejb/src/main/java/org/apache/geronimo/cxf/ejb/EJBEndpoint.java
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/plugins/cxf/geronimo-cxf-ejb/src/main/java/org/apache/geronimo/cxf/ejb/EJBEndpoint.java?rev=685741r1=685740r2=685741view=diff
==
---
geronimo/server/trunk/plugins/cxf/geronimo-cxf-ejb/src/main/java/org/apache/geronimo/cxf/ejb/EJBEndpoint.java
(original)
+++
geronimo/server/trunk/plugins/cxf/geronimo-cxf-ejb/src/main/java/org/apache/geronimo/cxf/ejb/EJBEndpoint.java
Wed Aug 13 18:34:00 2008
@@ -23,6 +23,7 @@
import javax.naming.InitialContext;
import javax.naming.NamingException;
+import javax.xml.ws.EndpointReference;
import javax.xml.ws.WebServiceContext;
import javax.xml.ws.WebServiceException;
@@ -42,6 +43,8 @@
import org.apache.geronimo.jaxws.JNDIResolver;
import org.apache.openejb.DeploymentInfo;
+import org.w3c.dom.Element;
+
public class EJBEndpoint extends CXFEndpoint {
public EJBEndpoint(Bus bus,
@@ -140,5 +143,14 @@
// shutdown server
super.stop();
}
+
+public EndpointReference getEndpointReference(Element...
referenceParameters) {
+throw new UnsupportedOperationException();
+}
+
+public T extends EndpointReference T getEndpointReference(ClassT
clazz,
+Element...
referenceParameters) {
+throw new UnsupportedOperationException();
+}
}
Modified:
geronimo/server/trunk/plugins/cxf/geronimo-cxf/src/main/java/org/apache/geronimo/cxf/pojo/POJOEndpoint.java
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/plugins/cxf/geronimo-cxf/src/main/java/org/apache/geronimo/cxf/pojo/POJOEndpoint.java?rev=685741r1=685740r2=685741view=diff
==
---
geronimo/server/trunk/plugins/cxf/geronimo-cxf/src/main/java/org/apache/geronimo/cxf/pojo/POJOEndpoint.java
(original)
+++
geronimo/server/trunk/plugins/cxf/geronimo-cxf/src/main/java/org/apache/geronimo/cxf/pojo/POJOEndpoint.java
Wed Aug 13 18:34:00 2008
@@ -21,6 +21,7 @@
import java.net.URL;
import javax.naming.Context;
+import javax.xml.ws.EndpointReference;
import javax.xml.ws.WebServiceException;
import org.slf4j.Logger;
@@ -36,6 +37,8 @@
import org.apache.geronimo.jaxws.JNDIResolver;
import org.apache.geronimo.jaxws.annotations.AnnotationHolder;
+import org.w3c.dom.Element;
+
public class POJOEndpoint extends CXFEndpoint {
private static final Logger LOG =
LoggerFactory.getLogger(POJOEndpoint.class);
@@ -112,4 +115,14 @@
// shutdown server
super.stop();
}
+
+public EndpointReference getEndpointReference(Element...
referenceParameters) {
+throw new UnsupportedOperationException();
+}
+
+public T extends EndpointReference T getEndpointReference(ClassT
clazz,
+Element...
referenceParameters) {
+throw new UnsupportedOperationException();
+}
+
}
Why is getEndpointReference not part of CXFEndpoint class?
It is. This commit was about upgrading the API jar. Once I actaully
update CXF and Axis2 to their latest versions these new methods will
be implemented properly. I'm trying to do things in smaller steps
instead all of it at once.
Jarek
[jira] Created: (GERONIMO-4243) EJB Deploy Error
EJB Deploy Error
Key: GERONIMO-4243
URL: https://issues.apache.org/jira/browse/GERONIMO-4243
Project: Geronimo
Issue Type: Sub-task
Security Level: public (Regular issues)
Components: console, deployment, Tomcat
Affects Versions: 2.1.2
Environment: Java
java.awt.graphicsenvsun.awt.X11GraphicsEnvironment
java.awt.printerjob sun.print.PSPrinterJob
java.class.path
/usr/local/geronimo/bin/server.jar
/usr/local/geronimo/bin/jpa.jar
java.class.version 49.0
java.endorsed.dirs
/usr/local/geronimo/lib/endorsed
/usr/local/java/jre/lib/endorsed
java.ext.dirs
/usr/local/geronimo/lib/ext
/usr/local/java/jre/lib/ext
java.home /home/oxseed/jdk1.5.0_15/jre
java.io.tmpdir /home/oxseed/geronimo-tomcat6-javaee5-2.1.2/var/temp
java.library.path
/home/oxseed/jdk1.5.0_15/jre/lib/i386/server
/home/oxseed/jdk1.5.0_15/jre/lib/i386
/home/oxseed/jdk1.5.0_15/jre/../lib/i386
java.runtime.name Java(TM) 2 Runtime Environment, Standard Edition
java.runtime.version1.5.0_15-b04
java.specification.name Java Platform API Specification
java.specification.vendor Sun Microsystems Inc.
java.specification.version 1.5
java.util.prefs.PreferencesFactory
java.vendor-Sun Microsystems Inc.
java.vendor.url http://java.sun.com/
java.vendor.url.bug http://java.sun.com/cgi-bin/bugreport.cgi
java.version- 1.5.0_15
Virtual Machine
java.vm.infomixed mode
java.vm.nameJava HotSpot(TM) Server VM
java.vm.specification.name Java Virtual Machine Specification
java.vm.specification.vendorSun Microsystems Inc.
java.vm.specification.version 1.0
java.vm.vendor Sun Microsystems Inc.
java.vm.version 1.5.0_15-b04
Operating System
os.arch i386
os.name Linux
os.version 2.6.16.33-xen
Sun
sun.arch.data.model 32
sun.boot.class.path
/usr/local/geronimo/lib/endorsed/yoko-spec-corba-1.0.jar
/usr/local/geronimo/lib/endorsed/yoko-rmi-spec-1.0.jar
/home/oxseed/jdk1.5.0_15/jre/lib/rt.jar
/home/oxseed/jdk1.5.0_15/jre/lib/i18n.jar
/home/oxseed/jdk1.5.0_15/jre/lib/sunrsasign.jar
/home/oxseed/jdk1.5.0_15/jre/lib/jsse.jar
/home/oxseed/jdk1.5.0_15/jre/lib/jce.jar
/home/oxseed/jdk1.5.0_15/jre/lib/charsets.jar
/home/oxseed/jdk1.5.0_15/jre/classes
sun.boot.library.path
/home/oxseed/jdk1.5.0_15/jre/lib/i386
sun.cpu.endian little
sun.cpu.isalist
sun.io.unicode.encoding UnicodeLittle
sun.java2d.fontpath
sun.os.patch.level unknown
User
user.countryUS
user.dir/home/oxseed
user.home /home/oxseed
user.language en
user.name oxseed
user.timezone Europe/Berlin
user.variant
Etc
admin.disabled true
catalina.base /home/oxseed/geronimo-tomcat6-javaee5-2.1.2/var/catalina
catalina.home /home/oxseed/geronimo-tomcat6-javaee5-2.1.2/var/catalina
catalina.useNaming false
com.sun.management.jmxremote
com.sun.management.jmxremote.authenticate false
com.sun.management.jmxremote.port 8004
com.sun.management.jmxremote.sslfalse
common.loader ${catalina.home}/lib ${catalina.home}/lib/*.jar
derby.storage.fileSyncTransactionLogtrue
derby.system.home /home/oxseed
duct tape
file.encoding ANSI_X3.4-1968
file.encoding.pkg sun.io
file.separator /
java.naming.factory.initial
org.apache.xbean.naming.global.GlobalContextManager
java.naming.factory.url.pkgsorg.apache.xbean.naming
java.naming.provider.urlrmi://0.0.0.0:1099
java.net.preferIPv4Stacktrue
java.rmi.server.RMIClassLoaderSpi
org.apache.geronimo.kernel.rmi.RMIClassLoaderSpiImpl
java.rmi.server.randomIDs true
java.security.Provider SUN
javax.rmi.CORBA.PortableRemoteObjectClass
org.apache.yoko.rmi.impl.PortableRemoteObjectImpl
javax.rmi.CORBA.StubClass org.apache.yoko.rmi.impl.StubImpl
javax.rmi.CORBA.UtilClass org.apache.geronimo.corba.util.UtilDelegateImpl
javax.security.jacc.PolicyConfigurationFactory.provider
org.apache.geronimo.security.jacc.mappingprovider.GeronimoPolicyConfigurationFactory
javax.security.jacc.policy.provider
org.apache.geronimo.security.jacc.mappingprovider.GeronimoPolicy
javax.xml.soap.MessageFactory
org.apache.geronimo.webservices.saaj.GeronimoMessageFactory
javax.xml.soap.MetaFactory
org.apache.geronimo.webservices.saaj.GeronimoMetaFactory
javax.xml.soap.SOAPConnectionFactory
org.apache.geronimo.webservices.saaj.GeronimoSOAPConnectionFactory
javax.xml.soap.SOAPFactory
org.apache.geronimo.webservices.saaj.GeronimoSOAPFactory
line.separator
noBannertrue
openejb.logger.external true
openejb.naming xbean
openejb.nobannertrue
org.apache.activeio.journal.active.lockMap:/home/oxseed/geronimo-tomcat6-javaee5-2.1.2/var/activemq/journal/control.dat
true
org.apache.catalina.STRICT_SERVLET_COMPLIANCE true
[jira] Updated: (GERONIMO-4243) EAR Deploy Error
[
https://issues.apache.org/jira/browse/GERONIMO-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
gennadibereshnoi updated GERONIMO-4243:
---
Summary: EAR Deploy Error (was: EJB Deploy Error)
EAR Deploy Error
Key: GERONIMO-4243
URL: https://issues.apache.org/jira/browse/GERONIMO-4243
Project: Geronimo
Issue Type: Sub-task
Security Level: public(Regular issues)
Components: console, deployment, Tomcat
Affects Versions: 2.1.2
Environment: Java
java.awt.graphicsenv sun.awt.X11GraphicsEnvironment
java.awt.printerjob sun.print.PSPrinterJob
java.class.path
/usr/local/geronimo/bin/server.jar
/usr/local/geronimo/bin/jpa.jar
java.class.version49.0
java.endorsed.dirs
/usr/local/geronimo/lib/endorsed
/usr/local/java/jre/lib/endorsed
java.ext.dirs
/usr/local/geronimo/lib/ext
/usr/local/java/jre/lib/ext
java.home /home/oxseed/jdk1.5.0_15/jre
java.io.tmpdir/home/oxseed/geronimo-tomcat6-javaee5-2.1.2/var/temp
java.library.path
/home/oxseed/jdk1.5.0_15/jre/lib/i386/server
/home/oxseed/jdk1.5.0_15/jre/lib/i386
/home/oxseed/jdk1.5.0_15/jre/../lib/i386
java.runtime.name Java(TM) 2 Runtime Environment, Standard Edition
java.runtime.version 1.5.0_15-b04
java.specification.name Java Platform API Specification
java.specification.vendor Sun Microsystems Inc.
java.specification.version1.5
java.util.prefs.PreferencesFactory
java.vendor- Sun Microsystems Inc.
java.vendor.url http://java.sun.com/
java.vendor.url.bug http://java.sun.com/cgi-bin/bugreport.cgi
java.version- 1.5.0_15
Virtual Machine
java.vm.info mixed mode
java.vm.name Java HotSpot(TM) Server VM
java.vm.specification.nameJava Virtual Machine Specification
java.vm.specification.vendor Sun Microsystems Inc.
java.vm.specification.version 1.0
java.vm.vendorSun Microsystems Inc.
java.vm.version 1.5.0_15-b04
Operating System
os.arch i386
os.name Linux
os.version2.6.16.33-xen
Sun
sun.arch.data.model 32
sun.boot.class.path
/usr/local/geronimo/lib/endorsed/yoko-spec-corba-1.0.jar
/usr/local/geronimo/lib/endorsed/yoko-rmi-spec-1.0.jar
/home/oxseed/jdk1.5.0_15/jre/lib/rt.jar
/home/oxseed/jdk1.5.0_15/jre/lib/i18n.jar
/home/oxseed/jdk1.5.0_15/jre/lib/sunrsasign.jar
/home/oxseed/jdk1.5.0_15/jre/lib/jsse.jar
/home/oxseed/jdk1.5.0_15/jre/lib/jce.jar
/home/oxseed/jdk1.5.0_15/jre/lib/charsets.jar
/home/oxseed/jdk1.5.0_15/jre/classes
sun.boot.library.path
/home/oxseed/jdk1.5.0_15/jre/lib/i386
sun.cpu.endianlittle
sun.cpu.isalist
sun.io.unicode.encoding UnicodeLittle
sun.java2d.fontpath
sun.os.patch.levelunknown
User
user.country US
user.dir /home/oxseed
user.home /home/oxseed
user.language en
user.name oxseed
user.timezone Europe/Berlin
user.variant
Etc
admin.disabledtrue
catalina.base /home/oxseed/geronimo-tomcat6-javaee5-2.1.2/var/catalina
catalina.home /home/oxseed/geronimo-tomcat6-javaee5-2.1.2/var/catalina
catalina.useNamingfalse
com.sun.management.jmxremote
com.sun.management.jmxremote.authenticate false
com.sun.management.jmxremote.port 8004
com.sun.management.jmxremote.ssl false
common.loader ${catalina.home}/lib ${catalina.home}/lib/*.jar
derby.storage.fileSyncTransactionLog true
derby.system.home /home/oxseed
duct tape
file.encoding ANSI_X3.4-1968
file.encoding.pkg sun.io
file.separator/
java.naming.factory.initial
org.apache.xbean.naming.global.GlobalContextManager
java.naming.factory.url.pkgs org.apache.xbean.naming
java.naming.provider.url rmi://0.0.0.0:1099
java.net.preferIPv4Stack true
java.rmi.server.RMIClassLoaderSpi
org.apache.geronimo.kernel.rmi.RMIClassLoaderSpiImpl
java.rmi.server.randomIDs true
java.security.ProviderSUN
javax.rmi.CORBA.PortableRemoteObjectClass
org.apache.yoko.rmi.impl.PortableRemoteObjectImpl
javax.rmi.CORBA.StubClass org.apache.yoko.rmi.impl.StubImpl
javax.rmi.CORBA.UtilClass org.apache.geronimo.corba.util.UtilDelegateImpl
javax.security.jacc.PolicyConfigurationFactory.provider
org.apache.geronimo.security.jacc.mappingprovider.GeronimoPolicyConfigurationFactory
javax.security.jacc.policy.provider
org.apache.geronimo.security.jacc.mappingprovider.GeronimoPolicy
javax.xml.soap.MessageFactory
org.apache.geronimo.webservices.saaj.GeronimoMessageFactory
javax.xml.soap.MetaFactory
org.apache.geronimo.webservices.saaj.GeronimoMetaFactory
javax.xml.soap.SOAPConnectionFactory
org.apache.geronimo.webservices.saaj.GeronimoSOAPConnectionFactory
javax.xml.soap.SOAPFactory
[jira] Updated: (GERONIMO-4243) EAR Deploy Error
[
https://issues.apache.org/jira/browse/GERONIMO-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
gennadibereshnoi updated GERONIMO-4243:
---
Priority: Blocker (was: Major)
EAR Deploy Error
Key: GERONIMO-4243
URL: https://issues.apache.org/jira/browse/GERONIMO-4243
Project: Geronimo
Issue Type: Sub-task
Security Level: public(Regular issues)
Components: console, deployment, Tomcat
Affects Versions: 2.1.2
Environment: Java
java.awt.graphicsenv sun.awt.X11GraphicsEnvironment
java.awt.printerjob sun.print.PSPrinterJob
java.class.path
/usr/local/geronimo/bin/server.jar
/usr/local/geronimo/bin/jpa.jar
java.class.version49.0
java.endorsed.dirs
/usr/local/geronimo/lib/endorsed
/usr/local/java/jre/lib/endorsed
java.ext.dirs
/usr/local/geronimo/lib/ext
/usr/local/java/jre/lib/ext
java.home /home/oxseed/jdk1.5.0_15/jre
java.io.tmpdir/home/oxseed/geronimo-tomcat6-javaee5-2.1.2/var/temp
java.library.path
/home/oxseed/jdk1.5.0_15/jre/lib/i386/server
/home/oxseed/jdk1.5.0_15/jre/lib/i386
/home/oxseed/jdk1.5.0_15/jre/../lib/i386
java.runtime.name Java(TM) 2 Runtime Environment, Standard Edition
java.runtime.version 1.5.0_15-b04
java.specification.name Java Platform API Specification
java.specification.vendor Sun Microsystems Inc.
java.specification.version1.5
java.util.prefs.PreferencesFactory
java.vendor- Sun Microsystems Inc.
java.vendor.url http://java.sun.com/
java.vendor.url.bug http://java.sun.com/cgi-bin/bugreport.cgi
java.version- 1.5.0_15
Virtual Machine
java.vm.info mixed mode
java.vm.name Java HotSpot(TM) Server VM
java.vm.specification.nameJava Virtual Machine Specification
java.vm.specification.vendor Sun Microsystems Inc.
java.vm.specification.version 1.0
java.vm.vendorSun Microsystems Inc.
java.vm.version 1.5.0_15-b04
Operating System
os.arch i386
os.name Linux
os.version2.6.16.33-xen
Sun
sun.arch.data.model 32
sun.boot.class.path
/usr/local/geronimo/lib/endorsed/yoko-spec-corba-1.0.jar
/usr/local/geronimo/lib/endorsed/yoko-rmi-spec-1.0.jar
/home/oxseed/jdk1.5.0_15/jre/lib/rt.jar
/home/oxseed/jdk1.5.0_15/jre/lib/i18n.jar
/home/oxseed/jdk1.5.0_15/jre/lib/sunrsasign.jar
/home/oxseed/jdk1.5.0_15/jre/lib/jsse.jar
/home/oxseed/jdk1.5.0_15/jre/lib/jce.jar
/home/oxseed/jdk1.5.0_15/jre/lib/charsets.jar
/home/oxseed/jdk1.5.0_15/jre/classes
sun.boot.library.path
/home/oxseed/jdk1.5.0_15/jre/lib/i386
sun.cpu.endianlittle
sun.cpu.isalist
sun.io.unicode.encoding UnicodeLittle
sun.java2d.fontpath
sun.os.patch.levelunknown
User
user.country US
user.dir /home/oxseed
user.home /home/oxseed
user.language en
user.name oxseed
user.timezone Europe/Berlin
user.variant
Etc
admin.disabledtrue
catalina.base /home/oxseed/geronimo-tomcat6-javaee5-2.1.2/var/catalina
catalina.home /home/oxseed/geronimo-tomcat6-javaee5-2.1.2/var/catalina
catalina.useNamingfalse
com.sun.management.jmxremote
com.sun.management.jmxremote.authenticate false
com.sun.management.jmxremote.port 8004
com.sun.management.jmxremote.ssl false
common.loader ${catalina.home}/lib ${catalina.home}/lib/*.jar
derby.storage.fileSyncTransactionLog true
derby.system.home /home/oxseed
duct tape
file.encoding ANSI_X3.4-1968
file.encoding.pkg sun.io
file.separator/
java.naming.factory.initial
org.apache.xbean.naming.global.GlobalContextManager
java.naming.factory.url.pkgs org.apache.xbean.naming
java.naming.provider.url rmi://0.0.0.0:1099
java.net.preferIPv4Stack true
java.rmi.server.RMIClassLoaderSpi
org.apache.geronimo.kernel.rmi.RMIClassLoaderSpiImpl
java.rmi.server.randomIDs true
java.security.ProviderSUN
javax.rmi.CORBA.PortableRemoteObjectClass
org.apache.yoko.rmi.impl.PortableRemoteObjectImpl
javax.rmi.CORBA.StubClass org.apache.yoko.rmi.impl.StubImpl
javax.rmi.CORBA.UtilClass org.apache.geronimo.corba.util.UtilDelegateImpl
javax.security.jacc.PolicyConfigurationFactory.provider
org.apache.geronimo.security.jacc.mappingprovider.GeronimoPolicyConfigurationFactory
javax.security.jacc.policy.provider
org.apache.geronimo.security.jacc.mappingprovider.GeronimoPolicy
javax.xml.soap.MessageFactory
org.apache.geronimo.webservices.saaj.GeronimoMessageFactory
javax.xml.soap.MetaFactory
org.apache.geronimo.webservices.saaj.GeronimoMetaFactory
javax.xml.soap.SOAPConnectionFactory
org.apache.geronimo.webservices.saaj.GeronimoSOAPConnectionFactory
javax.xml.soap.SOAPFactory
org.apache.geronimo.webservices.saaj.GeronimoSOAPFactory
line.separator
[jira] Commented: (GERONIMO-4243) EAR Deploy Error
[
https://issues.apache.org/jira/browse/GERONIMO-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12622556#action_12622556
]
Jarek Gawor commented on GERONIMO-4243:
---
What type of libraries are in the ear file? Can you send us the ear file?
You can bypass this problem by setting the following property before starting
the server:
export JAVA_OPTS=-Dorg.apache.geronimo.jaxws.builder.useSimpleFinder=true
EAR Deploy Error
Key: GERONIMO-4243
URL: https://issues.apache.org/jira/browse/GERONIMO-4243
Project: Geronimo
Issue Type: Sub-task
Security Level: public(Regular issues)
Components: console, deployment, Tomcat
Affects Versions: 2.1.2
Environment: Java
java.awt.graphicsenv sun.awt.X11GraphicsEnvironment
java.awt.printerjob sun.print.PSPrinterJob
java.class.path
/usr/local/geronimo/bin/server.jar
/usr/local/geronimo/bin/jpa.jar
java.class.version49.0
java.endorsed.dirs
/usr/local/geronimo/lib/endorsed
/usr/local/java/jre/lib/endorsed
java.ext.dirs
/usr/local/geronimo/lib/ext
/usr/local/java/jre/lib/ext
java.home /home/oxseed/jdk1.5.0_15/jre
java.io.tmpdir/home/oxseed/geronimo-tomcat6-javaee5-2.1.2/var/temp
java.library.path
/home/oxseed/jdk1.5.0_15/jre/lib/i386/server
/home/oxseed/jdk1.5.0_15/jre/lib/i386
/home/oxseed/jdk1.5.0_15/jre/../lib/i386
java.runtime.name Java(TM) 2 Runtime Environment, Standard Edition
java.runtime.version 1.5.0_15-b04
java.specification.name Java Platform API Specification
java.specification.vendor Sun Microsystems Inc.
java.specification.version1.5
java.util.prefs.PreferencesFactory
java.vendor- Sun Microsystems Inc.
java.vendor.url http://java.sun.com/
java.vendor.url.bug http://java.sun.com/cgi-bin/bugreport.cgi
java.version- 1.5.0_15
Virtual Machine
java.vm.info mixed mode
java.vm.name Java HotSpot(TM) Server VM
java.vm.specification.nameJava Virtual Machine Specification
java.vm.specification.vendor Sun Microsystems Inc.
java.vm.specification.version 1.0
java.vm.vendorSun Microsystems Inc.
java.vm.version 1.5.0_15-b04
Operating System
os.arch i386
os.name Linux
os.version2.6.16.33-xen
Sun
sun.arch.data.model 32
sun.boot.class.path
/usr/local/geronimo/lib/endorsed/yoko-spec-corba-1.0.jar
/usr/local/geronimo/lib/endorsed/yoko-rmi-spec-1.0.jar
/home/oxseed/jdk1.5.0_15/jre/lib/rt.jar
/home/oxseed/jdk1.5.0_15/jre/lib/i18n.jar
/home/oxseed/jdk1.5.0_15/jre/lib/sunrsasign.jar
/home/oxseed/jdk1.5.0_15/jre/lib/jsse.jar
/home/oxseed/jdk1.5.0_15/jre/lib/jce.jar
/home/oxseed/jdk1.5.0_15/jre/lib/charsets.jar
/home/oxseed/jdk1.5.0_15/jre/classes
sun.boot.library.path
/home/oxseed/jdk1.5.0_15/jre/lib/i386
sun.cpu.endianlittle
sun.cpu.isalist
sun.io.unicode.encoding UnicodeLittle
sun.java2d.fontpath
sun.os.patch.levelunknown
User
user.country US
user.dir /home/oxseed
user.home /home/oxseed
user.language en
user.name oxseed
user.timezone Europe/Berlin
user.variant
Etc
admin.disabledtrue
catalina.base /home/oxseed/geronimo-tomcat6-javaee5-2.1.2/var/catalina
catalina.home /home/oxseed/geronimo-tomcat6-javaee5-2.1.2/var/catalina
catalina.useNamingfalse
com.sun.management.jmxremote
com.sun.management.jmxremote.authenticate false
com.sun.management.jmxremote.port 8004
com.sun.management.jmxremote.ssl false
common.loader ${catalina.home}/lib ${catalina.home}/lib/*.jar
derby.storage.fileSyncTransactionLog true
derby.system.home /home/oxseed
duct tape
file.encoding ANSI_X3.4-1968
file.encoding.pkg sun.io
file.separator/
java.naming.factory.initial
org.apache.xbean.naming.global.GlobalContextManager
java.naming.factory.url.pkgs org.apache.xbean.naming
java.naming.provider.url rmi://0.0.0.0:1099
java.net.preferIPv4Stack true
java.rmi.server.RMIClassLoaderSpi
org.apache.geronimo.kernel.rmi.RMIClassLoaderSpiImpl
java.rmi.server.randomIDs true
java.security.ProviderSUN
javax.rmi.CORBA.PortableRemoteObjectClass
org.apache.yoko.rmi.impl.PortableRemoteObjectImpl
javax.rmi.CORBA.StubClass org.apache.yoko.rmi.impl.StubImpl
javax.rmi.CORBA.UtilClass org.apache.geronimo.corba.util.UtilDelegateImpl
javax.security.jacc.PolicyConfigurationFactory.provider
org.apache.geronimo.security.jacc.mappingprovider.GeronimoPolicyConfigurationFactory
javax.security.jacc.policy.provider
org.apache.geronimo.security.jacc.mappingprovider.GeronimoPolicy
javax.xml.soap.MessageFactory
org.apache.geronimo.webservices.saaj.GeronimoMessageFactory
javax.xml.soap.MetaFactory
Geronimo Futures - JSR 291 OSGi containers ?
Hi Rick, just saw your name on the wiki [1] JSR 291 OSGi containers ? - Rick McGuire Where are we starting? Just curious about it as we just added support in Axis2 to work well in OSGi containers [2] thanks, dims [1] http://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+Futures [2] http://markmail.org/message/dgl5b4xhosjskvue -- Davanum Srinivas :: http://davanum.wordpress.com
Re: Geronimo Futures
OK, I updated the page, as I had several errors on it and had misunderstood what several people were looking at -Donald Donald Woods wrote: Can everyone update the following wiki page with information on JEE6, JSRs or integration with other projects they are working on which would be considered post-2.2 items? http://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+Futures This will help other community members know who to talk to if they have questions regarding those areas or would like to assist. -Donald smime.p7s Description: S/MIME Cryptographic Signature
Re: Geronimo Futures
My goal was to help publicize what others in the community are working/looking at as we can keep lively discussions going on the mailing list. -Donald Jacek Laskowski wrote: On Wed, Aug 13, 2008 at 5:25 PM, Donald Woods [EMAIL PROTECTED] wrote: This will help other community members know who to talk to if they have questions regarding those areas or would like to assist. This drew my attention - shouldn't all questions be asked on mailing lists so those who are not blessed with technology could become at some point? Jacek smime.p7s Description: S/MIME Cryptographic Signature
Re: [DISCUSS] Release Geronimo Eclipse Plugin 2.1.2 (RC1)
Do we have any release notes for GEP 2.1.2, to denote what has changed? Like support for Ganymede, Java SE 6, additional deployment plan editors, replaced Download and Install a server feature with just a link to the Geronimo Server download page, JIRAs that were included, -Donald Tim McConnell wrote: smime.p7s Description: S/MIME Cryptographic Signature
[jira] Created: (GERONIMO-4244) Update to latest wadi 2.0-SNAPSHOT
Update to latest wadi 2.0-SNAPSHOT -- Key: GERONIMO-4244 URL: https://issues.apache.org/jira/browse/GERONIMO-4244 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: Clustering Affects Versions: 2.2 Reporter: Jason Warner Assignee: Jason Warner Priority: Minor Updating to the latest wadi snapshot to pick up some new functionality. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Geronimo Futures - JSR 291 OSGi containers ?
Hi Dims, I just updated the wiki page to correct some of the info I had put out there in a hurry the other day Rick is really just investigating OSGi (not a specific JSR) and can comment further on the specific areas -Donald Davanum Srinivas wrote: Hi Rick, just saw your name on the wiki [1] JSR 291 OSGi containers ? - Rick McGuire Where are we starting? Just curious about it as we just added support in Axis2 to work well in OSGi containers [2] thanks, dims [1] http://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+Futures [2] http://markmail.org/message/dgl5b4xhosjskvue smime.p7s Description: S/MIME Cryptographic Signature
Re: Geronimo Futures - JSR 291 OSGi containers ?
Davanum Srinivas wrote: Hi Rick, just saw your name on the wiki [1] JSR 291 OSGi containers ? - Rick McGuire Where are we starting? Just curious about it as we just added support in Axis2 to work well in OSGi containers [2] I'm afraid Don seriously overstated what I'm doing with OSGi right now. At the moment, all I'm doing is some personal education on how OSGi works, with an eye toward how Geronimo might function as a platform for hosting OSGi applications. This has involved reading a LOT of OSGi specifications and RFCs. I've not started any concrete work on this yet, and mostly trying to keep my head exploding from all of the information I've had to absorb lately. As for JSR 291I didn't even know there was a JSR on this until I read your email. I've definitely not been looking into that, though I might see if I can find a corner of my brain to fit that in as well. All of this investigation could result in some proposals for adding OSGi to Geronimo, but right now, I'm just trying to learn enough that I can participate in any conversations that might pop up. Rick thanks, dims [1] http://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+Futures [2] http://markmail.org/message/dgl5b4xhosjskvue
Re: [DISCUSS] Release Geronimo Eclipse Plugin 2.1.2 (RC1)
Also need to update trunk, which is still set to version=2.1.2. Is trunk going to become 2.1.3 or 2.2.0? If 2.2.0, then lets create a branches/2.1 for any future 2.1.3 bug fixes -Donald Tim McConnell wrote: smime.p7s Description: S/MIME Cryptographic Signature
[jira] Resolved: (GERONIMO-4240) Many connections in XATransactionTester are not closed
[ https://issues.apache.org/jira/browse/GERONIMO-4240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-4240. --- Resolution: Invalid Many connections in XATransactionTester are not closed -- Key: GERONIMO-4240 URL: https://issues.apache.org/jira/browse/GERONIMO-4240 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: testsuite Reporter: Hao Zhong As shown in the code snippets [1], many connections in XATransactionTester.run() are not closed. [1]http://www.google.com/codesearch?hl=enq=lang:java+getConnection+javax.sql.XAConnection+show:nbY4cjIv14c:E8MKX3dKMuE:JpztyHwM76Qsa=Nct=rxcd=10cs_p=http://archive.apache.org/dist/geronimo/1.0-M5/geronimo-1.0-M5-src.zipcs_f=geronimo-1.0-M5/modules/transaction/src/test/org/apache/geronimo/transaction/manager/XATransactionTester.javacs_p=http://archive.apache.org/dist/geronimo/1.0-M5/geronimo-1.0-M5-src.zipcs_f=geronimo-1.0-M5/modules/transaction/src/test/org/apache/geronimo/transaction/manager/XATransactionTester.java -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4245) Upgrade to Tomcat 6.0.18 to pickup latest security fixes
Upgrade to Tomcat 6.0.18 to pickup latest security fixes Key: GERONIMO-4245 URL: https://issues.apache.org/jira/browse/GERONIMO-4245 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: dependencies Affects Versions: 2.1.2, 2.1.1, 2.1, 2.0.2, 2.0.1, 2.0, 2.0.3, 2.1.3, 2.2 Reporter: Donald Woods Assignee: Donald Woods Priority: Critical Fix For: 2.0.3, 2.1.3, 2.2 Need to upgrade to Tomcat 6.0.18 to pickup the latest security fixes, as listed on the following Tomcat webpage - http://tomcat.apache.org/security-6.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4246) Upgrade 1.1 branch to Tomcat 5.5.27 to pickup latest security fixes
Upgrade 1.1 branch to Tomcat 5.5.27 to pickup latest security fixes --- Key: GERONIMO-4246 URL: https://issues.apache.org/jira/browse/GERONIMO-4246 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 1.1.2 Reporter: Donald Woods Fix For: 1.1.2 Several security fixes have been integrated into Tomcat 5.5.SVN (next release after 5.5.26) that we need to pull into a Geronimo 1.1.x snapshot build. See the following Tomcat webpage for more details - http://tomcat.apache.org/security-5.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Geronimo Futures - JSR 291 OSGi containers ?
Sounds good Rick. Am ready to pitch in when you are! :) -- dims On Thu, Aug 14, 2008 at 11:07 AM, Rick McGuire [EMAIL PROTECTED] wrote: Davanum Srinivas wrote: Hi Rick, just saw your name on the wiki [1] JSR 291 OSGi containers ? - Rick McGuire Where are we starting? Just curious about it as we just added support in Axis2 to work well in OSGi containers [2] I'm afraid Don seriously overstated what I'm doing with OSGi right now. At the moment, all I'm doing is some personal education on how OSGi works, with an eye toward how Geronimo might function as a platform for hosting OSGi applications. This has involved reading a LOT of OSGi specifications and RFCs. I've not started any concrete work on this yet, and mostly trying to keep my head exploding from all of the information I've had to absorb lately. As for JSR 291I didn't even know there was a JSR on this until I read your email. I've definitely not been looking into that, though I might see if I can find a corner of my brain to fit that in as well. All of this investigation could result in some proposals for adding OSGi to Geronimo, but right now, I'm just trying to learn enough that I can participate in any conversations that might pop up. Rick thanks, dims [1] http://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+Futures [2] http://markmail.org/message/dgl5b4xhosjskvue -- Davanum Srinivas :: http://davanum.wordpress.com
Re: [DISCUSS] Release Geronimo Eclipse Plugin 2.1.2 (RC1)
On Thu, Aug 14, 2008 at 10:46 AM, Donald Woods [EMAIL PROTECTED] wrote: Do we have any release notes for GEP 2.1.2, to denote what has changed? Like support for Ganymede, Java SE 6, additional deployment plan editors, replaced Download and Install a server feature with just a link to the Geronimo Server download page, JIRAs that were included, I like the idea of creating, packaging and shipping a release notes file. The about and/or license .html files might even point to the ibm-changes.txt file (which would mean bundling it in the updatesite and deployable .zip files) which would allow users to view them before downloading them. Ted -Donald Tim McConnell wrote:
Should GEP open the Geronimo console in a big external browser window instead of the small internal browser window in eclipse?
When running/interacting with a Geronimo server in eclipse using GEP, in the servers view there is a popup menu option of launching a console window. Currently, this console window opens inside eclipse, in a small internal window. I just recently discovered that is easy to have this console window open in the user's web browser. I think this option is preferable for users, but wanted to get community feedback before making the change. It would be good to get this change into GEP 212, but that window may be closed as it is out for vote. Ted Kirby
[jira] Created: (GERONIMO-4247) Maven Plugin Documentation Shows Outdated Configuration
Maven Plugin Documentation Shows Outdated Configuration
---
Key: GERONIMO-4247
URL: https://issues.apache.org/jira/browse/GERONIMO-4247
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: documentation
Affects Versions: 2.1.2
Reporter: Geoffrey Wiseman
The [usage
examples|http://geronimo.apache.org/maven/server/maven-plugins/geronimo-maven-plugin/usage/server.html]
for the Maven plugin documentation contain some awkward examples that make it
difficult to get started.
The group id of the plugin should now be {{org.apache.geronimo.buildsupport}}.
The {{geronimo-jetty-j2ee}} assembly should instead be
{{geronimo-jetty6-javaee5}}.
It'd be nice if it were a little more clear that the versions of the plugin and
assembly should be in synch and that these correspond to the version of
Geronimo in use, which would help when getting started with these for the first
time, particularly if you find yourself looking at an out-dated plugin or
assembly, as is the case when you follow the usage documentation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: svn commit: r685643 - in /geronimo/devtools/eclipse-plugin/trunk: ./ plugins/org.apache.geronimo.st.core/src/main/java/org/apache/geronimo/st/core/jaxb/ plugins/org.apache.geronimo.st.core/src/tes
On Aug 13, 2008, at 3:24 PM, [EMAIL PROTECTED] wrote: Author: mcconne Date: Wed Aug 13 12:24:11 2008 New Revision: 685643 URL: http://svn.apache.org/viewvc?rev=685643view=rev Log: GERONIMODEVTOOLS-468 Support Java 5 and 6 for both build-time and runtime Tim, Friendly reminder -- please include the contributor's name in your commit message when applying a patch. --kevan
Re: Should GEP open the Geronimo console in a big external browser window instead of the small internal browser window in eclipse?
On Thu, Aug 14, 2008 at 7:29 PM, Ted Kirby [EMAIL PROTECTED] wrote: When running/interacting with a Geronimo server in eclipse using GEP, in the servers view there is a popup menu option of launching a console window. Currently, this console window opens inside eclipse, in a small internal window. I just recently discovered that is easy to have this console window open in the user's web browser. I think this option is preferable for users, but wanted to get community feedback before making the change. It would be good to get this change into GEP 212, but that window may be closed as it is out for vote. I'd go for an configuration option so people could select what they prefer. Jacek -- Jacek Laskowski Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl
[ANN] GMaven 1.0-rc-3 Released
Its been a while, but its finally out. Read about it more here: http://groovy.codehaus.org/GMaven+-+1.0-rc-3+Release Will probably take a few hours to sync to central. I'm pushing out the new generated documentation now, which will take much longer I suspect. Cheers, --jason
daytrader
Hi, I saw Donald started a geronimo release for the rest of this year thread and it mentioned daytrader, so I thought I should update everyone on daytrader, before I forget them. Build - you should be able to build daytrader trunk without any error. It may require you to build 2.2 server first. The improvement of daytrader from the previous release is that now all the artifacts are also delivered in plugin format. Instead of deploying the ear file, you can install the daytrader plugins (there are five of them: db, jms, daytrader, ws-appclient and streamer-appclient). Because our c-m-p doesn't support appclient yet (GERONIMO-4221), the app client plugins are created slightly differently than the other plugins and a user has to update the plugin catalog file manually for app clients. Deploy install-plugin doesn't work for the app clients with 2.1.2 server but should be okay with 2.2 or 2.1.3 server. Lin
Axis2: Using CXF tooling instead of Sun tooling to generate WSDL
Hi, Right now, when using Axis2 as the JAX-WS provider, Geronimo will use Sun tooling (wsgen/wsimport) to generate the WSDL and other artifacts for the web service. That requires some Sun libraries to be distributed with Geronimo such as jaxws-rt.jar, jaxws-tools.jar, etc. I am wondering what people think if we switched Geronimo to use CXF tooling instead of Sun tooling (in Geronimo 2.2 only; assuming CXF tooling passes all the TCK tests (which it does AFAIK)). Jarek
[jira] Closed: (GERONIMO-4244) Update to latest wadi 2.0-SNAPSHOT
[ https://issues.apache.org/jira/browse/GERONIMO-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Warner closed GERONIMO-4244. -- Resolution: Fixed Fix Version/s: 2.2 committed in revision 686040 Update to latest wadi 2.0-SNAPSHOT -- Key: GERONIMO-4244 URL: https://issues.apache.org/jira/browse/GERONIMO-4244 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Clustering Affects Versions: 2.2 Reporter: Jason Warner Assignee: Jason Warner Priority: Minor Fix For: 2.2 Updating to the latest wadi snapshot to pick up some new functionality. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Axis2: Using CXF tooling instead of Sun tooling to generate WSDL
Hi, Do we have a feel about how stable is the CXF wsdl generation code, besides tck? I remember way back we decided we could not use Axis2's wsdl generation code as it didn't support annotation. Should we also look into where Axis2's wsdl generation code is now and assess if we should use Axis2's or CXF's? Lin On Thu, Aug 14, 2008 at 4:45 PM, Jarek Gawor [EMAIL PROTECTED] wrote: Hi, Right now, when using Axis2 as the JAX-WS provider, Geronimo will use Sun tooling (wsgen/wsimport) to generate the WSDL and other artifacts for the web service. That requires some Sun libraries to be distributed with Geronimo such as jaxws-rt.jar, jaxws-tools.jar, etc. I am wondering what people think if we switched Geronimo to use CXF tooling instead of Sun tooling (in Geronimo 2.2 only; assuming CXF tooling passes all the TCK tests (which it does AFAIK)). Jarek
Re: Geronimo releases for 3Q/4Q-2008
Wow this looks like lots of releases in a short timeframe. :) I wonder if we should merge daytrader into samples so save us from releasing one project... I kinda like this, as daytrader is a sample anyway. Lin On Wed, Aug 13, 2008 at 9:39 PM, Donald Woods [EMAIL PROTECTED] wrote: Want to get everyone starting to think about the releases we want for the rest of this year. Here is a potential list, to start the discussion 3Q08 - GEP - 2.1.2 - Support Ganymede and Java SE 6. Tim/BJ/Ted, we're close to a RC, right? Samples - 2.1.2 - Finish any last minute updates and release ASAP Daytrader - 2.1 - finally release a version for 2.1 Server - 2.1.3 - Release current patches and upgrade to Tomcat 6.0.18 to pickup latest security updates (and rev any other components that have released any security updates) 4Q08 - Server - 2.2 - http://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+2.2+Release+Roadmap Samples - 2.2 - target 30 days within 2.2 server release Daytrader - 2.2 - target 30 days within a 2.2 server release GEP - 2.2.0 - target 30-60 days within 2.2 server release The above and past releases are captured in the PMGT wiki at - http://cwiki.apache.org/confluence/display/GMOxPMGT/Apache+Geronimo+Release+Roadmaps Looking for feedback and people to volunteer as RMs... :-) If no one wants to step forward for the 2.1.3 Server, I'll volunteer, as long as I can get assistance from a prior RM (like Joe) to help me through my first release and for Jason/Jay/Joe to run the TCK. -Donald
Re: daytrader
On Aug 14, 2008, at 1:31 PM, Lin Sun wrote: Hi, I saw Donald started a geronimo release for the rest of this year thread and it mentioned daytrader, so I thought I should update everyone on daytrader, before I forget them. Build - you should be able to build daytrader trunk without any error. It may require you to build 2.2 server first. The improvement of daytrader from the previous release is that now all the artifacts are also delivered in plugin format. Instead of deploying the ear file, you can install the daytrader plugins (there are five of them: db, jms, daytrader, ws-appclient and streamer-appclient). Because our c-m-p doesn't support appclient yet (GERONIMO-4221), the app client plugins are created slightly differently than the other plugins and a user has to update the plugin catalog file manually for app clients. Deploy install-plugin doesn't work for the app clients with 2.1.2 server but should be okay with 2.2 or 2.1.3 server. It might be nice to extract the db2 and oracle plan info from the appropriate plans and create alternate db plugins for them with artifact-aliases so that switching back ends is as simple as installing one of these plugins. thanks david jencks Lin
Re: Geronimo releases for 3Q/4Q-2008
On Aug 14, 2008, at 2:18 PM, Lin Sun wrote: Wow this looks like lots of releases in a short timeframe. :) I wonder if we should merge daytrader into samples so save us from releasing one project... I kinda like this, as daytrader is a sample anyway. I think daytrader is dramatically different from all the other samples and is likely to need a release schedule different from them so I doubt this will make anything easier. I could see moving it under plugins (not server/trunk/plugins, but top level plugins). thanks david jencks Lin On Wed, Aug 13, 2008 at 9:39 PM, Donald Woods [EMAIL PROTECTED] wrote: Want to get everyone starting to think about the releases we want for the rest of this year. Here is a potential list, to start the discussion 3Q08 - GEP - 2.1.2 - Support Ganymede and Java SE 6. Tim/BJ/Ted, we're close to a RC, right? Samples - 2.1.2 - Finish any last minute updates and release ASAP Daytrader - 2.1 - finally release a version for 2.1 Server - 2.1.3 - Release current patches and upgrade to Tomcat 6.0.18 to pickup latest security updates (and rev any other components that have released any security updates) 4Q08 - Server - 2.2 - http://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+2.2+Release+Roadmap Samples - 2.2 - target 30 days within 2.2 server release Daytrader - 2.2 - target 30 days within a 2.2 server release GEP - 2.2.0 - target 30-60 days within 2.2 server release The above and past releases are captured in the PMGT wiki at - http://cwiki.apache.org/confluence/display/GMOxPMGT/Apache+Geronimo+Release+Roadmaps Looking for feedback and people to volunteer as RMs... :-) If no one wants to step forward for the 2.1.3 Server, I'll volunteer, as long as I can get assistance from a prior RM (like Joe) to help me through my first release and for Jason/Jay/Joe to run the TCK. -Donald
Re: svn commit: r686040 - /geronimo/server/trunk/pom.xml
On Thu, Aug 14, 2008 at 10:54 PM, [EMAIL PROTECTED] wrote: Author: jawarner Date: Thu Aug 14 13:54:03 2008 New Revision: 686040 URL: http://svn.apache.org/viewvc?rev=686040view=rev Log: GERONIMO-4244: Update to new wadi snapshot Modified: geronimo/server/trunk/pom.xml Modified: geronimo/server/trunk/pom.xml URL: http://svn.apache.org/viewvc/geronimo/server/trunk/pom.xml?rev=686040r1=686039r2=686040view=diff == --- geronimo/server/trunk/pom.xml (original) +++ geronimo/server/trunk/pom.xml Thu Aug 14 13:54:03 2008 @@ -82,7 +82,7 @@ plutoVersion1.1.6-G643117/plutoVersion openjpaVersion1.0.2/openjpaVersion xbeanVersion3.4.1/xbeanVersion -wadiVersion2.0/wadiVersion +wadiVersion2.0-SNAPSHOT/wadiVersion How can 2.0-SNAPSHOT be newer than 2.0? I'm a bit confused. Jacek -- Jacek Laskowski Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl
Re: svn commit: r685643 - in /geronimo/devtools/eclipse-plugin/trunk: ./ plugins/org.apache.geronimo.st.core/src/main/java/org/apache/geronimo/st/core/jaxb/ plugins/org.apache.geronimo.st.core/src/tes
Oh my fault. Will remember next time though Kevan Miller wrote: On Aug 13, 2008, at 3:24 PM, [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Author: mcconne Date: Wed Aug 13 12:24:11 2008 New Revision: 685643 URL: http://svn.apache.org/viewvc?rev=685643view=rev http://svn.apache.org/viewvc?rev=685643view=rev Log: GERONIMODEVTOOLS-468 Support Java 5 and 6 for both build-time and runtime Tim, Friendly reminder -- please include the contributor's name in your commit message when applying a patch. --kevan -- Thanks, Tim McConnell
[jira] Created: (GERONIMO-4248) dependency history
dependency history -- Key: GERONIMO-4248 URL: https://issues.apache.org/jira/browse/GERONIMO-4248 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: car-maven-plugin Affects Versions: 2.2 Reporter: David Jencks Assignee: David Jencks Fix For: 2.2 Make the car maven plugin compare the current build's plugin dependencies with what was there last time, saved in svn. Fail the build if it's changed, and output difference between now and then. This should make it a lot easier to turn on useMavenDependencies and not break stuff, and also pick up unwanted artifact changes. Current impl does this: - keeps historical dependencies in src/main/history/dependencies.xml - if the file is missing, it creates it with current dependency info - if the file is there, it compares with current dependency info and if it's changed writes out dependences.added.xml and dependencies.removed.xml - by default it fails on changes, although this can be turned off. - respects current useTransitiveDependencies flag setting. After checking in the plugin mods we'll need to build and check in all the new history files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r686040 - /geronimo/server/trunk/pom.xml
My bad, I was so used to release milestone releases that when I published 2.0 I simply forgot to move the snapshot version of WADI to 2.1. I am publishing 2.1-SNAPSHOT right now. Thanks, Gianny On 15/08/2008, at 7:34 AM, Jacek Laskowski wrote: On Thu, Aug 14, 2008 at 10:54 PM, [EMAIL PROTECTED] wrote: Author: jawarner Date: Thu Aug 14 13:54:03 2008 New Revision: 686040 URL: http://svn.apache.org/viewvc?rev=686040view=rev Log: GERONIMO-4244: Update to new wadi snapshot Modified: geronimo/server/trunk/pom.xml Modified: geronimo/server/trunk/pom.xml URL: http://svn.apache.org/viewvc/geronimo/server/trunk/pom.xml? rev=686040r1=686039r2=686040view=diff = = --- geronimo/server/trunk/pom.xml (original) +++ geronimo/server/trunk/pom.xml Thu Aug 14 13:54:03 2008 @@ -82,7 +82,7 @@ plutoVersion1.1.6-G643117/plutoVersion openjpaVersion1.0.2/openjpaVersion xbeanVersion3.4.1/xbeanVersion -wadiVersion2.0/wadiVersion +wadiVersion2.0-SNAPSHOT/wadiVersion How can 2.0-SNAPSHOT be newer than 2.0? I'm a bit confused. Jacek -- Jacek Laskowski Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl
Re: car-maven-plugin and useTransitiveDependenciestrue/useTransitiveDependencies
On Aug 13, 2008, at 3:16 PM, David Jencks wrote: On Aug 13, 2008, at 12:57 PM, Jarek Gawor wrote: On Wed, Aug 13, 2008 at 2:23 AM, David Jencks [EMAIL PROTECTED] wrote: I'm suggesting 2 things: 1. fix our dependencies so they are correct. This, by itself, will make useTransitiveDependencies=true work properly. Any problems such as unwanted inclusions are bugs that have a good chance of producing highly undesirable behavior in maven if they haven't already done so. 2. make the build-time classpath match the run-time classpath by using the cars to aggregate their dependencies in maven, just like they do in the running geronimo server. This should dramatically reduce the number of dependencies in most of the plugin poms. I agree that we should fix our DM so that build-time classpath matches the run-time classpath, however, the reality is that no one really maintains the DM. Things get very quickly out of date and we might end up pulling in stuff into server that we don't really need. My guess is that if we go ahead with the transitive dependencies a few days before the next release somebody will realize that the DM is messed up and try to fix it which will cause build or maybe even runtime errors. The point is that if we go ahead with the transitive deps we must pay much better attention to the DM and/or have better tools to catch the problems in the DM early. I suspect that we have this kind of problems today and don't know about them and also think that for the most part the reason we don't have more such problems is that I've made most of the dependency changes in all the plugin poms. This is too much for me to keep doing; we need a better system. IMO relying more on maven dependencies is the first step. Using maven dependency:analyze on framework modules is proving rather interesting and showing up some surprises. I think this might make the module poms reasonably accurate. For plugins, I had an idea that might help. We could have a mojo in c-m-p come up with a list of dependencies for the geronimo- plugin.xml and optionally save it in a file which we would commit to svn. In any case it would compare the current file with the existing file and if there is a difference either fail or emit a loud warning. If you want to change the output dependencies you'd have to update the file in svn. I've implemented this, see https://issues.apache.org/jira/browse/GERONIMO-4248 . I'm testing to see if the build can be done twice without failure, then will commit the history files or fix any problems that show up. What the new mojo does is like this (from the JIRA): * keeps historical dependencies in src/main/history/ dependencies.xml * if the file is missing, it creates it with current dependency info * if the file is there, it compares with current dependency info and if it's changed writes out dependences.added.xml and dependencies.removed.xml * by default it fails on changes, although this can be turned off. * respects current useTransitiveDependencies flag setting. The first time it runs it can't fail. If this causes problems we should be able to work around them by removing the history files with find . -name dependencies.xml|xargs rm thanks david jencks Anyone have any other ideas? Btw, does Maven support artifact substitution? E.g. substitute commons-logging-api with jcl104-over-slf4j or javax.activation with geronimo-activation_1.1_spec, etc.? Won't this also make the DM grow overall (even if we split it among the modules)? For example, virtually every library has a dependency on commons-logging or commons-logging-api so we will need to add an exclusion to each library. I don't know of such a feature thanks david jencks Jarek
[jira] Commented: (GERONIMO-4248) dependency history
[ https://issues.apache.org/jira/browse/GERONIMO-4248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12622751#action_12622751 ] David Jencks commented on GERONIMO-4248: rev 686088 and 686089 are c-m-p implementation. dependency history -- Key: GERONIMO-4248 URL: https://issues.apache.org/jira/browse/GERONIMO-4248 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: car-maven-plugin Affects Versions: 2.2 Reporter: David Jencks Assignee: David Jencks Fix For: 2.2 Make the car maven plugin compare the current build's plugin dependencies with what was there last time, saved in svn. Fail the build if it's changed, and output difference between now and then. This should make it a lot easier to turn on useMavenDependencies and not break stuff, and also pick up unwanted artifact changes. Current impl does this: - keeps historical dependencies in src/main/history/dependencies.xml - if the file is missing, it creates it with current dependency info - if the file is there, it compares with current dependency info and if it's changed writes out dependences.added.xml and dependencies.removed.xml - by default it fails on changes, although this can be turned off. - respects current useTransitiveDependencies flag setting. After checking in the plugin mods we'll need to build and check in all the new history 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-4249) Integrate jetty7 (servlet 3.0) with jaspi support
Integrate jetty7 (servlet 3.0) with jaspi support - Key: GERONIMO-4249 URL: https://issues.apache.org/jira/browse/GERONIMO-4249 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: Jetty Affects Versions: 2.2 Reporter: David Jencks Assignee: David Jencks Fix For: 2.2 I've been working on a jetty7 jaspi implementation and integrating this in geronimo. The main code is at https://svn.apache.org/repos/asf/geronimo/sandbox/djencks/jetty7 I'll attach a patch to the main build so the jetty7 plugins get used instead of the jetty6 plugins. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4249) Integrate jetty7 (servlet 3.0) with jaspi support
[ https://issues.apache.org/jira/browse/GERONIMO-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated GERONIMO-4249: --- Attachment: jetty-6-to-7.patch Patch to main build to make it use the sandbox jetty7 integration. Note you need the jetty jaspi branch from here... https://svn.codehaus.org/jetty/jetty/branches/jetty-7-jaspi Integrate jetty7 (servlet 3.0) with jaspi support - Key: GERONIMO-4249 URL: https://issues.apache.org/jira/browse/GERONIMO-4249 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: Jetty Affects Versions: 2.2 Reporter: David Jencks Assignee: David Jencks Fix For: 2.2 Attachments: jetty-6-to-7.patch I've been working on a jetty7 jaspi implementation and integrating this in geronimo. The main code is at https://svn.apache.org/repos/asf/geronimo/sandbox/djencks/jetty7 I'll attach a patch to the main build so the jetty7 plugins get used instead of the jetty6 plugins. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r686040 - /geronimo/server/trunk/pom.xml
I'll make the necessary change then. Thanks On Thu, Aug 14, 2008 at 7:40 PM, Gianny Damour [EMAIL PROTECTED] wrote: My bad, I was so used to release milestone releases that when I published 2.0 I simply forgot to move the snapshot version of WADI to 2.1. I am publishing 2.1-SNAPSHOT right now. Thanks, Gianny On 15/08/2008, at 7:34 AM, Jacek Laskowski wrote: On Thu, Aug 14, 2008 at 10:54 PM, [EMAIL PROTECTED] wrote: Author: jawarner Date: Thu Aug 14 13:54:03 2008 New Revision: 686040 URL: http://svn.apache.org/viewvc?rev=686040view=rev Log: GERONIMO-4244: Update to new wadi snapshot Modified: geronimo/server/trunk/pom.xml Modified: geronimo/server/trunk/pom.xml URL: http://svn.apache.org/viewvc/geronimo/server/trunk/pom.xml ?rev=686040r1=686039r2=686040view=diff == --- geronimo/server/trunk/pom.xml (original) +++ geronimo/server/trunk/pom.xml Thu Aug 14 13:54:03 2008 @@ -82,7 +82,7 @@ plutoVersion1.1.6-G643117/plutoVersion openjpaVersion1.0.2/openjpaVersion xbeanVersion3.4.1/xbeanVersion -wadiVersion2.0/wadiVersion +wadiVersion2.0-SNAPSHOT/wadiVersion How can 2.0-SNAPSHOT be newer than 2.0? I'm a bit confused. Jacek -- Jacek Laskowski Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl -- ~Jason Warner
Re: [DISCUSS] Release Geronimo Eclipse Plugin 2.1.2 (RC1)
Hi Donald, yes I failed to FTP them along with the GEP instructions. I also updated the instructions to reference them. I'll update our release process so that it doesn't happen for the next release. Thanks - http://people.apache.org/~mcconne/releases/2.1.2/RC1/PLUGIN_RELEASE-NOTES-2.1.2.txt Donald Woods wrote: Do we have any release notes for GEP 2.1.2, to denote what has changed? Like support for Ganymede, Java SE 6, additional deployment plan editors, replaced Download and Install a server feature with just a link to the Geronimo Server download page, JIRAs that were included, -Donald Tim McConnell wrote: -- Thanks, Tim McConnell
Re: Should GEP open the Geronimo console in a big external browser window instead of the small internal browser window in eclipse?
Hi Ted, I could go either way here. I tend to use the Eclipse Internal web browser although the screen size if severely limited in Eclipse. I would expect that end-users would like find the external browser more useful though. But maybe a preference option is the best way to go as Jacek suggests since it would satisfy those who prefer the internal browser, and those who don't. Ted Kirby wrote: When running/interacting with a Geronimo server in eclipse using GEP, in the servers view there is a popup menu option of launching a console window. Currently, this console window opens inside eclipse, in a small internal window. I just recently discovered that is easy to have this console window open in the user's web browser. I think this option is preferable for users, but wanted to get community feedback before making the change. It would be good to get this change into GEP 212, but that window may be closed as it is out for vote. Ted Kirby -- Thanks, Tim McConnell
Re: [VOTE] Release Geronimo Eclipse Plugin 2.1.2 (RC1)
+1 I installed GEP 2.1.2 via the staging update site, and successfully ran the 5-minute tutorial on the G 2.1.2 server, in these environments: 1. Europa on Windows with Java 5 2. Ganymede on Mac with Java 5 3. Ganymede on Mac with Java 6 Ted Kirby On Thu, Aug 14, 2008 at 4:41 AM, Tim McConnell [EMAIL PROTECTED] wrote: Hi everyone, Please review and vote on the maintenance release of the Geronimo Eclipse Plugin 2.1.2 RC1. The deployable zip file is here: http://people.apache.org/~mcconne/releases/2.1.2/RC1/geronimo-eclipse-plugin-2.1.2-deployable.zip The update site zip file is here: http://people.apache.org/~mcconne/releases/2.1.2/RC1/geronimo-eclipse-plugin-2.1.2-updatesite.zip The current svn location is here (revision number 685795): https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.1.2 The future svn location will be here (when approved): https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.1.2 There is a rudimentary set of install instructions available at the URL below that will hopefully describe the necessary prereq(s) and steps required to install and run the GEP: http://people.apache.org/~mcconne/releases/2.1.2/RC1/Geronimo_Eclipse_Plugin_2.1.2_Instructions-RC1.txt In an effort to get more people to review and vote I'd recommend going through this quick but useful tutorial demonstrating some of the capabilities of the GEP: http://cwiki.apache.org/GMOxDOC21/5-minute-tutorial-on-enterprise-application-development-with-eclipse-and-geronimo.html Additionally, there is an ant build.xml file that can be used to download the prereq(s) for the GEP. It is documented in the instructions. Finally, I've created a Staging Site that can used to test the update manager functions (i.e., p2 in Ganymede) of Eclipse for downloading the GEP itself. This is also documented in the instructions. Please let me know if there are any questions and/or problems. The vote is open over the weekend and will conclude on Monday (8/18) at Noon ET. [ ] +1 Release Geronimo Eclipse Plugin 2.1.2 [ ] +0 No opinion [ ] -1 Don't release Geronimo Eclipse Plugin 2.1.2 -- Thanks, Tim McConnell
Re: [VOTE] Release Geronimo Eclipse Plugin 2.1.2 (RC1)
+1 Tim McConnell wrote: Hi everyone, Please review and vote on the maintenance release of the Geronimo Eclipse Plugin 2.1.2 RC1. The deployable zip file is here: http://people.apache.org/~mcconne/releases/2.1.2/RC1/geronimo-eclipse-plugin-2.1.2-deployable.zip The update site zip file is here: http://people.apache.org/~mcconne/releases/2.1.2/RC1/geronimo-eclipse-plugin-2.1.2-updatesite.zip The current svn location is here (revision number 685795): https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.1.2 The future svn location will be here (when approved): https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.1.2 There is a rudimentary set of install instructions available at the URL below that will hopefully describe the necessary prereq(s) and steps required to install and run the GEP: http://people.apache.org/~mcconne/releases/2.1.2/RC1/Geronimo_Eclipse_Plugin_2.1.2_Instructions-RC1.txt In an effort to get more people to review and vote I'd recommend going through this quick but useful tutorial demonstrating some of the capabilities of the GEP: http://cwiki.apache.org/GMOxDOC21/5-minute-tutorial-on-enterprise-application-development-with-eclipse-and-geronimo.html Additionally, there is an ant build.xml file that can be used to download the prereq(s) for the GEP. It is documented in the instructions. Finally, I've created a Staging Site that can used to test the update manager functions (i.e., p2 in Ganymede) of Eclipse for downloading the GEP itself. This is also documented in the instructions. Please let me know if there are any questions and/or problems. The vote is open over the weekend and will conclude on Monday (8/18) at Noon ET. [ ] +1 Release Geronimo Eclipse Plugin 2.1.2 [ ] +0 No opinion [ ] -1 Don't release Geronimo Eclipse Plugin 2.1.2 -- Thanks, Tim McConnell -- Thanks, Tim McConnell
Re: Should GEP open the Geronimo console in a big external browser window instead of the small internal browser window in eclipse?
I don't have a strong preference either way, but do feel that this should go into a post-2.1.2 release, since it is already out for a vote. -Donald Ted Kirby wrote: When running/interacting with a Geronimo server in eclipse using GEP, in the servers view there is a popup menu option of launching a console window. Currently, this console window opens inside eclipse, in a small internal window. I just recently discovered that is easy to have this console window open in the user's web browser. I think this option is preferable for users, but wanted to get community feedback before making the change. It would be good to get this change into GEP 212, but that window may be closed as it is out for vote. Ted Kirby smime.p7s Description: S/MIME Cryptographic Signature
Re: [DISCUSS] Release Geronimo Eclipse Plugin 2.1.2 (RC1)
Per the GEP release process trunk is not updated until after the release is approved. See step #18: - http://cwiki.apache.org/confluence/pages/editpage.action?pageId=63893 Donald Woods wrote: Also need to update trunk, which is still set to version=2.1.2. Is trunk going to become 2.1.3 or 2.2.0? If 2.2.0, then lets create a branches/2.1 for any future 2.1.3 bug fixes -Donald Tim McConnell wrote: -- Thanks, Tim McConnell
[jira] Updated: (GERONIMO-4244) Update to latest wadi 2.1-SNAPSHOT
[ https://issues.apache.org/jira/browse/GERONIMO-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Warner updated GERONIMO-4244: --- Summary: Update to latest wadi 2.1-SNAPSHOT (was: Update to latest wadi 2.0-SNAPSHOT) updating to correct snapshot, committed in revision 686113 Update to latest wadi 2.1-SNAPSHOT -- Key: GERONIMO-4244 URL: https://issues.apache.org/jira/browse/GERONIMO-4244 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Clustering Affects Versions: 2.2 Reporter: Jason Warner Assignee: Jason Warner Priority: Minor Fix For: 2.2 Updating to the latest wadi snapshot to pick up some new functionality. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [DISCUSS] Release Geronimo Eclipse Plugin 2.1.2 (RC1)
That doesn't follow how we do server releases. Once a branch is created (like 2.1.2) the prior code location should be incremented. We need to update the GEP release process -Donald Tim McConnell wrote: Per the GEP release process trunk is not updated until after the release is approved. See step #18: - http://cwiki.apache.org/confluence/pages/editpage.action?pageId=63893 Donald Woods wrote: Also need to update trunk, which is still set to version=2.1.2. Is trunk going to become 2.1.3 or 2.2.0? If 2.2.0, then lets create a branches/2.1 for any future 2.1.3 bug fixes -Donald Tim McConnell wrote: smime.p7s Description: S/MIME Cryptographic Signature
Re: [VOTE] Release Geronimo Eclipse Plugin 2.1.2 (RC1)
+1 Just a couple of minor notes (maybe for future releases): 1) In Geronimo_Eclipse_Plugin_2.1.2_Instructions-RC1.txt maybe describe scenario #2 first and scenario #1 second. Seems to me like most people would install GEP using the staging site. 2) Since the instructions assume Ganymede maybe the 5-minute tutorial should be updated to also assume Ganymede. I've noticed a couple of differences between Ganymede and the screenshots in the tutorial. Jarek On Thu, Aug 14, 2008 at 4:41 AM, Tim McConnell [EMAIL PROTECTED] wrote: Hi everyone, Please review and vote on the maintenance release of the Geronimo Eclipse Plugin 2.1.2 RC1. The deployable zip file is here: http://people.apache.org/~mcconne/releases/2.1.2/RC1/geronimo-eclipse-plugin-2.1.2-deployable.zip The update site zip file is here: http://people.apache.org/~mcconne/releases/2.1.2/RC1/geronimo-eclipse-plugin-2.1.2-updatesite.zip The current svn location is here (revision number 685795): https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.1.2 The future svn location will be here (when approved): https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.1.2 There is a rudimentary set of install instructions available at the URL below that will hopefully describe the necessary prereq(s) and steps required to install and run the GEP: http://people.apache.org/~mcconne/releases/2.1.2/RC1/Geronimo_Eclipse_Plugin_2.1.2_Instructions-RC1.txt In an effort to get more people to review and vote I'd recommend going through this quick but useful tutorial demonstrating some of the capabilities of the GEP: http://cwiki.apache.org/GMOxDOC21/5-minute-tutorial-on-enterprise-application-development-with-eclipse-and-geronimo.html Additionally, there is an ant build.xml file that can be used to download the prereq(s) for the GEP. It is documented in the instructions. Finally, I've created a Staging Site that can used to test the update manager functions (i.e., p2 in Ganymede) of Eclipse for downloading the GEP itself. This is also documented in the instructions. Please let me know if there are any questions and/or problems. The vote is open over the weekend and will conclude on Monday (8/18) at Noon ET. [ ] +1 Release Geronimo Eclipse Plugin 2.1.2 [ ] +0 No opinion [ ] -1 Don't release Geronimo Eclipse Plugin 2.1.2 -- Thanks, Tim McConnell
Possible user code changes required when we upgrade to Tomcat 6.0.18
This is a notice to developers and users - I've run into several JSP files in our build (mainly the monitor webapp) that require code changes to work with Tomcat 6.0.18, due to tightened code around the JSP 2.0 spec in Jasper during the Tomcat 6.0.17 release. The build errors look something like - org.apache.jasper.JasperException: file:/Users/drwoods/geronimo/server-trunk/plugins/monitoring/mconsole-war/src/main/webapp/WEB-INF/view/monitoringEditView.jsp(168,168) Attribute value rs.getString(server_id) is quoted with which must be escaped when used within the value at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40) There are several places in the portlet code where we have - value=%=rs.getString(server_id)% which had to be changed to value='%=rs.getString(server_id)%' The full text of the Tomcat Jasper change can be found at - https://issues.apache.org/bugzilla/show_bug.cgi?id=45015 with the basic explanation being - According to JSP 2.0 specification (chapter 1.7 page 72,73) This code is illegal: mytags:tag value=%= hi! % / Instead the correct sentence would be: mytags:tag value='%= hi! %' / mytags:tag value=%= \hi!\ % / mytags:tag value='%= \name\ %' / ... -Donald smime.p7s Description: S/MIME Cryptographic Signature
Re: daytrader
Thanks for the reminder of the other databases - I've only used derby so far. Will look into building plugins for db2 and oracle, as you suggested below. Lin On Thu, Aug 14, 2008 at 5:27 PM, David Jencks [EMAIL PROTECTED] wrote: It might be nice to extract the db2 and oracle plan info from the appropriate plans and create alternate db plugins for them with artifact-aliases so that switching back ends is as simple as installing one of these plugins. thanks david jencks
[jira] Commented: (GERONIMO-4245) Upgrade to Tomcat 6.0.18 to pickup latest security fixes
[ https://issues.apache.org/jira/browse/GERONIMO-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12622804#action_12622804 ] Donald Woods commented on GERONIMO-4245: I've run into several JSP files in our build (mainly the monitor webapp) that require code changes to work with Tomcat 6.0.18, due to tightened code around the JSP 2.0 spec in Jasper during the Tomcat 6.0.17 release. The build errors look something like - org.apache.jasper.JasperException: file:/Users/drwoods/geronimo/server-trunk/plugins/monitoring/mconsole-war/src/main/webapp/WEB-INF/view/monitoringEditView.jsp(168,168) Attribute value rs.getString(server_id) is quoted with which must be escaped when used within the value at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40) There are several places in the portlet code where we have - value=%=rs.getString(server_id)% which had to be changed to value='%=rs.getString(server_id)%' The full text of the Tomcat Jasper change can be found at - https://issues.apache.org/bugzilla/show_bug.cgi?id=45015 with the basic explanation being - According to JSP 2.0 specification (chapter 1.7 page 72,73) This code is illegal: mytags:tag value=%= hi! % / Instead the correct sentence would be: mytags:tag value='%= hi! %' / mytags:tag value=%= \hi!\ % / mytags:tag value='%= \name\ %' / ... Upgrade to Tomcat 6.0.18 to pickup latest security fixes Key: GERONIMO-4245 URL: https://issues.apache.org/jira/browse/GERONIMO-4245 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: dependencies Affects Versions: 2.0, 2.0.1, 2.0.2, 2.0.3, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.2 Reporter: Donald Woods Assignee: Donald Woods Priority: Critical Fix For: 2.0.3, 2.1.3, 2.2 Need to upgrade to Tomcat 6.0.18 to pickup the latest security fixes, as listed on the following Tomcat webpage - http://tomcat.apache.org/security-6.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-4245) Upgrade to Tomcat 6.0.18 to pickup latest security fixes
[ https://issues.apache.org/jira/browse/GERONIMO-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12622806#action_12622806 ] Donald Woods commented on GERONIMO-4245: Trunk (2.2-SNAPSHOT) upgraded to Tomcat 6.0.18 with r686143 and r686146. Upgrade to Tomcat 6.0.18 to pickup latest security fixes Key: GERONIMO-4245 URL: https://issues.apache.org/jira/browse/GERONIMO-4245 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: dependencies Affects Versions: 2.0, 2.0.1, 2.0.2, 2.0.3, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.2 Reporter: Donald Woods Assignee: Donald Woods Priority: Critical Fix For: 2.0.3, 2.1.3, 2.2 Need to upgrade to Tomcat 6.0.18 to pickup the latest security fixes, as listed on the following Tomcat webpage - http://tomcat.apache.org/security-6.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Axis2: Using CXF tooling instead of Sun tooling to generate WSDL
I'm pretty confident in CXF tooling but not so much about Axis2. Sure, we can re-assess Axis2 tooling first. Is this something you can take a look at? Thanks, Jarek On Thu, Aug 14, 2008 at 5:13 PM, Lin Sun [EMAIL PROTECTED] wrote: Hi, Do we have a feel about how stable is the CXF wsdl generation code, besides tck? I remember way back we decided we could not use Axis2's wsdl generation code as it didn't support annotation. Should we also look into where Axis2's wsdl generation code is now and assess if we should use Axis2's or CXF's? Lin On Thu, Aug 14, 2008 at 4:45 PM, Jarek Gawor [EMAIL PROTECTED] wrote: Hi, Right now, when using Axis2 as the JAX-WS provider, Geronimo will use Sun tooling (wsgen/wsimport) to generate the WSDL and other artifacts for the web service. That requires some Sun libraries to be distributed with Geronimo such as jaxws-rt.jar, jaxws-tools.jar, etc. I am wondering what people think if we switched Geronimo to use CXF tooling instead of Sun tooling (in Geronimo 2.2 only; assuming CXF tooling passes all the TCK tests (which it does AFAIK)). Jarek
