Mauricio, sorry for the delay. So I think already posted the most important parts. But here is the complete code again:
// create configuration context
ConfigurationContext configurationContext = ConfigurationContextFactory
.createConfigurationContextFromFileSystem(config
.getString(Config.CORE_AXIS_REPOSITORY), null);
// additional configuration of axis2 when required
...
// create the stub
MessagingClientServiceStub stub = new MessagingClientServiceStub(
configurationContext, config
.getString(Config.CORE_SYSTEM_EPR));
// configure the stub/ service client via policies
Options options = stub._getServiceClient().getOptions();
StAXOMBuilder builder = new StAXOMBuilder("policy.xml");
options.setProperty(RampartMessageData.KEY_RAMPART_POLICY,
PolicyEngine.getPolicy(builder.getDocumentElement()) );
// working with the stub
...
I think this is the main part. Just try to configure your Rampart with
policies. The old configuration is deprecated and doesn't work for me.
Good luck...
Regards,
Sebastian
Mauricio Wodarski da Silva schrieb:
> Sebastian,
>
> Could you send your complete client code, please?
> I'm trying to do a client using rampart without axis2.xml
> unsuccessfully here.
>
> Thanks,
> Mauricio
>
> 2007/1/24, Sebastian Roschke <[EMAIL PROTECTED]>:
>> Hi Ruchith,
>>
>> thanks for this important hint. Your proposal works fine. I removed the
>> axis2.xml as configuration. Now I do all the necessary configs by myself
>> in the client code. I changed your proposal a little bit:
>>
>> ConfigurationContext configurationContext =
>> ConfigurationContextFactory
>> .createConfigurationContextFromFileSystem(config
>> .getString(Config.CORE_AXIS_REPOSITORY),
>> null);
>>
>>
>> configurationContext.getAxisConfiguration().getTransportIn(new
>> QName("http"))
>> .getParameter("port").setValue("3003");
>>
>>
>> configurationContext.getAxisConfiguration().engageModule(new
>> QName("addressing"));
>>
>> configurationContext.getAxisConfiguration().engageModule(new
>> QName("rampart"));
>>
>> This works fine for my case. Thanks a lot!!!
>>
>> Regards,
>> Sebastian
>>
>> Ruchith Fernando schrieb:
>> > Hi Sebastian,
>> >
>> > I used the generated stub to successfully create a request[1] and
>> > engage Rampart on the client without any configuration. Note that I
>> > did not use an axis2.xml file[2]. Can you try using this [2] approach.
>> >
>> > Thanks,
>> > Ruchith
>> >
>> > [1] http://rafb.net/p/pw9xDl42.html
>> > [2] http://rafb.net/p/HUA3Rs76.html
>> >
>> > On 1/24/07, Sebastian Roschke <[EMAIL PROTECTED]>
>> > wrote:
>> >> Hi Ruchith,
>> >>
>> >> thanks for the support. Yes, I use the ADB databinding. And here
>> is the
>> >> wsdl:
>> >>
>> >> <wsdl:definitions
>> xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/";
>> >> xmlns:http="http://schemas.xmlsoap.org/wsdl/http/";
>> >> xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/";
>> >> xmlns:xmime="http://www.w3.org/2005/05/xmlmime";
>> >>
>> xmlns:types="http://www.hpi.uni-potsdam.de/dbrep/wsmessaging/types";
>> >> xmlns:lk="http://www.hpi.uni-potsdam.de/dbrep/wsmessaging/";
>> >> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
>> >> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
>> >>
>> targetNamespace="http://www.hpi.uni-potsdam.de/dbrep/wsmessaging/";>
>> >>
>> >> <wsdl:types>
>> >> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema";
>> >> attributeFormDefault="qualified" elementFormDefault="qualified"
>> >>
>> targetNamespace="http://www.hpi.uni-potsdam.de/dbrep/wsmessaging/types";>
>> >> <xs:import namespace="http://www.w3.org/2005/05/xmlmime";
>> >> schemaLocation="xmime.xsd" />
>> >> <xs:element name="addClient">
>> >> <xs:complexType>
>> >> <xs:sequence>
>> >> <xs:element name="agentName" nillable="true"
>> >> type="xs:string" />
>> >> <xs:element name="className" nillable="true"
>> >> type="xs:string" />
>> >> <xs:element name="configPath" nillable="true"
>> >> type="xs:string" />
>> >> </xs:sequence>
>> >> </xs:complexType>
>> >> </xs:element>
>> >> <xs:element name="queue">
>> >> <xs:complexType name="message">
>> >> <xs:sequence>
>> >> <xs:element name="to" nillable="true"
>> >> type="xs:string" />
>> >> <xs:element name="from" nillable="true"
>> >> type="xs:string" />
>> >> <xs:element name="content" nillable="true"
>> >> type="xmime:base64Binary"/>
>> >> </xs:sequence>
>> >> </xs:complexType>
>> >> </xs:element>
>> >> <xs:element name="queueError">
>> >> <xs:complexType name="errorMessage">
>> >> <xs:sequence>
>> >> <xs:element name="to" nillable="true"
>> >> type="xs:string" />
>> >> <xs:element name="from" nillable="true"
>> >> type="xs:string" />
>> >> <xs:element name="errorType" nillable="true">
>> >> <xs:simpleType name="errorTypeEnum">
>> >> <xs:restriction base="xs:string">
>> >> <xs:enumeration
>> >> value="RecipientNotFound"/>
>> >> <xs:enumeration value="Custom"/>
>> >> </xs:restriction>
>> >> </xs:simpleType>
>> >> </xs:element>
>> >> <xs:element name="errorDescription"
>> >> nillable="true" type="xs:string" />
>> >> </xs:sequence>
>> >> </xs:complexType>
>> >> </xs:element>
>> >> </xs:schema>
>> >> </wsdl:types>
>> >>
>> >> <wsdl:message name="addClientMessage">
>> >> <wsdl:part name="part1" element="types:addClient" />
>> >> </wsdl:message>
>> >>
>> >> <wsdl:message name="queueMessage">
>> >> <wsdl:part name="part1" element="types:queue" />
>> >> </wsdl:message>
>> >>
>> >> <wsdl:message name="queueErrorMessage">
>> >> <wsdl:part name="part1" element="types:queueError" />
>> >> </wsdl:message>
>> >>
>> >> <wsdl:portType name="MessagingClientServicePortType">
>> >> <wsdl:operation name="addClient">
>> >> <wsdl:input message="lk:addClientMessage" />
>> >> </wsdl:operation>
>> >> <wsdl:operation name="queue">
>> >> <wsdl:input message="lk:queueMessage" />
>> >> </wsdl:operation>
>> >> <wsdl:operation name="queueError">
>> >> <wsdl:input message="lk:queueErrorMessage" />
>> >> </wsdl:operation>
>> >> </wsdl:portType>
>> >>
>> >> <wsdl:binding name="MessagingClientServiceSOAP11Binding"
>> >> type="lk:MessagingClientServicePortType">
>> >> <soap:binding
>> transport="http://schemas.xmlsoap.org/soap/http";
>> >> style="document" />
>> >> <wsdl:operation name="addClient">
>> >> <soap:operation soapAction="urn:addClient"
>> >> style="document" />
>> >> <wsdl:input>
>> >> <soap:body use="literal"
>> >> namespace="http://www.hpi.uni-potsdam.de/dbrep/wsmessaging/"; />
>> >> </wsdl:input>
>> >> </wsdl:operation>
>> >> <wsdl:operation name="queue">
>> >> <soap:operation soapAction="urn:queue"
>> style="document" />
>> >> <wsdl:input>
>> >> <soap:body use="literal"
>> >> namespace="http://www.hpi.uni-potsdam.de/dbrep/wsmessaging/"; />
>> >> </wsdl:input>
>> >> </wsdl:operation>
>> >> <wsdl:operation name="queueError">
>> >> <soap:operation soapAction="urn:queueError"
>> >> style="document" />
>> >> <wsdl:input>
>> >> <soap:body use="literal"
>> >> namespace="http://www.hpi.uni-potsdam.de/dbrep/wsmessaging/"; />
>> >> </wsdl:input>
>> >> </wsdl:operation>
>> >> </wsdl:binding>
>> >>
>> >> <wsdl:binding name="MessagingClientServiceSOAP12Binding"
>> >> type="lk:MessagingClientServicePortType">
>> >> <soap12:binding
>> transport="http://schemas.xmlsoap.org/soap/http";
>> >> style="document" />
>> >> <wsdl:operation name="addClient">
>> >> <soap12:operation soapAction="urn:addClient"
>> >> style="document" />
>> >> <wsdl:input>
>> >> <soap12:body use="literal"
>> >> namespace="http://www.hpi.uni-potsdam.de/dbrep/wsmessaging/"; />
>> >> </wsdl:input>
>> >> </wsdl:operation>
>> >> <wsdl:operation name="queue">
>> >> <soap12:operation soapAction="urn:queue"
>> style="document" />
>> >> <wsdl:input>
>> >> <soap12:body use="literal"
>> >> namespace="http://www.hpi.uni-potsdam.de/dbrep/wsmessaging/"; />
>> >> </wsdl:input>
>> >> </wsdl:operation>
>> >> <wsdl:operation name="queueError">
>> >> <soap12:operation soapAction="urn:queueError"
>> >> style="document" />
>> >> <wsdl:input>
>> >> <soap12:body use="literal"
>> >> namespace="http://www.hpi.uni-potsdam.de/dbrep/wsmessaging/"; />
>> >> </wsdl:input>
>> >> </wsdl:operation>
>> >> </wsdl:binding>
>> >>
>> >> <wsdl:service name="MessagingClientService">
>> >> <wsdl:port name="MessagingClientServiceSOAP11port"
>> >> binding="lk:MessagingClientServiceSOAP11Binding">
>> >> <soap:address
>> >>
>> location="http://localhost:8080/axis2/services/MessagingClientService";
>> >> />
>> >> </wsdl:port>
>> >> <wsdl:port name="MessagingClientServiceSOAP12port"
>> >> binding="lk:MessagingClientServiceSOAP12Binding">
>> >> <soap12:address
>> >>
>> location="http://localhost:8080/axis2/services/MessagingClientService";
>> >> />
>> >> </wsdl:port>
>> >> </wsdl:service>
>> >> </wsdl:definitions>
>> >>
>> >> Do you think that this problem occurs due to this databinding? The
>> >> client throws the exception during the first addClient(...) call.
>> MTOM
>> >> is disabled at the moment.
>> >>
>> >> Do you have any questions?
>> >>
>> >> Regards,
>> >> Sebastian
>> >>
>> >>
>> >> Ruchith Fernando schrieb:
>> >> > Hi Sebastian,
>> >> >
>> >> > Are you using ADB databinding? Can you please post the WSDL?
>> >> >
>> >> > Thanks,
>> >> > Ruchith
>> >> >
>> >> > On 1/20/07, Sebastian Roschke
>> <[EMAIL PROTECTED]>
>> >> > wrote:
>> >> >> Hi Hailong,
>> >> >>
>> >> >> as far as I know the axis stack is used for the client api as
>> >> well. When
>> >> >> not configured axis uses a default configuration (Please correct
>> >> me if I
>> >> >> am wrong). So when you want to configure the axis2 client to
>> use for
>> >> >> example the rampart module for outgoing messages, you have to ask
>> >> your
>> >> >> axis2 to do so.
>> >> >>
>> >> >> One way to do this is via axis2.xml, where you can configure your
>> >> axis2
>> >> >> to use this module. You can specify your config file in the
>> >> constructor
>> >> >> of your stub.
>> >> >>
>> >> >> ConfigurationContext configurationContext =
>> >> ConfigurationContextFactory
>> >> >>
>> >> >> .createConfigurationContextFromFileSystem(axisRepositoryPath,
>> >> >> axisConfigPath);
>> >> >>
>> >> >> MessagingClientServiceStub stub = new MessagingClientServiceStub(
>> >> >> configurationContext, serviceUrl);
>> >> >>
>> >> >> Regards,
>> >> >> Sebastian
>> >> >>
>> >> >>
>> >> >> Wang, Hailong (NIH/CIT) [C] schrieb:
>> >> >> > I understand that the server needs the axis2.xml, why the client
>> >> also
>> >> >> > need axis2.xml?
>> >> >> >
>> >> >> >
>> >> >> > Hailong
>> >> >> >
>> >> >> > -----Original Message-----
>> >> >> > From: Sebastian Roschke
>> >> [mailto:[EMAIL PROTECTED]
>> >> >> > Sent: Friday, January 19, 2007 4:10 AM
>> >> >> > To: [email protected]
>> >> >> > Subject: Re: [Axis2] [rampart] Problems using rampart
>> >> >> >
>> >> >> > Hi Dimuthu,
>> >> >> >
>> >> >> > thanks for your support solving this problem. I'm currently
>> using
>> >> >> > rampart-1.1 and axis2-1.1.1. I have no policy configured at
>> all. I
>> >> >> > removed all configurations but the failure remains. The only
>> thing
>> >> >> that
>> >> >> > is configured is that the client should use the rampart
>> module. I
>> >> >> have a
>> >> >> >
>> >> >> > <module ref="rampart"/>
>> >> >> >
>> >> >> > in the axis2 related config file. The exception is thrown on
>> client
>> >> >> side
>> >> >> > while the rampart module is invoked on the axis2 stack. Do
>> you need
>> >> >> any
>> >> >> > additional information?
>> >> >> >
>> >> >> > Regards,
>> >> >> > Sebastian
>> >> >> >
>> >> >> >
>> >> >> > Dimuthu Leelaratne schrieb:
>> >> >> >
>> >> >> >> Hi Sebastian,
>> >> >> >>
>> >> >> >> Looks like I was wrong in the previos mail. Can you pls tell me
>> >> the
>> >> >> >> rampart version that you are using, so that I can look into
>> it the
>> >> >> >> matter? One more question, do you load Policy at the client
>> side?
>> >> >> >>
>> >> >> >> Thank you,
>> >> >> >> Dimuthu.
>> >> >> >>
>> >> >> >>
>> >> >> >> On 1/18/07, Sebastian Roschke
>> >> <[EMAIL PROTECTED]>
>> >> >> >> wrote:
>> >> >> >>
>> >> >> >>> Hi Dimuthu,
>> >> >> >>>
>> >> >> >>> Thanks for the hint... The SOAP messages I use are really
>> simple.
>> >> >> >>>
>> >> >> > There
>> >> >> >
>> >> >> >>> is nothing special I think. It is something like that:
>> >> >> >>>
>> >> >> >>> <?xml version='1.0' encoding='utf-8'?>
>> >> >> >>> <soapenv:Envelope
>> >> >> xmlns:wsa="http://www.w3.org/2005/08/addressing";
>> >> >> >>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
>> >> >> >>> <soapenv:Header>
>> >> >> >>>
>> >> >> >>>
>> >> >> >>>
>> >> >> >
>> >> >>
>> >>
>> <wsa:To>http://localhost:3003/axis2/services/MessagingClientService</wsa
>> >> >> > :To>
>> >> >> >
>> >> >> >>> <wsa:ReplyTo>
>> >> >> >>>
>> >> >> >>>
>> >> >> >>>
>> >> >> >
>> >> >>
>> >>
>> <wsa:Address>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address
>> >> >> >
>> >> >> >>> </wsa:ReplyTo>
>> >> >> >>>
>> >> >> >>>
>> >> >> >>>
>> >> >> >
>> >> >>
>> >>
>> <wsa:MessageID>urn:uuid:8655FCF2CBB79A97C711691163447531</wsa:MessageID>
>> >> >> >
>> >> >> >>> <wsa:Action>urn:addClient</wsa:Action>
>> >> >> >>> </soapenv:Header>
>> >> >> >>> <soapenv:Body>
>> >> >> >>> <ns2:addClient
>> >> >> >>>
>> >> >> >>>
>> >> >> >
>> >> >>
>> >>
>> xmlns:ns2="http://www.hpi.uni-potsdam.de/skid.common/wsmessaging/types";>
>> >> >> >
>> >> >> >>> <ns2:agentName>test</ns2:agentName>
>> >> >> >>>
>> >> <ns2:className>skid.agent.test.TestAgent</ns2:className>
>> >> >> >>>
>> <ns2:configPath>messaging_test.config</ns2:configPath>
>> >> >> >>> <ns2:messageFactoryClassName />
>> >> >> >>> </ns2:addClient>
>> >> >> >>> </soapenv:Body>
>> >> >> >>> </soapenv:Envelope>
>> >> >> >>>
>> >> >> >>> Maybe you have any ideas. Please write when you have
>> >> suggestions...
>> >> >> >>>
>> >> >> >>> Regards,
>> >> >> >>> Sebastian
>> >> >> >>>
>> >> >> >>>
>> >> >> >>> Dimuthu Leelaratne schrieb:
>> >> >> >>>
>> >> >> >>>> Hi Sebastian,
>> >> >> >>>>
>> >> >> >>>> This is not a rampart problem. The pointed out JIRA shows the
>> >> bug.
>> >> >> >>>>
>> >> >> > I
>> >> >> >
>> >> >> >>>> walked through the stack trace. This happens for specific
>> SOAP
>> >> >> >>>> messages, when they are converted to DOOM as mentioned. I
>> have
>> >> >> >>>>
>> >> >> > never
>> >> >> >
>> >> >> >>>> experienced the problem. Maybe because the SOAP messages that
>> >> I use
>> >> >> >>>> wouldn't re-create the problem.
>> >> >> >>>>
>> >> >> >>>> Regards,
>> >> >> >>>> Dimuthu
>> >> >> >>>>
>> >> >> >>>>
>> >> >> >>>> On 1/17/07, Sebastian Roschke
>> >> >> >>>>
>> >> >> > <[EMAIL PROTECTED]>
>> >> >> >
>> >> >> >>>> wrote:
>> >> >> >>>>
>> >> >> >>>>> Hi everybody,
>> >> >> >>>>>
>> >> >> >>>>> I have a problem using rampart in axis2. I just have
>> configured
>> >> >> >>>>>
>> >> >> > the
>> >> >> >
>> >> >> >>>>> axis2-client.xml this way, that it should use rampart. At
>> the
>> >> >> >>>>>
>> >> >> >>> moment I
>> >> >> >>>
>> >> >> >>>>> have no configuration for the rampart module at all. While
>> >> using
>> >> >> >>>>>
>> >> >> > the
>> >> >> >
>> >> >> >>>>> client api to invoke a soap request, I get the following
>> >> >> >>>>>
>> >> >> > exceptions:
>> >> >> >
>> >> >> >>>>> org.apache.axis2.AxisFault: Error in extracting message
>> >> >> >>>>>
>> >> >> > properties;
>> >> >> >
>> >> >> >>>>> nested exception is:
>> >> >> >>>>> org.apache.rampart.RampartException: Error in extracting
>> >> >> >>>>>
>> >> >> > message
>> >> >> >
>> >> >> >>>>> properties
>> >> >> >>>>> at
>> >> >> >>>>>
>> >> >> >>>>>
>> >> >> >
>> >>
>> org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65)
>> >> >> >
>> >> >> >>>>> at org.apache.axis2.engine.Phase.invoke(Phase.java:381)
>> >> >> >>>>> at
>> >> >> >>>>>
>> >> >> > org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:518)
>> >> >> >
>> >> >> >>>>> at
>> >> >> >>>>>
>> >> >> > org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:651)
>> >> >> >
>> >> >> >>>>> at
>> >> >> >>>>>
>> >> >> >>>>>
>> >> >> >
>> >> >>
>> >>
>> org.apache.axis2.description.OutOnlyAxisOperationClient.execute(OutOnlyA
>> >> >> > xisOperation.java:353)
>> >> >> >
>> >> >> >>>>> at
>> >> >> >>>>>
>> >> >> >>>>>
>> >> >> >
>> >> >>
>> >>
>> skid.messaging.ws.client.client.MessagingClientServiceStub.addClient(Mes
>> >> >> > sagingClientServiceStub.java:126)
>> >> >> >
>> >> >> >>>>> at
>> >> >> >>>>>
>> >> >> >>>
>> skid.messaging.client.ClientControl.main(ClientControl.java:55)
>> >> >> >>>
>> >> >> >>>>> Caused by: org.apache.rampart.RampartException: Error in
>> >> >> >>>>>
>> >> >> > extracting
>> >> >> >
>> >> >> >>>>> message properties
>> >> >> >>>>> at
>> >> >> >>>>>
>> >> >> >>>>>
>> >> >> >
>> >> >>
>> >>
>> org.apache.rampart.RampartMessageData.<init>(RampartMessageData.java:294
>> >> >> > )
>> >> >> >
>> >> >> >>>>> at
>> >> >> >>>>>
>> >> >> >>>
>> org.apache.rampart.MessageBuilder.build(MessageBuilder.java:56)
>> >> >> >>>
>> >> >> >>>>> at
>> >> >> >>>>>
>> >> >> >>>>>
>> >> >> >
>> >>
>> org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:59)
>> >> >> >
>> >> >> >>>>> ... 6 more
>> >> >> >>>>> Caused by: org.apache.ws.security.WSSecurityException:
>> Error in
>> >> >> >>>>> converting SOAP Envelope to Document; nested exception is:
>> >> >> >>>>> org.apache.axiom.om.OMException:
>> >> >> >>>>>
>> >> >> >>> javax.xml.stream.XMLStreamException
>> >> >> >>>
>> >> >> >>>>> at
>> >> >> >>>>>
>> >> >> >>>>>
>> >> >> >
>> >> >>
>> >>
>> org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.
>> >> >> > java:121)
>> >> >> >
>> >> >> >>>>> at
>> >> >> >>>>>
>> >> >> >>>>>
>> >> >> >
>> >> >>
>> >>
>> org.apache.rampart.RampartMessageData.<init>(RampartMessageData.java:146
>> >> >> > )
>> >> >> >
>> >> >> >>>>> ... 8 more
>> >> >> >>>>> Caused by: org.apache.axiom.om.OMException:
>> >> >> >>>>> javax.xml.stream.XMLStreamException
>> >> >> >>>>> at
>> >> >> >>>>>
>> >> >> >>>>>
>> >> >> >
>> >> >>
>> >>
>> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:1
>> >> >> > 99)
>> >> >> >
>> >> >> >>>>> at
>> >> >> >>>>>
>> >> >> > org.apache.axiom.om.impl.dom.NodeImpl.build(NodeImpl.java:469)
>> >> >> >
>> >> >> >>>>> at
>> >> >> >>>>>
>> >> >> >>>>>
>> >> >> >
>> >>
>> org.apache.axiom.om.impl.dom.DocumentImpl.build(DocumentImpl.java:476)
>> >> >> >
>> >> >> >>>>> at
>> >> >> >>>>>
>> >> >> >>>>>
>> >> >> >
>> >> >>
>> >>
>> org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.
>> >> >> > java:107)
>> >> >> >
>> >> >> >>>>> ... 9 more
>> >> >> >>>>> Caused by: javax.xml.stream.XMLStreamException
>> >> >> >>>>> at
>> >> >> >>>>>
>> >> >> >>>>>
>> >> >> >
>> >> >>
>> >>
>> org.apache.axiom.om.impl.llom.OMStAXWrapper.updateLastNode(OMStAXWrapper
>> >> >> > .java:952)
>> >> >> >
>> >> >> >>>>> at
>> >> >> >>>>>
>> >> >> >>>>>
>> >> >> >
>> >> >>
>> >>
>> org.apache.axiom.om.impl.llom.OMStAXWrapper.next(OMStAXWrapper.java:913)
>> >> >> >
>> >> >> >>>>> at
>> >> >> >>>>>
>> >> >> >>>>>
>> >> >> >
>> >> >>
>> >>
>> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:1
>> >> >> > 16)
>> >> >> >
>> >> >> >>>>> ... 12 more
>> >> >> >>>>>
>> >> >> >>>>> This exception is thrown when invoking the first request
>> on the
>> >> >> >>>>>
>> >> >> >>> stub. I
>> >> >> >>>
>> >> >> >>>>> can find the following link concerning that problem:
>> >> >> >>>>>
>> >> http://www.mail-archive.com/[email protected]/msg25582.html
>> >> >> >>>>>
>> >> >> >>>>>
>> >> >> >>>>> As proposed in this post I should check wether the soap
>> message
>> >> >> >>>>>
>> >> >> >>> includes
>> >> >> >>>
>> >> >> >>>>> MIME parts. I used MIME parts in former times, but at the
>> >> moment I
>> >> >> >>>>> disabled all MTOM related things.
>> >> >> >>>>>
>> >> >> >>>>> Do you have any suggestions concernings this problem? Is
>> it a
>> >> >> >>>>>
>> >> >> > known
>> >> >> >
>> >> >> >>>>> problem or a bug?
>> >> >> >>>>>
>> >> >> >>>>>
>> >> >> >>>>>
>> >> >> >>>>>
>> >> >> >>>>>
>> >> >> >>>>>
>> >> >> >>>>
>> >> >> >
>> >> ---------------------------------------------------------------------
>> >> >> >
>> >> >> >>>> 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]
>
signature.asc
Description: OpenPGP digital signature
