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 Manuel Jung <Ma...@concrete-logic.de> on 2005/12/23 12:17:07 UTC
wss4j with SUNAPP 8.1 on a SunWorkstation
Hello all,
i programmed a SOAP application using WSS4J for signatures.
All works fine, if I using TOMCAT 5.0 (or lower)
Deploying my Application on a Sun Application Server 8.1, I get a
error. The Remote side informed me, that there is no certificate in the
request.
Monitoring the outgoing Traffic with the AXIS TCP-Monitor confirmed my
suggestion. The XML is not signed my WSS4J. Here the output with the
TCP-Monitor
on a Sun App Server:
POST /incoming/BLS_Stoerungsmeldung HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.2
Host: 192.168.1.220:9999
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: ""
Content-Length: 2959
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:exe
cute soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1="http://www.telekom.de/t-com/resaleDSL/webservices"><xmldata
xsi:type="xsd:string"><?xml version="1.0"
encoding="UTF-8" standalone="yes"?>
<StoerungResaleDSL
xmlns="http://www.telekom.de/t-com/resaleDSL/webservices/Daten">
;
<Stoerungsmeldung>
<Version>001.000</Version>
<AuftragStoerungsmeldung>
<ResellerStoerungsID>0000000364</ResellerStoerungsID>
<Anschluss>
<ONKZ>343</ONKZ>
<Rufnummer>343</Rufnummer>
<AnschlussStandort>
<Ort>sdf</Ort>
<PLZ>33333</PLZ>
<Strasse>sdf</Strasse>
<Hausnummer>1q</Hausnummer>
</AnschlussStandort>
<AnschlussDaten>
<Produkt>Resale DSL 1000</Produkt>
<Zusatzleistungen>
<ErhoehterUpstream>ja</ErhoehterUpstream>
<Fastpath>ja</Fastpath>
</Zusatzleistungen>
</AnschlussDaten>
</Anschluss>
<Kontakt>
<KontaktpersonVorname>asd</KontaktpersonVorname>
<KontaktpersonNachname>sadf</KontaktpersonNachname>
<ONKZ>343</ONKZ>
<Rufnummer>343</Rufnummer>
</Kontakt>
<Stoerungsdaten>
<FunktionierteResaleDSLBisher>ja</FunktionierteResaleDSLBisher>
<BauartModem>intern</BauartModem>
<RouterAngeschlossen>ja</RouterAngeschlossen>
<DSLModemLEDSynchronGruen>ja</DSLModemLEDSynchronGruen>
<ModemUR2Faehig>ja</ModemUR2Faehig>
<AlleGeraeteverbindungenGesteckt>ja</AlleGeraeteverbindungenGesteck
t>
<InternetVerbindung>ja</InternetVerbindung>
<AbbruchInternetVerbindungen>ja</AbbruchInternetVerbindungen>
<ModemAktivFuerPruefzwecke>ja</ModemAktivFuerPruefzwecke>
<Stoerungsbeschreibung>as</Stoerungsbeschreibung>
</Stoerungsdaten>
</AuftragStoerungsmeldung>
</Stoerungsmeldung>
</StoerungResaleDSL>
Trying the same thing with a TOMCAT it work correctly.
I experiment a little bit with the JAR on my SUNApp 8.1 (witch runs in
MS-Windows) with
the following libs: saaj.jar axis-saaj.jar. Now it seems to work with
MS-Windows.
Trying the same steps on SUN-Workstation with the SunApp 8.1 it does not
work.
The request is not signed.
So, I think my application is programmed correcty, but it seems to be a
configurationproblem
on my SUN-Workstation.
Have anybody out there any tips, what i could try at next?
Thanks to all and merry X-MAS!
Best regards
Manuel Jung
--
Manuel Jung Dipl.-Inform. (FH) Email:
<ma...@concrete-logic.de> Manuel.Jung@concrete-logic.de
Concrete Logic GmbH http://www.concrete-logic.de
In den Dauen 6 Telefon: +49-228-62077214
53117 Bonn Telefax: +49-228-62077222