[status] build: FAILED, test: FAILED | Linux 2.4.26, 2004-08-11
NIGHTLY BUILD/TEST Date: Wed Aug 11 05:34:25 EDT 2004 Kernel: Linux 2.4.26 Host: beaver.codehaus.org Java: 1.4.2_04-b05, mixed mode Maven: 1.0 CHECKOUT: incubator-geronimo BUILDING: incubator-geronimo [junit] [ERROR] TEST org.apache.geronimo.network.protocol.SocketProtocolStressTest FAILED BUILD FAILED BUILD FAILED Total time: 7 minutes 50 seconds Finished at: Wed Aug 11 05:43:23 EDT 2004
[jira] Commented: (GERONIMO-269) webservice deployment with ews
The following comment has been added to this issue: Author: Srinath Perera Created: Wed, 11 Aug 2004 3:58 AM Body: with the new patch fix the class loading stuff. Now the complete geronimo supports the Simple type web serivices. The WebServiceTest now has code to do the actual web service invocation tests. There is a class loading problem for the Complex type web services in the openejb service invocation. I add a test case to cover this but exclude it. I need to check it in the new openEJB cvs and get help from the open ejb ppl if there is a problem. --Srinath - View this comment: http://issues.apache.org/jira/browse/GERONIMO-269?page=comments#action_37167 - View the issue: http://issues.apache.org/jira/browse/GERONIMO-269 Here is an overview of the issue: - Key: GERONIMO-269 Summary: webservice deployment with ews Type: New Feature Status: Unassigned Priority: Major Project: Apache Geronimo Assignee: Reporter: Srinath Perera Created: Wed, 21 Jul 2004 7:08 PM Updated: Wed, 11 Aug 2004 3:58 AM Environment: all Description: this patch has code to deploy the webservice in the geronimo. there is a 1) WebServiceDeployerGbean and by calling deploy GBean method one can deploy a webservice. right now Axis service keep a seperate config-store but that can be changed when we decide on the final thing 2)the Deployer accept a webservice jar file and generate the required code using ews and deploy them. for time been the Axis GBean need to restart to get the new deploymnet. 3)the complete senario is shown in the WebServiceTest.java test. But to run this code need the JAVA_HOME/lib/tools.jar in the classpth. Since still can not get it in the classpath of maven I exclude the tests. If somebody using IDE and add the tools.jar in the classpath they should work fine :) 4) let me add some doc to the wiki about how this works. - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-269) webservice deployment with ews
The following issue has been updated: Updater: Srinath Perera (mailto:[EMAIL PROTECTED]) Date: Wed, 11 Aug 2004 4:00 AM Comment: this is the patch to enable complete support to simple type web services Changes: Attachment changed to patch.txt - For a full history of the issue, see: http://issues.apache.org/jira/browse/GERONIMO-269?page=history - View the issue: http://issues.apache.org/jira/browse/GERONIMO-269 Here is an overview of the issue: - Key: GERONIMO-269 Summary: webservice deployment with ews Type: New Feature Status: Unassigned Priority: Major Project: Apache Geronimo Assignee: Reporter: Srinath Perera Created: Wed, 21 Jul 2004 7:08 PM Updated: Wed, 11 Aug 2004 4:00 AM Environment: all Description: this patch has code to deploy the webservice in the geronimo. there is a 1) WebServiceDeployerGbean and by calling deploy GBean method one can deploy a webservice. right now Axis service keep a seperate config-store but that can be changed when we decide on the final thing 2)the Deployer accept a webservice jar file and generate the required code using ews and deploy them. for time been the Axis GBean need to restart to get the new deploymnet. 3)the complete senario is shown in the WebServiceTest.java test. But to run this code need the JAVA_HOME/lib/tools.jar in the classpth. Since still can not get it in the classpath of maven I exclude the tests. If somebody using IDE and add the tools.jar in the classpath they should work fine :) 4) let me add some doc to the wiki about how this works. - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-269) webservice deployment with ews
The following comment has been added to this issue: Author: Davanum Srinivas Created: Wed, 11 Aug 2004 6:30 AM Body: Updated EWS snapshot jar and applied patch in geronimo. Please cross-check. -- dims - View this comment: http://issues.apache.org/jira/browse/GERONIMO-269?page=comments#action_37173 - View the issue: http://issues.apache.org/jira/browse/GERONIMO-269 Here is an overview of the issue: - Key: GERONIMO-269 Summary: webservice deployment with ews Type: New Feature Status: Unassigned Priority: Major Project: Apache Geronimo Assignee: Reporter: Srinath Perera Created: Wed, 21 Jul 2004 7:08 PM Updated: Wed, 11 Aug 2004 6:30 AM Environment: all Description: this patch has code to deploy the webservice in the geronimo. there is a 1) WebServiceDeployerGbean and by calling deploy GBean method one can deploy a webservice. right now Axis service keep a seperate config-store but that can be changed when we decide on the final thing 2)the Deployer accept a webservice jar file and generate the required code using ews and deploy them. for time been the Axis GBean need to restart to get the new deploymnet. 3)the complete senario is shown in the WebServiceTest.java test. But to run this code need the JAVA_HOME/lib/tools.jar in the classpth. Since still can not get it in the classpath of maven I exclude the tests. If somebody using IDE and add the tools.jar in the classpath they should work fine :) 4) let me add some doc to the wiki about how this works. - JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
Re: Strange XSD error after WAR deploying
Bordet, Simone wrote: Hi, I'm still aside, but I've found some time to explore Geronimo :) Hey Simone, You must be lucky to find some free time :) Nice to see you over there! I've been able to successfully deploy a WAR, but when I start the server: org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name 'j2ee:jsp-configType' to a(n) 'type definition' component. Could you describe a bit more what the WAR is. More importantly, you could share the web.xml. There was times when I was facing some problems with deploying WAR (blojsom) and had to add some XML stuff to web.xml and after deploying remove them. It's not longer required. BTW, also the DebugConsole refuses to start with the same error. Have you tried to run Geronimo before deploying the WAR? It shouldn't matter, though. Simon Jacek
Re: Strange XSD error after WAR deploying
That is really weird. Do any of your files contain the text jsp-configType? Just a guess, but maybe this is something that the file at http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd is pulling in? Does it work if you remove the xsi:schemaLocation attribute? -dain On Aug 11, 2004, at 8:20 AM, Bordet, Simone wrote: Hi, I've been able to successfully deploy a WAR, but when I start the server: org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name 'j2ee:jsp-configType' to a(n) 'type definition' component. Could you describe a bit more what the WAR is. More importantly, you could share the web.xml. There was times when I was facing some problems with deploying WAR (blojsom) and had to add some XML stuff to web.xml and after deploying remove them. It's not longer required. It's simpler than HelloWorld: WAR: /index.jsp /WEB-INF/ /WEB-INF/web.xml /WEB-INF/geronimo-jetty.xml web.xml: ?xml version=1.0 encoding=ISO-8859-1? web-app xmlns=http://java.sun.com/xml/ns/j2ee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd; version=2.4 /web-app geronimo-jetty.xml ?xml version=1.0 encoding=UTF-8? web-app xmlns=http://geronimo.apache.org/xml/ns/web/jetty; configId=org/apache/geronimo/Console parentId=org/apache/geronimo/Server context-root/console/context-root context-priority-classloaderfalse/context-priority-classloader /web-app Thanks Simon
RE: Strange XSD error after WAR deploying
Hi, That is really weird. Do any of your files contain the text jsp-configType? No. Just a guess, but maybe this is something that the file at http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd is pulling in? Does it work if you remove the xsi:schemaLocation attribute? The XSD at http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd is, I guess, buggy. The element jsp-config is declared but never defined; not so happens for all other elements, for example welcome-file-list or error-page. It seems to me that Jetty is checking for XSDs, but I could not find any Jetty config file. I am really a newby here, if someone can help... Also, I tried to fix the XSD and let it be served by a local server, but the thing is going back home (at java.sun.com) every time. I checked Jetty, and it seems to have hardcoded the URL, it explains the going back home. I am really puzzled by the fact that apparently noone noticed the XSD bug, and it's there since 24 Nov 2003 ! Does this means Geronimo must always be online to work ? Sorry if you already discussed this, I'm trying to catch up. Thanks, Simon
Re: Strange XSD error after WAR deploying
On Wed, Aug 11, 2004 at 07:53:15PM +0200, Bordet, Simone wrote: The element jsp-config is declared but never defined; not so happens for all other elements, for example welcome-file-list or error-page. It looks as if it's defined in jsp_2_0.xsd which is included in web-app_2_4.xsd so the schema's valid and this should be OK, but maybe there's a problem with the XML parser resolving schema includes from remote URL's.
