Hmmm. I still don't quite understand what you need to accomplish. You have emphasized *soap:Envelope*, *soap:Header* and *soap:Body*, which is just a change of namespace prefix from SOAP-ENV to soap. The way you would achieve that is to change Constants.java and make sure its .class file gets loaded instead of the "sanctioned" one from a distribution. Are there other aspects to the request that you do not know how to do with Apache SOAP?
On 3 Jul 2003 at 11:53, Daniel Zhang wrote: > Scott - > > What need to be changed are not only prefix, also include SOAP Header, > Body, and their > sub-elements. Our customer required a specific format for SOAP Request > and Response. > Example of SOAP request like: > > <*soap:Envelope* xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:cb="http://mycompany.com/cbody.xsd"; > xmlns:ch="http://mycompany.com/cheader.xsd"; > > xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd"; > > xmlns:xlink="http://www.w3.org/1999/xlink"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:xs="http://www.w3/org/2001/XMLSchema"; > xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ > > http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd > cbody.xsd cheader.xsd status.xsd > ticket.xsd response.xsd" > > * <soap:Header> * > <eb:MessageHeader eb:id="ID000001" > eb:version="2.0"soap:mustUnderstand = "1"> > <eb:From> > <eb:Role>String</eb:Role> > </eb:From> > <eb:To> > <eb:Role>String</eb:Role> > </eb:To> > <eb:CPAId>TBD</eb:CPAId> > <eb:ConversationId>934523405</eb:ConversationId> > <eb:Service>service</eb:Service> > <eb:Action>Application</eb:Action> > </eb:MessageHeader> > <ch:cHeader> > <ch:version>1.0</ch:version> > <ch:messageType type="xs:string">string</ch:messageType> > </ch:cHeader> > *</soap:Header>* > * <soap:Body>* > <eb:Manifest eb:id="ID000002" eb:version="2.0"> > <eb:xlink="http://mycompany.com/link"; /> > </eb:Manifest> > <cb:cBody> > <cb:MessageType> > <cb:Name>John</cb:Name> > <cb:Phone>1233456789</cb:Phone> > ..... > </cb:MessageType> > </cb:cBody> > *</soap:Body>** > </soap:Envelope> * > > So how can I achieve this in SOAP RPC call(call.invoke())? Apache SOAP > is pretty much predefine those tags. > All I think now is to use message call to achieve but it can not embed > object or attachment, isn't it? > > -Daniel > > > Scott Nichol wrote: > > >Can you be more specific about what you mean by your "own SOAP tags"? > >Your example shows a different namespace prefix. Is that all you > >want to do, change the namespace prefixes? > > > >On 3 Jul 2003 at 8:12, Daniel Zhang wrote: > > > > > > > >>I need to write my own SOAP tags in SOAP message. I prefer to use SOAP > >>RPC call(call.invoke()), but I found > >>it's not easy to change the SOAP tag(e.g change default Apache SOAP > >>default <SOAP-ENV: Envelope ... to > >><soap:Envelope ..., also change other tags). So I turned to use SOAP > >>Message transmission since it's easy to write > >>your own tag and make it as message.send(). However, I found it's hard > >>to pass any object or attachment. > >> > >>I wonder how I can solve this problem? Does SOAP RPC call allow you to > >>construct your own tags for SOAP > >>header and body? Or does SOAP Message allow you to embed any object or > >>attachment? > >> > >>Thank you all in advance, > >> > >>-Daniel > >> > >> > >> > >> > > > > > >Scott Nichol > > > >Do not reply directly to this e-mail address, > >as it is filtered to only receive e-mail from > >specific mailing lists. > > > > > > > > > Scott Nichol Do not reply directly to this e-mail address, as it is filtered to only receive e-mail from specific mailing lists.
