RE: Geronimo Axis2 Integration
Hi Lasantha, This is great! Thanks. I have been also looking into Axis2 integration w/ G lately and started w/ the CXF integration code. The work I've done is similar as what you have, except that I also created config dir for axis2 and axis2-deployer. I'll submit that as a patch today. By looking at your patch, how did you get the jaxb generated code? I haven't been figured out how yet so I had planned to use the xmlbean generated code, similar as Axis1. Since there are some common code between CXF and Axis integration, I think it would be good to have one portInfo, parseWebServiceDescriptor at the Geronimo webservices level. Lin -Original Message- From: Lasantha Ranaweera [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 2:30 AM To: dev@geronimo.apache.org Subject: Geronimo Axis2 Integration Hi, The initial implementation of the Axis2 integration with Geronimo uploaded in to the JIRA (Geronimo-2717). Most of the source code is taken out from the CXF project of the Geronimo and it is only a maven2 skeleton. I am expecting some help from person who knows Axis2 to implement Axis2WebServiceContainer.java class and hoping to contribute Geronimo in this area. Thanks, Lasantha Ranaweera
RE: Geronimo Axis2 Integration
Hi Dims, that's cool! Do you think Axis2 will provide and build this generated code for Geronimo to use, similar as what CXF does? This way, we don't necessarily need the java code in Geronimo. Lin -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 11:25 AM To: dev@geronimo.apache.org Subject: Re: Geronimo Axis2 Integration Lin, We generated the jaxb code by hand since the SUN xsd's can't be checked in. -- dims On 1/10/07, Lin Sun [EMAIL PROTECTED] wrote: Hi Lasantha, This is great! Thanks. I have been also looking into Axis2 integration w/ G lately and started w/ the CXF integration code. The work I've done is similar as what you have, except that I also created config dir for axis2 and axis2-deployer. I'll submit that as a patch today. By looking at your patch, how did you get the jaxb generated code? I haven't been figured out how yet so I had planned to use the xmlbean generated code, similar as Axis1. Since there are some common code between CXF and Axis integration, I think it would be good to have one portInfo, parseWebServiceDescriptor at the Geronimo webservices level. Lin -Original Message- From: Lasantha Ranaweera [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 2:30 AM To: dev@geronimo.apache.org Subject: Geronimo Axis2 Integration Hi, The initial implementation of the Axis2 integration with Geronimo uploaded in to the JIRA (Geronimo-2717). Most of the source code is taken out from the CXF project of the Geronimo and it is only a maven2 skeleton. I am expecting some help from person who knows Axis2 to implement Axis2WebServiceContainer.java class and hoping to contribute Geronimo in this area. Thanks, Lasantha Ranaweera -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
[jira] Created: (GERONIMODEVTOOLS-119) import simple hello.war results xml-fragment tag in geronimo-web.xml
import simple hello.war results xml-fragment tag in geronimo-web.xml
Key: GERONIMODEVTOOLS-119
URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-119
Project: Geronimo-Devtools
Issue Type: Bug
Components: eclipse-plugin
Affects Versions: 1.2.0
Environment: patched created with latest trunk 480183
Reporter: Lin Sun
Tried to import a simple hello war file however after import the
geronimo-web.xml file contains xml-fragment tag which prevents the hello
project from being deployed to server. tried to print out the following var
plan in ImportDeploymentPlanOperation.java
plan = runtime.fixGeronimoWebSchema(planFile);
System.out.println(plan 1: + plan.toString());
Here's the printout:
plan 1: xml-fragment xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.1;
xmlns:sec=http://geronimo.apache.org/xml/ns/security-1.1;
xmlns:sys=http://geronimo.apache.org/xml/ns/deployment-1.1;
xmlns:web=http://geronimo.apache.org/xml/ns/j2ee/web-1.1;
sys:environment
sys:moduleId
sys:groupIdsamples/sys:groupId
sys:artifactIdcviewer/sys:artifactId
sys:version1.1/sys:version
sys:typewar/sys:type
/sys:moduleId
sys:dependencies/
sys:hidden-classes/
sys:non-overridable-classes/
/sys:environment
web:context-root/cviewer/web:context-root
/xml-fragment
Note this is not a valid plan.
I updated the following method in
org.apache.geronimo.st.v11.core.GeronimoRuntime and it is working now (for war
file).
public XmlObject fixGeronimoWebSchema(IFile plan) throws XmlException {
XmlObject xmlplan = getXmlObject(plan);
if (plan != null) {
SchemaConversionUtils.fixGeronimoSchema(xmlplan,
GerWebAppDocument.type.getDocumentElementName(),
GerWebAppType.type);
save(xmlplan, plan);
return xmlplan;
}
return null;
//return SchemaConversionUtils.fixGeronimoSchema(getXmlObject(plan),
GerWebAppDocument.type.getDocumentElementName(), GerWebAppType.type);
}
Also added the save method back from 1.0 to
org.apache.geronimo.st.v11.core.GeronimoRuntime:
private void save(XmlObject object, IFile file) {
try {
object.save(file.getLocation().toFile());
file.refreshLocal(IFile.DEPTH_ONE, null);
} catch (IOException e) {
e.printStackTrace();
} catch (CoreException e) {
e.printStackTrace();
}
}
Patch has been tested on importing war projects and worked well.
--
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-2369) Need to set db2 port to 50000 in the ra.xml for tranql db2 xa wrapper
Need to set db2 port to 5 in the ra.xml for tranql db2 xa wrapper - Key: GERONIMO-2369 URL: http://issues.apache.org/jira/browse/GERONIMO-2369 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: connector Affects Versions: 1.1 Environment: winxp Reporter: Lin Sun Priority: Minor In the ra.xml for the tranql db2 xa wrapper. it has: config-property description Specifies the port number the remote database server is listening on for incoming connections. The default for a DB2 server is 5. /description config-property-namePortNumber/config-property-name config-property-typejava.lang.Integer/config-property-type /config-property Since the default port for db2 server is 5, we should add the following line above the /config-property line. config-property-value5/config-property-value If this isn't added, and someone forgot to put a port when creating a db2 xa database pool, the pool will be unusable as it is defaulted to port 446. -- 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-2369) Need to set db2 port to 50000 in the ra.xml for tranql db2 xa wrapper
[ http://issues.apache.org/jira/browse/GERONIMO-2369?page=all ] Lin Sun updated GERONIMO-2369: -- Attachment: G2369.patch Need to set db2 port to 5 in the ra.xml for tranql db2 xa wrapper - Key: GERONIMO-2369 URL: http://issues.apache.org/jira/browse/GERONIMO-2369 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: connector Affects Versions: 1.1 Environment: winxp Reporter: Lin Sun Priority: Minor Attachments: G2369.patch In the ra.xml for the tranql db2 xa wrapper. it has: config-property description Specifies the port number the remote database server is listening on for incoming connections. The default for a DB2 server is 5. /description config-property-namePortNumber/config-property-name config-property-typejava.lang.Integer/config-property-type /config-property Since the default port for db2 server is 5, we should add the following line above the /config-property line. config-property-value5/config-property-value If this isn't added, and someone forgot to put a port when creating a db2 xa database pool, the pool will be unusable as it is defaulted to port 446. -- 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-2363) Console: create new pool using wizard, cannot use show plan button for any XA database, even derby
[
http://issues.apache.org/jira/browse/GERONIMO-2363?page=comments#action_12431340
]
Lin Sun commented on GERONIMO-2363:
---
The whole block of code doesn't seem to be needed. I've ran test without them
for create edit xa and non-xa pool they work fine.
This portion of deleted code is for generic pool, however the code resides in
the tag below.
c:when test=${pool.generic}
...
/c:when
c:otherwise %-- This is an XA or other connection factory that we don't have
special parameter handling for --%
... the code for generic pool was here which isn't correct.
/c:otherwise
Modified:
trunk/geronimo/applications/console-standard/src/webapp/WEB-INF/view/dbwizard/edit.jsp
===
td${ConfigParams[prop.key].description}/td
/tr
/c:forEach
- trtd colspan=2
-%-- Just to be safe, save all the Generic properties since we're not
going to edit them here --%
-input type=hidden name=user value=${pool.user} /
-input type=hidden name=password value=${pool.password} /
-input type=hidden name=driverClass value=${pool.driverClass} /
-input type=hidden name=url value=${pool.url} /
-input type=hidden name=jars value=${pool.jars} /
- /td/tr
/c:otherwise
/c:choose
!-- HEADER --
Console: create new pool using wizard, cannot use show plan button for any
XA database, even derby
Key: GERONIMO-2363
URL: http://issues.apache.org/jira/browse/GERONIMO-2363
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: console, databases
Affects Versions: 1.2, 1.1.1
Reporter: Ted Kirby
Attachments: dbwizard_edit.jsp.patch
From admin console, click Database Pools, Create new pool using the wizard,
choose an XA database type. If you select any driver jars, or none and click
show plan, you don't get a plan (all blank), but you do get this traceback in
the log/ on the console:
13:48:53,552 ERROR [DatabasePoolPortlet] Unable to save connection pool
java.lang.IllegalArgumentException: Invalid id:
at
org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java:49)
at
org.apache.geronimo.console.databasemanager.wizard.DatabasePoolPortlet.save(DatabasePoolPortlet.java:899)
at
org.apache.geronimo.console.databasemanager.wizard.DatabasePoolPortlet.processAction(DatabasePoolPortlet.java:340)
at
org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:229)
at
org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:163)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:615)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
at
org.apache.pluto.core.PortletServlet.service(PortletServlet.java:153)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
at
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574)
at
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499)
at
org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120)
at
org.apache.pluto.invoker.impl.PortletInvokerImpl.action(PortletInvokerImpl.java:68)
at
org.apache.pluto.PortletContainerImpl.processPortletAction(PortletContainerImpl.java:164)
at
org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.processPortletAction(PortletContainerWrapperImpl.java:82)
at org.apache.pluto.portalImpl.Servlet.doGet(Servlet.java:227)
at org.apache.pluto.portalImpl.Servlet.doPost(Servlet.java:267)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:615)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at
org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:52)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
at
org.apache.geronimo.tomcat.GeronimoStandardContext
[jira] Commented: (GERONIMODEVTOOLS-103) not able to get geronimo plan editor recognize openejb-jar.xml or geronimo-application.xml
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-103?page=comments#action_12429742 ] Lin Sun commented on GERONIMODEVTOOLS-103: -- After further investigation, the problem lies in that not able to get geronimo plan editor recognize openejb-jar.xml or geronimo-application.xml -- Key: GERONIMODEVTOOLS-103 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-103 Project: Geronimo-Devtools Issue Type: Bug Affects Versions: 1.1.0 Environment: Eclipse 3.2 and WTP 1.5 windows XP Reporter: Lin Sun I still have similar prob. The MDB openejb-jar.xml plan actually contains the fully qualified tags but it cannot be opened with the geornimo plan editor. Similar with a new openejb-jar.xml file created by default using the create new ejb project wizard. Is this also some code missed from 1.0? This was working in 1.0 from what I remember. -- 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: (GERONIMODEVTOOLS-103) not able to get geronimo plan editor recognize openejb-jar.xml or geronimo-application.xml
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-103?page=comments#action_12429744 ] Lin Sun commented on GERONIMODEVTOOLS-103: -- Sorry I hit enter by accident earlier. The problem lies in that deployment being null when fei.getFile() is a plan other than geronimo-web.xml, in the following code in AbstractGeronimoDeploymentPlanEditor. deploymentPlan = loadDeploymentPlan(fei.getFile()); I will supply a patch shortly. not able to get geronimo plan editor recognize openejb-jar.xml or geronimo-application.xml -- Key: GERONIMODEVTOOLS-103 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-103 Project: Geronimo-Devtools Issue Type: Bug Affects Versions: 1.1.0 Environment: Eclipse 3.2 and WTP 1.5 windows XP Reporter: Lin Sun I still have similar prob. The MDB openejb-jar.xml plan actually contains the fully qualified tags but it cannot be opened with the geornimo plan editor. Similar with a new openejb-jar.xml file created by default using the create new ejb project wizard. Is this also some code missed from 1.0? This was working in 1.0 from what I remember. -- 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: (GERONIMODEVTOOLS-103) not able to get geronimo plan editor recognize openejb-jar.xml or geronimo-application.xml
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-103?page=all ] Lin Sun updated GERONIMODEVTOOLS-103: - Attachment: devtools103.patch With the fix, I am able to open my mdb's openejb-jar.xml using the geronimo deployment plan editor. I am also able to open the newly created geornimo-application.xml and connector plan using the geronimo deployment plan editor. i tested with both 1.0 and 1.1 server. However, I am still not able to deploy my mdb jar file which I suspect is a WTP 1.5 prob. Whenever I right click on the project and do a run-run on server, I got a popup panel saying No launchable artifact could be found in the selection. I think I will open a eclipse wtp bugzilla on this unless Sachin feels differently. Lin not able to get geronimo plan editor recognize openejb-jar.xml or geronimo-application.xml -- Key: GERONIMODEVTOOLS-103 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-103 Project: Geronimo-Devtools Issue Type: Bug Affects Versions: 1.1.0 Environment: Eclipse 3.2 and WTP 1.5 windows XP Reporter: Lin Sun Attachments: devtools103.patch I still have similar prob. The MDB openejb-jar.xml plan actually contains the fully qualified tags but it cannot be opened with the geornimo plan editor. Similar with a new openejb-jar.xml file created by default using the create new ejb project wizard. Is this also some code missed from 1.0? This was working in 1.0 from what I remember. -- 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: (GERONIMODEVTOOLS-103) not able to get geronimo plan editor recognize openejb-jar.xml or geronimo-application.xml
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-103?page=comments#action_12429778 ] Lin Sun commented on GERONIMODEVTOOLS-103: -- You are right Sachin. WTP changes its behavior from 1.0.1 to 1.5. I always used run - run on server before. For the first time, I can get the mdb program to be deployed onto either 1.0 or 1.1 server, from within eclipse. not able to get geronimo plan editor recognize openejb-jar.xml or geronimo-application.xml -- Key: GERONIMODEVTOOLS-103 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-103 Project: Geronimo-Devtools Issue Type: Bug Affects Versions: 1.1.0 Environment: Eclipse 3.2 and WTP 1.5 windows XP Reporter: Lin Sun Attachments: devtools103.patch I still have similar prob. The MDB openejb-jar.xml plan actually contains the fully qualified tags but it cannot be opened with the geornimo plan editor. Similar with a new openejb-jar.xml file created by default using the create new ejb project wizard. Is this also some code missed from 1.0? This was working in 1.0 from what I remember. -- 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: (GERONIMODEVTOOLS-94) Importing archives with non qualified plans cannot be opened with the editor
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-94?page=all ] Lin Sun updated GERONIMODEVTOOLS-94: Attachment: devtools94.patch Patch has been tested on importing war projects. JAR project still doesn't want, but that is not because the import portion not working. Creating a new JAR project doesn't work either (devtools 103). Importing archives with non qualified plans cannot be opened with the editor Key: GERONIMODEVTOOLS-94 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-94 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 1.1.0 Environment: Windows XP + AG 1.1 + Devtools 1.1 Reporter: Lin Sun Assigned To: Sachin Patel Attachments: devtools94.patch This looks like a defect. I seem to have forgot to implement support for importing non-qualified plans for 1.1. (i.e Running SchemaConversionUtil on 1.1 plans). On Aug 1, 2006, at 3:00 PM, Lin Sun wrote: Hi there, Has anyone been able to running jar or ear from within eclipse using the devtools 1.1? I have a MDB sample (from confluence) and I managed to get it running using devtools 1.0 within eclipse. However, when I import my jar file in, the openejb-jar.xml cannot be read by the Geronimo application deployment plan editor. In the past experience, this is a pre-requisite before I can deploy anything to Geronimo server in Eclipse. I also tried to create a dummy EJB project and the default openejb-jar.xml cannot be opened by the Geronimo application deployment plan editor either. Similar prob with the EAR project. I am wondering if this is a known limitation of the 1.1 version of devtools project? Seems I can only get war project running... Thanks, Lin -- 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: (GERONIMODEVTOOLS-103) not able to get geronimo plan editor recognize openejb-jar.xml or geronimo-application.xml
not able to get geronimo plan editor recognize openejb-jar.xml or geronimo-application.xml -- Key: GERONIMODEVTOOLS-103 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-103 Project: Geronimo-Devtools Issue Type: Bug Affects Versions: 1.1.0 Environment: Eclipse 3.2 and WTP 1.5 windows XP Reporter: Lin Sun I still have similar prob. The MDB openejb-jar.xml plan actually contains the fully qualified tags but it cannot be opened with the geornimo plan editor. Similar with a new openejb-jar.xml file created by default using the create new ejb project wizard. Is this also some code missed from 1.0? This was working in 1.0 from what I remember. -- 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: (GERONIMODEVTOOLS-94) Importing archives with non qualified plans cannot be opened with the editor
[
http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-94?page=comments#action_12428561
]
Lin Sun commented on GERONIMODEVTOOLS-94:
-
The fix for devtools 94 doesn't work.
I tried to print out the following var plan in
ImportDeploymentPlanOperation.java
plan = runtime.fixGeronimoWebSchema(planFile);
System.out.println(plan 1: + plan.toString());
Here's the printout:
plan 1: xml-fragment xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.1;
xmlns:sec=http://geronimo.apache.org/xml/ns/security-1.1;
xmlns:sys=http://geronimo.apache.org/xml/ns/deployment-1.1;
xmlns:web=http://geronimo.apache.org/xml/ns/j2ee/web-1.1;
sys:environment
sys:moduleId
sys:groupIdsamples/sys:groupId
sys:artifactIdcviewer/sys:artifactId
sys:version1.1/sys:version
sys:typewar/sys:type
/sys:moduleId
sys:dependencies/
sys:hidden-classes/
sys:non-overridable-classes/
/sys:environment
web:context-root/cviewer/web:context-root
/xml-fragment
Note this is not a valid plan.
I updated the following method in
org.apache.geronimo.st.v11.core.GeronimoRuntime and it is working now (for war
file).
public XmlObject fixGeronimoWebSchema(IFile plan) throws XmlException {
XmlObject xmlplan = getXmlObject(plan);
if (plan != null) {
SchemaConversionUtils.fixGeronimoSchema(xmlplan,
GerWebAppDocument.type.getDocumentElementName(),
GerWebAppType.type);
save(xmlplan, plan);
return xmlplan;
}
return null;
//return SchemaConversionUtils.fixGeronimoSchema(getXmlObject(plan),
GerWebAppDocument.type.getDocumentElementName(), GerWebAppType.type);
}
Also added the save method back from 1.0 to
org.apache.geronimo.st.v11.core.GeronimoRuntime:
private void save(XmlObject object, IFile file) {
try {
object.save(file.getLocation().toFile());
file.refreshLocal(IFile.DEPTH_ONE, null);
} catch (IOException e) {
e.printStackTrace();
} catch (CoreException e) {
e.printStackTrace();
}
}
I 'll supply a patch for this tomorrow. This change needs to be applied for
other fixGeronimoXXXSchema method in GeronimoRuntime.java for both st.v1 and
st.v11.
Importing archives with non qualified plans cannot be opened with the editor
Key: GERONIMODEVTOOLS-94
URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-94
Project: Geronimo-Devtools
Issue Type: Bug
Components: eclipse-plugin
Affects Versions: 1.1.0
Environment: Windows XP + AG 1.1 + Devtools 1.1
Reporter: Lin Sun
Assigned To: Sachin Patel
This looks like a defect. I seem to have forgot to implement support for
importing non-qualified plans for 1.1. (i.e Running SchemaConversionUtil on
1.1 plans).
On Aug 1, 2006, at 3:00 PM, Lin Sun wrote:
Hi there,
Has anyone been able to running jar or ear from within eclipse using the
devtools 1.1?
I have a MDB sample (from confluence) and I managed to get it running using
devtools 1.0 within eclipse. However, when I import my jar file in, the
openejb-jar.xml cannot be read by the Geronimo application deployment plan
editor. In the past experience, this is a pre-requisite before I can deploy
anything to Geronimo server in Eclipse.
I also tried to create a dummy EJB project and the default openejb-jar.xml
cannot be opened by the Geronimo application deployment plan editor either.
Similar prob with the EAR project.
I am wondering if this is a known limitation of the 1.1 version of devtools
project? Seems I can only get war project running...
Thanks, Lin
--
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: (GERONIMODEVTOOLS-94) Importing archives with non qualified plans cannot be opened with the editor
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-94?page=comments#action_12428203 ] Lin Sun commented on GERONIMODEVTOOLS-94: - I still have similar prob. The MDB openejb-jar.xml plan actually contains the fully qualified tags but it cannot be opened with the geornimo plan editor. Similar with a new openejb-jar.xml file created by default using the create new ejb project wizard. Importing archives with non qualified plans cannot be opened with the editor Key: GERONIMODEVTOOLS-94 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-94 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 1.1.0 Environment: Windows XP + AG 1.1 + Devtools 1.1 Reporter: Lin Sun Assigned To: Sachin Patel This looks like a defect. I seem to have forgot to implement support for importing non-qualified plans for 1.1. (i.e Running SchemaConversionUtil on 1.1 plans). On Aug 1, 2006, at 3:00 PM, Lin Sun wrote: Hi there, Has anyone been able to running jar or ear from within eclipse using the devtools 1.1? I have a MDB sample (from confluence) and I managed to get it running using devtools 1.0 within eclipse. However, when I import my jar file in, the openejb-jar.xml cannot be read by the Geronimo application deployment plan editor. In the past experience, this is a pre-requisite before I can deploy anything to Geronimo server in Eclipse. I also tried to create a dummy EJB project and the default openejb-jar.xml cannot be opened by the Geronimo application deployment plan editor either. Similar prob with the EAR project. I am wondering if this is a known limitation of the 1.1 version of devtools project? Seems I can only get war project running... Thanks, Lin -- 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: (GERONIMODEVTOOLS-95) pim.xml still uses WTP 1.5.0
pim.xml still uses WTP 1.5.0 Key: GERONIMODEVTOOLS-95 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-95 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 1.1.0 Reporter: Lin Sun Priority: Minor The pom.xml at the root dir still uses: wtpUrlhttp://download.eclipse.org/webtools/downloads/drops/R1.5/R-1.5.0-200606281455/wtp-sdk-R-1.5.0-200606281455.zip/wtpUrl It should move to WTP 1.5.1 build ( for example: wtp-sdk-M-1.5.1-200608032139.zip), as WTP 1.5.1 is required for certain functions (devtools 93) checked in lately. -- 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: (GERONIMODEVTOOLS-96) Has to add xmlbeans as dependency in pom.xml to build devtools
Has to add xmlbeans as dependency in pom.xml to build devtools -- Key: GERONIMODEVTOOLS-96 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-96 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 1.1.0 Environment: WinXP + SUN JRE 1.4.2 Reporter: Lin Sun Attachments: devtools96.patch The new devtools change (devtools 94) uses classes from xmlbeans, however, the pom.xml isn't updated to reflect that yet. I had to add xmlbeans as a dependency in my plugins\org.apache.geronimo.st.core\pom.xml to build devtools successfully. -- 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: (GERONIMODEVTOOLS-97) Need to remove jetty and tomcat server dependency in assembly\pom.xml to build devtools.
Need to remove jetty and tomcat server dependency in assembly\pom.xml to build devtools. Key: GERONIMODEVTOOLS-97 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-97 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 1.1.0 Environment: WinXP + SUN 1.4.2 Reporter: Lin Sun Priority: Minor Attachments: devtools97.patch With the latest devtools 93 change, it is necessary to remove the jetty and tomcat server dependency in assembly\pom.xml. otherwise, devtools won't be able to build. -- 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: (GERONIMODEVTOOLS-94) cannot run jar or ear from within eclipse
cannot run jar or ear from within eclipse - Key: GERONIMODEVTOOLS-94 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-94 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 1.1.0 Environment: Windows XP + AG 1.1 + Devtools 1.1 Reporter: Lin Sun This looks like a defect. I seem to have forgot to implement support for importing non-qualified plans for 1.1. (i.e Running SchemaConversionUtil on 1.1 plans). On Aug 1, 2006, at 3:00 PM, Lin Sun wrote: Hi there, Has anyone been able to running jar or ear from within eclipse using the devtools 1.1? I have a MDB sample (from confluence) and I managed to get it running using devtools 1.0 within eclipse. However, when I import my jar file in, the openejb-jar.xml cannot be read by the Geronimo application deployment plan editor. In the past experience, this is a pre-requisite before I can deploy anything to Geronimo server in Eclipse. I also tried to create a dummy EJB project and the default openejb-jar.xml cannot be opened by the Geronimo application deployment plan editor either. Similar prob with the EAR project. I am wondering if this is a known limitation of the 1.1 version of devtools project? Seems I can only get war project running... Thanks, Lin -- 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: (GERONIMODEVTOOLS-94) cannot run jar or ear from within eclipse
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-94?page=comments#action_12425252 ] Lin Sun commented on GERONIMODEVTOOLS-94: - Thanks for the quick comments. Could you explain a bit more on Running SchemaConversionUtil on 1.1 plans? I searched SchemaConversionUtil of all the 1.1 plugins in my workspace, but no return. I also searched all of the 1.0 plugins, no return either. I assume this is something you implemented in 1.0 but forgot to port it in 1.1. Is that a good assumption? cannot run jar or ear from within eclipse - Key: GERONIMODEVTOOLS-94 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-94 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 1.1.0 Environment: Windows XP + AG 1.1 + Devtools 1.1 Reporter: Lin Sun This looks like a defect. I seem to have forgot to implement support for importing non-qualified plans for 1.1. (i.e Running SchemaConversionUtil on 1.1 plans). On Aug 1, 2006, at 3:00 PM, Lin Sun wrote: Hi there, Has anyone been able to running jar or ear from within eclipse using the devtools 1.1? I have a MDB sample (from confluence) and I managed to get it running using devtools 1.0 within eclipse. However, when I import my jar file in, the openejb-jar.xml cannot be read by the Geronimo application deployment plan editor. In the past experience, this is a pre-requisite before I can deploy anything to Geronimo server in Eclipse. I also tried to create a dummy EJB project and the default openejb-jar.xml cannot be opened by the Geronimo application deployment plan editor either. Similar prob with the EAR project. I am wondering if this is a known limitation of the 1.1 version of devtools project? Seems I can only get war project running... Thanks, Lin -- 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-2188) Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle
[ http://issues.apache.org/jira/browse/GERONIMO-2188?page=all ] Lin Sun updated GERONIMO-2188: -- Attachment: G2188.patch Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle Key: GERONIMO-2188 URL: http://issues.apache.org/jira/browse/GERONIMO-2188 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: connector Affects Versions: 1.1.1 Reporter: Krishnakumar B Assigned To: Donald Woods Attachments: G2188.patch We have to configure CommitBeforeAutCommit=true property exclusively in the database connection pool plan, to have the ejb -based transactions immediately committed for oracle database. Otherwise it only commits transaction when the server shuts-down. This problem is not faces with Derby database. -- 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-2188) Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle
[ http://issues.apache.org/jira/browse/GERONIMO-2188?page=comments#action_12421704 ] Lin Sun commented on GERONIMO-2188: --- Re Jenck's email: Yes with the generic tranql wrapper, setting the commitBeforeAutocommit to true would force the commit happen right away. However this commitBeforeAutocommit isn't available for tranql XA oracle wrapper. For Oracle wrapper's LocalMCF, I can just change: super(new OracleDataSource(), new OracleExceptionSorter(), false); to super(new OracleDataSource(), new OracleExceptionSorter(), true); However, for Oracle wrapper's XAMCF class, the parent class AbstractXADataSourceMCF's contructor only takes the first 2 parms. Here are two options I can think of: 1st option: add the boolean commitBeforeAutocommit parm into the AbstractXADataSourceMCF's contructor, which will also require changes to the localTransactionCommit method in ManagedXAConnection. Also all the other vendor wrappers (db2, derby, mysql) will have to be updated. 2nd option: create the OracleManagedXAConnection class that extends AbstractManagedConnection. I would vote for 1st option as we have a quite big number of buggy database vendors. What do you think? Lin Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle Key: GERONIMO-2188 URL: http://issues.apache.org/jira/browse/GERONIMO-2188 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: connector Affects Versions: 1.1.1 Reporter: Krishnakumar B Assigned To: Donald Woods We have to configure CommitBeforeAutCommit=true property exclusively in the database connection pool plan, to have the ejb -based transactions immediately committed for oracle database. Otherwise it only commits transaction when the server shuts-down. This problem is not faces with Derby database. -- 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: [Vote] Geronimo Eclipse Plugin v1.1.0
Hi Sachin, Ive tried the RC 4 or 5, and heres some feedback from me: 1) Simple jsp and servlet appears to be working with 1.1 server. 2) Simple jsp and servlet appears to be working with 1.0 server. 3) I started to have trouble with the tomcat-jsp 5.5.12-1 examples, as the deployment plan after import was not recognized by the Geronimo deployment plan editor. I have had similar prob in the past and the solution is a bit painful - covert the Geronimo-web.xml to whatever full qualified tags the plugin likes. (I posted a discussion on this a while back ago). 4) Is the release note avail? I can only find 1.0 release note. I 'd like to know the new functions in 1.1 besides the test environment option. 5) I don't see the update site package avail. I'd really like to see users being able to update from 1.0 plugin to 1.1's plugin via update manager. Lin -Original Message- From: Sachin Patel [mailto:[EMAIL PROTECTED] On Behalf Of Sachin Patel Sent: Tuesday, July 11, 2006 4:10 PM To: dev@geronimo.apache.org Subject: Re: [Vote] Geronimo Eclipse Plugin v1.1.0 FYI the current vote is on.. (breaking the all time software record on the number of release candidate drivers in one day) http://people.apache.org/dist/geronimo/eclipse/unstable/g-eclipse-plugin-1.1 -deployable-RC10.zip On Jul 11, 2006, at 1:48 PM, Sachin Patel wrote: done On Jul 11, 2006, at 1:24 PM, Lin Sun wrote: I just checked the g-eclipse-plugin-1.1-updatesite-RC5.zip file and only see Apache License there (not the full Apache 2.0 license) in all 3 features. It might be important to correct the license in these features as installing via update manager is the recommended method to install the Eclipse plugin. In Eclipse, user will have to accept the licenses in install panel before the Eclipse continues the installation. Lin -Original Message- From: Sachin Patel [mailto:[EMAIL PROTECTED] On Behalf Of Sachin Patel Sent: Tuesday, July 11, 2006 12:58 PM To: dev@geronimo.apache.org Subject: Re: [Vote] Geronimo Eclipse Plugin v1.1.0 Ok one last time hopefully... http://people.apache.org/dist/geronimo/eclipse/unstable/g-eclipse-plugin-1.1 -deployable-RC7.zip On Jul 11, 2006, at 10:03 AM, Sachin Patel wrote: [EMAIL PROTECTED] ok ignore rc6 On Jul 11, 2006, at 9:59 AM, Kevan Miller wrote: On Jul 11, 2006, at 8:41 AM, Sachin Patel wrote: On Jul 10, 2006, at 11:29 PM, Kevan Miller wrote: Sachin, At a minimum, you need to add: OpenEJB, MX4J, and XStream to the root LICENSE file Which root license file I you referring to? Do I just append each license to this? By root, I meant the notice and license files in g-eclipse-plugin-1-1/META-INF/. I actually don't think that they should be in the META-INF dir. I think you should end up with the following when you unzip: geronimo-eclipse-plugin-1-1/LICENSE geronimo-eclipse-plugin-1-1/NOTICE (both license and notice should either be .txt or have no suffix) geronimo-eclipse-plugin-1-1/plugins/... geronimo-eclipse-plugin-1-1/features/... The additional license and notice information should be appended to the ASL license and notice info. see geronimo/branches/modules/scripts/src/resources/LICENSE.txt and NOTICE.txt (you can just steal the appropriate sections from these files). Looks like some of the jar files are still missing LICENSE and NOTICE files. org.apache.geronimo.v11.deployment.model.edit_1.0.0.jar, for instance. --kevan MX4J, and XMLBeans to the root NOTICE file Again which root? Did you investigate Hessian licensing? Yeah its under Apache 1.0 I think, but could not find a copy of it on their site. I didn't find any licensing info (at first). So, took a look at the source. The first source file I looked at contained the following: /* * Copyright (c) 1998-2004 Caucho Technology -- all rights reserved * * This file is part of Resin(R) Open Source * * Each copy or derived work must preserve the copyright notice and this * notice unmodified. * * Resin Open Source is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation; either version 2 of the License, or * (at your option) any later version. * * Resin Open Source is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE, or any warranty * of NON-INFRINGEMENT. See the GNU General Public License for more * details. * * You should have received a copy of the GNU General Public License * along with Resin Open Source; if not, write to the * Free SoftwareFoundation, Inc. * 59 Temple Place, Suite 330 * Boston, MA 02111-1307 USA * * @author Scott Ferguson */ I now see the following statement on their wiki: Caucho Technology has released this Hessian implementation under an open source license (the Apache license). Anyone may freely download, use, and redistribute
[jira] Created: (GERONIMODEVTOOLS-91) WTP server adapters for geronimo needs to provide extensibility, like an OEM vendor.
WTP server adapters for geronimo needs to provide extensibility, like an OEM vendor. Key: GERONIMODEVTOOLS-91 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-91 Project: Geronimo-Devtools Type: New Feature Components: eclipse-plugin Versions: 1.1.0 Environment: all environments Reporter: Lin Sun The WTP server adapter for geronimo, also known as devtools project, needs to provide extensibility, like an OEM vendor so that other companies can build their additional plugins to brand Apache Geronimo to their companies' logo or name, with AG's eclipse plugins untouched.One example is that Eclipse allow other vendors to brand Eclipse, for example, you could configure a different splash screen. There are two things I see here, and there can be others that I am missing: 1) There is a geronimo-1.1 appended to the installation path after user clicks on the Download and Install button to download either the jetty or tomcat distribution. This is undesired. 2) There are two buttons (Jetty or Tomcat). It should be configurable as other companies may want to distribute jetty only, tomcat only or both. -- 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: [Vote] Geronimo Eclipse Plugin v1.1.0
I just checked the g-eclipse-plugin-1.1-updatesite-RC5.zip file and only see Apache License there (not the full Apache 2.0 license) in all 3 features. It might be important to correct the license in these features as installing via update manager is the recommended method to install the Eclipse plugin. In Eclipse, user will have to accept the licenses in install panel before the Eclipse continues the installation. Lin -Original Message- From: Sachin Patel [mailto:[EMAIL PROTECTED] On Behalf Of Sachin Patel Sent: Tuesday, July 11, 2006 12:58 PM To: dev@geronimo.apache.org Subject: Re: [Vote] Geronimo Eclipse Plugin v1.1.0 Ok one last time hopefully... http://people.apache.org/dist/geronimo/eclipse/unstable/g-eclipse-plugin-1.1-deployable-RC7.zip On Jul 11, 2006, at 10:03 AM, Sachin Patel wrote: [EMAIL PROTECTED] ok ignore rc6 On Jul 11, 2006, at 9:59 AM, Kevan Miller wrote: On Jul 11, 2006, at 8:41 AM, Sachin Patel wrote: On Jul 10, 2006, at 11:29 PM, Kevan Miller wrote: Sachin, At a minimum, you need to add: OpenEJB, MX4J, and XStream to the root LICENSE file Which root license file I you referring to? Do I just append each license to this? By root, I meant the notice and license files in g-eclipse-plugin-1-1/META-INF/. I actually don't think that they should be in the META-INF dir. I think you should end up with the following when you unzip: geronimo-eclipse-plugin-1-1/LICENSE geronimo-eclipse-plugin-1-1/NOTICE (both license and notice should either be .txt or have no suffix) geronimo-eclipse-plugin-1-1/plugins/... geronimo-eclipse-plugin-1-1/features/... The additional license and notice information should be appended to the ASL license and notice info. see geronimo/branches/modules/scripts/src/resources/LICENSE.txt and NOTICE.txt (you can just steal the appropriate sections from these files). Looks like some of the jar files are still missing LICENSE and NOTICE files.org.apache.geronimo.v11.deployment.model.edit_1.0.0.jar, for instance. --kevan MX4J, and XMLBeans to the root NOTICE file Again which root? Did you investigate Hessian licensing? Yeah its under Apache 1.0 I think, but could not find a copy of it on their site. I didn't find any licensing info (at first). So, took a look at the source. The first source file I looked at contained the following: /* * Copyright (c) 1998-2004 Caucho Technology -- all rights reserved * * This file is part of Resin(R) Open Source * * Each copy or derived work must preserve the copyright notice and this * notice unmodified. * * Resin Open Source is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation; either version 2 of the License, or * (at your option) any later version. * * Resin Open Source is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE, or any warranty * of NON-INFRINGEMENT. See the GNU General Public License for more * details. * * You should have received a copy of the GNU General Public License * along with Resin Open Source; if not, write to the * Free SoftwareFoundation, Inc. * 59 Temple Place, Suite 330 * Boston, MA 02111-1307 USA * * @author Scott Ferguson */ I now see the following statement on their wiki: Caucho Technology has released this Hessian implementation under an open source license (the Apache license). Anyone may freely download, use, and redistribute the Hessian implementation. But that's the strongest source of licensing info, that I've found... --kevan On Jul 10, 2006, at 10:42 PM, Sachin Patel wrote: Fixed. Re-vote. http://people.apache.org/dist/geronimo/eclipse/unstable/g-eclipse-plugin-1.1-deployable-RC5.zip http://people.apache.org/dist/geronimo/eclipse/unstable/g-eclipse-plugin-1.1-updatesite-RC5.zip (still uploading available shortly) On Jul 10, 2006, at 8:21 PM, Kevan Miller wrote: Sachin, I'm afraid I don't see either a NOTICE or LICENSE files in the plugin zip file, itself, nor any of the embedded jar files. They all must contain both LICENSE and NOTICE files. Afraid this is a hard requirement. And you'll need to create new binaries... See http://www.apache.org/dev/release.html#what-must-every-release-contain for more information. We should be able to reuse some of the license information we generated for G 1.1. I'm happy to help with that. I'm not sure how we're putting the NOTICE and LICENSE info
RE: Geronimo Eclipse Plugin FAQ
Hi Sachin, It is great that you put out the FAQ - we definitely need that! One question I'd like to get answered is: There are two checkboxes in the AG server configuration panel: Enable in-place deployment Run standalone modules directly from workspace. What's the difference between them? I understand the in-place deployment, same as the deploy.bat --inPlace option. I figure that if a user chooses in-Place deployment, the project would stay where they are and won't be deployed to the repo thus the user will run it directly from the eclipse workspace. Doesn't the second checkbox mean the same? Thanks, Lin -Original Message- From: Sachin Patel [mailto:[EMAIL PROTECTED] On Behalf Of Sachin Patel Sent: Sunday, July 09, 2006 8:37 PM To: dev@geronimo.apache.org Subject: Geronimo Eclipse Plugin FAQ I've started a eclipse plugin FAQ at http://cwiki.apache.org/confluence/display/GMOxDOC11/Geronimo+Eclipse +Plugin+FAQ
RE: [Vote] Geronimo Eclipse Plugin v1.1.0
I started to have problems in deploying my second application which I had it running with v1.0's plugin. It is a simple ClassViewer application that has a jsp and a servlet. The jsp calls the servlet when user clicks on the submit button to get the class description. Upon deployment of the application, I got the following CNP exception when the two checkboxes (Enable in-place deployment Run standalone modules directly from workspace) are checked: Caused by: java.lang.ClassNotFoundException: samples.cviewer.ClassViewerServlet in classloader samples/cviewer/1.1/war at java.lang.Throwable.init(Throwable.java:57) at java.lang.Throwable.init(Throwable.java:81) at java.lang.ClassNotFoundException.init(ClassNotFoundException.java:80) at org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClass(MultiPare ntClassLoader.java:249) at java.lang.ClassLoader.loadClass(ClassLoader.java:561) at org.apache.geronimo.tomcat.GeronimoStandardContext.addChild(GeronimoStandard Context.java:234) ... 84 more I have gotten this error before (https://bugs.eclipse.org/bugs/show_bug.cgi?id=123803) in v1.0 but I don't think this is the same prob as I had before this time. I noticed that in my project's .classpath file, I have: classpathentry path=build/classes kind=output/ However, I don't have the servlet class in that directory. I tried to update it to the path where the servlet class is located (ImportedClasses /samples/cviewer) but still the same error. I'll look into more of this but I thought I'd let everyone know since it is voting time of the plugin. P.S. Later on I discovered that the sample works fine when I don't have the two checkboxes checked. I can see the servlet and jsp in the good structure in the repo. Lin -Original Message- From: Sachin Patel [mailto:[EMAIL PROTECTED] On Behalf Of Sachin Patel Sent: Sunday, July 09, 2006 4:25 PM To: dev@geronimo.apache.org Subject: [Vote] Geronimo Eclipse Plugin v1.1.0 The following distributions of the Geronimo Eclipse plugin are ready to be voted on for final release. Since binding votes are needed, each PMC member if possible, please cast your vote within 72 hours. http://people.apache.org/dist/geronimo/eclipse/unstable/g-eclipse- plugin-1.1-deployable-RC4.zip http://people.apache.org/dist/geronimo/eclipse/unstable/g-eclipse- plugin-1.1-updatesite-RC4.zip Here is my +1. - sachin
RE: daytrader with Tranql Oracle XA resource adapter
Hi David, I am using daytrader direct mode and Synchronous order processing mode. From reading the daytrader code and adding some trace, the connection is obtained from the pool and connection.commit() is used to commit a buy or sell order.My guess is that the delayed (20+ minutes) committing behavior can be related to something unique with the Oracle jdbc driver or the fact that connection is obtained from the pool. Thoughts? Lin -Original Message- From: David Jencks [mailto:[EMAIL PROTECTED] Sent: Thursday, June 29, 2006 5:13 PM To: dev@geronimo.apache.org Subject: Re: daytrader with Tranql Oracle XA resource adapter On Jun 29, 2006, at 1:42 PM, Lin Sun wrote: Hi there, I have been playing with the daytrader with Tranql Oracle XA resource adapter (tranql-connector-oracle-xa-1.1.rar). After I tweaked the plan a bit and I am able to get daytrader running well with oracle! One thing I noticed is that if I perform any trading activities as a user (say uid:1, account_id 50), I get the message that my order has been completed almost immediately. However, the order isn't committed into the oracle database until quite a while. I don't know the exact timing but seems to be over 20-30 minutes. Here is what I did to check if the order is recorded in the database: Select * from orderejb where account_id=50; If the order is committed into the database, I would expect a row that represents my previous order to be returned as the output of the sql command. If I run the same scenario with db2 or derby, I can see my order recorded in the orderejb table immediately. I looked at the tranql oracle vendor code but I didn't see anywhere specifying the commit timing thing. The generic resource adapter does offer an param called CommitBeforeAutCommit and by setting it to true would force the commit to happen immediately. Can someone shed some light on this? Can you figure out what transaction demarcation is being used for this work? Is the connection supposed to be autocommit, is connection.commit() being used, or is there a JTA transaction? If it's autocommit, it might be worth investigating what connection.getAutocommit() says. thanks david jencks Thanks, Lin
daytrader with Tranql Oracle XA resource adapter
Hi there, I have been playing with the daytrader with Tranql Oracle XA resource adapter (tranql-connector-oracle-xa-1.1.rar). After I tweaked the plan a bit and I am able to get daytrader running well with oracle! One thing I noticed is that if I perform any trading activities as a user (say uid:1, account_id 50), I get the message that my order has been completed almost immediately. However, the order isn't committed into the oracle database until quite a while. I don't know the exact timing but seems to be over 20-30 minutes. Here is what I did to check if the order is recorded in the database: Select * from orderejb where account_id=50; If the order is committed into the database, I would expect a row that represents my previous order to be returned as the output of the sql command. If I run the same scenario with db2 or derby, I can see my order recorded in the orderejb table immediately. I looked at the tranql oracle vendor code but I didn't see anywhere specifying the commit timing thing. The generic resource adapter does offer an param called CommitBeforeAutCommit and by setting it to true would force the commit to happen immediately. Can someone shed some light on this? Thanks, Lin
RE: RELEASE-NOTES-1.1
Hi Aaron, I am trying to learn what the in-place deployment mean and how to use it. My understanding was that users can update the hot deploy files (for example, update one jsp file) in the Geronimo_home\deploy directory and server will redeploy the change automatically. This was not working in 1.0, as users need to replace the entire directory in the Geronimo_home\deploy directory. But after reading your note below, I think I am lost. Please advise. Lin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron Mulder Sent: Thursday, June 08, 2006 7:23 PM To: dev@geronimo.apache.org Subject: Re: RELEASE-NOTES-1.1 - We should add a point about in-place deployment. Geronimo supports in-place deployment, which means an archive or directory can be deployed without being copied into the Geronimo directory tree.
RE: RELEASE-NOTES-1.1
Good point! I shutdown the server and renamed the hello directory. Then start the server afterwards. I saw the following exception when server attempted to start the hello module. I didn't see Geronimo server started at the end but luckily all the important module seemed to be started before my little hello module, which is the last in var\config\config.xml file. Module 24/24 hello/1.1/war Exception in threa d main java.lang.AssertionError: Expected one match for pattern ., but got 0 matches at org.apache.geronimo.kernel.config.ConfigurationUtil.preprocessGBeanDa ta(ConfigurationUtil.java:331) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio nGBeans(ConfigurationUtil.java:359) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(Ke rnelConfigurationManager.java:187) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon figuration(SimpleConfigurationManager.java:512) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon figuration(SimpleConfigurationManager.java:493) at org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastCla ssByCGLIB$$ce77a924.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java(Inlined Compil ed Code)) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod Invoker.java(Compiled Code)) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio n.java(Inlined Compiled Code)) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance. java(Compiled Code)) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java(I nlined Compiled Code)) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperat ionInvoker.java(Compiled Code)) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(Pro xyMethodInterceptor.java(Compiled Code)) at org.apache.geronimo.kernel.config.EditableConfigurationManager$$Enhan cerByCGLIB$$f05707cd.startConfiguration(generated) at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:297) at org.apache.geronimo.system.main.Daemon.init(Daemon.java:74) at org.apache.geronimo.system.main.Daemon.main(Daemon.java:377) I guess this error can be improved in the future releases, but for 1.1 user needs to be good aware of what inPlace means before they use it for 1.1. I hope this is less of a problem for scenario #2, as I am not aware of the in-place option to deploy a project in Eclipse/WTP but Sachin can certainly correct me as I haven't tried the 1.1 version of the Eclipse plugins yet. Lin -Original Message- From: Donald Woods [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 13, 2006 3:12 PM To: dev@geronimo.apache.org Subject: Re: RELEASE-NOTES-1.1 What happens in the case that the files no longer exist on the next server startup? Two scenarios I'm worried about: 1) files were loaded from an NFS/Samba/SMB share which has become disconnected 2) Eclipse users who deploy the app into the server, test it, stop the server and then delete the project and files from Eclipse -Donald Aaron Mulder wrote: On 6/13/06, Lin Sun [EMAIL PROTECTED] wrote: I am trying to learn what the in-place deployment mean and how to use it. My understanding was that users can update the hot deploy files (for example, update one jsp file) in the Geronimo_home\deploy directory and server will redeploy the change automatically. This was not working in 1.0, as users need to replace the entire directory in the Geronimo_home\deploy directory. That should be true in both 1.0 and 1.1 (if not, I guess it's a bug). But in 1.1, there is a separate option, which is to not copy your files to the hot deploy directory at all, but instead use the deploy tool with a special option to enable an in-place deployment. This means that instead of copying your files into the server directory at all, it will deploy and access them from wherever they currently are. Thanks, Aaron But after reading your note below, I think I am lost. Please advise. Lin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron Mulder Sent: Thursday, June 08, 2006 7:23 PM To: dev@geronimo.apache.org Subject: Re: RELEASE-NOTES-1.1 - We should add a point about in-place deployment. Geronimo supports in-place deployment, which means an archive or directory can be deployed without being copied into the Geronimo directory tree.
RE: Please try out the upgrade jar
Hi David, The dependency tags for the the module ID of the server wide datasource in the Geronimo-web.xml were not required for 1.0, so it is unnatural for user to know they are required for 1.1. If the upgrader tool doesnt indicate that, user will just have to go figure that out by luck. One a second thought, I dont quite understand why we need to have the datasource as the dependency in 1.1 while we dont need it as the dependency in 1.0. The Geronimo-web.xml already has the ref-name and resource-link information within the resource-ref tags. Thanks, Lin -Original Message- From: David Jencks [mailto:[EMAIL PROTECTED] Sent: Friday, June 02, 2006 12:01 AM To: dev@geronimo.apache.org Subject: Re: Please try out the upgrade jar On Jun 1, 2006, at 7:56 PM, Song Scorpio wrote: I just tried the new upgrade.jar within server runtime, context-priority-classloader element is gone. But there's still no datasource dependency, which will cause failure of application deployment.. Do you think the upgrade tool should insert comments into every plan about likely problems such as this one about datasources? Since it's possible to resolve a resource-ref without a plan entry if the resource-ref uses the same name as the datasource plan, we'd have to look at the j2ee deployment descriptors to be sure whether or not a jndi ref was present. Looking into dds is beyond what I think the upgrade tool should be doing. However, adding comments always would be pretty easy to do, I didn't think to do it however. thanks david jencks 2006/6/2, Donald Woods [EMAIL PROTECTED]: How old is the upgrade.jar you are using? Noticed that your generated plan still has the old context-priority-classloader element in it. -Donald Zhang Song wrote: For an application which is using datasource, we should manually add dependency to deployment plan upgraded by the tool. The plan upgraded by the tool is following: - # web-app xmlns =* http://geronimo.apache.org/xml/ns/j2ee/web-1.0*; xmlns:naming =*http://geronimo.apache.org/xml/ns/naming-1.1*; xmlns:sec= * http://geronimo.apache.org/xml/ns/security-1.1*; xmlns:sys= *http://geronimo.apache.org/xml/ns/deployment-1.1* - # sys:environment - # sys:moduleId sys:groupIdSample/ sys:groupId sys:artifactIdEMPdemo/ sys:artifactId sys:version1.1/ sys:version sys:typecar/ sys:type /sys:moduleId sys:dependencies / sys:hidden-classes / sys:non-overridable-classes / /sys:environment context-root/EMPdemo/ context-root context-priority-classloaderfalse /context-priority-classloader - # naming:resource-ref naming:ref-namejdbc/DataSource /naming:ref-name naming:resource-linkSystemDatasource /naming:resource-link /naming:resource-ref /web-app But this upgraded plan will cause following error during deployment: -- Error: Unable to distribute EMPdemo-1.0.war: Unable to resolve resource reference 'jdbc/DataSource' (Could not find resource 'jdbc/EmployeeDatasource'. Perhaps it has not yet been configured, or your application does not have a dependency declared for that resource module?) -- After I add datasource's module reference to the upgraded plan, that application can be deployed successfully. -- - # sys:environment - # sys:moduleId sys:groupIdSample/ sys:groupId sys:artifactIdEMPdemo/ sys:artifactId sys:version1.1/ sys:version sys:typecar/ sys:type /sys:moduleId - # sys:dependencies - # sys:dependency sys:groupIdSample/ sys:groupId sys:artifactIdEmployeeDatasource /sys:artifactId sys:version1.1/ sys:version sys:typecar/ sys:type /sys:dependency /sys:dependencies sys:hidden-classes / sys:non-overridable-classes / /sys:environment context-root/EMPdemo/ context-root context-priority-classloaderfalse /context-priority-classloader - # naming:resource-ref naming:ref-namejdbc/DataSource /naming:ref-name naming:resource-linkjdbc/EmployeeDatasource /naming:resource-link /naming:resource-ref /web-app -- Could the upgrade tool add some comments to plan or give a warning to user when processing with datasource?
RE: Please try out the upgrade jar
Hi David, How are we supposed to run the latest upgrade tool now that it is a module inside of Geronimo? I am able to see the upgraded plan from admin console, but I haven't been able to get the latest upgrade tool by itself running. What I did was: E:\geronimo-1.1-SNAPSHOT\binjava -jar client.jar geronimo/upgrade-cli/1.1-SNAPSHOT java.lang.IllegalArgumentException: Invalid id: geronimo/upgrade-cli/1.1-SNAPSHOT at org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java:4 9) at org.apache.geronimo.system.main.ClientCommandLine.main(ClientCommandL ine.java:46) I also tried to execute deploy.bat start geronimo/upgrade/1.1-SNAPSHOT/car before it, but it didn't make any difference. Thanks, Lin -Original Message- From: David Jencks [mailto:[EMAIL PROTECTED] Sent: Monday, May 29, 2006 1:36 PM To: dev@geronimo.apache.org Subject: Re: Please try out the upgrade jar Toby, Thanks for pointing this out. I've fixed it in 1.1, will port to trunk soon. See http://issues.apache.org/jira/browse/GERONIMO-2068 thanks david jencks On May 26, 2006, at 3:29 PM, toby cabot wrote: David, Thanks for providing this tool, it's a big help. I had some problems on a test geronimo-application.xml file that includes some gbean references (for hooking up to security gbeans). The file looks like: = ?xml version=1.0 ? application xmlns=http://geronimo.apache.org/xml/ns/j2ee/ application configId=hello parentId=geronimo/j2ee-security/1.0.1-SNAPSHOT/car gbean name=hello-realm class=org.apache.geronimo.security.realm.GenericSecurityRealm attribute name=realmNamehello-realm/attribute reference name=LoginModuleConfiguration namehello-login-chain/name /reference reference name=ServerInfo gbean- namegeronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee- system/1.0.1-SNAPSHOT/ car,J2EEServer=geronimo,j2eeType=GBean,name=ServerInfo/gbean-name /reference reference name=LoginService gbean- namegeronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee- security/1.0.1-SNAPSHOT/ car,J2EEServer=geronimo,j2eeType=JaasLoginService,name=JaasLoginServic e/gbean-name /reference /gbean gbean name=hello-login-chain class=org.apache.geronimo.security.jaas.JaasLoginModuleUse attribute name=controlFlagREQUIRED/attribute reference name=LoginModule namehello-login/name /reference /gbean gbean name=hello-login class=org.apache.geronimo.security.jaas.LoginModuleGBean attribute name=loginModuleClassreva.common.auth.TrivialLoginModule/ attribute attribute name=serverSidetrue/attribute attribute name=options usersURI=var/security/demo_users.properties groupsURI=var/security/demo_groups.properties /attribute attribute name=loginDomainNamehello-realm/attribute /gbean /application = The problem seems to be the application/gbean/reference/gbean-name elements, as the error I get at offline deploy time looks like: Deployer operation failed: org.apache.xmlbeans.XmlException: Invalid deployment descriptor: [error: cvc-complex-type.2.4a: Expected elements '[EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1' instead of '[EMAIL PROTECTED]://geronimo.apache.org/ xml/ns/deployment-1.1' here in element [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.1, error: cvc-complex-type. 2.4a: Expected elements '[EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1' instead of '[EMAIL PROTECTED]://geronimo.apache.org/ xml/ns/deployment-1.1' here in element [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.1] Descriptor: xml-fragment xmlns:dep=http://geronimo.apache.org/xml/ ns/deployment-1.1 dep:environment dep:moduleId dep:groupIddefault/dep:groupId dep:artifactIdhello/dep:artifactId dep:version1-default/dep:version dep:typecar/dep:type /dep:moduleId dep:dependencies dep:dependency dep:groupIdgeronimo/dep:groupId dep:artifactIdj2ee-security/dep:artifactId
RE: Please try out the upgrade jar
Thanks, that worked very well! -Original Message- From: Donald Woods [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 31, 2006 4:48 PM To: dev@geronimo.apache.org Subject: Re: Please try out the upgrade jar E:\geronimo-1.1-SNAPSHOT\binjava -jar upgrade.jar Parameter usage: inputPlan outputPlan or inputPlan in which case the output will be in the same location as inputPlan with '.upgraded' appended Lin Sun wrote: Hi David, How are we supposed to run the latest upgrade tool now that it is a module inside of Geronimo? I am able to see the upgraded plan from admin console, but I haven't been able to get the latest upgrade tool by itself running. What I did was: E:\geronimo-1.1-SNAPSHOT\binjava -jar client.jar geronimo/upgrade-cli/1.1-SNAPSHOT java.lang.IllegalArgumentException: Invalid id: geronimo/upgrade-cli/1.1-SNAPSHOT at org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java:4 9) at org.apache.geronimo.system.main.ClientCommandLine.main(ClientCommandL ine.java:46) I also tried to execute deploy.bat start geronimo/upgrade/1.1-SNAPSHOT/car before it, but it didn't make any difference. Thanks, Lin -Original Message- From: David Jencks [mailto:[EMAIL PROTECTED] Sent: Monday, May 29, 2006 1:36 PM To: dev@geronimo.apache.org Subject: Re: Please try out the upgrade jar Toby, Thanks for pointing this out. I've fixed it in 1.1, will port to trunk soon. See http://issues.apache.org/jira/browse/GERONIMO-2068 thanks david jencks On May 26, 2006, at 3:29 PM, toby cabot wrote: David, Thanks for providing this tool, it's a big help. I had some problems on a test geronimo-application.xml file that includes some gbean references (for hooking up to security gbeans). The file looks like: = ?xml version=1.0 ? application xmlns=http://geronimo.apache.org/xml/ns/j2ee/ application configId=hello parentId=geronimo/j2ee-security/1.0.1-SNAPSHOT/car gbean name=hello-realm class=org.apache.geronimo.security.realm.GenericSecurityRealm attribute name=realmNamehello-realm/attribute reference name=LoginModuleConfiguration namehello-login-chain/name /reference reference name=ServerInfo gbean- namegeronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee- system/1.0.1-SNAPSHOT/ car,J2EEServer=geronimo,j2eeType=GBean,name=ServerInfo/gbean-name /reference reference name=LoginService gbean- namegeronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee- security/1.0.1-SNAPSHOT/ car,J2EEServer=geronimo,j2eeType=JaasLoginService,name=JaasLoginServic e/gbean-name /reference /gbean gbean name=hello-login-chain class=org.apache.geronimo.security.jaas.JaasLoginModuleUse attribute name=controlFlagREQUIRED/attribute reference name=LoginModule namehello-login/name /reference /gbean gbean name=hello-login class=org.apache.geronimo.security.jaas.LoginModuleGBean attribute name=loginModuleClassreva.common.auth.TrivialLoginModule/ attribute attribute name=serverSidetrue/attribute attribute name=options usersURI=var/security/demo_users.properties groupsURI=var/security/demo_groups.properties /attribute attribute name=loginDomainNamehello-realm/attribute /gbean /application = The problem seems to be the application/gbean/reference/gbean-name elements, as the error I get at offline deploy time looks like: Deployer operation failed: org.apache.xmlbeans.XmlException: Invalid deployment descriptor: [error: cvc-complex-type.2.4a: Expected elements '[EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1' instead of '[EMAIL PROTECTED]://geronimo.apache.org/ xml/ns/deployment-1.1' here in element [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.1, error: cvc-complex-type. 2.4a: Expected elements '[EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1' instead of '[EMAIL PROTECTED]://geronimo.apache.org/ xml/ns/deployment-1.1' here in element [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.1] Descriptor: xml-fragment
[jira] Commented: (GERONIMODEVTOOLS-79) wtp adapter doesnt work with wtp 1.5rc1a
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-79?page=comments#action_12412529 ] Lin Sun commented on GERONIMODEVTOOLS-79: - This bug is reported to WTP 1.5, as a hot bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=141850 wtp adapter doesnt work with wtp 1.5rc1a Key: GERONIMODEVTOOLS-79 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-79 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Versions: 1.0.0 Environment: windows xp x86 Reporter: Panagiotis Korros Priority: Critical The geronimo plugin 1.0 gives me this error when i try to publish a project using wtp 1.5rc1a. java.lang.NoSuchMethodError: org.eclipse.wst.common.frameworks.datamodel.IDataModel.getDefaultOperation()Lorg/eclipse/wst/common/frameworks/datamodel/IDataModelOperation; at org.apache.geronimo.core.DeploymentUtils.createJarFile(DeploymentUtils.java:73) at org.apache.geronimo.core.commands.DistributeCommand.execute(DistributeCommand.java:43) at org.apache.geronimo.core.commands.SynchronizedDeploymentOp.run(SynchronizedDeploymentOp.java:77) at org.apache.geronimo.core.commands.SynchronizedDeploymentOp.execute(SynchronizedDeploymentOp.java:69) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.distribute(GeronimoServerBehaviour.java:337) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doDeploy(GeronimoServerBehaviour.java:258) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeCommand(GeronimoServerBehaviour.java:230) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModule(GeronimoServerBehaviour.java:214) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:672) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:752) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:610) at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:800) at org.eclipse.wst.server.core.internal.Server.publish(Server.java:788) at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:145) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58) -- 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: How do we build/run the latest Eclipse plug-in?
Hi Sachin, I am getting the same error when I tried to build the eclipse-plugin from trunk. I was hoping that I could run it as a second Eclipse instance using the runtime-workspace, so I tried to import all plugins and fragments into the workspace of my Eclipse , but saw many red errors related to the project cannot be built until the build path error is resolved. So how should we build it? Are you running this using Eclipse 3.2 and WTP 1.5 RCs? Thanks, Lin -Original Message- From: Donald Woods [mailto:[EMAIL PROTECTED] Sent: Thursday, May 11, 2006 10:23 AM To: dev@geronimo.apache.org Subject: How do we build the latest Eclipse plug-in? How are we supposed to build the latest source from - geronimo/devtools/eclipse-plugin/trunk There are no instruction on the Geronimo Subprojects - Devtools section, so I tried running a Maven build (using 2.0.4) from the trunk directory since there only exists a pom.xml now, by just running - mvn but it fails with the following - [INFO] Scanning for projects... Downloading: http://repo1.maven.org/maven2/org/apache/geronimo/devtools/eclipse- plugins-parent/1.0/eclipse-plugins-parent-1.0.pom [WARNING] Unable to get resource from repository central (http://repo1.maven.org /maven2) [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.apache.geronimo.devtools ArtifactId: eclipse-plugins-parent Version: 1.0 Reason: Unable to download the artifact from any repository org.apache.geronimo.devtools:eclipse-plugins-parent:pom:1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Cannot find parent: org.apache .geronimo.devtools:eclipse-plugins-parent for project: org.apache.geronimo.devto ols:config-store-service:jar:1.0 at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent : org.apache.geronimo.devtools:eclipse-plugins-parent for project: org.apache.ge ronimo.devtools:config-store-service:jar:1.0 at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(D efaultMavenProjectBuilder.java:1161) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Def aultMavenProjectBuilder.java:674) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFi leInternal(DefaultMavenProjectBuilder.java:416) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMave nProjectBuilder.java:192) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:491) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351) ... 11 more Caused by: org.apache.maven.project.ProjectBuildingException: POM 'org.apache.ge ronimo.devtools:eclipse-plugins-parent' not found in repository: Unable to downl oad the artifact from any repository org.apache.geronimo.devtools:eclipse-plugins-parent:pom:1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepo sitory(DefaultMavenProjectBuilder.java:513) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(D efaultMavenProjectBuilder.java:1157) ... 18 more Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository org.apache.geronimo.devtools:eclipse-plugins-parent:pom:1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
RE: org.apache.geronimo.feature.source feature and plug-in
It is helpful to confirm! Thanks Sachin. -Original Message- From: Sachin Patel [mailto:[EMAIL PROTECTED] Sent: Monday, April 24, 2006 4:18 PM To: dev@geronimo.apache.org Subject: Re: org.apache.geronimo.feature.source feature and plug-in The source feature and plugins provide no function, so removing that will have no impact. The purpose of them is to package the source of all the plugins and they are wrapped inside their own plugin to integrate nicely with the PDE. - sachin On Apr 24, 2006, at 4:04 PM, Lin Sun wrote: Hi Sachin, What is the use of this features\org.apache.geronimo.source.feature_1.0.0 feature and its associated plugins\org.apache.geronimo.feature.source_1.0.0 plug-in? It looks a dummy test feature and plug-in to me. I removed them off my eclipse home directory and everything worked fine from my limited testing. Could you please advise? Thanks, Lin
[jira] Created: (GERONIMO-1762) Create a derby network /embedded XA datasource via admin console fail
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 Components: console Environment: winXP Reporter: Lin Sun 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
[jira] Updated: (GERONIMO-1762) Create a derby network /embedded XA datasource via admin console fail
[ http://issues.apache.org/jira/browse/GERONIMO-1762?page=all ] Lin Sun updated GERONIMO-1762: -- Attachment: G1762.patch 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 Components: console Environment: winXP Reporter: Lin Sun 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
[jira] Created: (GERONIMO-1757) rarRelativePath is not set correctly cause showplan.jsp displayswrong instruction
rarRelativePath is not set correctly cause showplan.jsp displayswrong instruction - Key: GERONIMO-1757 URL: http://issues.apache.org/jira/browse/GERONIMO-1757 Project: Geronimo Type: Bug Components: console Versions: 1.x Environment: winXP Reporter: Lin Sun Priority: Minor Portions of this is working in version 1.0 but broken after 1/25's change of DatabasePoolPortlet.java. Problem: At the show database plan page, you see the following instructions and the rarRelativePath is wrong. Should be repository/tranql/rars/tranql-connector-1.1.rar Deploy Command: To deploy a database pool from the command line using this plan, copy and paste it to a file (say, plan-file.xml) and save it. Then run a command like: cd GERONIMO_HOME java -jar bin/deployer.jar deploy plan-file.xml \ tranql-connector-1.1.rar Debug: I printed the value of base and path (value of PortletManager.getRepositoryEntry(renderRequest, data.getRarPath()).getPath()) ***linsun***path: /C:/ag10/repository/tranql/rars/tranql-connector-1.1.rar ***linsun***base: C:\ag10 ***linsun***rarRelativePath: tranql-connector-1.1.rar Also, If the server is installed onto a directory that contains space, for example c:\program files, the path needs to be decoded using URLDecode. For example, here's the output: ***linsun***path: /C:/program%files/ag10/repository/tranql/rars/tranql-connector-1.1.rar ***linsun***base: C:\program files\ag10 ***linsun***rarRelativePath: tranql-connector-1.1.rar patch will be attached shortly -- 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-1757) rarRelativePath is not set correctly cause showplan.jsp displayswrong instruction
[ http://issues.apache.org/jira/browse/GERONIMO-1757?page=all ] Lin Sun updated GERONIMO-1757: -- Description: Portions of this is working in version 1.0 but broken after 1/25's change of DatabasePoolPortlet.java. Problem: At the show database plan page, you see the following instructions and the rarRelativePath is wrong. Should be repository/tranql/rars/tranql-connector-1.1.rar Deploy Command: To deploy a database pool from the command line using this plan, copy and paste it to a file (say, plan-file.xml) and save it. Then run a command like: cd GERONIMO_HOME java -jar bin/deployer.jar deploy plan-file.xml \ tranql-connector-1.1.rar Debug: I printed the value of base and path (value of PortletManager.getRepositoryEntry(renderRequest, data.getRarPath()).getPath()) ***linsun***path: /C:/ag10/repository/tranql/rars/tranql-connector-1.1.rar ***linsun***base: C:\ag10 ***linsun***rarRelativePath: tranql-connector-1.1.rar Also, If the server is installed onto a directory that contains space, for example c:\program files, the path needs to be decoded using URLDecode. For example, here's the output: ***linsun***path: /C:/program%20files/ag10/repository/tranql/rars/tranql-connector-1.1.rar ***linsun***base: C:\program files\ag10 ***linsun***rarRelativePath: tranql-connector-1.1.rar patch will be attached shortly was: Portions of this is working in version 1.0 but broken after 1/25's change of DatabasePoolPortlet.java. Problem: At the show database plan page, you see the following instructions and the rarRelativePath is wrong. Should be repository/tranql/rars/tranql-connector-1.1.rar Deploy Command: To deploy a database pool from the command line using this plan, copy and paste it to a file (say, plan-file.xml) and save it. Then run a command like: cd GERONIMO_HOME java -jar bin/deployer.jar deploy plan-file.xml \ tranql-connector-1.1.rar Debug: I printed the value of base and path (value of PortletManager.getRepositoryEntry(renderRequest, data.getRarPath()).getPath()) ***linsun***path: /C:/ag10/repository/tranql/rars/tranql-connector-1.1.rar ***linsun***base: C:\ag10 ***linsun***rarRelativePath: tranql-connector-1.1.rar Also, If the server is installed onto a directory that contains space, for example c:\program files, the path needs to be decoded using URLDecode. For example, here's the output: ***linsun***path: /C:/program%files/ag10/repository/tranql/rars/tranql-connector-1.1.rar ***linsun***base: C:\program files\ag10 ***linsun***rarRelativePath: tranql-connector-1.1.rar patch will be attached shortly rarRelativePath is not set correctly cause showplan.jsp displayswrong instruction - Key: GERONIMO-1757 URL: http://issues.apache.org/jira/browse/GERONIMO-1757 Project: Geronimo Type: Bug Components: console Versions: 1.x Environment: winXP Reporter: Lin Sun Priority: Minor Attachments: G1757.patch Portions of this is working in version 1.0 but broken after 1/25's change of DatabasePoolPortlet.java. Problem: At the show database plan page, you see the following instructions and the rarRelativePath is wrong. Should be repository/tranql/rars/tranql-connector-1.1.rar Deploy Command: To deploy a database pool from the command line using this plan, copy and paste it to a file (say, plan-file.xml) and save it. Then run a command like: cd GERONIMO_HOME java -jar bin/deployer.jar deploy plan-file.xml \ tranql-connector-1.1.rar Debug: I printed the value of base and path (value of PortletManager.getRepositoryEntry(renderRequest, data.getRarPath()).getPath()) ***linsun***path: /C:/ag10/repository/tranql/rars/tranql-connector-1.1.rar ***linsun***base: C:\ag10 ***linsun***rarRelativePath: tranql-connector-1.1.rar Also, If the server is installed onto a directory that contains space, for example c:\program files, the path needs to be decoded using URLDecode. For example, here's the output: ***linsun***path: /C:/program%20files/ag10/repository/tranql/rars/tranql-connector-1.1.rar ***linsun***base: C:\program files\ag10 ***linsun***rarRelativePath: tranql-connector-1.1.rar patch will be attached shortly -- 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-1757) rarRelativePath is not set correctly cause showplan.jsp displayswrong instruction
[ http://issues.apache.org/jira/browse/GERONIMO-1757?page=all ] Lin Sun updated GERONIMO-1757: -- Attachment: G1757.patch rarRelativePath is not set correctly cause showplan.jsp displayswrong instruction - Key: GERONIMO-1757 URL: http://issues.apache.org/jira/browse/GERONIMO-1757 Project: Geronimo Type: Bug Components: console Versions: 1.x Environment: winXP Reporter: Lin Sun Priority: Minor Attachments: G1757.patch Portions of this is working in version 1.0 but broken after 1/25's change of DatabasePoolPortlet.java. Problem: At the show database plan page, you see the following instructions and the rarRelativePath is wrong. Should be repository/tranql/rars/tranql-connector-1.1.rar Deploy Command: To deploy a database pool from the command line using this plan, copy and paste it to a file (say, plan-file.xml) and save it. Then run a command like: cd GERONIMO_HOME java -jar bin/deployer.jar deploy plan-file.xml \ tranql-connector-1.1.rar Debug: I printed the value of base and path (value of PortletManager.getRepositoryEntry(renderRequest, data.getRarPath()).getPath()) ***linsun***path: /C:/ag10/repository/tranql/rars/tranql-connector-1.1.rar ***linsun***base: C:\ag10 ***linsun***rarRelativePath: tranql-connector-1.1.rar Also, If the server is installed onto a directory that contains space, for example c:\program files, the path needs to be decoded using URLDecode. For example, here's the output: ***linsun***path: /C:/program%20files/ag10/repository/tranql/rars/tranql-connector-1.1.rar ***linsun***base: C:\program files\ag10 ***linsun***rarRelativePath: tranql-connector-1.1.rar patch will be attached shortly -- 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-1750) Unable to run tradeStreamerAppclient
Unable to run tradeStreamerAppclient Key: GERONIMO-1750 URL: http://issues.apache.org/jira/browse/GERONIMO-1750 Project: Geronimo Type: Bug Components: sample apps Versions: 1.0 Environment: winXP, Reporter: Lin Sun Priority: Minor I performed the following command: java -jar client.jar tradeStreamerAppclient then got the following exception: 09:37:12,203 INFO [Log4jService] -- 09:37:12,203 INFO [Log4jService] Started Logging Service 09:37:12,203 INFO [JvmVendor] IBM JVM detected from IBM Corporation 09:37:14,578 INFO [CommandLine] Server startup completed TradeStreamer getInitial Context 09:37:17,047 INFO [ActiveMQConnection] channel status changed: Channel: TcpTransportChannel: Socket[addr=localhost/127. 0.0.1,port=61616,localport=4290] has connected Caught an unexpected exception! java.lang.NullPointerException at javax.swing.ImageIcon.init(ImageIcon.java:168) at org.apache.geronimo.samples.daytrader.client.TradeClientGUI.init(TradeClientGUI.java:59) at org.apache.geronimo.samples.daytrader.client.TradeClient.startClient(TradeClient.java:81) at org.apache.geronimo.samples.daytrader.client.TradeClient.main(TradeClient.java:63) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at org.apache.geronimo.client.AppClientContainer.main(AppClientContainer.java:143) at org.apache.geronimo.client.AppClientContainer$$FastClassByCGLIB$$b5beae18.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:835) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:178) at org.apache.geronimo.system.main.CommandLine.invokeMainGBean(CommandLine.java:90) at org.apache.geronimo.system.main.ClientCommandLine.init(ClientCommandLine.java:71) at org.apache.geronimo.system.main.ClientCommandLine.main(ClientCommandLine.java:46) 09:37:21,328 INFO [CommandLine] Server shutdown begun 09:37:21,344 ERROR [GBeanInstance] GBeanInstance should already be stopped before die() is called: objectName=geronimo.c lient:J2EEApplication=client-application,J2EEServer=client,JCAResource=activemq/activemq-ra/3.2.2.ibm/rar,j2eeType=JCACo nnectionFactory,name=jms/TopicConnectionFactory state=starting 09:37:21,344 ERROR [GBeanInstance] GBeanInstance should already be stopped before die() is called: objectName=geronimo.c lient:J2EEApplication=client-application,J2EEServer=client,j2eeType=ResourceAdapterModule,name=activemq/activemq-ra/3.2. 2.ibm/rar state=starting 09:37:21,359 INFO [CommandLine] Client shutdown completed The reason caused this exception is that the client tries to load a picture file named /images/tradeLogoSmall.gif, but can't find it. Here's an excerpt from TradeClientGUI.java: private static final String TRADELOGO_FILENAME = /images/tradeLogoSmall.gif; private static final String WEBSPHERELOGO_FILENAME = /images/WEBSPHERE_18P_UNIX.GIF; ... ImageIcon iconTrade = new ImageIcon(this.getClass().getResource(TRADELOGO_FILENAME)); ImageIcon iconWS = new ImageIcon(this.getClass().getResource(WEBSPHERELOGO_FILENAME)); The fix is to supply these two images logo images to geronimo\daytrader\streamer\src\images directory . I used the existing images (DayTraderHead_red.gif GLogo_450x50.gif) from the web directory: private static final String TRADELOGO_FILENAME = /images/DayTraderHead_red.gif; private static final String GERONIMOLOGO_FILENAME = /images/GLogo_450x50.gif; ... ImageIcon iconTrade = new ImageIcon(this.getClass().getResource(TRADELOGO_FILENAME)); ImageIcon iconWS = new ImageIcon(this.getClass().getResource(GERONIMOLOGO_FILENAME)); And add the following in the -- 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-1750) Unable to run tradeStreamerAppclient
[ http://issues.apache.org/jira/browse/GERONIMO-1750?page=all ] Lin Sun updated GERONIMO-1750: -- Description: I performed the following command: java -jar client.jar tradeStreamerAppclient then got the following exception: 09:37:12,203 INFO [Log4jService] -- 09:37:12,203 INFO [Log4jService] Started Logging Service 09:37:12,203 INFO [JvmVendor] IBM JVM detected from IBM Corporation 09:37:14,578 INFO [CommandLine] Server startup completed TradeStreamer getInitial Context 09:37:17,047 INFO [ActiveMQConnection] channel status changed: Channel: TcpTransportChannel: Socket[addr=localhost/127. 0.0.1,port=61616,localport=4290] has connected Caught an unexpected exception! java.lang.NullPointerException at javax.swing.ImageIcon.init(ImageIcon.java:168) at org.apache.geronimo.samples.daytrader.client.TradeClientGUI.init(TradeClientGUI.java:59) at org.apache.geronimo.samples.daytrader.client.TradeClient.startClient(TradeClient.java:81) at org.apache.geronimo.samples.daytrader.client.TradeClient.main(TradeClient.java:63) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at org.apache.geronimo.client.AppClientContainer.main(AppClientContainer.java:143) at org.apache.geronimo.client.AppClientContainer$$FastClassByCGLIB$$b5beae18.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:835) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:178) at org.apache.geronimo.system.main.CommandLine.invokeMainGBean(CommandLine.java:90) at org.apache.geronimo.system.main.ClientCommandLine.init(ClientCommandLine.java:71) at org.apache.geronimo.system.main.ClientCommandLine.main(ClientCommandLine.java:46) 09:37:21,328 INFO [CommandLine] Server shutdown begun 09:37:21,344 ERROR [GBeanInstance] GBeanInstance should already be stopped before die() is called: objectName=geronimo.c lient:J2EEApplication=client-application,J2EEServer=client,JCAResource=activemq/activemq-ra/3.2.2.ibm/rar,j2eeType=JCACo nnectionFactory,name=jms/TopicConnectionFactory state=starting 09:37:21,344 ERROR [GBeanInstance] GBeanInstance should already be stopped before die() is called: objectName=geronimo.c lient:J2EEApplication=client-application,J2EEServer=client,j2eeType=ResourceAdapterModule,name=activemq/activemq-ra/3.2. 2.ibm/rar state=starting 09:37:21,359 INFO [CommandLine] Client shutdown completed The reason caused this exception is that the client tries to load a picture file named /images/tradeLogoSmall.gif, but can't find it. Here's an excerpt from TradeClientGUI.java: private static final String TRADELOGO_FILENAME = /images/tradeLogoSmall.gif; private static final String WEBSPHERELOGO_FILENAME = /images/WEBSPHERE_18P_UNIX.GIF; ... ImageIcon iconTrade = new ImageIcon(this.getClass().getResource(TRADELOGO_FILENAME)); ImageIcon iconWS = new ImageIcon(this.getClass().getResource(WEBSPHERELOGO_FILENAME)); The fix is to supply these two images logo images to geronimo\daytrader\streamer\src\images directory . I used the existing images (DayTraderHead_red.gif GLogo_450x50.gif) from the web directory: private static final String TRADELOGO_FILENAME = /images/DayTraderHead_red.gif; private static final String GERONIMOLOGO_FILENAME = /images/GLogo_450x50.gif; ... ImageIcon iconTrade = new ImageIcon(this.getClass().getResource(TRADELOGO_FILENAME)); ImageIcon iconWS = new ImageIcon(this.getClass().getResource(GERONIMOLOGO_FILENAME)); And add the following to the geronimo\daytrader\streamer\project.xml file: (below the /resource tag) resource directorysrc/directory includes includeimages/*.*/include /includes /resource was: I performed the following command: java -jar client.jar tradeStreamerAppclient then got the following exception: 09:37:12,203 INFO [Log4jService] -- 09:37:12,203 INFO [Log4jService] Started Logging Service 09:37:12,203 INFO [JvmVendor] IBM JVM detected from IBM Corporation 09:37:14,578 INFO
RE: valid XML checking
Seems there are two cases: 1) Ideally we want to provide a complete set of deployment plan editors so that users can start building plans from the editor. Like Sachin pointed out, this is not complete yet and users will have to use the text editor to make changes/add additions for now. 2) Even when the complete set of deployment plan editor is available, certain users may still want to use the text editor if they dont like the GUI or prefer text editor. For these users, they will not care if the plan will pass the XML checking done by EMF since they choose to editor it using the text editor. They just want to run their applications within the eclipse environment, same as using the admin console or command line deployer. Thus, if users use non-qualified plans (quite likely when they use the text editor), Id like to see the eclipse plugin handle it, same as the web console deployer or command line deployer. I spent some time going through the plugin debugger, heres roughly what happens when I remotely deployed the MDB war file using the plugin: n publishModule() n doDeploy() n ExecuteDistribute includes load file to server, distribute the module id MDBDemoWebApp n Start module. Failed here at trying to getConfigID of the targetModule (which is MDBDemoWebApp in my case). The code was trying to get the ConfigID from the web deployment plan however the resource was failed to load due to the fact that the ejb-ref tag within the deployment plan not recognized as valid by EMF. On my server, I verified that the MDBDemoWebApp distributed, but not started. Is there a reason that we do this in two steps (distribute + stop)? Seems to me that we could consolidate distribute + start into one step deploy and save us the need to get ConfigId of the module. (I dont see how users perform distribute applications in eclipse.) If we have to deploy an application in two steps and we need to find the configId of the module to start, maybe we could find a better way to parse the ConfigId value of the Geronimo deployment plans? Thanks, Lin -Original Message- From: Sachin Patel [mailto:[EMAIL PROTECTED] Sent: Thursday, March 09, 2006 7:02 PM To: dev@geronimo.apache.org Subject: Re: valid XML checking I'm already doing this on importing applications. Non-qualified plans can be imported, and I run the conversion to make it a valid doc so that the EMF models can process it. Once its processed and the namespaces have been entered from that point forward you have to use qualified elements if you're modifying the resource via the Text/XML editor otherwise you invaliding the document and thus the editors can be opened against it. I may be able to put in a hook to always run SchemaConverstionUtils on opening the editor which would resolve the problem. Go ahead and open a defect. But if you put unqualified elements and run the WTP xml validator its going to fail since technically it is an invalid document. I could add a ResourceChangeListener or Builder as well which would help as well. But the real solution will be for users not have to modify the xml at all and there needs to be a complete set of deployment plan editors. I've been very behind on this effort, what would help would be if someone could mock up how they wanted things to be layed out in the editors and then I could get it done much quicker. - sachin On Mar 9, 2006, at 2:59 PM, David Jencks wrote: The builders all run plans through SchemaConversionUtils to install the correct namespaces. Is there some way to get eclipse to do that? I don't know if it would be a good idea to then save the converted version. thanks david jencks On Mar 9, 2006, at 10:53 AM, Lin Sun wrote: Hi there, Ive spent quite some time trying to get the MDB sample (http://opensource2.atlassian.com/confluence/oss/display/GERONIMO/JBoss+to+Geronimo+-+EJB-MDB+Migration) deployed using the eclipse plugin. I was able to get it running eventually but I had to spend extra time in modifying the deployment plan to bypass the valid XML checking. The extra editing is are not needed if I use the command line deployer or admin console. The problem is that the plugin checks the deployment plan very strictly. ref-nameejb/CustomerHome/ref-name geronimo.server:EJBModule=MDBDemo,J2EEApplication=null,J2EEServer=geronimo,j2eeType=EntityBean,name=CustomerEJB /ejb-ref I had to change it to the following just for Eclipse environment. (xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.0 is specified earlier in the plan) nam:ejb-ref nam:target-name /nam:target-name
valid XML checking
Hi there, Ive spent quite some time trying to get the MDB sample (http://opensource2.atlassian.com/confluence/oss/display/GERONIMO/JBoss+to+Geronimo+-+EJB-MDB+Migration) deployed using the eclipse plugin. I was able to get it running eventually but I had to spend extra time in modifying the deployment plan to bypass the valid XML checking. The extra editing is are not needed if I use the command line deployer or admin console. The problem is that the plugin checks the deployment plan very strictly. I have to use fully qualified elements, otherwise the plans are not treated as valid xmls, and the model editor will not be able to parse the resource and throws exception in the eclipse log. For example: the following is not treated as valid Geronimo deployment plan in eclipse environment. But the command line deployer or admin console likes it: ejb-ref ref-nameejb/CustomerHome/ref-name target-name geronimo.server:EJBModule=MDBDemo,J2EEApplication=null,J2EEServer=geronimo,j2eeType=EntityBean,name=CustomerEJB /target-name /ejb-ref I had to change it to the following just for Eclipse environment. (xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.0 is specified earlier in the plan) nam:ejb-ref nam:ref-nameejb/CustomerHome/nam:ref-name nam:target-name geronimo.server:EJBModule=MDBDemo,J2EEApplication=null,J2EEServer=geronimo,j2eeType=EntityBean,name=CustomerEJB /nam:target-name /nam:ejb-ref Ideally, we dont want users to perform such extra efforts while porting their Geronimo specific plans in eclipse. I am not sure what can be done in the plugin code to perform a loose XML checking it seems to use the WTP/pre-requisites code to perform the XML checking. Thoughts? Thanks, Lin
RE: [wtp-dev] Proposal for Merging Server Runtime and Server Instance
With this change, could you go over a user case where user would develop/test his J2EE application locally first then deploy it to the remote production server? I could not think of how to tie the runtime and server together in remote deployment environment. Thanks, Lin -Original Message- From: Sachin Patel [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 01, 2006 7:34 PM To: dev@geronimo.apache.org Subject: Re: [wtp-dev] Proposal for Merging Server Runtime and Server Instance So hopefully this will make sense... :) In the two proposal notes I sent, the discussion is around the 3 concepts in WTP, runtimes, servers, and facets and what we can do to improve the definition, design and interaction between the frameworks that these concepts represent. So for those not familiar with WTP, let me start by describing these concepts from a users perspective. RUNTIMES SERVERS So currently WTP has a notion of defining a runtime and defining a server. So for a user wanting to create a j2ee app using WTP and deploy it to geronimo the user must perform currently two distinct tasks. (1) Is to define a Geronimo runtime using a wizard which asks the location of the runtime which you would point to a geronimo installation. During project creation you would choose this newly defined runtime and what this essentially does is configures the project to add a JRE and a runtime classpath container which contains all of the geronimo spec jars + other G jars. This means that this project is targeted to be deployed to geronimo. Now in order to deploy that application, the user currently has to perform a second task, and that is to define and point to the actual server instance. You may immediatly ask yourself, didn't I just do that by defining the runtime? This is currently confusing to users, as the note below indicates. Not only are the definition of the terms confusing in discussions as many times there are used interchangably, but from a users perspective they need to manage in the UI both the list of servers and runtimes and the mapping between the two. And most of all what is confusing in the above case, both the runtime and the server are pointing to the same thing! This usability needs to change. So one of the proposals is for these two to be merged togather, with all server instances being runtimes, but not vise versa. Runtimes may or may not represent a server instance. (Multiple server instances may have unique configuration/launching data in distinct location but share the same runtime jars. For example WebSphere has a concept of profiles). So with that re-read below and hopefully the note will make more sense. FACETS -- Facets are basically a unit of function that can be applied and removed to a given WTP project. For example, if a user is wanting to create a Web Project the web facet is selected and this creates the project directory structure specific for a web project, web.xml, etc So how do facets relate to geronimo runtimes and servers? Since G is headed toward a model where a user can produce a custom server image (i.e web container only, no j2ee, etc...) each distribution may be different. So after defining a runtime by pointing to this installation, some facets may or not be applicable to add on a project. So from a tooling perspective we should be able to ask...Given this runtime what kind of capabilties do I have? What kind of projects can I create? Now the second use case is that a user may not be interested in deploying his app yet and only concerned is developing a project that would be supported geronimo. So they may or may not have a local geronimo install image. So with our integration and use of maven, we should be able to take a more appcentric approach in the tools as well. So the user should be able to simply choose the ejb project creation wizard, select geronimo, and we should be able to dynamically generate the minimum runtime for that project by pulling in the necessary jars from their local install or from a maven repo. I hope that helps. - sachin On Mar 1, 2006, at 5:35 PM, Dain Sundstrom wrote: Sachin, can you translate this from eclipse speak to geronimo speak? -dain On Mar 1, 2006, at 1:23 PM, Sachin Patel wrote: Please respond with any comments or concerns you have with this second proposal as it will have a direct affect on G tooling. - sachin Begin forwarded message: From: Konstantin Komissarchik [EMAIL PROTECTED] Date: March 1, 2006 4:02:33 PM EST To: General discussion of project-wide or architectural issues. wtp-dev@eclipse.org Subject: [wtp-dev] Proposal for Merging Server Runtime and Server Instance Reply-To: General discussion of project-wide or architectural issues. wtp-dev@eclipse.org Currently the server tools framework has a separate notion of runtime and a server. Typically,
RE: WTP/Eclipse questions/defects
I read your wiki page on how to develop Geronimo within eclipse which was very helpful. However, I haven't been able to debug the Geronimo plugin within eclipse. Is there any document on how to that, similar as the wiki page for developing Geronimo? I think this will be very useful for anyone who wants to help out with the Geronimo plugin. Thanks, Lin -Original Message- From: Sachin Patel [mailto:[EMAIL PROTECTED] Sent: Monday, February 27, 2006 11:12 PM To: dev@geronimo.apache.org Subject: Re: WTP/Eclipse questions/defects Just like you would hunt down a problem in G or any other project. Use the debugger. Eclipse/WTP provides sdk distributions so all the source is available. You can put breakpoints in the geronimo code to see the method call hierarchy in the debug view in Eclipse to get an understanding of who calls what. Another common practice is to verify problems against other server adapters. This would be a good indication that the bug is in WTP and not the implementation of a given adapter. Then you can use the debugger to evaluate further. - sachin On Feb 27, 2006, at 10:33 PM, Lin Sun wrote: Hi Sachin, Thanks this information is very useful. I am relatively new to the plugin development... Could you shed some light on how to tell if a defect is in WTP or Geronimo devtools? Thanks, Lin -Original Message- From: Sachin Patel [mailto:[EMAIL PROTECTED] Sent: Monday, February 27, 2006 11:24 AM To: dev@geronimo.apache.org; user@geronimo.apache.org Subject: WTP/Eclipse questions/defects With the release of the Eclipse plugin, here are a list of helpful resources where WTP/Eclipse specific questions can be asked and where you'll be able to search for answers to many common questions. http://www.eclipse.org/newsgroups/index_project.php The newsgroup URL is news.eclipse.org and the WTP specific list is eclipse.webtools. The bug reporting tool for all Eclipse projects is https:// bugs.eclipse.org/bugs/ If you feel you find a defect in WTP that you feel affects the functionality of the Geronimo plugin, for tracking purposes open a Jira in Geronimo and link it to the bugzilla number. This way the project is aware and thus can ensure that the defect gets added to the WTP adopter list and can take a higher priority. Thanks. - sachin
RE: WTP/Eclipse questions/defects
Thanks. I am willing to help out the documentation once I figure out how to do that myself. I did go through a basic Hello plugin development tutorial but I still have the following specific questions: 1) When I imported devtools project into Eclipse, I imported it as a plugin development--plugin project. Then I gave it a project name and pointed the project contents to directory devtools\modules\eclipse-plugin. Selected default of the rest and finished creating the project. However, I noticed the devtools\modules\eclipse-plugin\plugin.xml file is created, which was not there before I imported the devtools project into Eclipse. 2) Also, I'd like to know what should I have on the java build path of the project? I tried to put everything I can think of -- WTP 1.0.1 SDK zip file, Eclipse 3.1.2. zip file, but when I tried to right click on GenericServerBehaviour (inside of GeronimoServerBehavior.java file) and selected open call hierarchy I got a the resource is not on the build path of a Java project error. I also could not find the java API doc of this file either. Thanks again for your help! Lin -Original Message- From: Sachin Patel [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 28, 2006 3:42 PM To: dev@geronimo.apache.org Subject: Re: WTP/Eclipse questions/defects Yes I can but it will be a while before I get to it. Most of the information you really need is in Plugin Development Guide in the Eclipse Help and the tutorials on the Eclipse site which is full of information to get started. But before anything, your best bet is to go though one of the tutorials on creating your first plugin to get familiar with the the plugin development environment and how the eclipse framework works. See http://www.eclipse.org/articles/ - sachin On Feb 28, 2006, at 3:24 PM, Lin Sun wrote: I read your wiki page on how to develop Geronimo within eclipse which was very helpful. However, I haven't been able to debug the Geronimo plugin within eclipse. Is there any document on how to that, similar as the wiki page for developing Geronimo? I think this will be very useful for anyone who wants to help out with the Geronimo plugin. Thanks, Lin -Original Message- From: Sachin Patel [mailto:[EMAIL PROTECTED] Sent: Monday, February 27, 2006 11:12 PM To: dev@geronimo.apache.org Subject: Re: WTP/Eclipse questions/defects Just like you would hunt down a problem in G or any other project. Use the debugger. Eclipse/WTP provides sdk distributions so all the source is available. You can put breakpoints in the geronimo code to see the method call hierarchy in the debug view in Eclipse to get an understanding of who calls what. Another common practice is to verify problems against other server adapters. This would be a good indication that the bug is in WTP and not the implementation of a given adapter. Then you can use the debugger to evaluate further. - sachin On Feb 27, 2006, at 10:33 PM, Lin Sun wrote: Hi Sachin, Thanks this information is very useful. I am relatively new to the plugin development... Could you shed some light on how to tell if a defect is in WTP or Geronimo devtools? Thanks, Lin -Original Message- From: Sachin Patel [mailto:[EMAIL PROTECTED] Sent: Monday, February 27, 2006 11:24 AM To: dev@geronimo.apache.org; user@geronimo.apache.org Subject: WTP/Eclipse questions/defects With the release of the Eclipse plugin, here are a list of helpful resources where WTP/Eclipse specific questions can be asked and where you'll be able to search for answers to many common questions. http://www.eclipse.org/newsgroups/index_project.php The newsgroup URL is news.eclipse.org and the WTP specific list is eclipse.webtools. The bug reporting tool for all Eclipse projects is https:// bugs.eclipse.org/bugs/ If you feel you find a defect in WTP that you feel affects the functionality of the Geronimo plugin, for tracking purposes open a Jira in Geronimo and link it to the bugzilla number. This way the project is aware and thus can ensure that the defect gets added to the WTP adopter list and can take a higher priority. Thanks. - sachin
RE: WTP/Eclipse questions/defects
Hi Sachin, Thanks this information is very useful. I am relatively new to the plugin development... Could you shed some light on how to tell if a defect is in WTP or Geronimo devtools? Thanks, Lin -Original Message- From: Sachin Patel [mailto:[EMAIL PROTECTED] Sent: Monday, February 27, 2006 11:24 AM To: dev@geronimo.apache.org; user@geronimo.apache.org Subject: WTP/Eclipse questions/defects With the release of the Eclipse plugin, here are a list of helpful resources where WTP/Eclipse specific questions can be asked and where you'll be able to search for answers to many common questions. http://www.eclipse.org/newsgroups/index_project.php The newsgroup URL is news.eclipse.org and the WTP specific list is eclipse.webtools. The bug reporting tool for all Eclipse projects is https:// bugs.eclipse.org/bugs/ If you feel you find a defect in WTP that you feel affects the functionality of the Geronimo plugin, for tracking purposes open a Jira in Geronimo and link it to the bugzilla number. This way the project is aware and thus can ensure that the defect gets added to the WTP adopter list and can take a higher priority. Thanks. - sachin
[jira] Created: (GERONIMODEVTOOLS-69) Unable to define a new remote server by File--New--Server--Server
Unable to define a new remote server by File--New--Server--Server - Key: GERONIMODEVTOOLS-69 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-69 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Versions: 1.0.0 Environment: Eclipse Geronimo Plugin 1.0.0 TAG Rev379240, WTP 1.0.1 candidate wtp-sdk-R-1.0.1-200602171228.zip and its pre-requisites, Eclipse 3.1.2 Reporter: Lin Sun With a clean workspace this is very easy to recreate. Steps: 1) launch eclipse using -clean and -debug options 2) Click on File--New--Server--Server, and define a Remote server B. 3) Enter the directory path to a local geronimo server as the server runtime. 4) At the screen that contains rmi, http, ejb ports and administrator username/password, you will see everything is filled out as default (1099, 8080) but on the top there is a red X is not valid. 5) Click on Finish to finish defining the server. 6) Open server at the server tab (under J2EE view). saw the following in the debug console and URL is null: Starting application: 19188 org.apache.geronimo.devtools.eclipse.core: GeronimoServerBehavior.initialize() org.apache.geronimo.devtools.eclipse.core: startUpdateServerStateTask() Apache Geronimo 1.0 org.apache.geronimo.devtools.eclipse.core: -- UpdateServerStateTask.run() Apac he Geronimo 1.0 org.apache.geronimo.devtools.eclipse.core: URL = null org.apache.geronimo.devtools.eclipse.core: -- UpdateServerStateTask.run() Apac he Geronimo 1.0 The workaround is to define a local server A, and open the server and modify the host to server B and save it.With that I can see the URL set correctly from the debug console. org.apache.geronimo.devtools.eclipse.core: GeronimoServerBehavior.initialize() org.apache.geronimo.devtools.eclipse.core: startUpdateServerStateTask() Apache Geronimo 1.0 org.apache.geronimo.devtools.eclipse.core: -- UpdateServerStateTask.run() Apac he Geronimo 1.0 org.apache.geronimo.devtools.eclipse.core: URL = service:jmx:rmi://localhost/jn di/rmi://localhost:1099/JMXConnector I tried to search the red X is not valid message of the devtools files, could not find any hit of not valid. Guess it is a message from the GenericServer. I can attach the screenshot of the error if needed. -- 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: (GERONIMODEVTOOLS-50) resource reference specified in geronimo-web.xml is not shown up in the naming tab of the geronimo web deployment plan editor
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-50?page=all ] Lin Sun closed GERONIMODEVTOOLS-50: --- This issue is fixed now. resource reference specified in geronimo-web.xml is not shown up in the naming tab of the geronimo web deployment plan editor - Key: GERONIMODEVTOOLS-50 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-50 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Environment: Eclipse 3.1.1, Geronimo 1.0, winxp, JDK 1.4.2 Reporter: Lin Sun Priority: Minor Imported a simple war file that contains a geronimo-web.xml. The geronimo-web.xml also contains a resource reference elements. 1) I can open the geronimo-web.xml file via the geronimo web deployment plan editor, but I don't see the resource reference I specified in the geronimo-web.xml file under the naming tab. 2) I tried to add a resource reference at the naming tab, and save the file. Reopen the geronimo-web.xml, the previous defined resource reference is replaced with the newly added one. -- 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: (GERONIMODEVTOOLS-54) start geronimo from eclipse, the console output could be enhanced
start geronimo from eclipse, the console output could be enhanced - Key: GERONIMODEVTOOLS-54 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-54 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Environment: winXP, JDK 1.4.2 Reporter: Lin Sun Priority: Minor When I start geronimo from eclipse, I only got the following ouput on the console tab: Booting Geronimo Kernel (in Java 1.4.2)... Geronimo startup complete I'd prefer it to be same informative output as the one when I launch the bin\startup.bat script...i'd like to see what services are started, which ports... -- 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: (GERONIMODEVTOOLS-50) resource reference specified in geronimo-web.xml is not shown up in the naming tab of the geronimo web deployment plan editor
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-50?page=comments#action_12363848 ] Lin Sun commented on GERONIMODEVTOOLS-50: - The behavior has changed a bit (my guess is due to devtools 49) 1) No. 1 is fixed now 2) Add/modify a resource reference still has probs. The save action will only save the current tab, not the content changed in other tabs. For example, I added a new source reference at the naming tab, then I went to the Source tab to see if the changes were reflected in the Source tab. After finding out nothing is changed in the source tab, I clicked on the close icon to close and save the file. The plugin saved the current page that I was at (which is the source tab), but not the changes I made at the naming tab. Thus my change at the naming tab is not saved. resource reference specified in geronimo-web.xml is not shown up in the naming tab of the geronimo web deployment plan editor - Key: GERONIMODEVTOOLS-50 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-50 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Environment: Eclipse 3.1.1, Geronimo 1.0, winxp, JDK 1.4.2 Reporter: Lin Sun Priority: Minor Imported a simple war file that contains a geronimo-web.xml. The geronimo-web.xml also contains a resource reference elements. 1) I can open the geronimo-web.xml file via the geronimo web deployment plan editor, but I don't see the resource reference I specified in the geronimo-web.xml file under the naming tab. 2) I tried to add a resource reference at the naming tab, and save the file. Reopen the geronimo-web.xml, the previous defined resource reference is replaced with the newly added one. -- 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-1534) Daytrader: ejb-ql-compiler-factory element is wrong for DB2 or Oracle db
Daytrader: ejb-ql-compiler-factory element is wrong for DB2 or Oracle db - Key: GERONIMO-1534 URL: http://issues.apache.org/jira/browse/GERONIMO-1534 Project: Geronimo Type: Bug Components: sample apps Versions: 1.0 Environment: WinXP, Reporter: Lin Sun Priority: Minor In daytrader plan it contains the following ejb-ql-compiler-factory elements: !-- For DB2 database users uncomment the following line. ejb-ql-compiler-factoryorg.tranql.ejbcompiler.DB2EJBQLCompilerFactory/ejb-ql-compiler-factory db-syntax-factoryorg.tranql.sql.db2.DB2DBSyntaxFactory/db-syntax-factory -- If you uncomment the following line and configure daytrader with DB2, you will see a classloader problem when deploying daytrader. This should be changed to ejbqlcompiler instead of ejbcompiler: ejb-ql-compiler-factoryorg.tranql.ejbqlcompiler.DB2EJBQLCompilerFactory/ejb-ql-compiler-factory db-syntax-factoryorg.tranql.sql.db2.DB2DBSyntaxFactory/db-syntax-factory Same problem with Oracle. -- 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: (GERONIMODEVTOOLS-51) Cannot remove published applications
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-51?page=all ] Lin Sun closed GERONIMODEVTOOLS-51: --- This issue is fixed. Cannot remove published applications Key: GERONIMODEVTOOLS-51 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-51 Project: Geronimo-Devtools Type: Bug Environment: WINXP, JDK 1.4.2 eclipse 3.1.1 Reporter: Lin Sun Assignee: Sachin Patel Priority: Blocker This problem started to appear in one of the very recent builds. 1) Start with a clean workspace: eclipse -clean and define the geronimo server. 2) Imported the Hello.war 3) did the normal Run on server 4) saw the hello page in the eclipse browser 5) any attempts to Run on server, Remove, ... failed. The .log and server.log was showing that the hello app was already on the server and it was not being redeployed. Did a deploy list-modules, and saw hello program with a + sign on the left indicating it is still running. -- 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-1534) Daytrader: ejb-ql-compiler-factory element is wrong for DB2 or Oracle db
[ http://issues.apache.org/jira/browse/GERONIMO-1534?page=all ] Lin Sun updated GERONIMO-1534: -- Attachment: G1534-daytrader.patch Daytrader: ejb-ql-compiler-factory element is wrong for DB2 or Oracle db - Key: GERONIMO-1534 URL: http://issues.apache.org/jira/browse/GERONIMO-1534 Project: Geronimo Type: Bug Components: sample apps Versions: 1.0 Environment: WinXP, Reporter: Lin Sun Priority: Minor Attachments: G1534-daytrader.patch In daytrader plan it contains the following ejb-ql-compiler-factory elements: !-- For DB2 database users uncomment the following line. ejb-ql-compiler-factoryorg.tranql.ejbcompiler.DB2EJBQLCompilerFactory/ejb-ql-compiler-factory db-syntax-factoryorg.tranql.sql.db2.DB2DBSyntaxFactory/db-syntax-factory -- If you uncomment the following line and configure daytrader with DB2, you will see a classloader problem when deploying daytrader. This should be changed to ejbqlcompiler instead of ejbcompiler: ejb-ql-compiler-factoryorg.tranql.ejbqlcompiler.DB2EJBQLCompilerFactory/ejb-ql-compiler-factory db-syntax-factoryorg.tranql.sql.db2.DB2DBSyntaxFactory/db-syntax-factory Same problem with Oracle. -- 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: (GERONIMODEVTOOLS-49) Add resource reference GUI created unnecessary target-name elements
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-49?page=all ] Lin Sun closed GERONIMODEVTOOLS-49: --- This is fixed Add resource reference GUI created unnecessary target-name elements --- Key: GERONIMODEVTOOLS-49 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-49 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Environment: WinXP, JDK 1.4.2, Geronimo 1.0, Eclipse 3.1.1 Reporter: Lin Sun Assignee: Sachin Patel Priority: Minor If you specify a resource reference via the naming page in geronimo-web.xml, the naming:target-name elements will be created unnecessarily, and it will cause deploy error when the module is deployed. For example: naming:resource-ref naming:ref-nametest/naming:ref-name naming:resource-linktest/naming:resource-link naming:target-name/naming:target-name /naming:resource-ref The workaround is to remove the naming:target-name/naming:target-name at the source tab and save the change. -- 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: (GERONIMODEVTOOLS-51) Cannot remove published applications
Cannot remove published applications Key: GERONIMODEVTOOLS-51 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-51 Project: Geronimo-Devtools Type: Bug Environment: WINXP, JDK 1.4.2 eclipse 3.1.1 Reporter: Lin Sun Priority: Blocker This problem started to appear in one of the very recent builds. 1) Start with a clean workspace: eclipse -clean and define the geronimo server. 2) Imported the Hello.war 3) did the normal Run on server 4) saw the hello page in the eclipse browser 5) any attempts to Run on server, Remove, ... failed. The .log and server.log was showing that the hello app was already on the server and it was not being redeployed. Did a deploy list-modules, and saw hello program with a + sign on the left indicating it is still running. -- 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-1499) Daytrader: uncomment the drop table statements in daytrader.sql
Daytrader: uncomment the drop table statements in daytrader.sql Key: GERONIMO-1499 URL: http://issues.apache.org/jira/browse/GERONIMO-1499 Project: Geronimo Type: Bug Components: sample apps Versions: 1.0 Environment: winxp, Reporter: Lin Sun Priority: Minor If the daytrader.sql is executed the 2nd time, you will see many errors like index already exisited...because the tables are not dropped.I think it is better to uncomment the drop table statements in daytrader/derby/src/sql/daytrader.sql. -- 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-1499) Daytrader: uncomment the drop table statements in daytrader.sql
[ http://issues.apache.org/jira/browse/GERONIMO-1499?page=all ] Lin Sun updated GERONIMO-1499: -- Attachment: G1499-daytrader-sql.patch Daytrader: uncomment the drop table statements in daytrader.sql Key: GERONIMO-1499 URL: http://issues.apache.org/jira/browse/GERONIMO-1499 Project: Geronimo Type: Bug Components: sample apps Versions: 1.0 Environment: winxp, Reporter: Lin Sun Priority: Minor Attachments: G1499-daytrader-sql.patch If the daytrader.sql is executed the 2nd time, you will see many errors like index already exisited...because the tables are not dropped.I think it is better to uncomment the drop table statements in daytrader/derby/src/sql/daytrader.sql. -- 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-1501) Daytrader: remove hardcoded dependency versions in project.xml
Daytrader: remove hardcoded dependency versions in project.xml --- Key: GERONIMO-1501 URL: http://issues.apache.org/jira/browse/GERONIMO-1501 Project: Geronimo Type: Bug Components: sample apps Environment: winxp Reporter: Lin Sun Priority: Minor In daytrader, there are quite a few places that have hardcoded dependency projects' version number in project.xml. They can be replaced with the versions specified in etc/project.properties. -- 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-1501) Daytrader: remove hardcoded dependency versions in project.xml
[ http://issues.apache.org/jira/browse/GERONIMO-1501?page=all ] Lin Sun updated GERONIMO-1501: -- Attachment: G1501-ejb.patch G1501-streamer.patch G1501-web.patch Daytrader: remove hardcoded dependency versions in project.xml --- Key: GERONIMO-1501 URL: http://issues.apache.org/jira/browse/GERONIMO-1501 Project: Geronimo Type: Bug Components: sample apps Environment: winxp Reporter: Lin Sun Priority: Minor Attachments: G1501-ejb.patch, G1501-streamer.patch, G1501-web.patch In daytrader, there are quite a few places that have hardcoded dependency projects' version number in project.xml. They can be replaced with the versions specified in etc/project.properties. -- 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-1501) Daytrader: remove hardcoded dependency versions in project.xml
[ http://issues.apache.org/jira/browse/GERONIMO-1501?page=all ] Lin Sun updated GERONIMO-1501: -- Attachment: G1501-wsappclient.patch Daytrader: remove hardcoded dependency versions in project.xml --- Key: GERONIMO-1501 URL: http://issues.apache.org/jira/browse/GERONIMO-1501 Project: Geronimo Type: Bug Components: sample apps Environment: winxp Reporter: Lin Sun Priority: Minor Attachments: G1501-ejb.patch, G1501-streamer.patch, G1501-web.patch, G1501-wsappclient.patch In daytrader, there are quite a few places that have hardcoded dependency projects' version number in project.xml. They can be replaced with the versions specified in etc/project.properties. -- 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: (GERONIMODEVTOOLS-34) cannot create a resource reference via plugin GUI
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-34?page=all ] Lin Sun closed GERONIMODEVTOOLS-34: --- This issue can be closed now. The only thing is that if you don't specify a target-name, the target-name element will still appear in the source, like: naming:resource-ref naming:ref-nametest/naming:ref-name naming:resource-linktest/naming:resource-link naming:target-name/naming:target-name /naming:resource-ref The workaround is to remove the naming:target-name/naming:target-name. Will open a seperate bug for this. cannot create a resource reference via plugin GUI - Key: GERONIMODEVTOOLS-34 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-34 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Environment: WinXP, Eclipse 3.1.1, WTP 1.0RC5, JDK 1.4.2 Reporter: Lin Sun Assignee: Sachin Patel Tried to add a resource reference from the geronimo-web.xml in the simple hello program (in the naming tab page, click on Add. At resource reference detail page, type resource name and resource link and click Finish. Got an error in a sec asking me to check error log. (It would be nice to indicate to the user where the error log is). I went to .metadata\.log file, and saw the following exception: !ENTRY org.eclipse.jface 4 2 2006-01-09 15:50:16.161 !MESSAGE Problems occurred when invoking code from plug-in: org.eclipse.jface. !STACK 0 java.util.MissingResourceException: The image resource 'full/obj16/ResourceRefType' could not be located at org.eclipse.emf.common.EMFPlugin.delegatedGetImage(EMFPlugin.java:319) at org.eclipse.emf.common.EMFPlugin.getImage(EMFPlugin.java:273) at org.apache.geronimo.xml.ns.naming.provider.ResourceRefTypeItemProvider.getColumnImage(ResourceRefTypeItemProvider.java:376) at org.eclipse.emf.edit.ui.provider.AdapterFactoryLabelProvider.getColumnImage(AdapterFactoryLabelProvider.java:229) at org.eclipse.jface.viewers.TableViewer.doUpdateItem(TableViewer.java:473) at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:434) at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java(Inlined Compiled Code)) at org.eclipse.core.runtime.Platform.run(Platform.java(Inlined Compiled Code)) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java(Inlined Compiled Code)) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java(Compiled Code)) at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:1763) at org.eclipse.jface.viewers.StructuredViewer.internalUpdate(StructuredViewer.java:1746) at org.eclipse.jface.viewers.StructuredViewer.update(StructuredViewer.java:1697) at org.eclipse.emf.edit.ui.provider.AdapterFactoryContentProvider$ViewerRefresh.run(AdapterFactoryContentProvider.java:309) at org.eclipse.emf.edit.ui.provider.AdapterFactoryContentProvider.notifyChanged(AdapterFactoryContentProvider.java:257) at org.eclipse.emf.edit.provider.ChangeNotifier.fireNotifyChanged(ChangeNotifier.java:45) at org.eclipse.emf.edit.provider.ComposedAdapterFactory.fireNotifyChanged(ComposedAdapterFactory.java:451) at org.apache.geronimo.xml.ns.naming.provider.NamingItemProviderAdapterFactory.fireNotifyChanged(NamingItemProviderAdapterFactory.java:530) at org.eclipse.emf.edit.provider.ItemProviderAdapter.fireNotifyChanged(ItemProviderAdapter.java:217) at org.apache.geronimo.xml.ns.naming.provider.ResourceRefTypeItemProvider.notifyChanged(ResourceRefTypeItemProvider.java:319) at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java(Compiled Code)) at org.apache.geronimo.xml.ns.naming.impl.ResourceRefTypeImpl.setResourceLink(ResourceRefTypeImpl.java:461) at org.apache.geronimo.xml.ns.naming.impl.ResourceRefTypeImpl.eSet(ResourceRefTypeImpl.java:574) at org.apache.geronimo.ui.wizards.DynamicAddEditWizard.processEAttributes(DynamicAddEditWizard.java:119) at org.apache.geronimo.ui.wizards.DynamicAddEditWizard.performFinish(DynamicAddEditWizard.java:92) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:676) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:349) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:556) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java(Compiled Code)) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java(Compiled Code)) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java(Inlined Compiled Code)) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java(Compiled Code
[jira] Created: (GERONIMODEVTOOLS-49) Add resource reference GUI created unnecessary target-name elements
Add resource reference GUI created unnecessary target-name elements --- Key: GERONIMODEVTOOLS-49 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-49 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Environment: WinXP, JDK 1.4.2, Geronimo 1.0, Eclipse 3.1.1 Reporter: Lin Sun Priority: Minor If you specify a resource reference via the naming page in geronimo-web.xml, the naming:target-name elements will be created unnecessarily, and it will cause deploy error when the module is deployed. For example: naming:resource-ref naming:ref-nametest/naming:ref-name naming:resource-linktest/naming:resource-link naming:target-name/naming:target-name /naming:resource-ref The workaround is to remove the naming:target-name/naming:target-name at the source tab and save the change. -- 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: (GERONIMODEVTOOLS-50) resource reference specified in geronimo-web.xml is not shown up in the naming tab of the geronimo web deployment plan editor
resource reference specified in geronimo-web.xml is not shown up in the naming tab of the geronimo web deployment plan editor - Key: GERONIMODEVTOOLS-50 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-50 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Environment: Eclipse 3.1.1, Geronimo 1.0, winxp, JDK 1.4.2 Reporter: Lin Sun Priority: Minor Imported a simple war file that contains a geronimo-web.xml. The geronimo-web.xml also contains a resource reference elements. 1) I can open the geronimo-web.xml file via the geronimo web deployment plan editor, but I don't see the resource reference I specified in the geronimo-web.xml file under the naming tab. 2) I tried to add a resource reference at the naming tab, and save the file. Reopen the geronimo-web.xml, the previous defined resource reference is replaced with the newly added one. -- 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-1452) Config.xml refers to the wrong JMX remote service gbean (Fix included)
Config.xml refers to the wrong JMX remote service gbean (Fix included) -- Key: GERONIMO-1452 URL: http://issues.apache.org/jira/browse/GERONIMO-1452 Project: Geronimo Type: Bug Versions: 1.0 Environment: Geronimo 1.0, Windows XP Reporter: Lin Sun Priority: Minor I 'd like to change the default RMI port 1099 to 1098 due to a port conflict. I made all the changes I can think of in config.xml but got the following error during startup: 11:00:19,651 WARN [0/car,J2EEServer=geronimo,j2eeType=GBean,name=JMXService] Fa ilure in JMXConnector service:jmx:rmi://localhost/jndi/rmi:/JMXConnector 11:00:19,651 ERROR [GBeanInstanceState] Error while starting; GBean is now in th e FAILED state: objectName=geronimo.server:J2EEApplication=null,J2EEModule=gero nimo/j2ee-security/1.0/car,J2EEServer=geronimo,j2eeType=GBean,name=JMXService java.io.IOException: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 9.37.242.136; nested exc eption is: java.net.ConnectException: Connection refused: connect] at mx4j.remote.resolver.rmi.Resolver.bindServer(Resolver.java:199) at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServ er.java:152) at org.apache.geronimo.jmxremoting.JMXConnector.doStart(JMXConnector.jav a:122) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanI nstance.java:936) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart (GBeanInstanceState.java:325) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInsta nceState.java:110) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(G BeanInstanceState.java:132) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanI nstance.java:537) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(Basi cKernel.java:208) at org.apache.geronimo.kernel.config.Configuration.startRecursiveGBeans( Configuration.java:315) at org.apache.geronimo.kernel.config.Configuration$$FastClassByCGLIB$$7f 4b4a9b.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod Invoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio n.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance. java:835) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java: 178) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java: 173) at org.apache.geronimo.kernel.config.ConfigurationManagerImpl.start(Conf igurationManagerImpl.java:142) at org.apache.geronimo.kernel.config.ConfigurationManagerImpl$$FastClass ByCGLIB$$fbed85d2.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod Invoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio n.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance. java:800) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:5 7) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperat ionInvoker.java:36) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(Pro xyMethodInterceptor.java:96) at org.apache.geronimo.kernel.config.ConfigurationManager$$EnhancerByCGL IB$$518f71dc.start(generated) at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:337) at org.apache.geronimo.system.main.Daemon.init(Daemon.java:86) at org.apache.geronimo.system.main.Daemon.main(Daemon.java:462) The fix is to replace: gbean name=JMXConnector with gbean name=JMXService I can start geronimo with rmi port 1098 with the above gbean name change in config.xml. I am running with tomcat, but i think the fix should be applied to jetty as well. -- 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-1352) RMI port number is not specified in URL for JMXConnector in server config.xml files
[ http://issues.apache.org/jira/browse/GERONIMO-1352?page=comments#action_12362479 ] Lin Sun commented on GERONIMO-1352: --- If it helps, here's the syntax I used to specify the port, which worked well for me: gbean name=JMXService attribute name=urlservice:jmx:rmi://0.0.0.0/jndi/rmi://localhost:1098/JMXConnector/attribute /gbean RMI port number is not specified in URL for JMXConnector in server config.xml files --- Key: GERONIMO-1352 URL: http://issues.apache.org/jira/browse/GERONIMO-1352 Project: Geronimo Type: Bug Components: startup/shutdown, usability Reporter: John Sisson Assignee: Aaron Mulder Fix For: 1.0.1 The port number should be specified in the JMXConnector URL so that a user can search and replace the current port number (e.g. 1099) with the new value. Currently the JMXConnector URL does not specified the port number therefore it always uses the default port. Currently if a user changes the RMI port number they will get exceptions at startup. *** I tried changing the JMXConnector URL to specify the port but it was not used. Basically this means if a site has port 1099 in use, they cannot run Geronimo. *** -- 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: (GERONIMODEVTOOLS-32) Plugin: cannot step through hello app in eclipse when server in debugging mode
Plugin: cannot step through hello app in eclipse when server in debugging mode -- Key: GERONIMODEVTOOLS-32 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-32 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Environment: win XP, AG 1.0 Eclipse 3.1.1, JDK 1.4.2, plugin I built a few days ago Reporter: Lin Sun 1) Able to deploy a simple hello program. 2) added a breakpoint in the hello program 3) restarted the server to let it run in debugging mode. (When attempting to right click the application and select debug--debug on server, a window popup asked me the server is not running in debugging mode, click restart button to restart it in debugging mode). 4) Click on debug--debug on server to start the debug for the hello program. 5) Got a unable to publish error, check .log for errors. error is copied below: java.lang.Exception: Module hello/hello already exists in the server. Try to undeploy it first or use the redeploy command. org.apache.geronimo.common.DeploymentException: Module hello/hello already exists in the server. Try to undeploy it first or use the redeploy command. at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:235) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:102) at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:835) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:178) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:125) at org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke 6) remove the hello program via eclipse using add/remove projects. Check deploy.bat list-modules but I still see hello programs running. (will report a seperate bug for this) 7) undeploy it using deploy.bat 8) repeat step 4, and got hello program published. However, it didn't stop at the breakpoint. -- 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: (GERONIMODEVTOOLS-33) Plugin: Add/remove programs doesn't work when server in debugging mode
Plugin: Add/remove programs doesn't work when server in debugging mode --- Key: GERONIMODEVTOOLS-33 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-33 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Environment: WinXP, JDK 1.4.2, Plugin I built a few days ago, Eclipse 3.1.1. Reporter: Lin Sun 1) Able to deploy a simple hello program. 2) added a breakpoint in the hello program 3) restarted the server to let it run in debugging mode. (When attempting to right click the application and select debug--debug on server, a window popup asked me the server is not running in debugging mode, click restart button to restart it in debugging mode). 4) Click on debug--debug on server to start the debug for the hello program. 5) Got a unable to publish error, check .log for errors. error is copied below: java.lang.Exception: Module hello/hello already exists in the server. Try to undeploy it first or use the redeploy command. org.apache.geronimo.common.DeploymentException: Module hello/hello already exists in the server. Try to undeploy it first or use the redeploy command. at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:235) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:102) at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:835) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:178) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:125) at org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke 6) remove the hello program via eclipse using add/remove projects. Check deploy.bat list-modules but I still see hello programs running. -- 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: (GERONIMODEVTOOLS-34) cannot create a resource reference via plugin GUI
cannot create a resource reference via plugin GUI - Key: GERONIMODEVTOOLS-34 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-34 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Environment: WinXP, Eclipse 3.1.1, WTP 1.0RC5, JDK 1.4.2 Reporter: Lin Sun Tried to add a resource reference from the geronimo-web.xml in the simple hello program (in the naming tab page, click on Add. At resource reference detail page, type resource name and resource link and click Finish. Got an error in a sec asking me to check error log. (It would be nice to indicate to the user where the error log is). I went to .metadata\.log file, and saw the following exception: !ENTRY org.eclipse.jface 4 2 2006-01-09 15:50:16.161 !MESSAGE Problems occurred when invoking code from plug-in: org.eclipse.jface. !STACK 0 java.util.MissingResourceException: The image resource 'full/obj16/ResourceRefType' could not be located at org.eclipse.emf.common.EMFPlugin.delegatedGetImage(EMFPlugin.java:319) at org.eclipse.emf.common.EMFPlugin.getImage(EMFPlugin.java:273) at org.apache.geronimo.xml.ns.naming.provider.ResourceRefTypeItemProvider.getColumnImage(ResourceRefTypeItemProvider.java:376) at org.eclipse.emf.edit.ui.provider.AdapterFactoryLabelProvider.getColumnImage(AdapterFactoryLabelProvider.java:229) at org.eclipse.jface.viewers.TableViewer.doUpdateItem(TableViewer.java:473) at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:434) at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java(Inlined Compiled Code)) at org.eclipse.core.runtime.Platform.run(Platform.java(Inlined Compiled Code)) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java(Inlined Compiled Code)) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java(Compiled Code)) at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:1763) at org.eclipse.jface.viewers.StructuredViewer.internalUpdate(StructuredViewer.java:1746) at org.eclipse.jface.viewers.StructuredViewer.update(StructuredViewer.java:1697) at org.eclipse.emf.edit.ui.provider.AdapterFactoryContentProvider$ViewerRefresh.run(AdapterFactoryContentProvider.java:309) at org.eclipse.emf.edit.ui.provider.AdapterFactoryContentProvider.notifyChanged(AdapterFactoryContentProvider.java:257) at org.eclipse.emf.edit.provider.ChangeNotifier.fireNotifyChanged(ChangeNotifier.java:45) at org.eclipse.emf.edit.provider.ComposedAdapterFactory.fireNotifyChanged(ComposedAdapterFactory.java:451) at org.apache.geronimo.xml.ns.naming.provider.NamingItemProviderAdapterFactory.fireNotifyChanged(NamingItemProviderAdapterFactory.java:530) at org.eclipse.emf.edit.provider.ItemProviderAdapter.fireNotifyChanged(ItemProviderAdapter.java:217) at org.apache.geronimo.xml.ns.naming.provider.ResourceRefTypeItemProvider.notifyChanged(ResourceRefTypeItemProvider.java:319) at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java(Compiled Code)) at org.apache.geronimo.xml.ns.naming.impl.ResourceRefTypeImpl.setResourceLink(ResourceRefTypeImpl.java:461) at org.apache.geronimo.xml.ns.naming.impl.ResourceRefTypeImpl.eSet(ResourceRefTypeImpl.java:574) at org.apache.geronimo.ui.wizards.DynamicAddEditWizard.processEAttributes(DynamicAddEditWizard.java:119) at org.apache.geronimo.ui.wizards.DynamicAddEditWizard.performFinish(DynamicAddEditWizard.java:92) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:676) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:349) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:556) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java(Compiled Code)) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java(Compiled Code)) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java(Inlined Compiled Code)) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java(Compiled Code)) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java(Compiled Code)) at org.eclipse.jface.window.Window.runEventLoop(Window.java(Compiled Code)) at org.eclipse.jface.window.Window.open(Window.java:787) at org.apache.geronimo.ui.sections.DynamicTableSection$3.widgetSelected(DynamicTableSection.java:300) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java(Compiled Code)) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java(Compiled Code)) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java(Inlined Compiled Code
[jira] Created: (GERONIMODEVTOOLS-35) Plugin: There are two generic servers at Run as--Run... view
Plugin: There are two generic servers at Run as--Run... view - Key: GERONIMODEVTOOLS-35 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-35 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Environment: WinXP, JDK 1.4.2, Plugin I built a few days ago, Eclipse 3.1.1. Reporter: Lin Sun Priority: Minor If I right click the hello program, and select Run as--Run..., the run configuration screen has two generic servers there like below: Apache Tomcat Eclipse Application Generic Server --Apache Geronimo 1.0 Generic Server The second generic server should be removed. Also, is there a reason why Apache Geronimo is under Generic Server, while Apache Tomcat is 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: (GERONIMO-1399) DeploymentFactory-Implementation-Class property missing from deployer.jar manifest
[ http://issues.apache.org/jira/browse/GERONIMO-1399?page=all ] Lin Sun closed GERONIMO-1399: - Verified it is fixed and I can deploy the hello program now. DeploymentFactory-Implementation-Class property missing from deployer.jar manifest -- Key: GERONIMO-1399 URL: http://issues.apache.org/jira/browse/GERONIMO-1399 Project: Geronimo Type: Bug Components: deployment Versions: 1.0 Environment: Geronimo 1.0, built a few days ago Eclipse SDK 3.1.1 WTP 1.0 RC 5 and its prerequisites Eclipse plug-in, built a few days ago Reporter: Lin Sun Assignee: Sachin Patel Fix For: 1.0 On Dec 22, 2005, at 4:48 PM, Lin Sun wrote: Thanks. After you point out where the log is, I saw the following in the .log file: java.lang.NullPointerException at java.lang.Class.forName1(Native Method) at java.lang.Class.forName(Class.java(Compiled Code)) at org.apache.geronimo.core.GeronimoConnectionFactory.discoverDeploymentF actory(GeronimoConnectionFactory.java:78) at org.apache.geronimo.core.GeronimoConnectionFactory.getDeploymentManage r(GeronimoConnectionFactory.java:45) at org.apache.geronimo.core.CommandLauncher.setDeploymentManager (CommandLauncher.java:87) at org.apache.geronimo.core.CommandLauncher.executeCommand (CommandLauncher.java:61) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doDeploy (GeronimoServerBehaviour.java:233) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeComman d(GeronimoServerBehaviour.java:207) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModul e(GeronimoServerBehaviour.java:194) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModul e(ServerBehaviourDelegate.java:658) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModul es(ServerBehaviourDelegate.java:738) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish (ServerBehaviourDelegate.java:596) at org.eclipse.wst.server.core.internal.Server.doPublish (Server.java:799) at org.eclipse.wst.server.core.internal.Server.publish(Server.java: 788) at org.eclipse.wst.server.core.internal.PublishServerJob.run (PublishServerJob.java:145) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76) --- Sachin Patel [EMAIL PROTECTED] wrote: Nevermind, I found the problem. In the future, eclipse plugin errors/ exceptions can be found in the .log in the workspace metadata. So you shouldn't just look for errors in the geronimo log. I just published and found a NPE attempting to discover the deploymentFactory. Something must have changed in the runtime that broke me... I'll look into it. - sachin On Dec 22, 2005, at 4:21 PM, Sachin Patel wrote: Ok, then please describe your steps, from project creation, to deployment. - sachin Steps: 1) launch eclipse using eclipse -clean and use a brand new workspace 2) change to J2EE view. Define a geronimo server and start it. 3) right click dynamic web projects and select import to import the hello.war file. Select default/next for everything except uncheck the add module to an ear application checkbox. 4) right click the hello folder and select run as--run on server. then I got the unable to publish error immediately. I'll send you the hello.war file in a seperate note to reduce the size of the email to the list. Thanks, Lin -- 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-1399) NPE when trying to publish a simple app via eclipse plugin
NPE when trying to publish a simple app via eclipse plugin -- Key: GERONIMO-1399 URL: http://issues.apache.org/jira/browse/GERONIMO-1399 Project: Geronimo Type: Bug Components: eclipse-plugin Versions: 1.0 Environment: Geronimo 1.0, built a few days ago Eclipse SDK 3.1.1 WTP 1.0 RC 5 and its prerequisites Eclipse plug-in, built a few days ago Reporter: Lin Sun On Dec 22, 2005, at 4:48 PM, Lin Sun wrote: Thanks. After you point out where the log is, I saw the following in the .log file: java.lang.NullPointerException at java.lang.Class.forName1(Native Method) at java.lang.Class.forName(Class.java(Compiled Code)) at org.apache.geronimo.core.GeronimoConnectionFactory.discoverDeploymentF actory(GeronimoConnectionFactory.java:78) at org.apache.geronimo.core.GeronimoConnectionFactory.getDeploymentManage r(GeronimoConnectionFactory.java:45) at org.apache.geronimo.core.CommandLauncher.setDeploymentManager (CommandLauncher.java:87) at org.apache.geronimo.core.CommandLauncher.executeCommand (CommandLauncher.java:61) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doDeploy (GeronimoServerBehaviour.java:233) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeComman d(GeronimoServerBehaviour.java:207) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModul e(GeronimoServerBehaviour.java:194) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModul e(ServerBehaviourDelegate.java:658) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModul es(ServerBehaviourDelegate.java:738) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish (ServerBehaviourDelegate.java:596) at org.eclipse.wst.server.core.internal.Server.doPublish (Server.java:799) at org.eclipse.wst.server.core.internal.Server.publish(Server.java: 788) at org.eclipse.wst.server.core.internal.PublishServerJob.run (PublishServerJob.java:145) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76) --- Sachin Patel [EMAIL PROTECTED] wrote: Nevermind, I found the problem. In the future, eclipse plugin errors/ exceptions can be found in the .log in the workspace metadata. So you shouldn't just look for errors in the geronimo log. I just published and found a NPE attempting to discover the deploymentFactory. Something must have changed in the runtime that broke me... I'll look into it. - sachin On Dec 22, 2005, at 4:21 PM, Sachin Patel wrote: Ok, then please describe your steps, from project creation, to deployment. - sachin Steps: 1) launch eclipse using eclipse -clean and use a brand new workspace 2) change to J2EE view. Define a geronimo server and start it. 3) right click dynamic web projects and select import to import the hello.war file. Select default/next for everything except uncheck the add module to an ear application checkbox. 4) right click the hello folder and select run as--run on server. then I got the unable to publish error immediately. I'll send you the hello.war file in a seperate note to reduce the size of the email to the list. Thanks, Lin -- 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: Tranql not building?
I ran into the exact same error when I tried to build tranql-1.1.jar (the tagged version). After I pulled the latest tranql/src/test-resources/org/tranql/ddl/DDLGeneratorTest from HEAD I was able to pass this error and build tranql-1.1.jar successfully. --- Alan D. Cabrera [EMAIL PROTECTED] wrote: I'm getting this error when I build on WinXP, JDK142: Testsuite: org.tranql.ddl.DDLGeneratorTest Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 0.15 sec Testcase: testGenerate(org.tranql.ddl.DDLGeneratorTest):FAILED expected:13 but was:10 junit.framework.AssertionFailedError: expected:13 but was:10 at org.tranql.ddl.DDLGeneratorTest.testGenerate(DDLGeneratorTest.java:67) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java:185) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) at org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.java:88) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) at com.werken.werkz.Goal.fire(Goal.java:639) at com.werken.werkz.Goal.attain(Goal.java:575) at com.werken.werkz.Goal.attainPrecursors(Goal.java:488) at com.werken.werkz.Goal.attain(Goal.java:573) at com.werken.werkz.Goal.attainPrecursors(Goal.java:488) at com.werken.werkz.Goal.attain(Goal.java:573) at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTag.java:127) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) at com.werken.werkz.Goal.fire(Goal.java:639) at com.werken.werkz.Goal.attain(Goal.java:575) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:671) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263) at org.apache.maven.cli.App.doMain(App.java:488) at org.apache.maven.cli.App.main(App.java:1239) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) Matt Hogstrom wrote, On 10/26/2005 12:17 PM: My bad...fixed a typo :) David Blevins wrote: Matt, Gianny, did we catch you in the middle of a checkin? http://ci.gbuild.org/continuum/servlet/continuum/target/ ProjectBuild.vm?view=ProjectBuildbuildId=141id=8 If so, just click the Build Now link next to tranql on this page: http://ci.gbuild.org/continuum/servlet/continuum/target/Summary.vm/ fid/continuumProject Just setup the automatic notifications today, so doing this one by hand :) -David thanks, Lin __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com
[jira] Commented: (GERONIMO-1089) Deployer failed to deploy certain applications if geronimo is installed to a directory that has space
[ http://issues.apache.org/jira/browse/GERONIMO-1089?page=comments#action_12332589 ] Lin Sun commented on GERONIMO-1089: --- From the geronimo.log, here's the stack trace: org.apache.geronimo.common.DeploymentException: Could not access contents of a connector at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.addModules(EARConfigBuilder.java:618) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getEarPlan(EARConfigBuilder.java:222) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getDeploymentPlan(EARConfigBuilder.java:118) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder$$FastClassByCGLIB$$38e56ec6.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:760) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:36) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.deployment.ConfigurationBuilder$$EnhancerByCGLIB$$8327c217.getDeploymentPlan(generated) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:145) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:91) at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:795) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:181) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:125) at org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:795) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:181) at org.apache.geronimo.kernel.jmx.MBeanServerDelegate.invoke(MBeanServerDelegate.java:117) at mx4j.remote.rmi.RMIConnectionInvoker.invoke(RMIConnectionInvoker.java:219) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at mx4j.remote.rmi.RMIConnectionProxy.invoke(RMIConnectionProxy.java:34) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.chain(RMIConnectionSubjectInvoker.java:99) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.access$000(RMIConnectionSubjectInvoker.java:31) at mx4j.remote.rmi.RMIConnectionSubjectInvoker$1.run(RMIConnectionSubjectInvoker.java:90) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at javax.security.auth.Subject.doAsPrivileged(Subject.java:709) at mx4j.remote.MX4JRemoteUtils.subjectInvoke(MX4JRemoteUtils.java:163) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.subjectInvoke(RMIConnectionSubjectInvoker.java:86) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.invoke(RMIConnectionSubjectInvoker.java:80) at $Proxy0.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:221) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code
[jira] Commented: (GERONIMO-1089) Deployer failed to deploy certain applications if geronimo is installed to a directory that has space
[ http://issues.apache.org/jira/browse/GERONIMO-1089?page=comments#action_12332616 ] Lin Sun commented on GERONIMO-1089: --- I followed the instruction of Debugging Geronimo as a Remote Java Application on the wiki, and able to debug it using eclipse. Since we don't have the implementation of the Repository interface in the geronimo source code (seems from CGLIB), I decided to work around this problem by using the URLDecoder. Deployer failed to deploy certain applications if geronimo is installed to a directory that has space - Key: GERONIMO-1089 URL: http://issues.apache.org/jira/browse/GERONIMO-1089 Project: Geronimo Type: Bug Components: deployment Versions: 1.0-M5 Environment: Windows + Tomcat Reporter: Lin Sun My geronimo is at directory e:\program files\geronimo\modules\assembly\target\geronimo-1.0-M5. When I deployed daytrader, I got the following failure: e:\program files\geronimo\modules\assembly\target\geronimo-1.0-M5\bindeploy.bat deploy \program files\sandbox\samples\Trade\daytrader-ear-1.0-SNAPSHOT.ear \ program files\sandbox\samples\Trade\dayTrader-plan.xml Username: system Password: Error: Unable to distribute daytrader-ear-1.0-SNAPSHOT.ear: Bad path to external module, a connector caused by Illegal character in opaque part at index 2: e:\program files\geronimo\modules\assembly\target\geronimo-1.0-M5\repository\tranql/rar s/tranql-connector-derby-embed-xa-1.0.rar This is caused by deployer not able to handle the external-pathtranql/rars/tranql-connector-derby-embed-xa-1.0.rar/external-path element specified in the daytrader-plan.xml. If I broke the daytrader database resource plan to a seperate plan, I can deploy the TradeDataSource as the workaround: e:\program files\geronimo\modules\assembly\target\geronimo-1.0-M5\bindeploy.bat deploy \program files\sandbox\samples\Trade\dayTrader-dbplan.xml ..\repositor y\tranql\rars\tranql-connector-derby-embed-xa-1.0.rar Username: system Password: Deployed TradeDataSource Similar problem happens with the external-raractivemq/rars/activemq-ra-3.2-M1.rar/external-rar element. I don't mind digging more into this...any help/hints is appreciated. I figure I should start at deployer.log, but I didn't see a deployer.log generated. -- 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-1089) Deployer failed to deploy certain applications if geronimo is installed to a directory that has space
[ http://issues.apache.org/jira/browse/GERONIMO-1089?page=all ] Lin Sun updated GERONIMO-1089: -- Attachment: Geronimo-1089.patch With the patch, I am able to deploy and undeploy daytrader when the geronimo home is e:\program files\geronimo-1.0-M5. Can someone apply the patch for me? Thanks, Lin Deployer failed to deploy certain applications if geronimo is installed to a directory that has space - Key: GERONIMO-1089 URL: http://issues.apache.org/jira/browse/GERONIMO-1089 Project: Geronimo Type: Bug Components: deployment Versions: 1.0-M5 Environment: Windows + Tomcat Reporter: Lin Sun Attachments: Geronimo-1089.patch My geronimo is at directory e:\program files\geronimo\modules\assembly\target\geronimo-1.0-M5. When I deployed daytrader, I got the following failure: e:\program files\geronimo\modules\assembly\target\geronimo-1.0-M5\bindeploy.bat deploy \program files\sandbox\samples\Trade\daytrader-ear-1.0-SNAPSHOT.ear \ program files\sandbox\samples\Trade\dayTrader-plan.xml Username: system Password: Error: Unable to distribute daytrader-ear-1.0-SNAPSHOT.ear: Bad path to external module, a connector caused by Illegal character in opaque part at index 2: e:\program files\geronimo\modules\assembly\target\geronimo-1.0-M5\repository\tranql/rar s/tranql-connector-derby-embed-xa-1.0.rar This is caused by deployer not able to handle the external-pathtranql/rars/tranql-connector-derby-embed-xa-1.0.rar/external-path element specified in the daytrader-plan.xml. If I broke the daytrader database resource plan to a seperate plan, I can deploy the TradeDataSource as the workaround: e:\program files\geronimo\modules\assembly\target\geronimo-1.0-M5\bindeploy.bat deploy \program files\sandbox\samples\Trade\dayTrader-dbplan.xml ..\repositor y\tranql\rars\tranql-connector-derby-embed-xa-1.0.rar Username: system Password: Deployed TradeDataSource Similar problem happens with the external-raractivemq/rars/activemq-ra-3.2-M1.rar/external-rar element. I don't mind digging more into this...any help/hints is appreciated. I figure I should start at deployer.log, but I didn't see a deployer.log generated. -- 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: [Daytrader] Converting to Maven 2
I would prefer daytrader working with maven 1.02 for a little while, till we convert the core geronimo code to Maven 2. Or we can provide a way to switch to build daytrader easily between maven 1.02 and 2? --- Matt Hogstrom [EMAIL PROTECTED] wrote: Go ahead and open a JIRA and post the patches and I'll take a look at the changes we need to make. I think most folks are of the mind to go for M2 after we get V1.0 out the door (hopefully later this year) Vincent Massol wrote: -Original Message- From: Matt Hogstrom [mailto:[EMAIL PROTECTED] Sent: mardi 18 octobre 2005 15:43 To: Vincent Massol Subject: Re: [Daytrader] Converting to Maven 2 Vincent, This is great. UI'd be happy to pull your changes into the sandbox. One question I have is the compatibility with maven 1. Is it possible to commit your changes and folks that are still using maven 1 would be able to build? Sure. I've been careful not to break the Maven 1 build. Also, m1 and m2 can coexist pacifically so there shouldn't be problems. The only issue is supporting both builds over time which is a bit tiresome. I'd suggest switching to a pure Maven 2 build whenever possible (maybe when Geronimo switches to Maven 2). If that is the case then I say let's move forward with the migration. Great. How do you want to proceed? Others? I think you meant to reply to everyone, so I'm cc-ing the Geronimo list... :-) Thanks -Vincent Vincent Massol wrote: Hi, I have discussed offline with Matt (a month or so back) who told me he'd be interested in porting the daytrader application to Maven 2. I'd like to help. My incentive is that I'd like to feature the daytrader application in a book chapter I'm writing (Maven 2 book). I've started modifying the daytrader build on my machine to make it comply with Maven 2 directory structure. I've kept the maven 1 build working. Basically here are the steps I've done: - moved all sources in src/main/java - moved all resources in src/main/resources - removed all tests (as they were not real tests - they were just fake tests probably generated by the genapp plugin) - removed some other genapp files (App.java, etc) - removed the core module which consists only in a genapp generated project - have the ear application.xml file generated by the ear plugin - fixed some project.xml stuff (like renaming id into artifactId, etc) - some other minor stuff (indentation fixes, etc) Is that ok to be committed? I'd like to know if you're still interested in doing this Maven 2 migration. If so how would you like to do it: a/ directly on the trunk in sandbox/daytrader b/ in a branch c/ somewhere else. I could leave your build code untouched and do all the migration in a separate SVN for the book. I think a/ should be the best option. Should I open a JIRA issue for this? How easy would it be possible for me to get commit access, etc? The next steps I'd like to perform are: - discuss with you about reorganizing the full directory structure to incorporate more things in the build: packaging, deployment, functional tests, etc. - create the m2 pom.xml files - write automated functional tests Thanks -Vincent thanks, Lin __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com
[jira] Commented: (GERONIMO-1083) daytrader does not work with tomcat
[ http://issues.apache.org/jira/browse/GERONIMO-1083?page=comments#action_12332370 ] Lin Sun commented on GERONIMO-1083: --- This can be closed now. Thanks everyone! daytrader does not work with tomcat --- Key: GERONIMO-1083 URL: http://issues.apache.org/jira/browse/GERONIMO-1083 Project: Geronimo Type: Bug Components: Tomcat, sample apps Versions: 1.0-M5 Environment: Windows and Tomcat as the default web container Reporter: Lin Sun Assignee: Matt Hogstrom when I deploy dayTrade with tomcat as the default web container, found below exceptions in the logs, and I could not even get to the http://localhost:8080/daytrader page. 16:45:38,534 DEBUG [ContainerBase] Add child StandardWrapper[org_apache_geronimo_samples_daytrader_TradeWSAction] StandardEngine[Geronimo].StandardHost[0.0.0.0].StandardContext[/trade] 16:45:38,537 ERROR [Digester] End event threw exception java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) ... ... Caused by: java.lang.NullPointerException at org.apache.catalina.core.StandardContext.addMessageDestinationRef(StandardContext.java:2121) ... 95 more 16:45:38,541 ERROR [ContextConfig] Parse error in application web.xml java.lang.NullPointerException at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java(Inlined Compiled Code)) at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java(Inlined Compiled Code)) at org.apache.tomcat.util.digester.Digester.endElement(Digester.java(Compiled Code)) ... 16:45:38,543 DEBUG [ContextConfig] == 16:45:38,543 ERROR [ContextConfig] Marking this application unavailable due to previous error(s) 16:45:38,543 ERROR [StandardContext] Error getConfigured 16:45:38,543 ERROR [StandardContext] Context [/trade] startup failed due to previous errors This is caused by the message-destination-ref tags inside the web.xml of tradeWeb.war. Somehow tomcat doesn't like it. I tried to comment out the following and things started to work again. However, without the message-destination-ref tags, the JMS resources are not defined correctly. !-- message-destination-ref id=MessageDestinationRef_1 message-destination-ref-namejms/TradeBrokerQueue/message-destination-ref-name message-destination-typejavax.jms.Queue/message-destination-type message-destination-usageProduces/message-destination-usage message-destination-linkTradeBrokerQueue/message-destination-link /message-destination-ref message-destination-ref id=MessageDestinationRef_2 message-destination-ref-namejms/TradeStreamerTopic/message-destination-ref-name message-destination-typejavax.jms.Topic/message-destination-type message-destination-usageProduces/message-destination-usage message-destination-linkTradeStreamerTopic/message-destination-link /message-destination-ref -- I don't mind digging more into this...any hint/advice is appreciated! -- 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-1089) Deployer failed to deploy certain applications if geronimo is installed to a directory that has space
Deployer failed to deploy certain applications if geronimo is installed to a directory that has space - Key: GERONIMO-1089 URL: http://issues.apache.org/jira/browse/GERONIMO-1089 Project: Geronimo Type: Bug Components: deployment Versions: 1.0-M5 Environment: Windows + Tomcat Reporter: Lin Sun My geronimo is at directory e:\program files\geronimo\modules\assembly\target\geronimo-1.0-M5. When I deployed daytrader, I got the following failure: e:\program files\geronimo\modules\assembly\target\geronimo-1.0-M5\bindeploy.bat deploy \program files\sandbox\samples\Trade\daytrader-ear-1.0-SNAPSHOT.ear \ program files\sandbox\samples\Trade\dayTrader-plan.xml Username: system Password: Error: Unable to distribute daytrader-ear-1.0-SNAPSHOT.ear: Bad path to external module, a connector caused by Illegal character in opaque part at index 2: e:\program files\geronimo\modules\assembly\target\geronimo-1.0-M5\repository\tranql/rar s/tranql-connector-derby-embed-xa-1.0.rar This is caused by deployer not able to handle the external-pathtranql/rars/tranql-connector-derby-embed-xa-1.0.rar/external-path element specified in the daytrader-plan.xml. If I broke the daytrader database resource plan to a seperate plan, I can deploy the TradeDataSource as the workaround: e:\program files\geronimo\modules\assembly\target\geronimo-1.0-M5\bindeploy.bat deploy \program files\sandbox\samples\Trade\dayTrader-dbplan.xml ..\repositor y\tranql\rars\tranql-connector-derby-embed-xa-1.0.rar Username: system Password: Deployed TradeDataSource Similar problem happens with the external-raractivemq/rars/activemq-ra-3.2-M1.rar/external-rar element. I don't mind digging more into this...any help/hints is appreciated. I figure I should start at deployer.log, but I didn't see a deployer.log generated. -- 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-1083) daytrader does not work with tomcat
daytrader does not work with tomcat --- Key: GERONIMO-1083 URL: http://issues.apache.org/jira/browse/GERONIMO-1083 Project: Geronimo Type: Bug Components: sample apps, Tomcat Versions: 1.0-M5 Environment: Windows and Tomcat as the default web container Reporter: Lin Sun when I deploy dayTrade with tomcat as the default web container, found below exceptions in the logs, and I could not even get to the http://localhost:8080/daytrader page. 16:45:38,534 DEBUG [ContainerBase] Add child StandardWrapper[org_apache_geronimo_samples_daytrader_TradeWSAction] StandardEngine[Geronimo].StandardHost[0.0.0.0].StandardContext[/trade] 16:45:38,537 ERROR [Digester] End event threw exception java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) ... ... Caused by: java.lang.NullPointerException at org.apache.catalina.core.StandardContext.addMessageDestinationRef(StandardContext.java:2121) ... 95 more 16:45:38,541 ERROR [ContextConfig] Parse error in application web.xml java.lang.NullPointerException at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java(Inlined Compiled Code)) at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java(Inlined Compiled Code)) at org.apache.tomcat.util.digester.Digester.endElement(Digester.java(Compiled Code)) ... 16:45:38,543 DEBUG [ContextConfig] == 16:45:38,543 ERROR [ContextConfig] Marking this application unavailable due to previous error(s) 16:45:38,543 ERROR [StandardContext] Error getConfigured 16:45:38,543 ERROR [StandardContext] Context [/trade] startup failed due to previous errors This is caused by the message-destination-ref tags inside the web.xml of tradeWeb.war. Somehow tomcat doesn't like it. I tried to comment out the following and things started to work again. However, without the message-destination-ref tags, the JMS resources are not defined correctly. !-- message-destination-ref id=MessageDestinationRef_1 message-destination-ref-namejms/TradeBrokerQueue/message-destination-ref-name message-destination-typejavax.jms.Queue/message-destination-type message-destination-usageProduces/message-destination-usage message-destination-linkTradeBrokerQueue/message-destination-link /message-destination-ref message-destination-ref id=MessageDestinationRef_2 message-destination-ref-namejms/TradeStreamerTopic/message-destination-ref-name message-destination-typejavax.jms.Topic/message-destination-type message-destination-usageProduces/message-destination-usage message-destination-linkTradeStreamerTopic/message-destination-link /message-destination-ref -- I don't mind digging more into this...any hint/advice is appreciated! -- 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-1083) daytrader does not work with tomcat
[ http://issues.apache.org/jira/browse/GERONIMO-1083?page=comments#action_12332262 ] Lin Sun commented on GERONIMO-1083: --- Here's the full stack trace: 13:47:50,312 DEBUG [ContainerBase] Add child StandardWrapper[org_apache_geronimo_samples_daytrader_TradeWSAction] StandardEngine[Geronimo].StandardHost[0.0.0.0].StandardContext[/daytrader] 13:47:50,322 ERROR [Digester] End event threw exception java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at org.apache.tomcat.util.IntrospectionUtils.callMethod1(IntrospectionUtils.java:890) at org.apache.tomcat.util.digester.SetNextRule.end(SetNextRule.java:192) at org.apache.tomcat.util.digester.Rule.end(Rule.java:228) at org.apache.tomcat.util.digester.Digester.endElement(Digester.java(Compiled Code)) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1561) at org.apache.catalina.startup.ContextConfig.applicationWebConfig(ContextConfig.java:339) at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:1031) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:255) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4053) at org.apache.geronimo.tomcat.GeronimoStandardContext.start(GeronimoStandardContext.java:163) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) at org.apache.geronimo.tomcat.TomcatContainer.addContext(TomcatContainer.java:267) at org.apache.geronimo.tomcat.TomcatContainer$$FastClassByCGLIB$$9370b073.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java(Inlined Compiled Code)) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java(Compiled Code)) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:760) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:36) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.tomcat.TomcatContainer$$EnhancerByCGLIB$$b41fcc54.addContext(generated) at org.apache.geronimo.tomcat.TomcatWebAppContext.doStart(TomcatWebAppContext.java:373) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java(Compiled Code)) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:325) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:110) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:132) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:497) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:211) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:140) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:497) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:211) at org.apache.geronimo.kernel.KernelGBean.startRecursiveGBean(KernelGBean.java:73
[jira] Created: (GERONIMO-1084) Trade web primitive--PingServlet2Include failed: getWriter() has already been called for this response
Trade web primitive--PingServlet2Include failed: getWriter() has already been called for this response --- Key: GERONIMO-1084 URL: http://issues.apache.org/jira/browse/GERONIMO-1084 Project: Geronimo Type: Bug Components: Tomcat Versions: 1.0-M5 Environment: Windows + Tomcat Reporter: Lin Sun Deployed daytrader and found out day/trader/servlet/PingServlet2Include didn't work, and the exceptions threw: Error: PingServlet2Include.doGet(...): general exception java.lang.IllegalStateException: getWriter() has already been called for this response java.lang.IllegalStateException: getWriter() has already been called for this response at org.apache.catalina.connector.Response.getOutputStream(Response.java:565) at org.apache.catalina.connector.ResponseFacade.getOutputStream(ResponseFacade.java:171) at org.apache.geronimo.samples.daytrader.web.prims.PingServlet2Include.doGet(PingServlet2Include.java:61) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.geronimo.tomcat.valve.TransactionContextValve.invoke(TransactionContextValve.java:53) at org.apache.geronimo.tomcat.valve.ComponentContextValve.invoke(ComponentContextValve.java:47) at org.apache.geronimo.tomcat.valve.InstanceContextValve.invoke(InstanceContextValve.java:60) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:526) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:568) java.lang.IllegalStateException: getWriter() has already been called for this response at org.apache.catalina.connector.Response.getOutputStream(Response.java:565) at org.apache.catalina.connector.ResponseFacade.getOutputStream(ResponseFacade.java:171) at org.apache.geronimo.samples.daytrader.web.prims.PingServlet2Include.doGet(PingServlet2Include.java:61) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.geronimo.tomcat.valve.TransactionContextValve.invoke(TransactionContextValve.java:53) at org.apache.geronimo.tomcat.valve.ComponentContextValve.invoke(ComponentContextValve.java:47) at org.apache.geronimo.tomcat.valve.InstanceContextValve.invoke(InstanceContextValve.java:60) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:526
[jira] Commented: (GERONIMO-1084) Trade web primitive--PingServlet2Include failed: getWriter() has already been called for this response
[ http://issues.apache.org/jira/browse/GERONIMO-1084?page=comments#action_12332276 ] Lin Sun commented on GERONIMO-1084: --- This worked on Jetty and here's the result: Ping Servlet 2 Include Init time : Mon Oct 17 14:49:41 EDT 2005 Hit Count: 0 Trade web primitive--PingServlet2Include failed: getWriter() has already been called for this response --- Key: GERONIMO-1084 URL: http://issues.apache.org/jira/browse/GERONIMO-1084 Project: Geronimo Type: Bug Components: Tomcat Versions: 1.0-M5 Environment: Windows + Tomcat Reporter: Lin Sun Deployed daytrader and found out day/trader/servlet/PingServlet2Include didn't work, and the exceptions threw: Error: PingServlet2Include.doGet(...): general exception java.lang.IllegalStateException: getWriter() has already been called for this response java.lang.IllegalStateException: getWriter() has already been called for this response at org.apache.catalina.connector.Response.getOutputStream(Response.java:565) at org.apache.catalina.connector.ResponseFacade.getOutputStream(ResponseFacade.java:171) at org.apache.geronimo.samples.daytrader.web.prims.PingServlet2Include.doGet(PingServlet2Include.java:61) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.geronimo.tomcat.valve.TransactionContextValve.invoke(TransactionContextValve.java:53) at org.apache.geronimo.tomcat.valve.ComponentContextValve.invoke(ComponentContextValve.java:47) at org.apache.geronimo.tomcat.valve.InstanceContextValve.invoke(InstanceContextValve.java:60) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:526) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:568) java.lang.IllegalStateException: getWriter() has already been called for this response at org.apache.catalina.connector.Response.getOutputStream(Response.java:565) at org.apache.catalina.connector.ResponseFacade.getOutputStream(ResponseFacade.java:171) at org.apache.geronimo.samples.daytrader.web.prims.PingServlet2Include.doGet(PingServlet2Include.java:61) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.geronimo.tomcat.valve.TransactionContextValve.invoke(TransactionContextValve.java:53) at org.apache.geronimo.tomcat.valve.ComponentContextValve.invoke(ComponentContextValve.java:47) at org.apache.geronimo.tomcat.valve.InstanceContextValve.invoke(InstanceContextValve.java:60) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126
[jira] Commented: (GERONIMO-1083) daytrader does not work with tomcat
[ http://issues.apache.org/jira/browse/GERONIMO-1083?page=comments#action_12332280 ] Lin Sun commented on GERONIMO-1083: --- Deleted the additional spaces, rebuilt using maven, redeploy daytrader, but still got the same error at the same line #: [ContextConfig] Occurred at line 368 column 33 daytrader does not work with tomcat --- Key: GERONIMO-1083 URL: http://issues.apache.org/jira/browse/GERONIMO-1083 Project: Geronimo Type: Bug Components: sample apps, Tomcat Versions: 1.0-M5 Environment: Windows and Tomcat as the default web container Reporter: Lin Sun Assignee: Matt Hogstrom when I deploy dayTrade with tomcat as the default web container, found below exceptions in the logs, and I could not even get to the http://localhost:8080/daytrader page. 16:45:38,534 DEBUG [ContainerBase] Add child StandardWrapper[org_apache_geronimo_samples_daytrader_TradeWSAction] StandardEngine[Geronimo].StandardHost[0.0.0.0].StandardContext[/trade] 16:45:38,537 ERROR [Digester] End event threw exception java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) ... ... Caused by: java.lang.NullPointerException at org.apache.catalina.core.StandardContext.addMessageDestinationRef(StandardContext.java:2121) ... 95 more 16:45:38,541 ERROR [ContextConfig] Parse error in application web.xml java.lang.NullPointerException at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java(Inlined Compiled Code)) at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java(Inlined Compiled Code)) at org.apache.tomcat.util.digester.Digester.endElement(Digester.java(Compiled Code)) ... 16:45:38,543 DEBUG [ContextConfig] == 16:45:38,543 ERROR [ContextConfig] Marking this application unavailable due to previous error(s) 16:45:38,543 ERROR [StandardContext] Error getConfigured 16:45:38,543 ERROR [StandardContext] Context [/trade] startup failed due to previous errors This is caused by the message-destination-ref tags inside the web.xml of tradeWeb.war. Somehow tomcat doesn't like it. I tried to comment out the following and things started to work again. However, without the message-destination-ref tags, the JMS resources are not defined correctly. !-- message-destination-ref id=MessageDestinationRef_1 message-destination-ref-namejms/TradeBrokerQueue/message-destination-ref-name message-destination-typejavax.jms.Queue/message-destination-type message-destination-usageProduces/message-destination-usage message-destination-linkTradeBrokerQueue/message-destination-link /message-destination-ref message-destination-ref id=MessageDestinationRef_2 message-destination-ref-namejms/TradeStreamerTopic/message-destination-ref-name message-destination-typejavax.jms.Topic/message-destination-type message-destination-usageProduces/message-destination-usage message-destination-linkTradeStreamerTopic/message-destination-link /message-destination-ref -- I don't mind digging more into this...any hint/advice is appreciated! -- 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] Commented: (GERONIMO-1083) daytrader does not work with tomcat
Matt, I added the following comments to the JIRA: Deleted the additional spaces, rebuilt using maven, redeploy daytrader, but still got the same error at the same line #: [ContextConfig] Occurred at line 368 column 33 Lin --- Matt Hogstrom [EMAIL PROTECTED] wrote: Lin, Can you please test this out and confirm you can now deploy on Tomcat? - Matt Matt Hogstrom (JIRA) wrote: [ http://issues.apache.org/jira/browse/GERONIMO-1083?page=comments#action_12332281 ] Matt Hogstrom commented on GERONIMO-1083: - Sendingweb.xml Transmitting file data . Committed revision 325967. Fixed daytrader does not work with tomcat --- Key: GERONIMO-1083 URL: http://issues.apache.org/jira/browse/GERONIMO-1083 Project: Geronimo Type: Bug Components: sample apps, Tomcat Versions: 1.0-M5 Environment: Windows and Tomcat as the default web container Reporter: Lin Sun Assignee: Matt Hogstrom when I deploy dayTrade with tomcat as the default web container, found below exceptions in the logs, and I could not even get to the http://localhost:8080/daytrader page. 16:45:38,534 DEBUG [ContainerBase] Add child StandardWrapper[org_apache_geronimo_samples_daytrader_TradeWSAction] StandardEngine[Geronimo].StandardHost[0.0.0.0].StandardContext[/trade] 16:45:38,537 ERROR [Digester] End event threw exception java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) ... ... Caused by: java.lang.NullPointerException at org.apache.catalina.core.StandardContext.addMessageDestinationRef(StandardContext.java:2121) ... 95 more 16:45:38,541 ERROR [ContextConfig] Parse error in application web.xml java.lang.NullPointerException at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java(Inlined Compiled Code)) at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java(Inlined Compiled Code)) at org.apache.tomcat.util.digester.Digester.endElement(Digester.java(Compiled Code)) ... 16:45:38,543 DEBUG [ContextConfig] == 16:45:38,543 ERROR [ContextConfig] Marking this application unavailable due to previous error(s) 16:45:38,543 ERROR [StandardContext] Error getConfigured 16:45:38,543 ERROR [StandardContext] Context [/trade] startup failed due to previous errors This is caused by the message-destination-ref tags inside the web.xml of tradeWeb.war. Somehow tomcat doesn't like it. I tried to comment out the following and things started to work again. However, without the message-destination-ref tags, the JMS resources are not defined correctly. !-- message-destination-ref id=MessageDestinationRef_1 message-destination-ref-namejms/TradeBrokerQueue/message-destination-ref-name message-destination-typejavax.jms.Queue/message-destination-type message-destination-usageProduces/message-destination-usage message-destination-linkTradeBrokerQueue/message-destination-link /message-destination-ref message-destination-ref id=MessageDestinationRef_2 message-destination-ref-namejms/TradeStreamerTopic/message-destination-ref-name message-destination-typejavax.jms.Topic/message-destination-type message-destination-usageProduces/message-destination-usage message-destination-linkTradeStreamerTopic/message-destination-link /message-destination-ref -- I don't mind digging more into this...any hint/advice is appreciated! __ Yahoo! Music Unlimited Access over 1 million songs. Try it free. http://music.yahoo.com/unlimited/
[jira] Created: (GERONIMO-1073) TradeDirect:init error on JNDI lookups of DataSource when TradeDataSource is already running
TradeDirect:init error on JNDI lookups of DataSource when TradeDataSource is already running Key: GERONIMO-1073 URL: http://issues.apache.org/jira/browse/GERONIMO-1073 Project: Geronimo Type: Bug Versions: 1.0-M5 Environment: Windows Reporter: Lin Sun Priority: Minor I had thought this issue is same as JIRA 512 (http://issues.apache.org/jira/browse/GERONIMO-512), but I did the following practice to force the JDBC resource available before I deployed daytrader: I broke the jdbc resource portion of the plan to a seperate plan and deployed the jdbc resource first. 11:10:36,399 DEBUG [GBeanInstanceState] GBeanInstanceState for: geronimo.server:J2EEApplication=null,J2EEServer=geronimo,Resource Adapter=TradeDataSource,j2eeType=JCAResource,name=TradeDataSource State changed from stopped to starting 11:10:36,399 DEBUG [GBeanInstanceState] GBeanInstanceState for: geronimo.server:J2EEApplication=null,J2EEServer=geronimo,Resource Adapter=TradeDataSource,j2eeType=JCAResource,name=TradeDataSource State changed from starting to running Then I deployed the daytrader plan, still got the error on JNDI lookups: 11:13:57,077 DEBUG [WebappClassLoader] Loading class from parent TradeLog:Fri Oct 14 11:13:57 EDT 2005-- Error: TradeDirect:init -- error on JNDI lookups of DataSource -- TradeDirect will not work javax.naming.NameNotFoundException: comp/env/jdbc/TradeDataSource javax.naming.NameNotFoundException: comp/env/jdbc/TradeDataSource at org.apache.geronimo.naming.java.RootContext.lookup(RootContex t.java:45) TradeDirect is working even with the exception, but I could not understand why I would get this error in the console. -- 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
xfire jar files needed at runtime?
Hi all, I noticed that the latest binary distribution of geronimo (1.0-169186) contains the following 2 xfire jar files: xfire-20050202.jar xfire-java-20050202.jar Do we really need them at runtime? Any info is appreciated. thanks, Lin __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: xfire jar files needed at runtime?
David, Thanks so much for your answer. Correct me if I understand incorrectly So we will need the two jar files to build the files you mentioned below, but we don't need the two jar files at runtime. Lin --- David Jencks [EMAIL PROTECTED] wrote: no, their use has been removed from head. In the interests of greater stability the files that depend on them, although not actually used, will not be removed from m4. We do hope to eventually create a working xfire ws implementation, but I hope we would do that as separate geronimo modules rather than embedded inside openejb core. thanks david jencks On Jul 21, 2005, at 10:51 AM, lin sun wrote: Hi all, I noticed that the latest binary distribution of geronimo (1.0-169186) contains the following 2 xfire jar files: xfire-20050202.jar xfire-java-20050202.jar Do we really need them at runtime? Any info is appreciated. thanks, Lin __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com thanks, Lin Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
