Hi Sandeep,
If you're working from existing Java code, your best approach is to use
Jibx2Wsdl (http://jibx.sourceforge.net/fromcode/jibx2wsdl.html) to
generate a WSDL service description. This also generates JiBX bindings,
so if you want you can continue to work with your existing code using
Does anybody have any clue on this end? It could be vague, but nothing seemed
documented for this.
-Sandeep
From: Sandeep Khurana [mailto:[email protected]]
Sent: Monday, February 22, 2010 2:48 PM
To: [email protected]
Subject: ADB server side
Andreas,
By using just the transport jar would not work ? i am getting an error if i
only use the axis http snapshot jar
java.lang.NoClassDefFoundError: org/apache/axis2/util/OnDemandLogger
at
org.apache.axis2.transport.http.AxisServlet.(AxisServlet.java:89)
at sun.reflect.NativeCo
Hi,
I am using Axis 2.1.5.1 .
In my Axis2.xml configuration, i removed the HTTP (
HTTP/1.1
chunked
Can someone please advice why is this an issue ?
Regards,
Vish
1) Here java.net is to be blamed. They broke several projects by
moving their Maven repository. Apparently they did other bad things
like that in the past (such as replacing an already released artifact
by a different one), so that e.g. the CXF project has chosen to copy
the artifacts they need to
This project is epic.
-Original Message-
From: Nan Null [mailto:[email protected]]
Sent: Monday, March 01, 2010 2:14 PM
To: [email protected]
Subject: Axis 1.5.1 Issues
I had a bad day with Axis. Usually, Apache projects are very high
quality and I don't encounter issues like the
Any idea on what these ports are for? I am unable to justify the use of
these ports to our network team about this. The only port I have configured
directly is 9002.
Thanks!
2010/2/3 Philippe A.
> Hello,
>
> I have configured the Axis2 standalone server to listen on port 9002 only
> (https). Af
I had a bad day with Axis. Usually, Apache projects are very high
quality and I don't encounter issues like these. I hope that the
developers listens and fix it accordingly.
So, let's go to the issue.
1) Building version 1.5.1 doesn't work.
It gave me some weird maven area about missing/invali
Hi,
at this time i make a comparison between axis 1 and 2 and i like to know is
it possible to enable rest support in apache axis 1?
or exists there any modules, tutorials a.s.o. which do this?
thank!
--
View this message in context:
http://old.nabble.com/RESTful-Support-on-Axis-1-1.4-tp277440
Your exceptions will need to use AxisFault (or a class which extends AxisFault)
..otherwise critical diagnostics will be lost
you'll need to engage addressing
If you have engaged addressing, then you must have wsa:action in the required
WS-Addressing header.
implemented in code by
option.s
can you confirm 8443 is the secure port for https only (and not tcp)
once you have decided to use HTTPS (port 8443) then i would suggest engaging
rampart module..here is a quick tutorial
http://wso2.org/library/3190
as mentioned securing a TCP connection uses a different architecture than
st
Chris,
Can you try this with a nightly build and by configuring the transport
receivers as described in [1]?
Andreas
[1] http://people.apache.org/~veithen/axis2/1_6/servlet-transport.html
On Mon, Mar 1, 2010 at 11:29, chu_man_fu wrote:
>
> Thanks for your reply.
> I already have the transport
Hi Balaji,
I am also facing the same issue with Axis2-1.5.1 version. Where in my case
object is of instace Date and it throws the below same exception:, Please
let me know if you have any work around for this issue.
java.lang.NullPointerException
at
org.apache.axis2.databinding.typemappi
-- Forwarded message --
From: Triquoit Mathieu
Date: 2010/3/1
Subject: Axis2 1.4.1, Struts 1.2.9 and Weblogic 8.1. Problem in the
deployment if the application is stressed.
To: [email protected]
Hello,
I have an application which runs under Weblogic 8.1SP3 (Solaris) and it
Thanks for your reply.
I already have the transport tag in my service file. I have takent he
Rampart bit out for now because I don't think it was doing much for me:
tcp
foo.bar.FirstService
In my axis2.xml file I have the following:
Are you saying that scope="soapsession" does not any longer work in
AXIS2 1.5.1?
Josef.Stadelmann
@axa-winterthur.ch
Von: jamie [mailto:[email protected]]
Gesendet: Samstag, 27. Februar 2010 20:25
An: [email protected]; [email protected]
Betreff: Re: Methods Not Called
I confirm - scope="SOAPSESSION" in conjunction with Service Groups
allows to identify the same instance of an object using it's
ServicegroupdID
We uses to map a users-clients-thread to reach always the same
per-session-thread-object which is a place-holder to communicate by IPC
with a per sessi
17 matches
Mail list logo