Sam,
Where in the spec did you find this mapping?
Sam wrote:
> Why not ?
>
> I just wrote a test service that takes a Document as an argument.
>
> The org.w3c. Document is standard mapping in the JAX-RPC specs.
> /s
>
>
> Doug Kohlert wrote:
>
>> Not at this time.
>>
>> Kevin Jones wrote:
>>
>>> I'm guessing the answer to this is no, but...
>>>
>>> In the JAXRPC RI can I define a Java interface that takes XML rather
>>> than one that takes specific Java types, and then generate the server
>>> from that itf definition. i.e. what I want to do is to have
>>>
>>> public boolean foo(Node n) or
>>> public boolean foo(Document d) or
>>> public boolean foo(SOAPElement s) or something similar
>>>
>>> In Axis I have the option of 'message' based services. I can have a
>>> method that looks like one of the following
>>>
>>> public Element [] method(Element [] bodies);
>>> public SOAPBodyElement [] method (SOAPBodyElement [] bodies);
>>> public Document method(Document body);
>>> public void method(SOAPEnvelope req, SOAPEnvelope resp);
>>> And get access to the SOAP message as raw XML.
>>>
>>> Kevin Jones
>>> http://kevinj.develop.com
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
>>> For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
>>>
>>>
>>
>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
> For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
>
>
--
Doug Kohlert
Java Software Division
Sun Microsystems, Inc.
phone: 503 345-9806
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net