multiref encoding has some distinguishing aspects:
1. Space savings by way of ref contrasted to duplication
2. Circular references can be represented. In place encoding
will result in infinite loop (stack overflow) as happens
with Apache BeanSerializer. Axis handles this.
3. Better inform
The idea that "Apache SOAP forces you to be
explicit about type" is a barrier in good system design.
This breaks abstraction. I should be able to use a serializer
for HashMap class where a serializer for Map is expected. Some
runtime interaction causes search for Map serializer. If there
is one --
Scott,
Neither am I a CORBA expert. However, as a OO Software developer
with CORBA experience, I can answer your first question with the
following statements:
SOAP is a XML based messaging protocol -- it does not care
what kind of higher software layer is using it. However, a higher
lay
This has been an interesting thread.
It is heartening to see serializer improvements that
will be taken up.
Great work, Scott!
Soumen Sarkar.
-Original Message-
From: Scott Nichol [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 02, 2002 7:04 PM
To: [EMAIL PROTECTED]
Subject: Re: Confusi
As per standard, WSDL is supposed to contain the host:port combination.
If you do not want to advertise transport end-points then use a high
level abstraction like CORBA Object reference.
You can have a level of indirection through DNS, but ultimately one can find
the host:port.
Here are the sta
How to use BeanInfo?
This is documented by SUN Microsystems in its JavaBeans Spec.
ftp://ftp.javasoft.com/docs/beans/beans.101.pdf
If you would like to go for tutorials:
http://java.sun.com/docs/books/tutorial/javabeans/beaninfo/
http://developer.java.sun.com/developer/onlineTraining/Beans/Beans
I beleive this is not a a Apache SOAP bug. White space and
lines between tags should not matter in XML parsing. Please
refer to XML specification as shown below:
=
http://www.xml.com/axml/testaxml.htm
2.10 White Space Handling
In editin
Then it should be fixed, IMHO. This is causing interop problem.
XML spec talks about significant and insignificant white space.
I am not clear on this. What does SOAP spec mandate -- looked
like SUN's SOAP server implementation goes by a strict XML schema.
Soumen Sarkar.
-Original Message--
Great work, Scott on XML spec interpretation. It would benefit many people
including me.
Soumen Sarkar.
-Original Message-
From: Scott Nichol [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 03, 2002 7:17 AM
To: [EMAIL PROTECTED]
Subject: Re: Extra line appearing in Apache Response [SP
SOAP is XML based application protocol mapped to some transport protocol.
Since you are transferring large file, transport protocol issues are
involved.
I beleive, you need to search for a SOAP implementation on some suitable
transport protocol. The document should be transferred as an attachment.
Scott,
In the example you have given, the web service handles
http://xml.apache.org/soap gracefully by ridirecting
to http://xml.apache.org/soap/. I beleive similar graceful
handling should be implemented for finding type mapping.
In other words the trailing / should not cause finding
type mapping
I knew that it would go to namespace schema comparison
where it has to match character by character. Seperators
like '/' does not carry special significance in
namespace names (i.e do not imply any structure). From
a structural point of view presence of trailing '/' does
not matter but as I said '/
12 matches
Mail list logo
