Re: Axis2 question
Hi Yve, can you exactly explain please what you want to do? I can not even understand the question... I think you won't get an answer without further explanation. Regards, Sebastian Rouleau, Yve wrote: > HI! > > It is possible to use Axis without Internet with the XML encoding method file > on the local machine ? > > Thanks > > > >> <º> >> > Yve Rouleau > Programmeur-analyste en géomatique marine > Service hydrographique du Canada > Institut Maurice-Lamontagne > Téléphone (418) 775-0827 > Télécopieur: (418) 775-0654 > > > -- -- B.Sc. Sebastian Roschke Lock-Keeper – Research Group Tel: +49-(0)331-5509-521, Office: B.1.12 Chair of Internet Technologies and Systems Hasso-Plattner-Institute at University of Potsdam Postfach 900460, D-14440, Potsdam, Germany http://www.hpi.uni-potsdam.de/ --- signature.asc Description: OpenPGP digital signature
Re: Change MessageContext AND envelope in Handler
Hi Deepal,
thanks for the answer. I know that there is no change in the envelope.
But is there any possibility to change the envelope? Would it be
possible to work directly within the envelope? When I get the envelope
object, and maybe a specific part of the header as OMElement, would I be
able to change the envelope in that way. For example:
OMElement element = msgContext.getEnvelope().getHeader().getFirstChild();
element.setText("hallo");
Would this affect the envelope itself?
Thanks for the help.
Regards,
Sebastian
Deepal Jayasinghe wrote:
> hi Sebastian ,
>
>> Hi,
>>
>> I've got a problem concerning the MessageContext used in Axis2
>> MessageReceivers and Handlers. Is it possible to change members of the
>> message context; e.g. WSAAction? How this changes can be applied to
>> envelope within this message context? I tried
>> msgContext.getEnvelope().buildWithAttachements() but it ignores the
>> changes of the WSAAction member completely.
>>
>>
> Envelope is built using input stream , so if you change the wsa action
> there will wont be any change in the envelope.
>
> Thanks
> Deepal
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
signature.asc
Description: OpenPGP digital signature
Change MessageContext AND envelope in Handler
Hi, I've got a problem concerning the MessageContext used in Axis2 MessageReceivers and Handlers. Is it possible to change members of the message context; e.g. WSAAction? How this changes can be applied to envelope within this message context? I tried msgContext.getEnvelope().buildWithAttachements() but it ignores the changes of the WSAAction member completely. Any suggestions? Thanks a lot for help. Regards, Sebastian signature.asc Description: OpenPGP digital signature
Re: [Axis2][Rampart] Rampart and SwA
Hi Thilina, thanks for the answer. I know that Rampart is able to secure MTOM messages. But utilizing MTOM is not usable for large messages. The amount of required memory is that high it is not usable for our project... I don't know the excact reasons for that, but in our performance tests the MTOM approach requires a lot of additional memory. The MTOM approach with file caching needs additional excecution time. Therefore we try to implement processing of large messages(more than 100MB) with SwA and java streams. Do you know where I can ask questions concerning the roadmap of specific components of Axis2? Maybe this is the wrong mailing list for such kind of question. But anyway, thanks for your answer... Regards, Sebastian Thilina Gunarathne schrieb: > Rampart has the capability to secure attachments send using MTOM.. > > I'm not sure whether is there or planned support for SwA.. > > Thanks, > Thilina > > On 3/1/07, Sebastian Roschke <[EMAIL PROTECTED]> > wrote: >> Hello, >> >> due to memory efficiency I work with SwA to send messages based on java >> streams. Is there a possibility to secure such messages with Rampart? Is >> there any support for SwA in Rampart planned for future releases? >> >> Regards, >> Sebastian >> >> >> > > signature.asc Description: OpenPGP digital signature
[Axis2][Rampart] Rampart and SwA
Hello, due to memory efficiency I work with SwA to send messages based on java streams. Is there a possibility to secure such messages with Rampart? Is there any support for SwA in Rampart planned for future releases? Regards, Sebastian signature.asc Description: OpenPGP digital signature
[Axis2][rampart] How to enable MTOM in rampart
Hi all, I try to send the encrypted parts optimized Mime parts. In Rampart 1.0 there was an option that helps to configure MTOM in SOAP messages. Is there an equivalent feature in Rampart 1.1? I tried something like ... but it doesn't work for me. How to configure Rampart 1.1 with policies to send MTOM messages? Thanks for the help, Regards, Sebastian signature.asc Description: OpenPGP digital signature
Re: [Axis2] [rampart] Problems using rampart
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:
>> >>
>> >> > 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/";>
>> >>
>> >>
>> >> http://www.w3.org/2001/XMLSchema";
>> >> attributeFormDefault="qualified" elementFormDefault="qualified"
>> >>
>> targetNamespace="http://www.hpi.uni-potsdam.de/dbrep/wsmessaging/types";>
>> >> http://www.w3.org/2005/05/xmlmime";
>> >> schemaLocation="xmime.xsd" />
>> >>
>> >>
>> >>
>> >> > >> type="xs:string" />
>> >> > >> type="xs:string" />
>> >> > >> type=&
Re: [Axis2] [rampart] Problems using rampart
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:
>>
>> 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/";>
>>
>>
>> http://www.w3.org/2001/XMLSchema";
>> attributeFormDefault="qualified" elementFormDefault="qualified"
>> targetNamespace="http://www.hpi.uni-potsdam.de/dbrep/wsmessaging/types";>
>> http://www.w3.org/2005/05/xmlmime";
>> schemaLocation="xmime.xsd" />
>>
>>
>>
>> > type="xs:string" />
>> > type="xs:string" />
>> > type="xs:string" />
>>
>>
>>
>>
>>
>>
>> > type="xs:string" />
>> > type="xs:string" />
>> > type="xmime:base64Binary"/>
>>
>>
>>
>>
>>
>>
>> > type="xs:string" />
>> > type="xs:string" />
>>
>>
>>
>> > value="RecipientNotFound"/>
>>
>>
>>
>>
>> > nillable="true" type="xs:string" />
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> > type="lk:MessagingClientServicePortType">
>> http://schemas.xmlsoap.org/soap/http";
>> style="document" />
>>
>> > style="document" />
>>
>> > namespace="http://www.hpi.uni-potsdam.de/dbrep/wsmessaging/"; />
>>
>>
Re: [Axis2] [rampart] Problems using rampart
Hi Ruchith, thanks for the support. Yes, I use the ADB databinding. And here is the wsdl: 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/";> http://www.w3.org/2001/XMLSchema"; attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://www.hpi.uni-potsdam.de/dbrep/wsmessaging/types";> http://www.w3.org/2005/05/xmlmime"; schemaLocation="xmime.xsd" /> http://schemas.xmlsoap.org/soap/http"; style="document" /> http://www.hpi.uni-potsdam.de/dbrep/wsmessaging/"; /> http://www.hpi.uni-potsdam.de/dbrep/wsmessaging/"; /> http://www.hpi.uni-potsdam.de/dbrep/wsmessaging/"; /> http://schemas.xmlsoap.org/soap/http"; style="document" /> http://www.hpi.uni-potsdam.de/dbrep/wsmessaging/"; /> http://www.hpi.uni-potsdam.de/dbrep/wsmessaging/"; /> http://www.hpi.uni-potsdam.de/dbrep/wsmessaging/"; /> http://localhost:8080/axis2/services/MessagingClientService"; /> http://localhost:8080/axis2/services/MessagingClientService"; /> 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] >>
Re: [Axis2] [rampart] Problems using rampart
Hi Dimuthu, I changed all the libs when engaging the rampart module to axis2. I know that the axiom-1.2.2 jars are used. What code do you need? I think of the stub, the skeleton and the part where the client calls the stub. Anything that is important? I will send this code in a archive to you personally. I don't think that I'm allowed to give out all code through a public mailing list. Is that ok? Regards, Sebastian Dimuthu Leelaratne schrieb: > Hi Sebestian, > > Can you check wether you are using the correct axiom jars in the class > path? > > It should be axiom 1.2.2 jars, namely axiom-dom, axiom-impl and > axiom-api. With rampart-1.1 both 1.2.2 and 1.2.1 axiom jar set should > work properly. > > If this step also doesn't work, then I can have a look at it if you > can send me the client code. > > Thank you, > Dimuthu. > > - > WSO2 -"Oxygenating the Web Service Platform" > www.wso2.com > > > On 1/22/07, Sebastian Roschke <[EMAIL PROTECTED]> > wrote: >> Hi Dimuthu, >> >> thanks for your help again!!! I tried all the examples and they are all >> working fine. I really don't know where this problem comes from. Do you >> have any ideas? >> >> Regards, >> Sebastian >> >> Dimuthu Leelaratne schrieb: >> > Hi Sebastian, >> > >> > I tried to recreate the scenario as follows. >> > >> > 1) I used axis2-1.1.1 and rampart 1.1 and executed the first rampart >> > smaple which is in samples/basic/sample01. Which is identical to your >> > situation. It executed without any problems >> > >> > 2) But then I realized that it didn't have any addressing headers as >> > yours. So I added some addressing headers and ran it, but it worked >> > perfectly too. >> > >> > 3) After that I added a null element and ran the sample which again >> > worked perfectly. So finally the SOAP message I observed was as >> > follows(Please refer [1]) and in the axis2.xml I had what you had >> > which is "" >> > >> > Did you try running the sample01 in rampart? It is an identical >> > situation where the axis2.xml has only engaged the module but doesn't >> > do any security actions. If it works fine in your machine then we can >> > narrow down the problem to scenario specific. Thank you. >> > >> > Rgds, >> > Dimuthu >> > - >> > WSO2 -"Oxygenating the Web Service Platform" >> > www.wso2.com >> > >> > >> > >> > [1] The soap messagge >> > >> > http://www.w3.org/2005/08/addressing"; >> > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> >> > >> > http://localhost:9080/axis2/services/sample01 >> > >> > >> > >> http://www.w3.org/2005/08/addressing/anonymous >> >> > >> > >> > >> urn:uuid:8655FCF2CBB79A97C711691163447531 >> > urn:echo >> > >> > >> > > > xmlns:ns1="http://sample01.samples.rampart.apache.org/xsd";> >> >lastMan >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > On 1/19/07, Sebastian Roschke <[EMAIL PROTECTED]> >> > wrote: >> >> 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 >> >> >> >> >> >> >> >> 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? O
Re: [Axis2] [rampart] Problems using rampart
Hi Dimuthu, thanks for your help again!!! I tried all the examples and they are all working fine. I really don't know where this problem comes from. Do you have any ideas? Regards, Sebastian Dimuthu Leelaratne schrieb: > Hi Sebastian, > > I tried to recreate the scenario as follows. > > 1) I used axis2-1.1.1 and rampart 1.1 and executed the first rampart > smaple which is in samples/basic/sample01. Which is identical to your > situation. It executed without any problems > > 2) But then I realized that it didn't have any addressing headers as > yours. So I added some addressing headers and ran it, but it worked > perfectly too. > > 3) After that I added a null element and ran the sample which again > worked perfectly. So finally the SOAP message I observed was as > follows(Please refer [1]) and in the axis2.xml I had what you had > which is "" > > Did you try running the sample01 in rampart? It is an identical > situation where the axis2.xml has only engaged the module but doesn't > do any security actions. If it works fine in your machine then we can > narrow down the problem to scenario specific. Thank you. > > Rgds, > Dimuthu > - > WSO2 -"Oxygenating the Web Service Platform" > www.wso2.com > > > > [1] The soap messagge > > http://www.w3.org/2005/08/addressing"; > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> > > http://localhost:9080/axis2/services/sample01 > > > http://www.w3.org/2005/08/addressing/anonymous > > > urn:uuid:8655FCF2CBB79A97C711691163447531 > urn:echo > > > xmlns:ns1="http://sample01.samples.rampart.apache.org/xsd";> >lastMan > > > > > > > > > > On 1/19/07, Sebastian Roschke <[EMAIL PROTECTED]> > wrote: >> 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 >> >> >> >> 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: >> >> >> >> >> >>http://www.w3.org/2005/08/addressing"; >> >> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> >> >> >> >> >> >> >> http://localhost:3003/axis2/services/MessagingClientService >> >> >> >> >> >> >> >> >> >> http://www.w3.org/2005/08/addressing/anonymous >> >> >> >> >> >> >> >> >> >> urn:uuid:8655FCF2CBB79A97C711691163447531 >> >>urn:addClient >> >> >> >> >> >>> >> >> xmlns:ns2="http://www.hpi.uni-potsdam.de/skid.common/wsmessaging/types";> >> >>test >> >>skid.agent.test.TestAgent >> >>messaging_test.config >> >> >> >> >> >> >> >> >> >> >> >> 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
Re: [Axis2] [rampart] Problems using rampart
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: axis-user@ws.apache.org > 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 > > > > 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: >>> >>> >>>http://www.w3.org/2005/08/addressing"; >>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> >>> >>> >>> >>> > http://localhost:3003/axis2/services/MessagingClientService :To> > >>> >>> >>> >>> > http://www.w3.org/2005/08/addressing/anonymous >>> >>> >>> >>> > urn:uuid:8655FCF2CBB79A97C711691163447531 > >>>urn:addClient >>> >>> >>>>> >>> > xmlns:ns2="http://www.hpi.uni-potsdam.de/skid.common/wsmessaging/types";> > >>>test >>>skid.agent.test.TestAgent >>>messaging_test.config >>> >>> >>> >>> >>> >>> 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 > &
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 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: >> >> >>http://www.w3.org/2005/08/addressing"; >> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> >> >> >> http://localhost:3003/axis2/services/MessagingClientService >> >> >> >> http://www.w3.org/2005/08/addressing/anonymous >> >> >> >> urn:uuid:8655FCF2CBB79A97C711691163447531 >>urn:addClient >> >> >>> xmlns:ns2="http://www.hpi.uni-potsdam.de/skid.common/wsmessaging/types";> >>test >>skid.agent.test.TestAgent >>messaging_test.config >> >> >> >> >> >> 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(OutOnlyAxisOperation.java:353) >> >> >> >> >> at >> >> >> skid.messaging.ws.client.client.MessagingClientServiceStub.addClient(MessagingClientServiceStub.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.(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.
Re: [Axis2] [rampart] Problems using rampart
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: http://www.w3.org/2005/08/addressing"; xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> http://localhost:3003/axis2/services/MessagingClientService http://www.w3.org/2005/08/addressing/anonymous urn:uuid:8655FCF2CBB79A97C711691163447531 urn:addClient http://www.hpi.uni-potsdam.de/skid.common/wsmessaging/types";> test skid.agent.test.TestAgent messaging_test.config 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(OutOnlyAxisOperation.java:353) >> >> at >> skid.messaging.ws.client.client.MessagingClientServiceStub.addClient(MessagingClientServiceStub.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.(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.(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:199) >> >> 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:116) >> >> ... 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/axis-dev@ws.apache.org/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] > signature.asc Description: OpenPGP digital signature
[Axis2] Question on TRANSPORT_IN_URL in Axis2-1.1.1
Hi all, I have updated my Axis2-1.1 to Axis2-1.1.1 today and encountered some problems. Currently I use the TRANSPORT_IN_URL field you can get with the following code inside a MessageReceiver or a Module: msgContext.getProperty(org.apache.axis2.Constants.Configuration.TRANSPORT_IN_URL); I used this field to send SOAP messages with completely different WSA:TO values to a specific service. Up till now the URL of the called service can be found in this field. Since Axis2-1.1.1 it seems that this filed is not used anymore... Do you have any idea wether this value(the address of the called service) is saved in the messageContext inside Axis2? Suggestions are welcome. Regards, Sebastian signature.asc Description: OpenPGP digital signature
[Axis2] [rampart] Problems using rampart
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(OutOnlyAxisOperation.java:353) at skid.messaging.ws.client.client.MessagingClientServiceStub.addClient(MessagingClientServiceStub.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.(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.(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:199) 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:116) ... 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/axis-dev@ws.apache.org/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? signature.asc Description: OpenPGP digital signature
