A very good summary of the state of the asynchronous web services
applications.
I think that a standard reliable transport may be covered by the
ebxml-msg and JAXM specifications. It appears that some of the JAXM
implementations use JMS internally for queuing and reliable semantics.
I am deploying a pretty simple service. The wsdd snippet is:
service name=urn:ldap-util provider=java:RPC
namespacehttp://www.libertyram.com//namespace
parameter name=className value=com.lram.cor.ldap.LDAPUtil/
parameter name=allowedMethods
An excellent summary !!
Another BIG thing about the Web Service and JMS semantic mismatch is about
the way they look at TRANSACTION (although there is not a widely-accepted
one at this moment, so I'm talking about the model behind BTP and
WS-Transaction).
In JMS, it is NOT possible to send
Hello,
when trying to start the attachment sample (sh testit.sh MYFILE) I
get the following error:
java.io.IOException: No support for attachments
AxisFault
faultCode: {http://xml.apache.org/axis/}Server.userException
faultString: java.io.IOException: No support for attachments
faultActor:
Hi all,
I'm having problems getting the getOption(s) to return anything from a
handler being invoked as a global request. They both always return null.
I'm new to axis so it may be pilot error on my part. I cannot find any
definitive doc saying that this should or should not work. Below is
Just FYI for those who are interested in this functionality.
Recent nightly builds (post 1.0) have support for custom fault data. It is still
pretty fresh, so bug reports are welcome.
The SOAP Builders interop event was held last week in Burlington, MA and Apache Axis
successfully completed
Hi all,
Is there a way to deserialize a DOM element into a java object with Axis?
(also how would it be possible to serialize and append an object to a DOM
element?)
I've successfully perform this feature with apache SOAP 2.3 using
unmarshaller, but I cannot see the process with Axis encoding
Yes, thanks Junaid. Works great.
- Original Message -
From: Martin Jericho [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; Sean [EMAIL PROTECTED]
Sent: Sunday, October 13, 2002 6:00 PM
Subject: Re: deploy on https
Is there any reason why you particularly want to deploy using SSL? You can
On Monday 14 October 2002 18:15, Matthias Brunner wrote:
Hello,
when trying to start the attachment sample (sh testit.sh MYFILE)
I get the following error:
java.io.IOException: No support for attachments
AxisFault
faultCode: {http://xml.apache.org/axis/}Server.userException
Hello,
I get a SAXParseException when trying to deserialize SOAP messages
with attachments.
Server:
public class MyService {
public String call()
{
SOAPMessage msg =
MessageContext.getCurrentContext().getResponseMessage();
When doing the same with DIME as the return type I get the following
message. (Again, serializiation works, only deserialization does
not.)
--
INFO: Mapping Exception to AxisFault
AxisFault
faultCode: {http://xml.apache.org/axis/}Server.userException
faultString:
I agree that SOAP over JMS over the intranet (to Dave's definition) is a
very practical approach today. although we still need to be aware of other
conflicting approaches as well
Without knowing the Sonic contribution, I', not sure if the message
correlation id is an explicit field
Royce,
can you post the stub of the .net class itself, rather than just the wsdl.
I'm working on some .net server axis client interop testing, see. I'd also
like to see what you are sending back as .net structures
-unsigned short is supported in axis with wrapper classes; there is no
ushort in
- Original Message -
From: Jian Zhang [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, October 10, 2002 7:37 AM
Subject: RE: Thanks, presentation, and DIME question
http://msdn.microsoft.com/downloads/default.asp?URL=/downloads/sample.asp?ur
- Original Message -
From: Ted Neward [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, October 10, 2002 1:26 PM
Subject: RE: Thanks, presentation, and DIME question
There's still some open questions about what form attachments should take
in
SOAP, AFAIK. Sun provides one
Ok.
can you please elaborate on how you define SOAP over JMS.
Since JMS is not a wire level protocol like HTTP/FTP/SMTP/other this term
IMHO is misleading.
SOAP over JMS, really means using the JMS API to send a SOAP message..
right ? So unless you use a standard wire protocol no two vendors
Axis: Next Generation Java SOAP, published by Wrox Press, 2002, has an
interesting section on writing an AXIS transport handler with the transport
being JMS (see pgs 154-166). It has been discussed in this mailing list
previously.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL
Title: Books on AXIS
Someone mentioned the WROX book, Axis: The Next Generation of Java SOAP. I was wondering if anyone knows of any other books like this about AXIS that are availabe now or soon will be?
Thanks.
CONFIDENTIALITY NOTICE
This message and any included attachments
are from
In an effort to organize a rather large set of API commands
in wsdl, we decided to break the wsdl file into multiple files and use import. Each of these files have
their own type, message, port, binding but no service. Each file uses the same namespace. I have a master file that imports
There is a DOM Element serializer/deserializer in Axis
(org.apache.axis.encoding.ser.ElementSerializer). Is this what you're
looking for?
-Junaid
SOAP over JMS means the SOAP engine calls JMS API to send and receive
messages. And because of JMS is an API but not protocol, SOAP over JMS
requires both ends to be using the same JMS vendor and lost SOAP's
heterogeneity characteristics. That works only within an intranet
environment where
Perhaps it would sound better if it were referred to as
SOAP-over-JMS-over-HTTP. No matter how you say it, its still acting in
the role of a protocol. Its a reliability layer that sits between the
SOAP marshalling and the underlying TCP/HTTP layer--a protocol on top of
a protocol. Yes JMS
Hello,
I downloaded TomCat 4.1.12(
jakarta-tomcat-4.1.12.exe ) and Axis
Release 1.0
and followed the instruction for Installing Axis on
window
I am getting this error when I run the validation on this page
http://localhost:8080/axis/index.html
I know I have the wrong version of something, but
I have a version of the WSIF DynamicInvoker client which handles complex
types in input and output. I try exactly the same WS invocation (of
Amazon's service) with the WSIFDynamicProvider flavors _ApacheAxis and
_ApacheSOAP. Things work fine with the Soap Provider against the 2002/10/14
nightly
What version of xerces (1 or 2) did you install?
-- Michael
On Mon, 14 Oct 2002, siamak wrote:
I downloaded TomCat 4.1.12( jakarta-tomcat-4.1.12.exe ) and Axis
Release 1.0 and followed the instruction for Installing Axis on
window
I am getting this error when I run the validation on this
I understand that Axis is using Xerces as XML parser.
Now, no offence for Xerces fans but I will like to use XP as XML parser,
it's much faster.
I there any way that I can use XP ?.
Do I need to modify the sources to get this support?.
Thanks,
Alin
26 matches
Mail list logo
