Hi,
Can someone guide me how i can Serialize java.util.Properties and send
across the wire over SOAP.
Does axis provide default serialization for java.util.Properties or do i
need to write my own serializer/deserializer for the same.
If i need to write my own serializer/deserialized then how do
How about unplugging your dev workstation from the Net and see if the
response time differs?
/Chris
http://cvs.apache.org/~haddadc
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, October 27, 2003 7:54 PM
To: [EMAIL PROTECTED]
Subject: axis performance
DIME is supported by the .NET WSE, MIME is not supported by .NET.
So if you are interested in interoperability, the winner is: DIME
/Chris
http://cvs.apache.org/~haddadc
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, October 27, 2003 8:22 PM
To:
Might be a DNS problem? Though 8 seconds seems too short for a name
lookup failure.
Jim
chris wrote:
How about unplugging your dev workstation from the Net and see if the
response time differs?
/Chris
http://cvs.apache.org/~haddadc
-Original Message-
From: [EMAIL PROTECTED]
Hi,
Do you have any example code showing how to use the SAX2EventRecorder
API? We have legacy sax2 deserializers, and this looks like it may make
our lives easier.
Matthew
Hello everyone,
I have a web service which returns a string. I have added security
handlers to the client side and server side and they work and everything
is okay.
I have another service which returns custom types, which work perfectly
fine without handlers. But when using the security handlers
Hi,
We are running a Web Service using Axis. I am now trying to build a
client using C#.
I generated the proxy classes using wsdl.exe sucessfully and can post
requests with the C#-proxy classes and receive a response.
-) If the response is a SOAP Fault an exception with the fault is thrown
Hi all,
I'm using Axis to process incoming XML messages. For this, we have
developped a message service with only one method that takes an array of
Element and returns another array of Element.
The problem is on the client side. A DOM object containing the whole
information is passed and we
munesh wrote:
Hi,
Can someone guide me how i can Serialize java.util.Properties and send
across the wire over SOAP.
Maybe this is naive... why can't you send the .properties file?
Bill de hÓra
Hello,
I try to use the SimpleJMSListener to ue SOAP over JMS. How can I configure services (
server-config.wsdd )?
Thanks for your help.
Thierry
Les informations contenues dans ce message sont confidentielles et peuvent constituer
des informations privilegiees. Si vous n etes pas le
Hello,
I have a webservices in a version.
In the next version, I want to add a field in bean which add an element in
the soap.
If I don't generate again the stubs with the ant task, i get an exception :
[junit] org.xml.sax.SAXException: Invalid element in
com.accor.services.ws.cli
Is it possible to pass javabeans as arguments from soap client to the soap
service without having to
code for custom serializers and de-serializers?
Thanks,
Olivier Lamy [EMAIL PROTECTED] on 28 Oct 2003 12:14
Please respond to [EMAIL PROTECTED]
To:Axis-User [EMAIL PROTECTED]
Subject:
I am having a strange issue with wsdl being generated by java2wsdl. It
seems to honor my requested namespace everywhere except for the first
schema tag in the wsdl:types section. For example, my java2wsdl task
looks like this.
axis-java2wsdl
bindingname=TradeServerSoapBinding
Do you have the custom types registered? Registration is either via
code or WSDD.
/Chris
http://cvs.apache.org/~haddadc
-Original Message-
From: Sunil Iyengar [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 28, 2003 9:10 AM
To: axis-user
Subject: handlers and custom types
Hello
Title: Message
Yes you dont have to write
any code in order for Axis to pass objects conforming to the Java beans
convention.
You do have to provide the serialization
framework configuration information; Specifically, the Java class,
corresponding XML QName, and appropriate
Title: july4.html
When Axis encounters a SOAP element that
does not conform to a corresponding Java object or attribute, a deserialization
error is thrown.
If the consumer or service *USES* the optional element, then the
message exchange will fail. Beans must be regenerated if you
Title: july4.html
IBM
XML Bean framework handles such a scenario. I was not sure about
AXIS.
Thanks
for the info.
-Original Message-From: chris
[mailto:[EMAIL PROTECTED]Sent: Tuesday, October 28, 2003
11:59 AMTo: [EMAIL PROTECTED]Subject: RE: AXIS and
optional changes to
Hi guys,
has anyone experiences with the RMIProvider? Do I just have to run a
RMIRegistry
bind a Service and then...? What then? Deploy as provider=java:RMI
with the bindingname
of the RMIService?
ThX, yours Thomas
Do you have to be in the directory of the wsdd of can you fully qualify
the path
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, October 27, 2003 5:17 PM
To: [EMAIL PROTECTED]
Subject: Re: AdminClient
The command is
java org.apache.axis.utils.admin
Either way. You need to then copy the server-config.wsdd file this
generates into WEB-INF
(In case you are using tomcat.)
Wilson, Allen [EMAIL PROTECTED] on 28 Oct 2003 14:16
Please respond to [EMAIL PROTECTED]
To:[EMAIL PROTECTED]
Subject:RE: AdminClient
Do you have to be in
Hi,
In SOAP 1.1 SOAPAction: is a HTTP Header that corresponds with
soapbind:operation soapAction="...".
How is the functionality of SOAPAction Header element
different in SOAP 1.2?
DoesAXIS support both SOAP 1.1 and SOAP 1.2 and if it
does then what are the guidelines to use SOAPAction
w.r.t.
As is mentioned in the docs, the server-config.wsdd is created as soon
as you do your first deployment thru AdminClient.
Use AdminClient to deploy the SOAPMonitor and then add SOAPMonitor
configuration xml to global configuration of server-config.wsdd...on a
dev't system it seems normal to
server-config.wsdd is the file which gets generated once you run the
AdminClient.
on your wsdd file.
After you code your service java class. Put your classes in the
WEB-INF/classes directory
Then edit your wsdd file to add the service and the allowed methods.
Run the AdminClient on that wsdd
This is done for you when you use java2wsdl...notice the typeMapping
entry (really an exploded beanMapping).
chris wrote:
Yes you dont have to write any code in order for Axis to pass
objects conforming to the Java beans convention.
You do have to provide the serialization framework
Actually it's wsdl2java that generates the correct wsdd files (with
mappings), etc.
The only code you should have to handroll in web services deployment (at
least for me so far...) is the underlying intf/impl that my soap service
is calling. You shouldn't need to handcode wsdl, wsdd, xsd, or
I guess I am just missing the boat because I yet the find the
server-config.wsdd file in the WEB-INF directory. I have the
SOAPMonitorApplet running (I used the command javac -classpath
WEB-INF/lib/axis.jar SOAPMonitorApplet.java) but when it starts it says
that the Monitor is unable to
Bh! All aboard...
You must have deployed at least once via AdminClient or ant task to see
a server-config.wsdd.
Was Tomcat running when you started the SOAPMonitor applet?
Your classpath is [EMAIL PROTECTED] up. Check each entry for path validity.
Axis libraries are delivered in a
As far
as I know, Axis hasn't been modified to support the new treatment of SOAPAction
yet.
However, I think I understand how it's different in SOAP
1.2.
In
SOAP 1.1 you'd have these HTTP headers.
Content-Type: text/xml
SOAPAction: "whatever"
In
SOAP 1.2 you'd have just this HTTP
Hi all,
Does somebody has any good idea about the strategy to adopt for versioning an API exposed as a webservice?
My first idea is to add the version of the WSDL in the target namespace, something like:
urn:v1_0.myservice.mycompany.com
but there might be a nicer solution for that.
Can
Here's the information that is in my paths:
AXIS_HOME=/opt/WWW/tomcat-4.1.18/webapps/axis
export AXIS_HOME
AXIS_LIB=$AXIS_HOME/lib
export AXIS_LIB
AXISCLASSPATH=/opt/WWW/tomcat-4.1.18/webapps/axis/WEB-INF/classes:$AXIS_
LIB/axis.jar:$AXIS_LIB/commons-discovery.jar:$AXIS_LIB/commons-logging.j
I think the problem is you're typing
java org.apache.axis.utils.admin
instead of
java org.apache.axis.utils.Admin
stephen
Wilson, Allen wrote:
Here's the information that is in my paths:
AXIS_HOME=/opt/WWW/tomcat-4.1.18/webapps/axis
export AXIS_HOME
AXIS_LIB=$AXIS_HOME/lib
export AXIS_LIB
Hi,
I know that you can serialize Hashtable without writing your custom
serializers/de-serializers.
Thanks,
Samir
-Original Message-
From: munesh [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 28, 2003 5:20 AM
To: [EMAIL PROTECTED]
Subject: java.util.Properties
Hi,
Can someone
Tried that one also
-Original Message-
From: Stephen Gordon [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 28, 2003 3:29 PM
To: [EMAIL PROTECTED]
Subject: Re: AdminClient
I think the problem is you're typing
java org.apache.axis.utils.admin
instead of
java
Allen,
java -classpath $AXISCLASSPATH org.apache.axis.client.AdminClient
your.wsdd
Make sure you have proper permissions to access the axis jars.
This assumes you are deploying to
http://localhost:8080/axis/servlet/AxisServlet
If you are not deploying to the local machine, you need to use the
Thunder and to anyone else that has sent me a replyfirst let me say
that I appreciate the help that everyone is trying to provide and I
hoped I have not ticked anyone off with my stupidity (to and beyond this
point)...
And believe me if you are in the Dallas area and have provided
help...once
Howdy all
I am trying to deserialize a Axis generated class (and subclasses) of
anxsd conplex type which i have generated with WSDL2java.
I have theserializer working and can serialize the object just to xml
just fine(Thanks to Toshiyuki Kimura's SerializationTester as a
framework to work
Hi Thierry,
The JMS sample includes a server-config.wsdd file which you can
modify to invoke other services. There's nothing JMS-specific in our
service invocation code (see SimpleJMSListener/Worker), so
you should be able to follow the instructions found in the
'Custom Deployment - Introducing
There was an interesting talk at JavaOne (yes I'm ashamed I went) that talked
about this. The proposed idea was to catalog your services in a UDDI registry.
Use dynamic binding to query to UDDI registry for endpoints. Then, as part of
a self-imposed standard, define String getVersion() for each
- Original Message -
From: BLIS Webmaster (Patrick Houbaux) [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, October 28, 2003 1:21 PM
Subject: Strategy for WSDL versioning?
Hi all,
Does somebody has any good idea about the strategy to adopt for versioning
an API exposed as a
Wilson, Allen wrote:
Here's the information that is in my paths:
AXIS_HOME=/opt/WWW/tomcat-4.1.18/webapps/axis
export AXIS_HOME
AXIS_LIB=$AXIS_HOME/lib
export AXIS_LIB
should be export AXIS_LIB=$AXIS_HOME/WEB-INF/lib in your case
Xavier
actually this happened to another guy about a week ago - same problem,
leaving out the WEB-INF.
guess i should have picked it up!!
stephen
Xavier Renard wrote:
Wilson, Allen wrote:
Here's the information that is in my paths:
AXIS_HOME=/opt/WWW/tomcat-4.1.18/webapps/axis
export AXIS_HOME
I am attempting to use JNI from an AXIS service under Tomcat.
Would appreciate any pointers on how to do this.
Thanks
Regards
Vijay
hi!
problem might occur in the serialization and deserialization part by handler
invoke. u can observe the soap serialization message patteren using tcp
monitor. then u can find out, what wrong in the serialization and
deserialization .
hope this 'll help u
regards
vtpavan
- Original
43 matches
Mail list logo