Hi
Today, most of the Soap implementations use HTTP for transport
protocol..However, in the near future, we expect more support for
"Asynchronous" transport protocol like SMTP, JMS, BEEP etc.
I have following concern in this regard:
1) Does the "Aynchrony" make sense in "RPC" (encoded) style
Hi
Following encapsulated all the security-related issue, which any
protocol should address to..
a) Privacy
b) Authntication
c) Integrity
d) Non-repudiation
e) Access Control (Authorization)
I have some questions about these in the context of SOAP and
Web-Services.
1) What is the status of
I feel like I'm missing something here.
On my server, I have a hierarchy of beans. The client
will call one method (which will go over SOAP to the
server) and get the whole hierarchy as the return
value. Some of the beans will have methods that will
in turn invoke SOAP calls back to the server. B
dims-
> Need Help!!! Am having problems using WSDL2Java with the following WSDL's:
> - http://www.dotnetjunkies.net/services/ContentServices.asmx?WSDL
[...]
> Looks like the schema is specified in the SOAP Response and not in the
> WSDL itself.
Exactly!
Regarding this bit from your WSDL:
I tested the example with latest download (March 7). Everything appears to
work...
Java2WSDL produces a wsdl file
WSDL2Java produces stubs which compile
However, there remain two problems:
1. The example client does not work. (It returns null.) (This client does
not use the stubs.)
2.
From: PAUL MAENNER
I have an existing service that I've used with Apache SOAP 2.2 for some
time. I was trying to get it to work with Axis (nightly build, 3-6-2002). I
performed Java2WSDL on the existing class and then WSDL2Java on
the resulting wsdl in order to generate the needed wsdd. (I ignore
I have not had time to work on these defects.
Let me re-state:
Issue 1: A List should be serialized as an array with arrayType
="xsd:anyType".
Status: I will begin working on the fix (and a testcase) this evening.
Issue 2: Smart reflection needed on server-side to invoke service method
that ha
WSDL2Java stopped giving me resource not found exceptions when I trimmed the
classpath to contain just the essential libraries:
- axis.jar
- excalibur-cli.jar
- commons-logging.jar
- wsdl4j.jar
- xerces.jar
I tried running a simple client with the generated stubs and got another
mi
Hi
Is This bug is fixed
kamlesh
-Original Message-
From: Vikram Rayabhari [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 28, 2002 12:32 AM
To: [EMAIL PROTECTED]
Subject: Re: Array Serializer and java.util.List
Hi Rich,
Thanks for the reply.
Isn't the expected xml elemen
There is a typo in the deploy.wsdd file. the word
'Order' in the qname value should have a capital O.
this is how it should read:
Bob Woodley
__
Do You Yahoo!?
Try FREE Yahoo! Mail - the world's greatest free email!
http://mail.yahoo.com/
Russell,
The timestamp on axis.jar reads 03/07/02. I looked the property file in
axis.jar and found that the resource 'optionHelp00' did indeed exist. I ran
it again with the verbose mode and got the following trace
Exception in thread "main" java.lang.ExceptionInInitializerError:
java.util.Missi
Title: RE: [WSDL2Java] No deserializer defined for array type http://[.. .]/: QueryProperty
I don't understand your problem here. Why can't your code reference QueryProperty instead of queryProperty?
I don't think you'll have much luck getting the JAX-RPC or JAXB (from which the XML mapping
It looks like you're missing the org/apache/axis/utils/resources.properties
file. Or you have an old version of it.
Russell Butek
[EMAIL PROTECTED]
"Maneesh Sahu" <[EMAIL PROTECTED]> on 03/07/2002 03:47:19 PM
Please respond to [EMAIL PROTECTED]
To:<[EMAIL PROTECTED]>
cc:
Subject:Miss
Hi,
I just updated axis to use the latest nightly build from the earlier alpha3
release. I am getting a missing resource exception when I run WSDL2Java:
D:\workdir\axis>java org.apache.axis.wsdl.WSDL2Java -p
com.interkeel.services.
notification http://maneesh:8080/axis/Contract.jws?wsdl
Exception
In my servlet, I want to create a javax.xml.soap.SOAPMessage object from
the HTTP
request body. I intend to use javax.xml.soap.MessageFactory.createMessage
() to do
this. However, when I try to create my factory via
javax.xml.soap.MessageFactory.newInstance(), I get the following error:
javax.
It think that the uppercase for first letter rule is a cosmetic concerns
that shouldn't be in the JAX-RPC spec.
First it mainly applies to the Java language which at the time of designing
a WSDL shouldn't be a concerns.
However, I do agree with the rules that change the names that would bring
Hi,
I have played attachements with Axis for couple of
days and could not make it work. There is a attachement sample under samples
directory. It does not work with latest Axis build. Here are my
questions:
1). Does the latest Axis build support the
attachement?
2). If yes, does the atta
I was told that Tomcat can dynamically load new
versions of classes. Whenever I modify a service and
re-deploy it in AXIS, I have to restart Tomcat
(Catalina) in order for a NEW client to use the
modified service. Is there any option I must set to
enable dynamic class loading?
Many thanks,
Nuno
Title: RE: [WSDL2Java] No deserializer defined for array type http://[...]/: QueryProperty
I do not see any inconsistencies. Reading carefully, the spec (in the appendix) states that the mapping does not change an XML name that is already a legal and *conventional* Java identifier. The stateme
>From: Dave Dunkin [mailto:[EMAIL PROTECTED]]
>WSDL2Java complies to the JAX-RPC specification for mapping XML identifiers
to Java identifiers. >That specifies that class should start with a capital
letter.
If I'm reading the spec correctly, this would appear to be an
inconsistency in it.
The ap
Hi,
I have JRun 3.1 too. I just use the installer.jar that you can download
in http://www.macromedia.com/software/jrun/download/web_services/
Then I could run the examples in axis without problens.
-Mensagem original-
De: Ma, June [mailto:[EMAIL PROTECTED]]
Enviada em: quarta-feira, 6 de
Yes!
Take a look at the source/javadoc for
org.apache.axis.handlers.SimpleSessionHandler.
-Original Message-
From: Willy Ching [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 06, 2002 7:37 PM
To: [EMAIL PROTECTED]
Subject: Session in Web Service
Hello All,
I'm new in web serv
Quick question ... maybe someone can give their quick opinion ...
I am developing an application which currently using XML-RPC over/inside a
servlet to communicate but I'd like to support the same operation with SOAP 1.1
via Axis (without having to *use* the whole Axis system/servlet/WSDD/etc).
OK thanks. I think I'm using something in a different way from the norm so
that's why I wanted the name. What I want probably doesn't follow if you have
multiple refs to the same object. My bad.
Rania
R J Scheuerle Jr wrote:
> Rania,
>
> There have been quite a few changes to the serializatio
Taras,
I have tried your example, but I got compile error.
for example, there is no way to find "GCSerializerConstants.TYPE_DELIVERY".
What build of AXIS did you use?
Thanks,
Emily
At 08:34 PM 3/4/2002 -0800, Taras Shkvarchuk wrote:
>This may not be the best example, but its something for
Thanks Dave for the pointer, however, am I the only one to find this quite
restrictive? I understand the needs for rules about XML to Java mapping but
the first letter uppercase one seems rather cosmetic to me.
I am interested in a solution to this problem.
1 - Should WSDL2Java allow a switch
I was hoping you'd show me code, but I think I understand your situation.
What you call data-holders I call beans or, more appropriately, type
classes (things generated from the clause in the WSDL). You want
to have the non-bean aspects of these classes available on the client.
You're doing some
I was looking at the message example of the nightbuild of 5-3. The
example creates some SOAPBodyelements and sends it to the service.
Instead of SOAPBodyelements I would like to send messages. I found the
message object in the API doc. How do I use it on the client and
service side?
Also I want
again with source examples an the nightly build of 2002-03-05.
There is something wrong with the bean serialization or .wsdd because I
get the following response when I try to execute the Client.java .
Do you know why ?
Guido Di Maio.
this is the soap envelope:
http://schemas.xmlsoap.org/soa
29 matches
Mail list logo
