You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by Rami Jaamour <rj...@parasoft.com> on 2004/07/20 00:44:01 UTC
Re: [jira] Commented: (WSFX-19) WSS4J Interoperability Features
Dims,
Do the latest sources compile successfully? After doing cvs up and
merging my changes I get:
compile.tests:
Trying to override old definition of task axis-wsdl2java
Trying to override old definition of task axis-admin
Trying to override old definition of task axis-java2wsdl
compile:
[axis-wsdl2java] log4j:WARN No appenders could be found for logger
(org.apache.axis.i18n.ProjectResourceBundle).
[axis-wsdl2java] log4j:WARN Please initialize the log4j system properly.
[axis-wsdl2java] WSDL2Java
/home/fox/rjaamour/ws-fx/wss4j/test/secconv/../../test/secconv/ping.wsdl
[axis-wsdl2java] PingBindingImpl.java already exists, WSDL2Java will not
overwrite it.
[copy] Copying 2 files to
/home/fox/rjaamour/ws-fx/wss4j/build/work/secconv
[copy] Copying 3 files to
/home/fox/rjaamour/ws-fx/wss4j/build/work/secconv
[javac] Compiling 8 source files to
/home/fox/rjaamour/ws-fx/wss4j/build/classes
[javac]
/home/fox/rjaamour/ws-fx/wss4j/build/work/secconv/WSConvScenario2.java:49:
cannot resolve symbol
[javac] symbol : method getWSConvScenario2 (java.net.URL)
[javac] location: class org.apache.ws.axis.oasis.ping.PingServiceLocator
[javac] PingPort port = (PingPort)
service.getWSConvScenario2(endpoint);
[javac] ^
[javac] 1 error
BUILD FAILED
I don't think that this is related to my changes.
Rami Jaamour
Software Engineer
SOAPtest Development
Parasoft Corporation
"We Make Software Work"
fx-dev@ws.apache.org wrote:
>The following comment has been added to this issue:
>
> Author: Davanum Srinivas
> Created: Sat, 17 Jul 2004 6:09 PM
> Body:
>Rami,
>
>Am terribly sorry about the delay...can you please re-submit a patch against latest CVS? Am afraid, a few things got changed since you submitted the patch (fixed imports and a patch from sam at least)
>
>thanks,
>dims
>---------------------------------------------------------------------
>View this comment:
> http://issues.apache.org/jira/browse/WSFX-19?page=comments#action_36734
>
>---------------------------------------------------------------------
>View the issue:
> http://issues.apache.org/jira/browse/WSFX-19
>
>Here is an overview of the issue:
>---------------------------------------------------------------------
> Key: WSFX-19
> Summary: WSS4J Interoperability Features
> Type: New Feature
>
> Status: Open
> Priority: Major
>
> Project: WSFX
> Components:
> WSS4J
>
> Assignee: Davanum Srinivas
> Reporter: Rami Jaamour
>
> Created: Tue, 13 Jul 2004 5:20 PM
> Updated: Sat, 17 Jul 2004 6:09 PM
>
>Description:
>Here is the new feature set I promissed! Now WSS4J API can interop successfully with the following:
>
>BEA WebLogic 8.1 SP2: Signature, Signature Verification, Encryption, Decryption and combinations of both
>IBM WebSphere 5.1: Signature and Signature Verification
>MS .NET WSE 1.0 SP1: Signature and Signature Verification
>
>The default settings keep WSS4J in OASIS 1.0 compliance.
>
>The WSS4J API is backward compatible but WSBaseMessage extenders and WSSecureityEngine methods now have additional signatures which take org.apache.ws.security.WSSConfig.
>
>The default WSSConfig whcih you can get using WSSconfig.getDefaultWSConfig() is pre-configuired to OASIS 1.0. You can, however, create a new instance of WSSConfig with settings that correspond to other implementations like .NET and BEA, etc. by WSSConfig.getNewInstance() then using the various methods to set stuff like WSSE URI, WSU URI, etc. You can alternatively set stuff to the global static instance, but I needed multi-instance support for my project, so here you go.
>
>WSS4J header processing should conform to the settings in WSSConfig you give it, and will fail if it gets a header which violates one of these, however, if you do
>wssConfig.setProcessNonCompliantMessages(true)
>then WSS4J will attempt to process all known formats, including all previous namespaces, etc. This is useful on the server side to have your service work with any of the above clients! :-)
>
>This new API is in a BETA stage. Particularly, what is missing is
>1. encryption/decryption interop with .NET WSE 1.0 SP1 and IBM WebSphere 5.1 that use some kind of a KeyIdentifier which I couldn't figure out yet.
>2. I did not create JUnit tests for the new features because I use a proprietary tool for creating tests in a binary format (SOAPtest).
>3. Username Token interop are not tested, I only tested what I have listed above so far.
>4. I did not modify the Axis handlers to support the new API, so they cannot be set by properties in the WSDD... Perhaps somebody who is interested in this can pick this up?
>
>
>---------------------------------------------------------------------
>JIRA INFORMATION:
>This message is automatically generated by JIRA.
>
>If you think it was sent incorrectly contact one of the administrators:
> http://issues.apache.org/jira/secure/Administrators.jspa
>
>If you want more information on JIRA, or have a bug to report see:
> http://www.atlassian.com/software/jira
>
>
>
>
Re: [jira] Commented: (WSFX-19) WSS4J Interoperability Features
Posted by Rami Jaamour <rj...@parasoft.com>.
That's what I did.
I refetched the whole WSS4J tree from scratch and still got the same error.
Rami Jaamour
Software Engineer
SOAPtest Development
Parasoft Corporation
"We Make Software Work"
Davanum Srinivas wrote:
>Please do a "cvs update -P -d" and try "ant clean test"
>
>thanks,
>dims
>
>
>----- Original Message -----
>From: Rami Jaamour <rj...@parasoft.com>
>Date: Mon, 19 Jul 2004 15:44:01 -0700
>Subject: Re: [jira] Commented: (WSFX-19) WSS4J Interoperability Features
>To: fx-dev@ws.apache.org
>
>
>
>
>
>
>
>
>Dims,
>
>
>
>Do the latest sources compile successfully? After doing cvs up and
>merging my changes I get:
>
>
>
>compile.tests:
>
>Trying to override old definition of task axis-wsdl2java
>
>Trying to override old definition of task axis-admin
>
>Trying to override old definition of task axis-java2wsdl
>
>
>
>compile:
>
>[axis-wsdl2java] log4j:WARN No appenders could be found for logger
>(org.apache.axis.i18n.ProjectResourceBundle).
>
>[axis-wsdl2java] log4j:WARN Please initialize the log4j system properly.
>
>[axis-wsdl2java] WSDL2Java
>/home/fox/rjaamour/ws-fx/wss4j/test/secconv/../../test/secconv/ping.wsdl
>
>[axis-wsdl2java] PingBindingImpl.java already exists, WSDL2Java will
>not overwrite it.
>
> [copy] Copying 2 files to
>/home/fox/rjaamour/ws-fx/wss4j/build/work/secconv
>
> [copy] Copying 3 files to
>/home/fox/rjaamour/ws-fx/wss4j/build/work/secconv
>
> [javac] Compiling 8 source files to
>/home/fox/rjaamour/ws-fx/wss4j/build/classes
>
> [javac]
>/home/fox/rjaamour/ws-fx/wss4j/build/work/secconv/WSConvScenario2.java:49:
>cannot resolve symbol
>
> [javac] symbol : method getWSConvScenario2 (java.net.URL)
>
> [javac] location: class
>org.apache.ws.axis.oasis.ping.PingServiceLocator
>
> [javac] PingPort port = (PingPort)
>service.getWSConvScenario2(endpoint);
>
> [javac] ^
>
> [javac] 1 error
>
>
>
>BUILD FAILED
>
>
>
>I don't think that this is related to my changes.
>
>
>
>
>
>
>
>Rami Jaamour
>
>Software Engineer
>
>SOAPtest
>Development
>
>Parasoft Corporation
>
>
>
>"We Make Software Work"
>
>
>
>
>
>
>fx-dev@ws.apache.org wrote:
>
>
> The following comment has been added to this issue:
>
> Author: Davanum Srinivas
> Created: Sat, 17 Jul 2004 6:09 PM
> Body:
>Rami,
>
>Am terribly sorry about the delay...can you please re-submit a patch
>against latest CVS? Am afraid, a few things got changed since you
>submitted the patch (fixed imports and a patch from sam at least)
>
>thanks,
>dims
>---------------------------------------------------------------------
>View this comment:
> http://issues.apache.org/jira/browse/WSFX-19?page=comments#action_36734
>
>---------------------------------------------------------------------
>View the issue:
> http://issues.apache.org/jira/browse/WSFX-19
>
>Here is an overview of the issue:
>---------------------------------------------------------------------
> Key: WSFX-19
> Summary: WSS4J Interoperability Features
> Type: New Feature
>
> Status: Open
> Priority: Major
>
> Project: WSFX
> Components:
> WSS4J
>
> Assignee: Davanum Srinivas
> Reporter: Rami Jaamour
>
> Created: Tue, 13 Jul 2004 5:20 PM
> Updated: Sat, 17 Jul 2004 6:09 PM
>
>Description:
>Here is the new feature set I promissed! Now WSS4J API can interop
>successfully with the following:
>
>BEA WebLogic 8.1 SP2: Signature, Signature Verification, Encryption,
>Decryption and combinations of both
>IBM WebSphere 5.1: Signature and Signature Verification
>MS .NET WSE 1.0 SP1: Signature and Signature Verification
>
>The default settings keep WSS4J in OASIS 1.0 compliance.
>
>The WSS4J API is backward compatible but WSBaseMessage extenders and
>WSSecureityEngine methods now have additional signatures which take
>org.apache.ws.security.WSSConfig.
>
>The default WSSConfig whcih you can get using
>WSSconfig.getDefaultWSConfig() is pre-configuired to OASIS 1.0. You
>can, however, create a new instance of WSSConfig with settings that
>correspond to other implementations like .NET and BEA, etc. by
>WSSConfig.getNewInstance() then using the various methods to set stuff
>like WSSE URI, WSU URI, etc. You can alternatively set stuff to the
>global static instance, but I needed multi-instance support for my
>project, so here you go.
>
>WSS4J header processing should conform to the settings in WSSConfig
>you give it, and will fail if it gets a header which violates one of
>these, however, if you do
>wssConfig.setProcessNonCompliantMessages(true)
>then WSS4J will attempt to process all known formats, including all
>previous namespaces, etc. This is useful on the server side to have
>your service work with any of the above clients! :-)
>
>This new API is in a BETA stage. Particularly, what is missing is
>1. encryption/decryption interop with .NET WSE 1.0 SP1 and IBM
>WebSphere 5.1 that use some kind of a KeyIdentifier which I couldn't
>figure out yet.
>2. I did not create JUnit tests for the new features because I use a
>proprietary tool for creating tests in a binary format (SOAPtest).
>3. Username Token interop are not tested, I only tested what I have
>listed above so far.
>4. I did not modify the Axis handlers to support the new API, so they
>cannot be set by properties in the WSDD... Perhaps somebody who is
>interested in this can pick this up?
>
>
>---------------------------------------------------------------------
>JIRA INFORMATION:
>This message is automatically generated by JIRA.
>
>If you think it was sent incorrectly contact one of the administrators:
> http://issues.apache.org/jira/secure/Administrators.jspa
>
>If you want more information on JIRA, or have a bug to report see:
> http://www.atlassian.com/software/jira
>
>
>
>
>
>
>
>
>
>
>
>
Re: [jira] Commented: (WSFX-19) WSS4J Interoperability Features
Posted by Davanum Srinivas <da...@gmail.com>.
Please do a "cvs update -P -d" and try "ant clean test"
thanks,
dims
----- Original Message -----
From: Rami Jaamour <rj...@parasoft.com>
Date: Mon, 19 Jul 2004 15:44:01 -0700
Subject: Re: [jira] Commented: (WSFX-19) WSS4J Interoperability Features
To: fx-dev@ws.apache.org
Dims,
Do the latest sources compile successfully? After doing cvs up and
merging my changes I get:
compile.tests:
Trying to override old definition of task axis-wsdl2java
Trying to override old definition of task axis-admin
Trying to override old definition of task axis-java2wsdl
compile:
[axis-wsdl2java] log4j:WARN No appenders could be found for logger
(org.apache.axis.i18n.ProjectResourceBundle).
[axis-wsdl2java] log4j:WARN Please initialize the log4j system properly.
[axis-wsdl2java] WSDL2Java
/home/fox/rjaamour/ws-fx/wss4j/test/secconv/../../test/secconv/ping.wsdl
[axis-wsdl2java] PingBindingImpl.java already exists, WSDL2Java will
not overwrite it.
[copy] Copying 2 files to
/home/fox/rjaamour/ws-fx/wss4j/build/work/secconv
[copy] Copying 3 files to
/home/fox/rjaamour/ws-fx/wss4j/build/work/secconv
[javac] Compiling 8 source files to
/home/fox/rjaamour/ws-fx/wss4j/build/classes
[javac]
/home/fox/rjaamour/ws-fx/wss4j/build/work/secconv/WSConvScenario2.java:49:
cannot resolve symbol
[javac] symbol : method getWSConvScenario2 (java.net.URL)
[javac] location: class
org.apache.ws.axis.oasis.ping.PingServiceLocator
[javac] PingPort port = (PingPort)
service.getWSConvScenario2(endpoint);
[javac] ^
[javac] 1 error
BUILD FAILED
I don't think that this is related to my changes.
Rami Jaamour
Software Engineer
SOAPtest
Development
Parasoft Corporation
"We Make Software Work"
fx-dev@ws.apache.org wrote:
The following comment has been added to this issue:
Author: Davanum Srinivas
Created: Sat, 17 Jul 2004 6:09 PM
Body:
Rami,
Am terribly sorry about the delay...can you please re-submit a patch
against latest CVS? Am afraid, a few things got changed since you
submitted the patch (fixed imports and a patch from sam at least)
thanks,
dims
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/WSFX-19?page=comments#action_36734
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/WSFX-19
Here is an overview of the issue:
---------------------------------------------------------------------
Key: WSFX-19
Summary: WSS4J Interoperability Features
Type: New Feature
Status: Open
Priority: Major
Project: WSFX
Components:
WSS4J
Assignee: Davanum Srinivas
Reporter: Rami Jaamour
Created: Tue, 13 Jul 2004 5:20 PM
Updated: Sat, 17 Jul 2004 6:09 PM
Description:
Here is the new feature set I promissed! Now WSS4J API can interop
successfully with the following:
BEA WebLogic 8.1 SP2: Signature, Signature Verification, Encryption,
Decryption and combinations of both
IBM WebSphere 5.1: Signature and Signature Verification
MS .NET WSE 1.0 SP1: Signature and Signature Verification
The default settings keep WSS4J in OASIS 1.0 compliance.
The WSS4J API is backward compatible but WSBaseMessage extenders and
WSSecureityEngine methods now have additional signatures which take
org.apache.ws.security.WSSConfig.
The default WSSConfig whcih you can get using
WSSconfig.getDefaultWSConfig() is pre-configuired to OASIS 1.0. You
can, however, create a new instance of WSSConfig with settings that
correspond to other implementations like .NET and BEA, etc. by
WSSConfig.getNewInstance() then using the various methods to set stuff
like WSSE URI, WSU URI, etc. You can alternatively set stuff to the
global static instance, but I needed multi-instance support for my
project, so here you go.
WSS4J header processing should conform to the settings in WSSConfig
you give it, and will fail if it gets a header which violates one of
these, however, if you do
wssConfig.setProcessNonCompliantMessages(true)
then WSS4J will attempt to process all known formats, including all
previous namespaces, etc. This is useful on the server side to have
your service work with any of the above clients! :-)
This new API is in a BETA stage. Particularly, what is missing is
1. encryption/decryption interop with .NET WSE 1.0 SP1 and IBM
WebSphere 5.1 that use some kind of a KeyIdentifier which I couldn't
figure out yet.
2. I did not create JUnit tests for the new features because I use a
proprietary tool for creating tests in a binary format (SOAPtest).
3. Username Token interop are not tested, I only tested what I have
listed above so far.
4. I did not modify the Axis handlers to support the new API, so they
cannot be set by properties in the WSDD... Perhaps somebody who is
interested in this can pick this up?
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
--
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: [jira] Commented: (WSFX-19) WSS4J Interoperability Features
Posted by Jason Essington <ja...@GreenRiverComputing.com>.
hi Rami
I have had to delete test/secconv/WSConvScenario2.java to get wss4j to
compile since that file was added (approx 4 days ago)
otherwise I get the same error as you are seeing there.
-jason
On Jul 19, 2004, at 4:44 PM, Rami Jaamour wrote:
> Dims,
>
> Do the latest sources compile successfully? After doing cvs up and
> merging my changes I get:
>
> compile.tests:
> Trying to override old definition of task axis-wsdl2java
> Trying to override old definition of task axis-admin
> Trying to override old definition of task axis-java2wsdl
>
> compile:
> [axis-wsdl2java] log4j:WARN No appenders could be found for logger
> (org.apache.axis.i18n.ProjectResourceBundle).
> [axis-wsdl2java] log4j:WARN Please initialize the log4j system
> properly.
> [axis-wsdl2java] WSDL2Java
> /home/fox/rjaamour/ws-fx/wss4j/test/secconv/../../test/secconv/
> ping.wsdl
> [axis-wsdl2java] PingBindingImpl.java already exists, WSDL2Java will
> not overwrite it.
> [copy] Copying 2 files to
> /home/fox/rjaamour/ws-fx/wss4j/build/work/secconv
> [copy] Copying 3 files to
> /home/fox/rjaamour/ws-fx/wss4j/build/work/secconv
> [javac] Compiling 8 source files to
> /home/fox/rjaamour/ws-fx/wss4j/build/classes
> [javac]
> /home/fox/rjaamour/ws-fx/wss4j/build/work/secconv/
> WSConvScenario2.java:49: cannot resolve symbol
> [javac] symbol : method getWSConvScenario2 (java.net.URL)
> [javac] location: class
> org.apache.ws.axis.oasis.ping.PingServiceLocator
> [javac] PingPort port = (PingPort)
> service.getWSConvScenario2(endpoint);
> [javac] ^
> [javac] 1 error
>
> BUILD FAILED
>
> I don't think that this is related to my changes.
>
>
> Rami Jaamour
> Software Engineer
> SOAPtest Development
> Parasoft Corporation
>
> "We Make Software Work"
>
>
>
> fx-dev@ws.apache.org wrote:
> The following comment has been added to this issue:
>
> Author: Davanum Srinivas
> Created: Sat, 17 Jul 2004 6:09 PM
> Body:
> Rami,
>
> Am terribly sorry about the delay...can you please re-submit a patch
> against latest CVS? Am afraid, a few things got changed since you
> submitted the patch (fixed imports and a patch from sam at least)
>
> thanks,
> dims
> ---------------------------------------------------------------------
> View this comment:
>
> http://issues.apache.org/jira/browse/WSFX-19?
> page=comments#action_36734
>
> ---------------------------------------------------------------------
> View the issue:
> http://issues.apache.org/jira/browse/WSFX-19
>
> Here is an overview of the issue:
> ---------------------------------------------------------------------
> Key: WSFX-19
> Summary: WSS4J Interoperability Features
> Type: New Feature
>
> Status: Open
> Priority: Major
>
> Project: WSFX
> Components:
> WSS4J
>
> Assignee: Davanum Srinivas
> Reporter: Rami Jaamour
>
> Created: Tue, 13 Jul 2004 5:20 PM
> Updated: Sat, 17 Jul 2004 6:09 PM
>
> Description:
> Here is the new feature set I promissed! Now WSS4J API can interop
> successfully with the following:
>
> BEA WebLogic 8.1 SP2: Signature, Signature Verification, Encryption,
> Decryption and combinations of both
> IBM WebSphere 5.1: Signature and Signature Verification
> MS .NET WSE 1.0 SP1: Signature and Signature Verification
>
> The default settings keep WSS4J in OASIS 1.0 compliance.
>
> The WSS4J API is backward compatible but WSBaseMessage extenders and
> WSSecureityEngine methods now have additional signatures which take
> org.apache.ws.security.WSSConfig.
>
> The default WSSConfig whcih you can get using
> WSSconfig.getDefaultWSConfig() is pre-configuired to OASIS 1.0. You
> can, however, create a new instance of WSSConfig with settings that
> correspond to other implementations like .NET and BEA, etc. by
> WSSConfig.getNewInstance() then using the various methods to set stuff
> like WSSE URI, WSU URI, etc. You can alternatively set stuff to the
> global static instance, but I needed multi-instance support for my
> project, so here you go.
>
> WSS4J header processing should conform to the settings in WSSConfig
> you give it, and will fail if it gets a header which violates one of
> these, however, if you do
> wssConfig.setProcessNonCompliantMessages(true)
> then WSS4J will attempt to process all known formats, including all
> previous namespaces, etc. This is useful on the server side to have
> your service work with any of the above clients! :-)
>
> This new API is in a BETA stage. Particularly, what is missing is
> 1. encryption/decryption interop with .NET WSE 1.0 SP1 and IBM
> WebSphere 5.1 that use some kind of a KeyIdentifier which I couldn't
> figure out yet.
> 2. I did not create JUnit tests for the new features because I use a
> proprietary tool for creating tests in a binary format (SOAPtest).
> 3. Username Token interop are not tested, I only tested what I have
> listed above so far.
> 4. I did not modify the Axis handlers to support the new API, so they
> cannot be set by properties in the WSDD... Perhaps somebody who is
> interested in this can pick this up?
>
>
> ---------------------------------------------------------------------
> JIRA INFORMATION:
> This message is automatically generated by JIRA.
>
> If you think it was sent incorrectly contact one of the administrators:
> http://issues.apache.org/jira/secure/Administrators.jspa
>
> If you want more information on JIRA, or have a bug to report see:
> http://www.atlassian.com/software/jira
>
>
>