Dennis Sosnoski wrote:
Long term it's clear that real data binding support needs to be
integrated into the SOAP framework. JAX-RPC 2.0 has the stated
intention of doing this using JAXB 2.0. Right now you can kind of do
this with Castor in Axis, if you're willing to go through enough
trouble
I try to import a schema in the WSDL.
With the types in the WSDL (WSDL1), Axis-WSDL2Java
works good.
With an import (WSDL2), i have an error
java.io.IOException: Type {urn:example}Request is
referenced but not defined.
I use the same namespace for the schema and WSDL.
Why doesn't it work?
WSDL1:
Hello,
My understanding is that Axis 1.1 is only support the Basic enterprise proxy. Does
any one know if Axis is planning to support the other type (Digest or NTLM) enterprise
proxy in the near future? If not, how do I change my client program to support the
Basic enterprise proxy? Can
Aleksander Slominski wrote:
Dennis Sosnoski wrote:
Long term it's clear that real data binding support needs to be
integrated into the SOAP framework
do you know if anybody tried to add support for XmlBeans
(http://xml.apache.org/xmlbeans/) to AXIS?
we have XmlBeans integrated in
Dennis Sosnoski wrote:
This is great to hear about, but information on WS/XSUL looks scarce
(I found your slide set - or is that slajd set?).
woes of trying to do power point to html conversion ... (BTW slajd is
in Polish for slide :) )
Can you point me at anything that's usable?
WS/XSUL
Does anyone know how to view detailed error messages (i.e. - stack traces)
for ?WSDL ? I am trying to use ?WSDL and I get a message that there was a
java.lang.reflect.InvocationTargetException, but I don't get a stack trace
so I can't figure out what's going wrong.
Thanks,
Matt
Aleksander Slominski wrote:
Dennis Sosnoski wrote:
I've got my own lightweight SOAP framework built around JiBX. I'll try
to get something out about that, probably adding it as a subproject in
conjunction with the beta 3a release next week, so that people who are
interested in a decoupled
Title: Turning off Discovery of Logging
Hi everyone-
Our application has Axis, as well as the other necessary Apache jar files obfuscated inside our own jar file, to avoid classpath problems with customer's applications. This works great until someone puts one of these jars on their
Thanks for the quick response.
Unfortunately, setting the org.apache.commons.logging.Log property
will affect all classes trying to use the logging stuff. I can't force
users of our code to use the log impl we have selected, and in fact,
since our code is obfuscated, it wouldn't work for them
Nelson Minar wrote:
This discussion has been very useful. Thank you!
Jim Murphy of MindReef/SOAPScope said:
What that means to me is that SOAP is the ... tags that allow service
designers to put application stuff in one bucket (soap:Body) and keep
that separate from non-functional stuff that goes
Dennis Sosnoski wrote:
Jim Murphy wrote:
IMHO, Web Service Message design has been an afterthought of the spec
working groups that comprise your typical WS stack. You need to know
a lot of grunge to design an easy to consume service:
1. XSD - what to use and what to avoid is the hard part
I favor the approach this suggests:
Make the SOAP stack an XML delivery and minimal SOAP processing engine
and leave XML-Java type translation to another layer. Chose Castor,
XmlBeans, JAXB 1.0, 2.0 whatever. The choice is dictated by how I want
to work witht he XML recognizing that the XML is
Jim Murphy wrote:
Dennis Sosnoski wrote:
doc/lit means you don't need to care about 1 or 3 - you specify the
XML format and let the clients worry about how they want to handle
it. 2 is a separate issue...
Really? I can see how it would be liberating to think this way but I
can break away from
The only problem with decoupling the SOAP processing layer from the Java
data binding layer is the implications such an approach has on intermediary
node processing. Almost every SOAP stack I've seen implements SOAP
intermediary nodes as some sort of interceptor (Axis handlers, JAX-RPC
handlers,
Title: Message
Hello
All,
Has anybody seen
this message before?
I wouldn't be so
confused if this error was consistent, but it only occurs when I try to run the
my JUnit test cases and NOT when I run my client
application.
I've checked for
differences in the classpaths for the two apps
Title: Message
P.S.
The same error occurs when I set my XML parser to be Xerces in stead of
Crimson
-Original Message-From: Nick Sharples
[mailto:[EMAIL PROTECTED] Sent: 17 March 2004
21:02To: [EMAIL PROTECTED]Subject:
SimpleDeserializer encountered a child element,
Anderson Jonathan wrote:
The only problem with decoupling the SOAP processing layer from the Java
data binding layer is the implications such an approach has on intermediary
node processing. Almost every SOAP stack I've seen implements SOAP
intermediary nodes as some sort of interceptor (Axis
Hi,
Does anyone know which version of axis is incorporated in JRun4? Is
is 1.1 or 1.0?
Thanks!
-- Niranjan.
JRun 4 uses Axis 1.0
JRun 4 SP1 uses Axis 1.1
Details are in the Service Pack release notes.
--
Tom Jordahl
Macromedia Server Development
-Original Message-
From: Ekbote, Niranjan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 17, 2004 3:20 PM
To: '[EMAIL PROTECTED]'
Cc: '[EMAIL
Anderson Jonathan wrote:
The problems is that intermediary nodes can change the content of the SOAP
envelope, plain and simple. This really complicates that SOAP XML data
binding issue. Intermediary node implementations need access to the SOAP
header information at the very least... any type of
Jim Murphy wrote:
I don't get why this is a problem. Say I have a handler that wants to
transform a request in some way (decrypt, remove a Header whatever).
Isn't that just consuming one stream and producing another? If it wants
to consume one stream map that to Java using some
Hello everyone, I hope someone can help me out with this issue.
I am trying to invoke a web service but getting soap fault code back and specifically
this string message:[org.apache.axis.AxisFault : ; nested exception is:
org.xml.sax.SAXException: SimpleDeserializer encountered a child
Anderson Jonathan wrote:
Jim Murphy wrote:
Why wouldn't a very thin Axis working with several Java
binding/marshaling layers be a compelling approach?
Problem is, I have yet to see a SOAP stack that works this way. Consuming
one stream and producing another implies that each intermediary
Hi everyone,
Is there anyway combine the rpc and message styles?
What I would like is to have a method signature something like this:
Document doSomething(CustomRequest req);
I will be using the data in the CustomRequest to interface with an existing
application that returns a DOM document
Title: Message
I get
the same error and it happens only in a particular scenario. I have aclass
like this
public
class BPEvent {
private String processName;
private HashMap attributes;
...
...
}
When I
add a String object to atts everythign works fine. However when I add my
customized
This is not directly related to the discussion on hand. But I have been trying to get around this problem in axis.
If you notice the element
processName xmlns=""CourseBusinessProcess/processName
why should the message have a namespace xmlns="" Is it right to have this for elements.
What is the
Regarding standard SOAP headers:
We will solve the security problem in the very near future.
OASIS WSS SOAP Message Security (the standardized version of WS-Security)
should be ratified as a formal OASIS standard by the end of the month.
OASIS WSS defines standard tags for you to put
Note that TREX was merged with RELAX to create RELAX NG.
Also -- more to the point -- note that RELAX NG does not define a type
system. It defers to XML Schema for the type system. Unfortunately, we
really can't escape XML Schema.
Sun, Microsoft, and everyone else has standardized in XML
To combine the rpc and the message style, why don't
you use the rpc style adding an xml document as
attachment?
--- Jason Calabrese [EMAIL PROTECTED] ha
scritto: Hi everyone,
Is there anyway combine the rpc and message styles?
What I would like is to have a method signature
something
Hi axis users,
I'd like to know if is there a way to declare in the
wsdl that a client of a ws has to send an attachment
as a parameter of the message, so that when I use
WSDL2Java I can use the portType in this way:
result = port.myMethod(dh, other parameters);
where dh is a DataHandler or some
30 matches
Mail list logo
