Title: Message
Christian,
the soapAction attribute is only valid for the binding
element, not the portType element
replace
operation
name="Execute" soapAction="http://localhost:8090/action/HelloWorld.Execute"
parameterOrder="nameParam"with
operation
Jason,
You should find the javax.wsdl package inside wsdl4j.jar
Check for the line starting with 'Found IBM's WSDL4Java ...' under
axis/happyaxis.jsp
Hth,
eric
-Original Message-
From: Jason Bodnar [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 14, 2004 2:30 PM
To: [EMAIL
Fabio,
The 39b-0 and 4ac-0 are the chunking size, related to chunked transfer.
They are the chunk-size - last-chunk, as defined in the Hypertext Transfer Protocol --
HTTP/1.1
specification.
see http://www.faqs.org/rfcs/rfc2616.html, section 3.6.1 Chunked Transfer Coding
From the parser error on
Cory,
With .Net, there are two flavors of document/literal requests you can generate. Once
you
have genereted the web reference, you can look at the generated code
(Web Reference\com.travelnow.test\Reference.cs) to figure out which style is in use.
Look at the value for the ParameterStyle
to
dispatch messages. 'SOAPAction is purely a hint to processors' (see
http://www.ws-i.org/Profiles/Basic/2003-06/BasicProfile-1.0-BdAD.html#refinement34343864).
*/Eric Rajkovic [EMAIL PROTECTED]/* wrote:
Cory,
With .Net, there are two flavors of document/literal requests you
can generate
Davin,
This is the size of the chunks (HTTP 1.1). You can look at [1] for some
example
hope this help,
eric
[1] http://apache-server.com/Podium/show.php?p=HTTPslide=8
Davinder Singh wrote:
Hi,
I have developed a document/literal webservice which generates the
following response when called
Nicola,
the SOAPAction has to be set in the HTTP header, not the SOAP header.
from Amazon's WSDL:
soap:operation soapAction=urn:PI/DevCentral/SoapService /
It's the same value for all operation, but it need to be there on the wire.
eric
Nicola Muratori wrote:
hi
i'm trying the amazon web
If you want to run asynch on the server, you have to create a separate
thread or push the data from the request into some queueing mechanism.
The current implementation is still sending an empty SOAP body back to
the caller and block until wait10sec returns.
in your stateless service class
Anne,
Just a little addition to your comment on WS-I BP:
WS-I has just published its Basic Profile
draft, which only supports document-style
In the current published revision, the profile support both rpc
and document styles. It only restrict the use to literal.
eric
because CEST is UTC +2, those two dates are equivalent.
2002-06-11T22:00:00.000Z = 2002-06-12T00:00:00.000+2:00
on the wire, axis always use Zulu (UTC, GMT) to transmit date.
If you want to send the day date, you should use a string as you will
get different result from different platforms.
Chris,
You may want to try to return a complex type from ValidateTailorDetails.
Java does not support in/out or out parameters.
public TailorDetail ValidateTailorDetails(String esid, String ScreenID, StringxmlESDO, int index){xmlESDO = "blah";return new TailorDetail( 0, xmlESDO);}Eric.
Hi, I
11 matches
Mail list logo
