Hi,
we have not tested with openssl 0.9.8h. Theoritically it
should work :)
. Is it possible for you to try with OpenSSL 0.9.8d or
0.9.8e and see
whether the problem exists? Then we can be sure whether the
problem is
openssl or something else and further investigate.
Optionally, you can
Hi,
Have you tried typing http://localhost/axis2/services in the browse?. That
should display the deployed services.
You can run the update_n_run,bat. But please note that in that file the
client talks to the http://localhost:9090/axis2/services/sec_echo. Please
change the port before running
Hi,
Another idea please ?
I'm completely blocked.
Fabien Couvert a écrit :
Fabien Couvert a écrit :
I checked the system classpath and it doesn't containt any jar. Only a
.zip file for quicktime.
Where tomcat can find Jaxb2.0 ?!
here is the error server side :
[ERROR]
Hi,
we had a default configuration for our axis2 webservices and now we
want to put this on a HTTPS configuration. The intention is also to
block the http request.
Because we've found some settings in the axis2.xml:
transportSender name=http
You can use Basic Authentication to make sure that only the right ppl
can access your WSDL file. The tutorial at [1] should give you a better
idea on implementing this. You can also use Apache Rampart if you need a
better security mechanism. A good tutorial on Rampart can be found at
[2].
1 -
Morning, everybody!
I recently tried to deploy the WAR distribution of Axis2 1.4 to a Websphere 6.0
AppServer running on J2RE 1.4.2.
Shortly after accessing axis2 I noticed several entries in the node's trace.log:
[07/07/08 16:52:44:984 CEST] 002d ServletWrappe E SRVE0100E: Did not
2008/7/7 Virtual Light [EMAIL PROTECTED]:
Docs for wsimport
http://www.sws.bfh.ch/~fischli/kurse/ead/jws/jaxws-2.0-doc/wsimport.html
wsimport seems to produce quite nice code, but I have a question.
wsdl2java also produces metadata like services.xml for your services
based on the WSDL, but
hi,
I was using Axis 1 to make my webservices but now I'm trying Axis 2, and I
don't know how to manage my errors, for sample I was using AxisFault
exception in Axis 1 to answer that I couldn't execute normally the service,
and instead of sending a normal xml response I was answering :
Code:
Hi David,
There is a sample included in Axis2 binary distribution which
demonstrates fault handling. You can find it in
AXIS2_HOME\samples\faulthandling (AXIS2_HOME is the directoiry where you
unzipped axis2 binary distro)
regards
Charitha
http://charithaka.blogspot.com
David wrote:
hi,
Thx, I missed it, I'm sorry.
Well I think I have all I need even if the sample appear to be very complete
comparing to my small need...
I will come back if I have problems during implementation.
regards
David
On Tue, Jul 8, 2008 at 1:32 PM, Charitha Kankanamge [EMAIL PROTECTED]
wrote:
Hi
Hello Chris,
If you are not using JAX-WS (and as you are using a 1.4.2 jre you aren't)
then you can eliminate the errors editing your axis2.xml file to remove
the following:
threadContextMigrators
threadContextMigrator listId=JAXWS-ThreadContextMigrator-List
Hi Guys,
Am facing a very peculiar problem while trying to set HTTP headers from
axis2 1.3api.
Setting some HTTP headers works while others do not. The following two
work like a charm,
_serviceClient.getOptions().setProperty(org.apache.axis2.transport.http.
HTTPConstants.HTTP_PROTOCOL_VERSION,
Hi,
I have generated the client using the wsdl2java tool. Unfortanately,
I'm having problems. The soap message generated by the tool corresponds
to the previous one:
?xml version='1.0' encoding='utf-8'?
soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
soapenv:Body
Hmmm,
I guess I'm already one step closer :).
Do I also need to define the transportreceiver for HTTPS? I've read
something about configure the services.xml with the following stuff:
transports
transporthttps/transport
/transports
So that you only have the https transport. But if I do
Can you look the request you send and the response you received using the
tcp mon. and send us?
thanks,
Amila.
On Tue, Jul 8, 2008 at 2:07 AM, Jake Goulding [EMAIL PROTECTED] wrote:
Apologies, but the XML should say:
tree xmlns=urn:/vivisimo/types
I attached an earlier version, before I
Amila:
Thank you for your response. I have attached the output of the
transaction from Wireshark, hopefully it has the equivalent data that
tcp mon would have. I have also attached the raw wireshark data.
To be clear, I have narrowed down this case from a more complicated
schema / soap
Hi all,
I followed Brian's advice (thank you!) and removed all references to
jaxws-classes in the 1.4 axis2 configuration file.
Axis2 1.4 starts up file and I am able to navigate through the web interface.
But now I am encountering another exception shortly after uploading my service:
In my case I have tried the option WSDL2Java and I have obtained the same
error An error occurred while
completing process -java.lang.reflect.InvocationTargetException. To use
WSDL2Java I have followed the web page:
http://ws.apache.org/axis2/tools/1_2/eclipse/wsdl2java-plugin.html.
I have
I've generated some java code using Axis and some wsdl and I'm having
trouble that I'm sure is in the client side. I'll try to make this
brief to see if any body has pointers, but I'm trying to serialize a
simple java.lang.String object that Axis is somehow mis-typing as an
xsi:guid.
Phil
I'm not an Axis1 expert, so I can't actually help you. But reading
your note I can tell that there isn't enough information for someone
to help you. You need to post some information on how you created the
client, or even better post the client code.
Paul
On Wed, Jul 9, 2008 at 4:29 AM,
This article on REST invocation might be helpful:
http://wso2.org/library/175
For JAX-WS, I believe the main difference here is that you use Sun's tools
to do the code generation, not Axis2's; if you use JAX-WS, then by default
you are also using JAXB to do the XML binding. More documentation
21 matches
Mail list logo
