[jira] Commented: (GERONIMO-3874) Deployment of Spring SpringContextResourceAdapter fails
[
https://issues.apache.org/jira/browse/GERONIMO-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743809#action_12743809
]
sebastien chatel commented on GERONIMO-3874:
It's caused by the protected getter :
protected String getContextConfigLocation() {
return this.contextConfigLocation;
}
Here is how the ConnectorModuleBuilder find property methods :
Class activationSpecClass = cl.loadClass(activationSpecClassName);
methods = activationSpecClass.getMethods();
but getMethods() return public methods only.
And then a getters.keySet().retainAll(setters);
Doesnt keep the setter property.
> Deployment of Spring SpringContextResourceAdapter fails
> ---
>
> Key: GERONIMO-3874
> URL: https://issues.apache.org/jira/browse/GERONIMO-3874
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment
>Affects Versions: 2.1
> Environment: Running the full geronimo tomcat 6 - 2.1 distribution on
> Fedora Core 5 Linux
>Reporter: Michael Lee
>
> I have been trying to prototype the deployment of Spring JMS application
> components in a Resource Adaptor format using the
> org.springframework.jca.context.SpringContextResourceAdapter introduced in
> Spring 2.5.
> After playing with various configurations I've attempted to take this right
> back to "vanilla" configurations of Spring RA config and Geronimo Deployment
> and I still get the same problem with deployment failure with the error
> message (in the server geronimo.out log): Unknown attribute
> "ContextConfigLocation".
> --
> ra.xml Descriptor
> --
> My ra.xml is currently a straight copy from
> http://static.springframework.org/spring/docs/2.5.x/api/org/springframework/jca/context/SpringContextResourceAdapter.html
>
>
> 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/connector_1_5.xsd";
> version="1.5">
> Spring Framework
> Spring Connector
> 1.0
>
>
> org.springframework.jca.context.SpringContextResourceAdapter
>
>
> ContextConfigLocation
>
> java.lang.String
>
> META-INF/applicationContext.xml
>
>
>
> --
> geronimo-ra.xml (built using maven - so pom values replaced)
> --
>
> xmlns:con="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2";
> xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.1";
> xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.1";>
>
>
> ${pom.groupId}
> ${pom.artifactId}
> ${pom.version}
> rar
>
>
>
> console.dbpool
> domain
>
>
>
>
>
>
>
> SpringCommonContextResourceAdapter
>
>
> DefaultWorkManager
>
>
>
>
>
> --
> Stack trace during deployment failure
> --
> 14:50:02,735 WARN [ConfigurationUtil] Could not load gbean
> default/job-creation-files/1.0.0-SNAPSHOT/rar?J2EEApplication=null,JCAResource=default/job-creation-files/1.0.0-SNAPSHOT/rar,ResourceAdapter=default/job-creation-files/1.0.0-SNAPSHOT/rar,ResourceAdapterModule=default/job-creation-files/1.0.0-SNAPSHOT/rar,j2eeType=JCAResourceAdapter,name=SpringCommonContextResourceAdapter
> org.apache.geronimo.gbean.InvalidConfigurationException: Could not inject
> configuration data into the GBean
> default/job-creation-files/1.0.0-SNAPSHOT/rar?J2EEApplication=null,JCAResource=default/job-creation-files/1.0.0-SNAPSHOT/rar,ResourceAdapter=default/job-creation-files/1.0.0-SNAPSHOT/rar,ResourceAdapterModule=default/job-creation-files/1.0.0-SNAPSHOT/rar,j2eeType=JCAResourceAdapter,name=SpringCommonContextResourceAdapter
> at
> org.apache.geronimo.gbean.runtime.GBeanInstance.(GBeanInstance.java:377)
> at
> org.apache.geronimo.kernel.basic.BasicKernel.loadGBean(BasicKernel.java:354)
> at
> org.apache.geron
[jira] Updated: (GERONIMO-4678) Initial Japanese translation
[ https://issues.apache.org/jira/browse/GERONIMO-4678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kan Ogawa updated GERONIMO-4678: Patch Info: [Patch Available] > Initial Japanese translation > > > Key: GERONIMO-4678 > URL: https://issues.apache.org/jira/browse/GERONIMO-4678 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: console >Reporter: Kan Ogawa >Assignee: Jarek Gawor >Priority: Minor > Fix For: 2.1.5, 2.2 > > Attachments: geronimo-v21_i18n-ja_G4485-G4532_v1.patch, > geronimo-v22_i18n-ja_G4474-G4484-G4517_v1.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4678) Initial Japanese translation
[ https://issues.apache.org/jira/browse/GERONIMO-4678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kan Ogawa updated GERONIMO-4678: Attachment: geronimo-v22_i18n-ja_G4474-G4484-G4517_v1.patch Jarek, Attached new Japanese translation patch for V2.2 (trunk). All resource bundles in this patch are created without native2ascii (see GERONIMO-4763 issue). Please commit it. > Initial Japanese translation > > > Key: GERONIMO-4678 > URL: https://issues.apache.org/jira/browse/GERONIMO-4678 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: console >Reporter: Kan Ogawa >Assignee: Jarek Gawor >Priority: Minor > Fix For: 2.1.5, 2.2 > > Attachments: geronimo-v21_i18n-ja_G4485-G4532_v1.patch, > geronimo-v22_i18n-ja_G4474-G4484-G4517_v1.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 804541
Geronimo Revision: 804541 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090815/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090815
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 40 minutes 37 seconds
[INFO] Finished at: Sat Aug 15 21:43:59 EDT 2009
[INFO] Final Memory: 687M/940M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090815/logs-2100-tomcat/
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:45.155
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:01:04.152)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:33.756)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:39.278)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:21.343)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:31.197)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:30.385)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:58.460)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:50.172)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:01:00.051)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:47.876)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:33.486)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:31.861)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:37.418)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:06.323)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests FAILURE (0:01:16.694) Java
returned: 1
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:51.423)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:29.360)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:53.855)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security FAILURE (0:00:47.645) Java
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:34.391)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:32.051)
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web-testsuite/test-myfaces SUCCESS (0:00:34.804)
[INFO] web-testsuite/test-tomcat RUNNING
Re: [BUILD] trunk: Failed for Revision: 804178
I think I fixed this in rev 804534.
thanks for figuring out where the problem is!
david jencks
On Aug 14, 2009, at 11:21 AM, Ivan wrote:
The failed console-advanced case is caused by
IlegalArgumentException "About the
IllegalArgumentException"Qualifier patterns must not be present when
first URLPattern is an exact pattern"
I found a JIRA 2709 and checked the codes in the Jetty's
securityHandler, I found some codes of replace %3A and : are removed,
So do we need recover those codes ? Or for some reasons, we do not
need them. Thanks for any comment !
2009/8/14
Geronimo Revision: 804178 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090814/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090814
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 43 minutes 54 seconds
[INFO] Finished at: Fri Aug 14 09:47:18 EDT 2009
[INFO] Final Memory: 402M/1003M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090814/logs-0900-tomcat/
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-
SNAPSHOT:provided
[INFO] Using geronimoHome: /home/geronimo/geronimo/trunk/testsuite/
target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding: /home/geronimo/.m2/repository/org/apache/geronimo/
assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-
javaee5-2.2-SNAPSHOT-bin.zip into /home/geronimo/geronimo/trunk/
testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to: /home/geronimo/geronimo/trunk/
testsuite/target/geronimo-logs/
org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:45.477
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml
to /home/geronimo/.m2/repository/org/apache/geronimo/testsuite/
testsuite/testing/testsuite-testing.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS
(0:01:15.516)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS
(0:00:34.504)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS
(0:00:41.232)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS
(0:00:21.612)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS
(0:06:36.297)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS
(0:01:34.386)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS
(0:02:02.926)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS
(0:00:53.859)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS
(0:00:47.690)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS
(0:00:47.352)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS
(0:00:34.048)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS
(0:00:30.219)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS
(0:00:35.109)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS
(0:01:12.949)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests FAILURE
(0:01:17.485) Java returned: 1
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS
(0:00:52.782)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS
(0:00:30.773)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tes
Re: [Doubts] X509 Signing
Hello David,
Thanks for your suggestions.
So far, after setting up UsernameToken profile, I have set the ws-security
(X509 profile - signing and encryption) with the property file for basic
security. I have attached the patches on the JIRA-4642.
Now I am after the things you suggested. It sounds a good idea to use the
geronimo built-in security for the same.
Many Thanks again for your immediate reply!
Rahul
On Wed, Aug 12, 2009 at 5:57 PM, David Jencks wrote:
> HI Rahul,
> I don't understand any details of what you are trying to do but I think you
> are trying to get access to a certificate so some parts of the xml message
> can be signed.
>
> In geronimo we have several gbeans to help with managing certificate stores
> and trust stores. These are set up so that if you get a reference to the
> appropriate gbean you should be able to access the cerificate as needed with
> no further passwords or authentication needed. While these are normally
> present in servers you can set one up in an app client if you want.
>
> The portal pages I think you are mentioning let you administer these
> gbeans.
>
> The jetty https connector is set up to use one of these gbeans, you might
> find it a useful example of how to proceed for
> instance HTTPSSelectChannelConnector and GeronimoSelectChannelSSLListener.
>
> The central class is
> org.apache.geronimo.management.geronimo.KeystoreManager implemented
> by org.apache.geronimo.security.keystore.FileKeystoreManager in the
> framework/modules/geronimo-security module.
>
> I'd suspect you might want to get a KeystoreInstance from the
> KeystoreManager and then get the Certificate you want from that.
>
> Hope this helps,
> david jencks
>
> On Aug 11, 2009, at 2:15 PM, rahul.soa wrote:
>
> Hello Jarek,
>
> I hope you are doing well.
>
> Presently, I am setting the signing at client side, I have a couple of
> doubts.
>
> I think, I can do something similar in the CXFPortMethodInterceptor
>
> String signatureKeyIdentifier = (String)
> properties.get("signatureKeyIdentifier");
> String user = (String) properties.get("user");
>
> //in case where Signature
> if (containsValue(action, WSHandlerConstants.SIGNATURE)) {
> * // doubt about this, how CXFPortMethodInterceptor will know about
> this*
> properties.put(WSHandlerConstants.SIG_PROP_FILE,
> clientKeystore.properties");
> // alias or user
>properties.put(WSHandlerConstants.USER, user);
>
> if(signatureKeyIdentifier.equals("DirectReference"))
> properties.put(WSHandlerConstants.SIG_KEY_ID,
> "DirectReference");
> if(signatureKeyIdentifier.equals("IssuerSerial"))
> properties.put(WSHandlerConstants.SIG_KEY_ID, "IssuerSerial");
> //in order to obtain the key password for the private key
> properties.put(WSHandlerConstants.PW_CALLBACK_CLASS,
> ClientKeystorePasswordCallback.class.getName());
>
> }
>
>
> I think we should specify the following things in the under the
> in the geronimo-web.xml at client side.
>
> Signature
> myclientkey
> IssuerSerial
>
> can we set the keypassword too in the property? what other things we should
> set in the property?
>
> Question:1
> Here, first thing is how we can provide signature property file, in the
> above case "clientKeystore.properties". It should be at client side. If this
> is in the client application written by the user then how can we give the
> reference of this in the CXFPortMethodInterceptor. In other words, *where
> to set this property *
> properties.put(WSHandlerConstants.SIG_PROP_FILE,
> clientKeystore.properties");
>
> Question2:
>
> For the ClientKeystorePasswordCallback, how can the client send the
> keypassword,
>
> through the geronimo-web.xml?
> keypass
>
>
> Another thing is, I noticed one thing, In geronimo server we have these two
> following tabs under the
>Security
> Keystores
> Certificate
> Authority
>
>
> What are these for?
>
>
> Thanks for your help.
>
> Best Regards,
> Rahul
>
>
>
> PS: for signing and encryption, I think we need the bouncy castle and the
> xalan jar files in the cxf plugin, I pulled them
>
>
>
[jira] Issue Comment Edited: (GERONIMO-4642) "WS-Security support for JAX-WS Web Services"
[
https://issues.apache.org/jira/browse/GERONIMO-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743746#action_12743746
]
Rahul Mehta edited comment on GERONIMO-4642 at 8/15/09 1:45 PM:
Hello Devs,
This patch allows to set the ws-security at the service side in CXF/Jetty. This
is done through by passing the properties file in the geronimo-web.xml.
Note: please apply UsernameToken_ServerSide[2].txt patch before this patch.
This patch (X509SigningEncrytion_ServerSide_CXF.txt) might have some duplicate
code of CXFEndpoint.java, as it is contained in both the patches.
But indeed David Jencks suggested a better approach for setting X509
sign/encrypt security with the use of geronimo built in security. I will move
on this to figure it out.
we can use something like this in the geronimo-web.xml at the service side:
DoubleItServiceImpl
Signature Encrypt Timestamp
myservicekey
skpass
serviceKeystore.properties
serviceKeystore.properties
Signature Encrypt Timestamp
myservicekey
serviceKeystore.properties
serviceKeystore.properties
myclientkey
DirectReference
skpass
http://www.w3.org/2001/04/xmlenc#tripledes-cbc
Jarek, should we make the tag optional in the xsd?
Many Thanks to Jarek and community members for the help.
Rahul
was (Author: rahul.soa):
Hello Devs,
This patch allows to set the ws-security at the service side in CXF/Jetty. This
is done through by passing the properties file in the geronimo-web.xml.
Note: please apply UsernameToken_ServerSide[2].txt patch before this patch.
This patch (X509SigningEncrytion_ServerSide_CXF.txt) might have some duplicate
code of CXFEndpoint.java, as it is contained in both the patches.
But indeed David Jencks suggested a better approach for setting X509
sign/encrypt security with the use of geronimo built in security. I will move
on this to figure it out.
Many Thanks to Jarek and community members for the help.
Rahul
> "WS-Security support for JAX-WS Web Services"
> -
>
> Key: GERONIMO-4642
> URL: https://issues.apache.org/jira/browse/GERONIMO-4642
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: webservices
> Environment: Apache Geronimo, Apache CXF, Apache Axis2, Ws-Security,
> Web Services, Java, Linux
>Reporter: Rahul Mehta
>Priority: Minor
> Attachments: RampartToAxis2.txt, site.patch, usernameToken.patch,
> usernameToken[2].patch, UsernameToken_ServerSide[2].txt,
> X509SigningEncrytion_CXF.txt, X509SigningEncrytion_ServerSide_CXF.txt
>
> Original Estimate: 2016h
> Remaining Estimate: 2016h
>
> To integrate and enable the WS-Security features of Apache Axis2 and Apache
> CXF in Apache Geronimo:
> --
> Apache Geronimo supports two JAX-WS providers: Axis2 and CXF and both of
> these libraries have some WS-Security features. But these features are not
> integrated/enabled in Geronimo. So the goal is to enable these features from
> within Geronimo. That involves basically two things:
> 1) that the modules (i.e. WSS4J) that provide the WS-Security features for
> Axis2 and CXF are installed with Geronimo, and
> 2) that the WS-Security features such as [XML Security ('XML Signature' -
> allows one to send along with the message a digital signature of it, which
> assures that no one modified the message content between the sender and
> receiver, 'XML Encryption' -allows one to encrypt the message body or only
> its part using the given cryptography algorithm) and Tokens ('Username
> Tokens' - WS-Security scenario adds username and password values to the
> message header, 'Timestamps' - Timestamps specify how long the security data
> remains valid, 'SAML Tokens')] can be enabled and configured on web services
> via Geronimo deployment descriptors and/or annotations. For example, given
> some web service that is annotated with @WebService; so to ensure that the
> service only accepts WS-Security -secured messages, it should be something
> like "to add @WS-Security annotation".
> Further in detail, we can consider WS-Security policies which can be applied
> to the SOAP messages that pass between web services and web service controls.
> A WS-Security is controlled in WS-Security policy files. The WS-Security
> policy file (WSSE file) defines the security policy applied to the SOAP
> messages that pass between web services and their clients.[1]
> So we can use something like following annotation @WS-Security
> file="MyWebServicePolicy.wsse" Example: @W
[BUILD] trunk: Failed for Revision: 804505
Geronimo Revision: 804505 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090815/build-1500.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090815
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 42 minutes 57 seconds
[INFO] Finished at: Sat Aug 15 15:46:12 EDT 2009
[INFO] Final Memory: 403M/1015M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090815/logs-1500-tomcat/
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:47.140
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:01:12.599)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:35.142)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:41.188)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:21.205)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:32.998)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:36.762)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:02.729)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:54.405)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:58.978)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:46.915)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:34.387)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:30.384)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:35.682)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:05.356)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests FAILURE (0:01:19.279) Java
returned: 1
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:53.812)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:31.507)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:53.270)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security FAILURE (0:00:48.665) Java
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:32.784)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:31.515)
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web-testsuite/test-myfaces SUCCESS (0:00:33.471)
[INFO] web-testsuite/test-tomcat RUNNING
Re: Trunk build failed
I'm wiping out the entire directory and starting from scratch. Moving back a Maven version is causing some issues, and there's some file permissions issues, somehow, even though I've used my current account to do everything. Eric -- View this message in context: http://www.nabble.com/Trunk-build-failed-tp24974418s134p24987208.html Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
[jira] Updated: (GERONIMO-4642) "WS-Security support for JAX-WS Web Services"
[
https://issues.apache.org/jira/browse/GERONIMO-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Mehta updated GERONIMO-4642:
--
Attachment: X509SigningEncrytion_ServerSide_CXF.txt
Hello Devs,
This patch allows to set the ws-security at the service side in CXF/Jetty. This
is done through by passing the properties file in the geronimo-web.xml.
Note: please apply UsernameToken_ServerSide[2].txt patch before this patch.
This patch (X509SigningEncrytion_ServerSide_CXF.txt) might have some duplicate
code of CXFEndpoint.java, as it is contained in both the patches.
But indeed David Jencks suggested a better approach for setting X509
sign/encrypt security with the use of geronimo built in security. I will move
on this to figure it out.
Many Thanks to Jarek and community members for the help.
Rahul
> "WS-Security support for JAX-WS Web Services"
> -
>
> Key: GERONIMO-4642
> URL: https://issues.apache.org/jira/browse/GERONIMO-4642
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: webservices
> Environment: Apache Geronimo, Apache CXF, Apache Axis2, Ws-Security,
> Web Services, Java, Linux
>Reporter: Rahul Mehta
>Priority: Minor
> Attachments: RampartToAxis2.txt, site.patch, usernameToken.patch,
> usernameToken[2].patch, UsernameToken_ServerSide[2].txt,
> X509SigningEncrytion_CXF.txt, X509SigningEncrytion_ServerSide_CXF.txt
>
> Original Estimate: 2016h
> Remaining Estimate: 2016h
>
> To integrate and enable the WS-Security features of Apache Axis2 and Apache
> CXF in Apache Geronimo:
> --
> Apache Geronimo supports two JAX-WS providers: Axis2 and CXF and both of
> these libraries have some WS-Security features. But these features are not
> integrated/enabled in Geronimo. So the goal is to enable these features from
> within Geronimo. That involves basically two things:
> 1) that the modules (i.e. WSS4J) that provide the WS-Security features for
> Axis2 and CXF are installed with Geronimo, and
> 2) that the WS-Security features such as [XML Security ('XML Signature' -
> allows one to send along with the message a digital signature of it, which
> assures that no one modified the message content between the sender and
> receiver, 'XML Encryption' -allows one to encrypt the message body or only
> its part using the given cryptography algorithm) and Tokens ('Username
> Tokens' - WS-Security scenario adds username and password values to the
> message header, 'Timestamps' - Timestamps specify how long the security data
> remains valid, 'SAML Tokens')] can be enabled and configured on web services
> via Geronimo deployment descriptors and/or annotations. For example, given
> some web service that is annotated with @WebService; so to ensure that the
> service only accepts WS-Security -secured messages, it should be something
> like "to add @WS-Security annotation".
> Further in detail, we can consider WS-Security policies which can be applied
> to the SOAP messages that pass between web services and web service controls.
> A WS-Security is controlled in WS-Security policy files. The WS-Security
> policy file (WSSE file) defines the security policy applied to the SOAP
> messages that pass between web services and their clients.[1]
> So we can use something like following annotation @WS-Security
> file="MyWebServicePolicy.wsse" Example: @WebService @WS-Security
> file="MyWebServicePolicy.wsse"
> public class xyz
> The @WS-Security annotation determines the WS-Security policy file (WSSE) to
> be applied to (1) incoming SOAP invocations of the web service's methods and
> (2) the outgoing SOAP messages containing the value returned by the web
> service's methods.[1]. The attribute file in the above mentioned annotation
> specifies the path to the WS-Security policy file (WSSE file -
> MyWebServicePolicy.wsse) used by the web service.
> Besides configuring WS-Security properties for web services we also need to
> configure the same sort of properties for Web Service references
> (@WebServiceRef) so that clients can also make WS-Security secured calls.
> In addition, I think we can also define some security feature something like
> SecurityFeature similar to other WebService Feature(s) such as
> AddressingFeature, MTOMFeature and RespectBindingFeature . This new feature
> can also have the "enabled property" like other features that is used to
> store whether a particular feature should be enabled or disabled. This type
> should provide either a constructor argument and/or a method that will allow
> the web service developer to set the enabled property. The meaning
[jira] Updated: (GERONIMO-4642) "WS-Security support for JAX-WS Web Services"
[
https://issues.apache.org/jira/browse/GERONIMO-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Mehta updated GERONIMO-4642:
--
Attachment: UsernameToken_ServerSide[2].txt
Corrected JettyModuleBuilder part of the UsernameToken_ServerSide[1].txt patch
to get all the properties passed in geronimo-web.xml (at service side) and pass
them into ServletConfiguration.
Renamed into UsernameToken_ServerSide[2].txt
PS: this patch provides the support for UsernameToken Profile at server side in
(CXF and Jetty).
Thank you.
Rahul
> "WS-Security support for JAX-WS Web Services"
> -
>
> Key: GERONIMO-4642
> URL: https://issues.apache.org/jira/browse/GERONIMO-4642
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: webservices
> Environment: Apache Geronimo, Apache CXF, Apache Axis2, Ws-Security,
> Web Services, Java, Linux
>Reporter: Rahul Mehta
>Priority: Minor
> Attachments: RampartToAxis2.txt, site.patch, usernameToken.patch,
> usernameToken[2].patch, UsernameToken_ServerSide[2].txt,
> X509SigningEncrytion_CXF.txt
>
> Original Estimate: 2016h
> Remaining Estimate: 2016h
>
> To integrate and enable the WS-Security features of Apache Axis2 and Apache
> CXF in Apache Geronimo:
> --
> Apache Geronimo supports two JAX-WS providers: Axis2 and CXF and both of
> these libraries have some WS-Security features. But these features are not
> integrated/enabled in Geronimo. So the goal is to enable these features from
> within Geronimo. That involves basically two things:
> 1) that the modules (i.e. WSS4J) that provide the WS-Security features for
> Axis2 and CXF are installed with Geronimo, and
> 2) that the WS-Security features such as [XML Security ('XML Signature' -
> allows one to send along with the message a digital signature of it, which
> assures that no one modified the message content between the sender and
> receiver, 'XML Encryption' -allows one to encrypt the message body or only
> its part using the given cryptography algorithm) and Tokens ('Username
> Tokens' - WS-Security scenario adds username and password values to the
> message header, 'Timestamps' - Timestamps specify how long the security data
> remains valid, 'SAML Tokens')] can be enabled and configured on web services
> via Geronimo deployment descriptors and/or annotations. For example, given
> some web service that is annotated with @WebService; so to ensure that the
> service only accepts WS-Security -secured messages, it should be something
> like "to add @WS-Security annotation".
> Further in detail, we can consider WS-Security policies which can be applied
> to the SOAP messages that pass between web services and web service controls.
> A WS-Security is controlled in WS-Security policy files. The WS-Security
> policy file (WSSE file) defines the security policy applied to the SOAP
> messages that pass between web services and their clients.[1]
> So we can use something like following annotation @WS-Security
> file="MyWebServicePolicy.wsse" Example: @WebService @WS-Security
> file="MyWebServicePolicy.wsse"
> public class xyz
> The @WS-Security annotation determines the WS-Security policy file (WSSE) to
> be applied to (1) incoming SOAP invocations of the web service's methods and
> (2) the outgoing SOAP messages containing the value returned by the web
> service's methods.[1]. The attribute file in the above mentioned annotation
> specifies the path to the WS-Security policy file (WSSE file -
> MyWebServicePolicy.wsse) used by the web service.
> Besides configuring WS-Security properties for web services we also need to
> configure the same sort of properties for Web Service references
> (@WebServiceRef) so that clients can also make WS-Security secured calls.
> In addition, I think we can also define some security feature something like
> SecurityFeature similar to other WebService Feature(s) such as
> AddressingFeature, MTOMFeature and RespectBindingFeature . This new feature
> can also have the "enabled property" like other features that is used to
> store whether a particular feature should be enabled or disabled. This type
> should provide either a constructor argument and/or a method that will allow
> the web service developer to set the enabled property. The meaning of enabled
> or disabled is determined by each individual WebServiceFeature. It is
> important that web services developers be able to enable/disable specific
> features when writing their web applications. [2]
> References:
> [1] [WWW] http://e-docs.bea.com/workshop/docs81/doc/en/core/index.html
> [2] [WWW] http://jcp.
[jira] Updated: (GERONIMO-4642) "WS-Security support for JAX-WS Web Services"
[
https://issues.apache.org/jira/browse/GERONIMO-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Mehta updated GERONIMO-4642:
--
Attachment: (was: UsernameToken_ServerSide[1].txt)
> "WS-Security support for JAX-WS Web Services"
> -
>
> Key: GERONIMO-4642
> URL: https://issues.apache.org/jira/browse/GERONIMO-4642
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: webservices
> Environment: Apache Geronimo, Apache CXF, Apache Axis2, Ws-Security,
> Web Services, Java, Linux
>Reporter: Rahul Mehta
>Priority: Minor
> Attachments: RampartToAxis2.txt, site.patch, usernameToken.patch,
> usernameToken[2].patch, X509SigningEncrytion_CXF.txt
>
> Original Estimate: 2016h
> Remaining Estimate: 2016h
>
> To integrate and enable the WS-Security features of Apache Axis2 and Apache
> CXF in Apache Geronimo:
> --
> Apache Geronimo supports two JAX-WS providers: Axis2 and CXF and both of
> these libraries have some WS-Security features. But these features are not
> integrated/enabled in Geronimo. So the goal is to enable these features from
> within Geronimo. That involves basically two things:
> 1) that the modules (i.e. WSS4J) that provide the WS-Security features for
> Axis2 and CXF are installed with Geronimo, and
> 2) that the WS-Security features such as [XML Security ('XML Signature' -
> allows one to send along with the message a digital signature of it, which
> assures that no one modified the message content between the sender and
> receiver, 'XML Encryption' -allows one to encrypt the message body or only
> its part using the given cryptography algorithm) and Tokens ('Username
> Tokens' - WS-Security scenario adds username and password values to the
> message header, 'Timestamps' - Timestamps specify how long the security data
> remains valid, 'SAML Tokens')] can be enabled and configured on web services
> via Geronimo deployment descriptors and/or annotations. For example, given
> some web service that is annotated with @WebService; so to ensure that the
> service only accepts WS-Security -secured messages, it should be something
> like "to add @WS-Security annotation".
> Further in detail, we can consider WS-Security policies which can be applied
> to the SOAP messages that pass between web services and web service controls.
> A WS-Security is controlled in WS-Security policy files. The WS-Security
> policy file (WSSE file) defines the security policy applied to the SOAP
> messages that pass between web services and their clients.[1]
> So we can use something like following annotation @WS-Security
> file="MyWebServicePolicy.wsse" Example: @WebService @WS-Security
> file="MyWebServicePolicy.wsse"
> public class xyz
> The @WS-Security annotation determines the WS-Security policy file (WSSE) to
> be applied to (1) incoming SOAP invocations of the web service's methods and
> (2) the outgoing SOAP messages containing the value returned by the web
> service's methods.[1]. The attribute file in the above mentioned annotation
> specifies the path to the WS-Security policy file (WSSE file -
> MyWebServicePolicy.wsse) used by the web service.
> Besides configuring WS-Security properties for web services we also need to
> configure the same sort of properties for Web Service references
> (@WebServiceRef) so that clients can also make WS-Security secured calls.
> In addition, I think we can also define some security feature something like
> SecurityFeature similar to other WebService Feature(s) such as
> AddressingFeature, MTOMFeature and RespectBindingFeature . This new feature
> can also have the "enabled property" like other features that is used to
> store whether a particular feature should be enabled or disabled. This type
> should provide either a constructor argument and/or a method that will allow
> the web service developer to set the enabled property. The meaning of enabled
> or disabled is determined by each individual WebServiceFeature. It is
> important that web services developers be able to enable/disable specific
> features when writing their web applications. [2]
> References:
> [1] [WWW] http://e-docs.bea.com/workshop/docs81/doc/en/core/index.html
> [2] [WWW] http://jcp.org/aboutJava/communityprocess/mrel/jsr224/index2.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4795) Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances
[ https://issues.apache.org/jira/browse/GERONIMO-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743725#action_12743725 ] David Jencks commented on GERONIMO-4795: IMO the techniques you mention are usually not the best way to deal with multiple server instances. (2) doesn't make any sense to me -- a plugin has already made use of a deployment plan, and is in a state where an additional deployment plan cannot be interpreted. Recommended (by me) ways to deal with more than one server instance in an installation: a. add a new server instance using the new server instance command: this will create the base directory and proceed to install all the plugins installed in the source server. Since the repo is shared, nothing will change in the repo, but the plugins being installed into the new server will set up the config.xml, and related files and unpack any plugin specific content into the appropriate places. b. Giving an existing additional server instance with a plugin present in the geronimo repo but not installed in the additional instance, installing it into the additional instance will add the config.xml content and related file content and unpack any files needed. if you copy a var directory per your (1) you will get any local changes and edits and data that happen to be present in the server instance, so the results are inherently unpredictable. (a) produces a fresh server without local modifications. > Multiple Server Instances: Uninstalling an application does not remove the > entry from config.xml of other server instances > -- > > Key: GERONIMO-4795 > URL: https://issues.apache.org/jira/browse/GERONIMO-4795 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: commands >Affects Versions: 2.1.3, 2.1.4 > Environment: Windows XP G 214 >Reporter: Ashish Jain >Assignee: Ashish Jain > Fix For: 2.2 > > > 1) Setup another geronimo instance out of the same installation directory. > 2) Deploy an applicaton to one instance. This will result in entry being > created in config.xml for both the instances > 3) Undeploy the application. This results in entry being removed from > config.xml of one instance and other instance > still has entry of the application in config.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 804463
Geronimo Revision: 804463 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090815/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090815
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 45 minutes 39 seconds
[INFO] Finished at: Sat Aug 15 09:48:57 EDT 2009
[INFO] Final Memory: 403M/1015M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090815/logs-0900-tomcat/
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:46.927
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:01:14.050)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:35.958)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:42.254)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:21.634)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:33.285)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:35.559)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:02.850)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:54.701)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:59.824)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:49.709)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:33.450)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:31.182)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:34.929)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:09.330)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests FAILURE (0:01:12.410) Java
returned: 1
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:51.716)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:32.326)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:58.574)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security FAILURE (0:00:48.315) Java
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:32.475)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:31.585)
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web-testsuite/test-myfaces SUCCESS (0:00:33.296)
[INFO] web-testsuite/test-tomcat RUNNING
[BUILD] trunk: Failed for Revision: 804438
Geronimo Revision: 804438 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090815/build-0300.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090815
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 44 minutes 1 second
[INFO] Finished at: Sat Aug 15 03:47:35 EDT 2009
[INFO] Final Memory: 434M/972M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090815/logs-0300-tomcat/
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:47.998
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:01:15.419)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:35.350)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:40.511)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:21.162)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:35.820)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:47.296)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:04.672)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:58.406)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:57.218)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:47.327)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:34.475)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:32.951)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:35.467)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:19.927)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests FAILURE (0:01:15.415) Java
returned: 1
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:51.845)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:31.444)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:54.610)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security FAILURE (0:00:48.003) Java
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:33.466)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:30.954)
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web-testsuite/test-myfaces SUCCESS (0:00:34.308)
[INFO] web-testsuite/test-tomcat RUNNING
