does anyone know anything about the filestructure?
Philipp Perner schrieb:
I think you are right.
The problem is, that my client doesn't uses/find? the rampart module
engaged in axis2.xml.
But the file structure of the client's builds is similar to the
samples of rampart.
Do you know, how the file structure has to be, that the my client's
uses the rampart module and the axis2.xml?
Due to the fact, I am temporarily using the ant file of the rampart
sample my file structure looks like this:
build/temp_client --> path to classes, client.jks and client.properties
build/client_repositories/conf --> path to axis2.xml
build/client_repositories/modules --> path to rampart1.1
my ant task to run the client looks like this:
<java classname="sample.soapwithattachments.SWAClient" fork="true">
<arg value="${test.services.url}/[EMAIL PROTECTED]" />
<arg value="${client.repos.dir}/" />
<classpath>
<fileset dir="${lib.dir}">
<include name="**/*.jar" />
</fileset>
<dirset dir="${temp.client.dir}" />
</classpath>
</java>
Do you know, what's going wrong?
philipp
Mary Thompson schrieb:
I haven't tried encryption, but have signature verification working
with Axis2-1.1.(1) and Rampart 1.1.
Do you have the rampart module findable by your client? ie, engaged
in axis2.xml and available at run time. I copied the following
command line from an example somewhere.
#!/bin/sh
. setclasspath.sh
java -Daxis2.xml=repo/axis2.xml QueryReservationClient repo
https://domain.name/axis2-1.1.1/services/OSCARS
where the repo/modules contains the rampart.mar, and repo contains
the sec.properties and jks files.
Mary Thompson
---------------------------------------------------------------------
Mary R. Thompson <[EMAIL PROTECTED]>
Secure Grid Technologies Group (510) 486-7408
Lawrence Berkeley National Lab http://dsd.lbl.gov/~mrt
---------------------------------------------------------------------
Philipp Perner wrote:
I have a service to transfer files.
I am using SwA with ADB as data binding. But in my opinion, the
client doesn't even take the client's axis2.xml when running, so
outflow configuration from client doesn't even make timestamp,
signature or encryption. It doesn't matter which items i have in the
outflow configuration of the client, the soap message is generated
everytime without these items.
The server does everything correct - Timestamp, Signature,
Encryption...
This doesn't matter as long as I want to encrypt from service to
client, and client's axis2.xml has to be taken to decrypt.
swaramp.client:
[copy] Copying 1 file to
D:\Development\eclipse3.2\WebClient\WEB-INF\build\client_repositories\test01\conf
[copy] Copying 1 file to
D:\Development\eclipse3.2\WebClient\WEB-INF\build\client_repositories\test01\modules
[copy] Copying 1 file to
D:\Development\eclipse3.2\WebClient\WEB-INF\build\temp_client
[java] java.lang.RuntimeException: java.lang.RuntimeException:
Unexpected subelement EncryptionMethod
[java] at
sample.soapwithattachments.SWASampleServiceStub.fromOM(Unknown Source)
[java] at
sample.soapwithattachments.SWASampleServiceStub.uploadFile(Unknown
Source)
[java] at
sample.soapwithattachments.SWAClient.transferFile(Unknown Source)
[java] at sample.soapwithattachments.SWAClient.main(Unknown Source)
[java] Caused by: java.lang.RuntimeException: Unexpected
subelement EncryptionMethod
[java] at
sample.soapwithattachments.service.xsd.UploadFileResponse$Factory.parse(Unknown
Source)
[java] ... 4 more
[java] Exception in thread "main"
[java] Java Result: 1
BUILD SUCCESSFUL
Is there any further configuration I have to do? Or is it just an
incompatibility from axis2 1.1 to rampart1.1 ?
I don't understand why the samples of rampart1.1 are working with
axis2-1.1
I'm using the client and service keys from the rampart tutorials.
Has anyone else encountered this error?
philipp
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
