Possible user code changes required when we upgrade to Tomcat 6.0.18
This is a notice to developers and users -
I've run into several JSP files in our build (mainly the monitor webapp)
that require code changes to work with Tomcat 6.0.18, due to tightened
code around the JSP 2.0 spec in Jasper during the Tomcat 6.0.17 release.
The build errors look something like -
org.apache.jasper.JasperException:
file:/Users/drwoods/geronimo/server-trunk/plugins/monitoring/mconsole-war/src/main/webapp/WEB-INF/view/monitoringEditView.jsp(168,168)
Attribute value rs.getString("server_id") is quoted with " which must be
escaped when used within the value
at
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
There are several places in the portlet code where we have -
value="<%=rs.getString("server_id")%>"
which had to be changed to
value='<%=rs.getString("server_id")%>'
The full text of the Tomcat Jasper change can be found at -
https://issues.apache.org/bugzilla/show_bug.cgi?id=45015
with the basic explanation being -
According to JSP 2.0 specification (chapter 1.7 page 72,73)
This code is illegal:
" />
Instead the correct sentence would be:
" />
...
-Donald
smime.p7s
Description: S/MIME Cryptographic Signature
config files tutorial
Hi all, Would you have some pointer as where i can find some good tutorials (or books) explaining what goes in the different config files? I find it really difficult to use an app server due to the number of config files and the amount of info going into those. Additionally there are little documentation and examples are often a good starting point but can't be generalized. Furthermore I find it difficult to distinguish between the separation of openejb-jar.xml and ejb-jarxml or application.xml and geronimo-application.xml. Brief, I am looking for something like "app server config for dummies". Thank you in advance JFR -- View this message in context: http://www.nabble.com/config-files-tutorial-tp18993144s134p18993144.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Help! Could not publish to server error
I was able to do this: http://cwiki.apache.org/GMOxDOC21/5-minute-tutorial-on-enterprise-application-development-with-eclipse-and-geronimo.html . Can you do that? Also, with J6, I created a dynamic web project with New->Project... I then right-clicked on the new project, and chose New->Servlet. That generated the java code for me. Do those steps work for you? What steps are you using? Are there any errors in the .log file in your workspace/.metadata directory? Ted On Thu, Aug 14, 2008 at 2:37 PM, gsilverman <[EMAIL PROTECTED]> wrote: > Problem with new GEP!!! You can't add a servlet to a Dynamic Web Application > project. The wizard adds the servlet mapping elements to web.xml, but does > not create the java file. Therefore, I can't test to see if it fixed > publishing issue. > > gsilverman wrote: > Help! I cannot publish a dynamic web application to Geronimo v2.1.2 using > Eclipse 3.4. I followed the tutorial, Web Application for EJB access, to the > letter and I get the following error when I add the ejb and web projects to > the running Geronimo server in Eclipse: Publishing to Apache Geronimo v2.1 > Server at localhost...has encountered a problem. Could not publish to > servrer. The "details" page explains this is due to a > "java.lang.NullPointerException". What's going on. Has anyone been able to > publish to tutorial app? > > > View this message in context: Re: Help! Could not publish to server error > Sent from the Apache Geronimo - Users mailing list archive at Nabble.com. >
Re: Connecting my application to a connection pool
I just double checked... yes it is. djencks wrote: > > Are you sure the geronimo-web you show is actually the plan being > deployed against? The dependency on your db pool is not showing up in > the list of modules searched for matches. > > thanks > david jencks > On Aug 14, 2008, at 2:51 PM, purdticker wrote: > > -- View this message in context: http://www.nabble.com/Connecting-my-application-to-a-connection-pool-tp18990389s134p18990753.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Connecting my application to a connection pool
Are you sure the geronimo-web you show is actually the plan being deployed against? The dependency on your db pool is not showing up in the list of modules searched for matches. thanks david jencks On Aug 14, 2008, at 2:51 PM, purdticker wrote: I've deployed a database pool on my geronimo server. Now, I'm trying to connect my application to that pool. I tried following the directions from the "Usage" link next to that pool, but I get an error (seen below). My web.xml and geronimo-web.xml: http://www.nabble.com/file/p18990389/web.xml web.xml http://www.nabble.com/file/p18990389/geronimo-web.xml geronimo-web.xml The error when deploying: Distribution of module failed. See log for details. Unable to resolve resource reference 'EBSPool' (Could not auto-map to resource. Try adding a resource-ref mapping to your Geronimo deployment plan. Search conducted in current module and dependencies: [ALL: org.apache.geronimo.configs/j2ee-server//car] [ALL: org.apache.geronimo.configs/openejb//car] [ALL: org.apache.geronimo.configs/system-database//car] [ALL: org.apache.geronimo.configs/jetty6//car] [ALL: org.apache.geronimo.configs/j2ee-corba-yoko//car] [ALL: org.apache.geronimo.configs/openjpa//car] [ALL: org.apache.geronimo.configs/axis//car] [ALL: org.apache.geronimo.configs/cxf//car] ) org.apache.geronimo.common.DeploymentException: Unable to resolve resource reference 'EBSPool' (Could not auto-map to resource. Try adding a resource-ref mapping to your Geronimo deployment plan. Search conducted in current module and dependencies: [ALL: org.apache.geronimo.configs/j2ee-server//car] [ALL: org.apache.geronimo.configs/openejb//car] [ALL: org.apache.geronimo.configs/system-database//car] [ALL: org.apache.geronimo.configs/jetty6//car] [ALL: org.apache.geronimo.configs/j2ee-corba-yoko//car] [ALL: org.apache.geronimo.configs/openjpa//car] [ALL: org.apache.geronimo.configs/axis//car] [ALL: org.apache.geronimo.configs/cxf//car] ) at org .apache .geronimo .connector .deployment.ResourceRefBuilder.buildNaming(ResourceRefBuilder.java: 216) at org .apache .geronimo .j2ee .deployment .NamingBuilderCollection.buildNaming(NamingBuilderCollection.java:53) at org .apache .geronimo .openejb .deployment.EjbDeploymentBuilder.addEnc(EjbDeploymentBuilder.java:321) at org .apache .geronimo .openejb .deployment.EjbDeploymentBuilder.buildEnc(EjbDeploymentBuilder.java: 286) at org .apache .geronimo .openejb.deployment.EjbModuleBuilder.addGBeans(EjbModuleBuilder.java: 761) at org .apache .geronimo .j2ee .deployment .EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:647) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:254) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:133) at sun.reflect.GeneratedMethodAccessor198.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org .apache .geronimo .gbean .runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java: 34) at org .apache .geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org .apache .geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java: 239) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java: 342) at sun.reflect.GeneratedMethodAccessor106.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org .apache .geronimo .gbean .runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java: 34) at org .apache .geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org .apache .geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java: 239) at org .apache .geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java: 172) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(Unknown Source) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.access$200(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl $PrivilegedOperation.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at javax .management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.invoke(Unknown Source) at sun.reflect.GeneratedMethodAccessor83.invoke(Unknown So
Connecting my application to a connection pool
I've deployed a database pool on my geronimo server. Now, I'm trying to connect my application to that pool. I tried following the directions from the "Usage" link next to that pool, but I get an error (seen below). My web.xml and geronimo-web.xml: http://www.nabble.com/file/p18990389/web.xml web.xml http://www.nabble.com/file/p18990389/geronimo-web.xml geronimo-web.xml The error when deploying: Distribution of module failed. See log for details. Unable to resolve resource reference 'EBSPool' (Could not auto-map to resource. Try adding a resource-ref mapping to your Geronimo deployment plan. Search conducted in current module and dependencies: [ALL: org.apache.geronimo.configs/j2ee-server//car] [ALL: org.apache.geronimo.configs/openejb//car] [ALL: org.apache.geronimo.configs/system-database//car] [ALL: org.apache.geronimo.configs/jetty6//car] [ALL: org.apache.geronimo.configs/j2ee-corba-yoko//car] [ALL: org.apache.geronimo.configs/openjpa//car] [ALL: org.apache.geronimo.configs/axis//car] [ALL: org.apache.geronimo.configs/cxf//car] ) org.apache.geronimo.common.DeploymentException: Unable to resolve resource reference 'EBSPool' (Could not auto-map to resource. Try adding a resource-ref mapping to your Geronimo deployment plan. Search conducted in current module and dependencies: [ALL: org.apache.geronimo.configs/j2ee-server//car] [ALL: org.apache.geronimo.configs/openejb//car] [ALL: org.apache.geronimo.configs/system-database//car] [ALL: org.apache.geronimo.configs/jetty6//car] [ALL: org.apache.geronimo.configs/j2ee-corba-yoko//car] [ALL: org.apache.geronimo.configs/openjpa//car] [ALL: org.apache.geronimo.configs/axis//car] [ALL: org.apache.geronimo.configs/cxf//car] ) at org.apache.geronimo.connector.deployment.ResourceRefBuilder.buildNaming(ResourceRefBuilder.java:216) at org.apache.geronimo.j2ee.deployment.NamingBuilderCollection.buildNaming(NamingBuilderCollection.java:53) at org.apache.geronimo.openejb.deployment.EjbDeploymentBuilder.addEnc(EjbDeploymentBuilder.java:321) at org.apache.geronimo.openejb.deployment.EjbDeploymentBuilder.buildEnc(EjbDeploymentBuilder.java:286) at org.apache.geronimo.openejb.deployment.EjbModuleBuilder.addGBeans(EjbModuleBuilder.java:761) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:647) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:254) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:133) at sun.reflect.GeneratedMethodAccessor198.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342) at sun.reflect.GeneratedMethodAccessor106.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(Unknown Source) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.access$200(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.invoke(Unknown Source) at sun.reflect.GeneratedMethodAccessor83.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source) at sun.rmi.transport.Transport$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.
RE: Maven Plugin and Changing Ports
Yes, that did it. 1051 is apparently consumed by iTunesHelper.exe, but control over port will give me enough to find a port that's free on the developer workstations. Great - I'll put a custom assembly aside for now and come back to it later. -Original Message- From: Jarek Gawor [mailto:[EMAIL PROTECTED] Sent: Thursday, August 14, 2008 3:44 PM To: user@geronimo.apache.org Subject: Re: Maven Plugin and Changing Ports Thanks. I think the property should have been: -Dorg.apache.geronimo.config.substitution.COSNamingPort=1051. (no .prefix) Jarek On Thu, Aug 14, 2008 at 3:20 PM, Geoffrey Wiseman <[EMAIL PROTECTED]> wrote: > Issue filed for the docs: > https://issues.apache.org/jira/browse/GERONIMO-4247 > > The property is seemingly accepted, but doesn't change the end result -- > I disabled ccApp.exe for now, so it gets to startup and tells me that > the CORBA Naming Service is running on 1050. Looking into why, but will > fall back to looking at making my own server assembly soon, since that's > probably the end-goal given what I'm likely to need right now. > > -Original Message- > From: Jarek Gawor [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 14, 2008 1:37 PM > To: user@geronimo.apache.org > Subject: Re: Maven Plugin and Changing Ports > > Take a look at > http://svn.apache.org/viewvc/geronimo/server/trunk/testsuite/pom.xml?vie > w=markup > starting at line 201. You should be able to add something like: > > -Dorg.apache.geronimo.config.substitution.prefix.COSNamingPort=1 > 051. > > Also, can you open a bug on the documentation problem? > > Thanks. > > Jarek > > >
Re: Maven Plugin and Changing Ports
Thanks. I think the property should have been: -Dorg.apache.geronimo.config.substitution.COSNamingPort=1051. (no .prefix) Jarek On Thu, Aug 14, 2008 at 3:20 PM, Geoffrey Wiseman <[EMAIL PROTECTED]> wrote: > Issue filed for the docs: > https://issues.apache.org/jira/browse/GERONIMO-4247 > > The property is seemingly accepted, but doesn't change the end result -- > I disabled ccApp.exe for now, so it gets to startup and tells me that > the CORBA Naming Service is running on 1050. Looking into why, but will > fall back to looking at making my own server assembly soon, since that's > probably the end-goal given what I'm likely to need right now. > > -Original Message- > From: Jarek Gawor [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 14, 2008 1:37 PM > To: user@geronimo.apache.org > Subject: Re: Maven Plugin and Changing Ports > > Take a look at > http://svn.apache.org/viewvc/geronimo/server/trunk/testsuite/pom.xml?vie > w=markup > starting at line 201. You should be able to add something like: > > -Dorg.apache.geronimo.config.substitution.prefix.COSNamingPort=1 > 051. > > Also, can you open a bug on the documentation problem? > > Thanks. > > Jarek > > >
RE: Maven Plugin and Changing Ports
Issue filed for the docs: https://issues.apache.org/jira/browse/GERONIMO-4247 The property is seemingly accepted, but doesn't change the end result -- I disabled ccApp.exe for now, so it gets to startup and tells me that the CORBA Naming Service is running on 1050. Looking into why, but will fall back to looking at making my own server assembly soon, since that's probably the end-goal given what I'm likely to need right now. -Original Message- From: Jarek Gawor [mailto:[EMAIL PROTECTED] Sent: Thursday, August 14, 2008 1:37 PM To: user@geronimo.apache.org Subject: Re: Maven Plugin and Changing Ports Take a look at http://svn.apache.org/viewvc/geronimo/server/trunk/testsuite/pom.xml?vie w=markup starting at line 201. You should be able to add something like: -Dorg.apache.geronimo.config.substitution.prefix.COSNamingPort=1 051. Also, can you open a bug on the documentation problem? Thanks. Jarek
Re: Help! Could not publish to server error
Problem with new GEP!!! You can't add a servlet to a Dynamic Web Application project. The wizard adds the servlet mapping elements to web.xml, but does not create the java file. Therefore, I can't test to see if it fixed publishing issue. gsilverman wrote: > > Help! I cannot publish a dynamic web application to Geronimo v2.1.2 using > Eclipse 3.4. > > I followed the tutorial, Web Application for EJB access, to the letter and > I get the following error when I add the ejb and web projects to the > running Geronimo server in Eclipse: > > Publishing to Apache Geronimo v2.1 Server at localhost...has encountered a > problem. Could not publish to servrer. > > The "details" page explains this is due to a > "java.lang.NullPointerException". > > What's going on. Has anyone been able to publish to tutorial app? > > > > > > -- View this message in context: http://www.nabble.com/Help%21-Could-not-publish-to-server-error-tp18984957s134p18987218.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Is config.ser ever used??
On Aug 14, 2008, at 10:11 AM, Luciano Salotto wrote: David Thanks for your quick replay, It is very definitely used. Deployment in geronimo consists of translating whatever deployment plans (javaee spec dds, annotations, geronimo service plans, etc) into geronimo service component (gbean) descriptors (GBeanData) and serializing them into the config.ser file. When you start a plugin (module) the config.ser is deserialized and the components configured and started. Ok, then how is it possible that I sent a config.ser from a very different isntallation, and it worked well? random accident? :-) Will config.ser change if the EAR structure is different or could I just have it create once and then leave it as it is for ever? Most application configuration changes would result in config.ser changes. For instance adding or removing an ejb would add or remove a gbean from the configuration. Changing something in web.xml or ejb- jar.xml or the geronimo or openejb plans would result in a change. Changing the code inside one of your components (servlet, ejb) without changing the ejb interface should not result in a change. I definitely would not advise trying to work around the deployment process. Tomcat doesn't fit all that well into this idea and the main tomcat application gbean includes the web.xml as a data element. That will explain the web.xml like entries in the config.ser. FWIW I'd suggest you look into the custom server assembly features using maven and the car-maven-plugin available in the latest was ce (and geronimo 2.1 and later). I'm not familiar with exactly what comes with was ce but using geronimo I'd assemble a custom server directly, something like what is outlined here: http://cwiki.apache.org/GMOxDOC21/constructing-a-special-purpose-server-using-maven.html We can't use that since we are working on WASCE 2.0, when I heard of that functionality of 2.1 I wanted to move to that version, but we are too close to deliver data for such a change, anyways many thanks for your suggestion You still might be able to script deploying/undeploying your application using the geronimo-maven-plugin if you are OK with use of maven. thanks david jencks Thanks again for all your help! Luciano
Re: Help! Could not publish to server error
Sorry, I should have been more clear. It supports Java 1.5 and Java 1.6. Ted Kirby On Thu, Aug 14, 2008 at 1:34 PM, gsilverman <[EMAIL PROTECTED]> wrote: > I'll get the new Geronimo plugin and see if that helps. By the way, does > this versin support Java 1.6, or do I still need to use 1.5? > > gsilverman wrote: > Seems there are others on this forum with the same problem, and it appears > to be a Java version issue. I'm using 1.6 but will have to try it with 1.5. > > gsilverman wrote: > Help! I cannot publish a dynamic web application to Geronimo v2.1.2 using > Eclipse 3.4. > > > View this message in context: Re: Help! Could not publish to server error > Sent from the Apache Geronimo - Users mailing list archive at Nabble.com. >
Re: Maven Plugin and Changing Ports
Take a look at http://svn.apache.org/viewvc/geronimo/server/trunk/testsuite/pom.xml?view=markup starting at line 201. You should be able to add something like: -Dorg.apache.geronimo.config.substitution.prefix.COSNamingPort=1051. Also, can you open a bug on the documentation problem? Thanks. Jarek On Thu, Aug 14, 2008 at 1:22 PM, Geoffrey Wiseman <[EMAIL PROTECTED]> wrote: > Yes, I did think about doing my own server assembly, seemed to be an option > based on the release notes I'd seen for 2.1, but I was hoping to get things > up and running first and then look at cutting back after that, mostly > because, as you say, it's another thing to learn. ;) > > > > I'll see if I can make it happen with a system property first, but if that > fails, or looks like it might be as much work as figuring out how to make my > own assembly, I might just do that. Thanks. > > > > From: David Jencks [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 14, 2008 1:08 PM > To: user@geronimo.apache.org > Subject: Re: Maven Plugin and Changing Ports > > > > > > On Aug 14, 2008, at 9:32 AM, Vamsavardhana Reddy wrote: > > Look at plugins\corba\j2ee-corba-yoko\pom.xml . You can modify > 1050 to > include your own port number so that the binaries you build will use that > port number you specify. > > > > I don't think that will work because the value is overridden in the > config.xml snippet in geronimo-plugin.xml generated from the pom and the > value ends up getting set from the > var/config/config-substitutions.properties file. > > > > From your first post I suspect you might want a lighter-weight server than > full geronimo. You might consider assembling your own server with just the > bits you need, just like we do :-) In this case you can change the port > value by including a plugin that only has the overriding value in the > geronimo-plugin.xml. > > > > If you don't want to learn how to assemble your own server just yet you can > also override the value on the geronimo command line; I think its possible > to do this through the g-m-p but I'm not sure how. > > > > You'd need the equivalent of > -Dorg.apache.geronimo.config.substitution.prefix.COSNamingPort=1051 > > You might also be able to set an environment property to make this work. > > > > Hope this helps > > david jencks > > > > ++Vamsi > > On Thu, Aug 14, 2008 at 9:52 PM, Geoffrey Wiseman <[EMAIL PROTECTED]> > wrote: > > Ok, with the Geronimo Plugin and Assemblies to 2.1.2, both > Geronimo-tomcat6-javaee5 and Geronimo-jetty6-javaee5 seem to load partially, > although the Yoko ORB wants to grab Port 1050 that's currently held by > ccApp.exe (Norton AntiVirus), which seems to be a known problem. > > > > Is there any way to change the ports used by an assembly that comes out of > the repo, rather than one you have installed locally? Some kind of > configuration parameter that I can feed into the POM to change the port? > > > >
Re: Help! Could not publish to server error
I'll get the new Geronimo plugin and see if that helps. By the way, does this versin support Java 1.6, or do I still need to use 1.5? gsilverman wrote: > > Seems there are others on this forum with the same problem, and it appears > to be a Java version issue. I'm using 1.6 but will have to try it with > 1.5. > > > gsilverman wrote: >> >> Help! I cannot publish a dynamic web application to Geronimo v2.1.2 using >> Eclipse 3.4. >> > > -- View this message in context: http://www.nabble.com/Help%21-Could-not-publish-to-server-error-tp18984957s134p18986213.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
RE: Maven Plugin and Changing Ports
Yes, I did think about doing my own server assembly, seemed to be an option based on the release notes I'd seen for 2.1, but I was hoping to get things up and running first and then look at cutting back after that, mostly because, as you say, it's another thing to learn. ;) I'll see if I can make it happen with a system property first, but if that fails, or looks like it might be as much work as figuring out how to make my own assembly, I might just do that. Thanks. From: David Jencks [mailto:[EMAIL PROTECTED] Sent: Thursday, August 14, 2008 1:08 PM To: user@geronimo.apache.org Subject: Re: Maven Plugin and Changing Ports On Aug 14, 2008, at 9:32 AM, Vamsavardhana Reddy wrote: Look at plugins\corba\j2ee-corba-yoko\pom.xml . You can modify 1050 to include your own port number so that the binaries you build will use that port number you specify. I don't think that will work because the value is overridden in the config.xml snippet in geronimo-plugin.xml generated from the pom and the value ends up getting set from the var/config/config-substitutions.properties file. >From your first post I suspect you might want a lighter-weight server than full geronimo. You might consider assembling your own server with just the bits you need, just like we do :-) In this case you can change the port value by including a plugin that only has the overriding value in the geronimo-plugin.xml. If you don't want to learn how to assemble your own server just yet you can also override the value on the geronimo command line; I think its possible to do this through the g-m-p but I'm not sure how. You'd need the equivalent of -Dorg.apache.geronimo.config.substitution.prefix.COSNamingPort=1051 You might also be able to set an environment property to make this work. Hope this helps david jencks ++Vamsi On Thu, Aug 14, 2008 at 9:52 PM, Geoffrey Wiseman <[EMAIL PROTECTED]> wrote: Ok, with the Geronimo Plugin and Assemblies to 2.1.2, both Geronimo-tomcat6-javaee5 and Geronimo-jetty6-javaee5 seem to load partially, although the Yoko ORB wants to grab Port 1050 that's currently held by ccApp.exe (Norton AntiVirus), which seems to be a known problem. Is there any way to change the ports used by an assembly that comes out of the repo, rather than one you have installed locally? Some kind of configuration parameter that I can feed into the POM to change the port?
RE: Geronimo Maven Plugin
Sorry, I meant to include a link to the documentation I was using. Basically the first hit that comes back on Geronimo-maven-plugin from Google, which is this: http://geronimo.apache.org/maven/server/maven-plugins/geronimo-maven-plu gin/usage/modules.html From: David Jencks [mailto:[EMAIL PROTECTED] Sent: Thursday, August 14, 2008 12:57 PM To: user@geronimo.apache.org Subject: Re: Geronimo Maven Plugin On Aug 14, 2008, at 8:34 AM, Geoffrey Wiseman wrote: I'd like to use Geronimo to run some integration tests in Maven that are going to require a container and a message queue. To that end, I briefly looked at Cargo, which I've used in the past, but they seem to support 1.0.X, not even 1.1, let alone 2.X, so I decided that was a little too far back, and I didn't really want to upgrade/maintain the Cargo container definition, at least, not when I'm fairly new to Geronimo. That meant it was time to take a look at Geronimo-maven-plugin, which I did, ran into some issues. I searched the mailing list, but didn't find much recent traffic about the plugin at all. Either I'm incapable of running a good search, not many people are using the plugin lately, they're discussing it somewhere else, or they're not running into the problems I'm having, I'm not sure which. Either way, I'd like to clarify some points, so if there's a better place to discuss this, let me know. In short: * What's a good, working configuration for a relatively current Maven to get a J2EE Geronimo up and running? * Should I use org.apache.geronimo.plugins or org.apache.geronimo.buildsupport? * Do the plugin version and assembly version need to be in sync, and do they correspond to the version of Geronimo that I'm getting? * If not: o What version of the plugin should I use? o What assembly and assembly version should I use? I ran into a bunch of issues, I think many of which were related to the fact that the example in the documentation pointed me at some elements that aren't incredibly up-to-date (old plugin groupid, old assembly artifactids) and I ended up with assemblies and plugins at different version numbers, which I suspect is a problem, although I haven't yet gotten any combination working. If the assembly and plugin don't need to be in sync, then I can report a whack of issues that you might encounter when they aren't in sync. Now that I've found higher version numbers and more combinations, I'm going to keep trying, and I may find something that works, but pointers to a working config would probably help as well. You should use the plugin corresponding to your geronimo version. The one in buildsupport is current, the other is antique. Where is the bad documentation? Maybe we should update or remove it. I would check out geronimo server/branches/2.1 or server/tags/2.1.2 or server/trunk, build it with maven 2.0.9, and look into the testsuite directory. It's a bit convoluted (but ___much___ simpler than it used to be) but is a working example of how to run integration tests in geronimo using the geronimo-maven-plugin along with some other useful infrastructure. thanks david jencks
Re: Is config.ser ever used??
David Thanks for your quick replay, It is very definitely used. Deployment in geronimo consists of translating > whatever deployment plans (javaee spec dds, annotations, geronimo service > plans, etc) into geronimo service component (gbean) descriptors (GBeanData) > and serializing them into the config.ser file. When you start a plugin > (module) the config.ser is deserialized and the components configured and > started. > Ok, then how is it possible that I sent a config.ser from a very different isntallation, and it worked well? Will config.ser change if the EAR structure is different or could I just have it create once and then leave it as it is for ever? > Tomcat doesn't fit all that well into this idea and the main tomcat > application gbean includes the web.xml as a data element. > That will explain the web.xml like entries in the config.ser. > > FWIW I'd suggest you look into the custom server assembly features using > maven and the car-maven-plugin available in the latest was ce (and geronimo > 2.1 and later). I'm not familiar with exactly what comes with was ce but > using geronimo I'd assemble a custom server directly, something like what is > outlined here: > > > http://cwiki.apache.org/GMOxDOC21/constructing-a-special-purpose-server-using-maven.html > We can't use that since we are working on WASCE 2.0, when I heard of that functionality of 2.1 I wanted to move to that version, but we are too close to deliver data for such a change, anyways many thanks for your suggestion Thanks again for all your help! Luciano
Re: Help! Could not publish to server error
What version of the Geronimo Eclipse Plugin (GEP) did you use? We are about to release GEP 212, which should fix this problem. See http://mail-archives.apache.org/mod_mbox/geronimo-dev/200808.mbox/ajax/[EMAIL PROTECTED] for details on how to get it. It would be useful for us to know if that fixes the problem for you. Thanks, Ted Kirby On Thu, Aug 14, 2008 at 12:31 PM, gsilverman <[EMAIL PROTECTED]> wrote: > Seems there are others on this forum with the same problem, and it appears > to be a Java version issue. I'm using 1.6 but will have to try it with 1.5. > > gsilverman wrote: > Help! I cannot publish a dynamic web application to Geronimo v2.1.2 using > Eclipse 3.4. > > > View this message in context: Re: Help! Could not publish to server error > Sent from the Apache Geronimo - Users mailing list archive at Nabble.com. >
Re: Maven Plugin and Changing Ports
On Aug 14, 2008, at 9:32 AM, Vamsavardhana Reddy wrote: Look at plugins\corba\j2ee-corba-yoko\pom.xml . You can modify 1050 to include your own port number so that the binaries you build will use that port number you specify. I don't think that will work because the value is overridden in the config.xml snippet in geronimo-plugin.xml generated from the pom and the value ends up getting set from the var/config/config- substitutions.properties file. From your first post I suspect you might want a lighter-weight server than full geronimo. You might consider assembling your own server with just the bits you need, just like we do :-) In this case you can change the port value by including a plugin that only has the overriding value in the geronimo-plugin.xml. If you don't want to learn how to assemble your own server just yet you can also override the value on the geronimo command line; I think its possible to do this through the g-m-p but I'm not sure how. You'd need the equivalent of - Dorg.apache.geronimo.config.substitution.prefix.COSNamingPort=1051 You might also be able to set an environment property to make this work. Hope this helps david jencks ++Vamsi On Thu, Aug 14, 2008 at 9:52 PM, Geoffrey Wiseman <[EMAIL PROTECTED] > wrote: Ok, with the Geronimo Plugin and Assemblies to 2.1.2, both Geronimo- tomcat6-javaee5 and Geronimo-jetty6-javaee5 seem to load partially, although the Yoko ORB wants to grab Port 1050 that's currently held by ccApp.exe (Norton AntiVirus), which seems to be a known problem. Is there any way to change the ports used by an assembly that comes out of the repo, rather than one you have installed locally? Some kind of configuration parameter that I can feed into the POM to change the port?
Re: Geronimo Maven Plugin
On Aug 14, 2008, at 8:34 AM, Geoffrey Wiseman wrote: I’d like to use Geronimo to run some integration tests in Maven that are going to require a container and a message queue. To that end, I briefly looked at Cargo, which I’ve used in the past, but they seem to support 1.0.X, not even 1.1, let alone 2.X, so I decided that was a little too far back, and I didn’t really want to upgrade/maintain the Cargo container definition, at least, not when I’m fairly new to Geronimo. That meant it was time to take a look at Geronimo-maven-plugin, which I did, ran into some issues. I searched the mailing list, but didn’t find much recent traffic about the plugin at all. Either I’m incapable of running a good search, not many people are using the plugin lately, they’re discussing it somewhere else, or they’re not running into the problems I’m having, I’m not sure which. Either way, I’d like to clarify some points, so if there’s a better place to discuss this, let me know. In short: · What’s a good, working configuration for a relatively current Maven to get a J2EE Geronimo up and running? · Should I use org.apache.geronimo.plugins or org.apache.geronimo.buildsupport? · Do the plugin version and assembly version need to be in sync, and do they correspond to the version of Geronimo that I’m getting? · If not: o What version of the plugin should I use? o What assembly and assembly version should I use? I ran into a bunch of issues, I think many of which were related to the fact that the example in the documentation pointed me at some elements that aren’t incredibly up-to-date (old plugin groupid, old assembly artifactids) and I ended up with assemblies and plugins at different version numbers, which I suspect is a problem, although I haven’t yet gotten any combination working. If the assembly and plugin don’t need to be in sync, then I can report a whack of issues that you might encounter when they aren’t in sync. Now that I’ve found higher version numbers and more combinations, I’m going to keep trying, and I may find something that works, but pointers to a working config would probably help as well. You should use the plugin corresponding to your geronimo version. The one in buildsupport is current, the other is antique. Where is the bad documentation? Maybe we should update or remove it. I would check out geronimo server/branches/2.1 or server/tags/2.1.2 or server/trunk, build it with maven 2.0.9, and look into the testsuite directory. It's a bit convoluted (but ___much___ simpler than it used to be) but is a working example of how to run integration tests in geronimo using the geronimo-maven-plugin along with some other useful infrastructure. thanks david jencks
Re: Is config.ser ever used??
On Aug 14, 2008, at 8:12 AM, Luciano Salotto wrote: We are working on creating an 'image' of WASCE (2.0), with the application already bundled. Initially we have a clean install of WASCE and deploy the application to it, then upload that to a server for the end user to download and use locally. We don't want to do that on every code change, so we just replace the corresponding modified (or add the new) jar in the expanded EAR structure in the repository entry. On a full repository entry change (means we created the full expanded EAR structure and replace that in the server) we had failures saying that the application couldn't be found. That's when knew about this config.ser, config.sha1 and config.id files. What I did then, was to hand over the files of another WASCE local installation I have (I had deployed the application through the Eclipse plugin, so that generated those files), to my surprise that made the application work, even though we all have very different install directories (I can see in the config.ser that there is a part that looks like the web.xml that has a context parameter refering to my local install) and mostly what surprised me is that my workspace was outdated, meaning that the EAR that was generated for the server version had more jars than my local one. That made me think about the question on the subject.. is the config.ser ever used at all? or just some code checking that the serialization file is there? It is very definitely used. Deployment in geronimo consists of translating whatever deployment plans (javaee spec dds, annotations, geronimo service plans, etc) into geronimo service component (gbean) descriptors (GBeanData) and serializing them into the config.ser file. When you start a plugin (module) the config.ser is deserialized and the components configured and started. Tomcat doesn't fit all that well into this idea and the main tomcat application gbean includes the web.xml as a data element. FWIW I'd suggest you look into the custom server assembly features using maven and the car-maven-plugin available in the latest was ce (and geronimo 2.1 and later). I'm not familiar with exactly what comes with was ce but using geronimo I'd assemble a custom server directly, something like what is outlined here: http://cwiki.apache.org/GMOxDOC21/constructing-a-special-purpose-server-using-maven.html thanks david jencks Thanks in advance Luciano
Re: EAR bundle dir classpath issue
I think you've identified two bugs. Could you please open jira issues
for them?
https://issues.apache.org/jira/browse/GERONIMO
I don't immediately see a workaround other than defining the "lib"
directory to be / and putting all the lib jars in the root of the ear.
thanks
david jencks
On Aug 14, 2008, at 7:13 AM, fmeili wrote:
Hi,
I've try to build an EAR with the default lib/ bundle directory
without
using the manifes Class-Path entry in all WAR's which references the
jar
files in the lib/ directory. This EAR should be standard JEE5
compliant and
should be deployable without any change in Geronimo 2.1.2 and
GlassFish
(latest Version).
Now I found a difference in how to access the jar files located in
the EARs
lib/ directory from within an WAR module.
In Geronimo I have to use:
getClass().getClassLoader().getResourceAsStream("lib/sample.jar")
to get the jar file content.
In GlassFish I have to use:
getClass().getClassLoader().getResourceAsStream("sample.jar")
notice - without the lib/ prefix.
As far as I understand the JEE5 specification (section 8.2.1 Bundled
Libraries), all JAR-Files in the EARs lib/ directory should be
available in
all (also WAR) Modules classloaders. So I think the lib/ prefix
should not
be specified.
I've tried to workaround this problem by specifying the lib
directory in the
WAR manifest entry with the following entry:
ClassPath: lib/
But this results in an deployment error in Geronimo with the following
message:
15:20:13,170 ERROR [DirectoryHotDeployer] Unable to deploy: Manifest
class
path
entries must end with the .jar extension (J2EE 1.4 Section 8.2):
module=../
org.apache.geronimo.common.DeploymentException: Manifest class path
entries
must
end with the .jar extension (J2EE 1.4 Section 8.2): module=../
at
org.apache.geronimo.deployment.DeploymentContext.addManifestClassPath
(DeploymentContext.java:419)
...
I think this is definitely an error because the JEE5 specification
section
8.2.1 explicitely allows directories in manifest Class-Path entries.
So it seems the workaround didn't work, too.
Do I make something wrong?
If not, do I have a chance to generate an generic EAR file (with the
same
source code) with bundled lib/ directory usage from WAR modules,
which is
deployable under Geronimo and GlassFish?
Thanks,
Frank
--
View this message in context:
http://www.nabble.com/EAR-bundle-dir-classpath-issue-tp18982334s134p18982334.html
Sent from the Apache Geronimo - Users mailing list archive at
Nabble.com.
Re: Maven Plugin and Changing Ports
Look at plugins\corba\j2ee-corba-yoko\pom.xml . You can modify 1050 to include your own port number so that the binaries you build will use that port number you specify. ++Vamsi On Thu, Aug 14, 2008 at 9:52 PM, Geoffrey Wiseman <[EMAIL PROTECTED]>wrote: > Ok, with the Geronimo Plugin and Assemblies to 2.1.2, both > Geronimo-tomcat6-javaee5 and Geronimo-jetty6-javaee5 seem to load partially, > although the Yoko ORB wants to grab Port 1050 that's currently held by > ccApp.exe (Norton AntiVirus), which seems to be a known problem. > > > > Is there any way to change the ports used by an assembly that comes out of > the repo, rather than one you have installed locally? Some kind of > configuration parameter that I can feed into the POM to change the port? >
Re: Help! Could not publish to server error
Seems there are others on this forum with the same problem, and it appears to be a Java version issue. I'm using 1.6 but will have to try it with 1.5. gsilverman wrote: > > Help! I cannot publish a dynamic web application to Geronimo v2.1.2 using > Eclipse 3.4. > -- View this message in context: http://www.nabble.com/Help%21-Could-not-publish-to-server-error-tp18984957s134p18985110.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Maven Plugin and Changing Ports
Ok, with the Geronimo Plugin and Assemblies to 2.1.2, both Geronimo-tomcat6-javaee5 and Geronimo-jetty6-javaee5 seem to load partially, although the Yoko ORB wants to grab Port 1050 that's currently held by ccApp.exe (Norton AntiVirus), which seems to be a known problem. Is there any way to change the ports used by an assembly that comes out of the repo, rather than one you have installed locally? Some kind of configuration parameter that I can feed into the POM to change the port?
Help! Could not publish to server error
Help! I cannot publish a dynamic web application to Geronimo v2.1.2 using Eclipse 3.4. I followed the tutorial, Web Application for EJB access, to the letter and I get the following error when I add the ejb and web projects to the running Geronimo server in Eclipse: Publishing to Apache Geronimo v2.1 Server at localhost...has encountered a problem. Could not publish to servrer. The "details" page explains this is due to a "java.lang.NullPointerException". What's going on. Has anyone been able to publish to tutorial app? -- View this message in context: http://www.nabble.com/Help%21-Could-not-publish-to-server-error-tp18984957s134p18984957.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
SCA support in Geronimo by integrating Tuscany
I am looking at providing SCA support in Geronimo by integrating Tuscany which implements SCA v1.0 specifications [1]. Last year Manu and myself have developed a Tuscany plugin for Geronimo with limited functionality where the services are exposed as webservices using the web container in Geronimo and service references used EJB binding. The plugin works with v2.0 of Geronimo. The code is available in Geronimo svn at [2]. That integration is not a full fledged integration. Now there is also an SCA Java EE Integration Specification [3] v1.0 released in May 2008. We have been discussing in Tuscany dev-list on and off (see [4]) about the specific scenarios and use cases to be considered as a starting point and work towards a full implementation of the SCA Java EE Spec. But, nothing is like hearing first hand from the the users what function would they want to see and what are the important use cases. Some of the functions needed are common to Java EE servers as such and ideal place for this is Tuscany codebase. Starting with the SCA Java EE Spec, I have been working on modelling regular JavaEE applications as SCA contributions (which is not specific to Geronimo). I should have sent this mail much earlier to get input from Geronimo user community, but, better late than never. Please reply to this e-mail on what use cases and scenarios are important to you and you will be looking forward to consume. Your input will be very helpful in driving this integration effort. Thanks and best regards, Vamsi [1] http://www.osoa.org/display/Main/Service+Component+Architecture+Specifications [2] http://svn.apache.org/repos/asf/geronimo/plugins/tuscany/ [3] http://www.osoa.org/download/attachments/35/SCA_JAVAEE_Integration_V100.pdf?version=1 [4] http://www.mail-archive.com/[EMAIL PROTECTED]/msg00365.html
Geronimo Maven Plugin
I'd like to use Geronimo to run some integration tests in Maven that are going to require a container and a message queue. To that end, I briefly looked at Cargo, which I've used in the past, but they seem to support 1.0.X, not even 1.1, let alone 2.X, so I decided that was a little too far back, and I didn't really want to upgrade/maintain the Cargo container definition, at least, not when I'm fairly new to Geronimo. That meant it was time to take a look at Geronimo-maven-plugin, which I did, ran into some issues. I searched the mailing list, but didn't find much recent traffic about the plugin at all. Either I'm incapable of running a good search, not many people are using the plugin lately, they're discussing it somewhere else, or they're not running into the problems I'm having, I'm not sure which. Either way, I'd like to clarify some points, so if there's a better place to discuss this, let me know. In short: * What's a good, working configuration for a relatively current Maven to get a J2EE Geronimo up and running? * Should I use org.apache.geronimo.plugins or org.apache.geronimo.buildsupport? * Do the plugin version and assembly version need to be in sync, and do they correspond to the version of Geronimo that I'm getting? * If not: o What version of the plugin should I use? o What assembly and assembly version should I use? I ran into a bunch of issues, I think many of which were related to the fact that the example in the documentation pointed me at some elements that aren't incredibly up-to-date (old plugin groupid, old assembly artifactids) and I ended up with assemblies and plugins at different version numbers, which I suspect is a problem, although I haven't yet gotten any combination working. If the assembly and plugin don't need to be in sync, then I can report a whack of issues that you might encounter when they aren't in sync. Now that I've found higher version numbers and more combinations, I'm going to keep trying, and I may find something that works, but pointers to a working config would probably help as well.
Is config.ser ever used??
We are working on creating an 'image' of WASCE (2.0), with the application already bundled. Initially we have a clean install of WASCE and deploy the application to it, then upload that to a server for the end user to download and use locally. We don't want to do that on every code change, so we just replace the corresponding modified (or add the new) jar in the expanded EAR structure in the repository entry. On a full repository entry change (means we created the full expanded EAR structure and replace that in the server) we had failures saying that the application couldn't be found. That's when knew about this config.ser, config.sha1 and config.id files. What I did then, was to hand over the files of another WASCE local installation I have (I had deployed the application through the Eclipse plugin, so that generated those files), to my surprise that made the application work, even though we all have very different install directories (I can see in the config.ser that there is a part that looks like the web.xml that has a context parameter refering to my local install) and mostly what surprised me is that my workspace was outdated, meaning that the EAR that was generated for the server version had more jars than my local one. That made me think about the question on the subject.. is the config.ser ever used at all? or just some code checking that the serialization file is there? Thanks in advance Luciano
EAR bundle dir classpath issue
Hi,
I've try to build an EAR with the default lib/ bundle directory without
using the manifes Class-Path entry in all WAR's which references the jar
files in the lib/ directory. This EAR should be standard JEE5 compliant and
should be deployable without any change in Geronimo 2.1.2 and GlassFish
(latest Version).
Now I found a difference in how to access the jar files located in the EARs
lib/ directory from within an WAR module.
In Geronimo I have to use:
getClass().getClassLoader().getResourceAsStream("lib/sample.jar")
to get the jar file content.
In GlassFish I have to use:
getClass().getClassLoader().getResourceAsStream("sample.jar")
notice - without the lib/ prefix.
As far as I understand the JEE5 specification (section 8.2.1 Bundled
Libraries), all JAR-Files in the EARs lib/ directory should be available in
all (also WAR) Modules classloaders. So I think the lib/ prefix should not
be specified.
I've tried to workaround this problem by specifying the lib directory in the
WAR manifest entry with the following entry:
ClassPath: lib/
But this results in an deployment error in Geronimo with the following
message:
15:20:13,170 ERROR [DirectoryHotDeployer] Unable to deploy: Manifest class
path
entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../
org.apache.geronimo.common.DeploymentException: Manifest class path entries
must
end with the .jar extension (J2EE 1.4 Section 8.2): module=../
at
org.apache.geronimo.deployment.DeploymentContext.addManifestClassPath
(DeploymentContext.java:419)
...
I think this is definitely an error because the JEE5 specification section
8.2.1 explicitely allows directories in manifest Class-Path entries.
So it seems the workaround didn't work, too.
Do I make something wrong?
If not, do I have a chance to generate an generic EAR file (with the same
source code) with bundled lib/ directory usage from WAR modules, which is
deployable under Geronimo and GlassFish?
Thanks,
Frank
--
View this message in context:
http://www.nabble.com/EAR-bundle-dir-classpath-issue-tp18982334s134p18982334.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Antwort: Re: Re: Re: Re: Re: Antwort: Re: Change Version of Apache CXF for Geronimo
Hi Jarek, I will open a Geronimo-Bug on the deployment-issue after my 10-days holidays. Concerning the Webservice-Issue I added the Apache CXF-User-List to this issue. The error arises on the server, but is not logged there. The stacktrace I posted is from the client. I tried to debug the problem but I got lost somewhere in Apache CXF. Here the error once more: Stacktrace: javax.xml.ws.soap.SOAPFaultException: An error was discovered processing the header at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:175) at $Proxy21.empfangeDatenbestandDelta(Unknown Source) at de.mypath.ws.OrigReadWSClientImpl.callWebservice(OrigReadWSClientImpl.java:157) at de.mypath.ws.OrigReadWSClientImpl.leseDatenbestand(OrigReadWSClientImpl.java:61) at de.mypath.ws.OrigReadWSClientImplTest.testLeseDatenbestand(OrigReadWSClientImplTest.java:33) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99) at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75) at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45) at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:66) at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:35) at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: org.apache.cxf.binding.soap.SoapFault: An error was discovered processing the header at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:70) at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:35) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:208) at org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:96) at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:183) at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:56) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:208) at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:429) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1955) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1791) at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66) at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:575) at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:208) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:276) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:222) at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73) at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135) ... 24 more Security-Header: http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"; soap:mustUnderstand="1"> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; wsu:Id="UsernameToken-25089808"> myuse
