Hi,
Is there an option to start axis2server.sh in a different port than 8080.
The '-p' (-p9090) option doesn't work with current axis2server.sh.
(As a workaround I manged to do it with editing axis2.xml)
regards,
Kasun.
Hi Andreas,
I did see that is fixed in 1.6, unfortunately i am on 1.5.1 and for me to
move to 1.6 is very difficult. Would be great if you could point me to code
that i can merge with 1.5.l and fix this issue ?
Thanks,
Vish
On Fri, Apr 23, 2010 at 1:34 PM, Andreas Veithen
wrote:
> See AXIS2-3
I solved it - just in case another poor soul makes the same mistake I did -
the env.setNamespace(ns) below is not necessary and it causes the issue.
Demetris wrote:
I gave up using the POJO method for generating the outgoing SOAP
message as it does
not seem to work. I am able to generate a cor
I gave up using the POJO method for generating the outgoing SOAP message
as it does
not seem to work. I am able to generate a correct SOAP envelope using
the SOAPFactory
etc explicitly. However, I get the following:
org.apache.axis2.AxisFault: Unknown SOAP Version. Current Axis handles
only SO
You are right it is present in the classpath - so I can remove it and
instead include the commons-logging
jars in the classpath?
Andreas Veithen wrote:
Axis2 uses commons-logging. If log4j is present in the classpath, it
takes precedence over java.util.logging and you must supply a
log4j.prop
I gave up using the POJO method for generating the outgoing SOAP message
as it does
not seem to work. I am able to generate a correct SOAP envelope using
the SOAPFactory
etc explicitly. However, I get the following:
org.apache.axis2.AxisFault: Unknown SOAP Version. Current Axis handles
only
Got it - thanks.
Andreas Veithen wrote:
Axis2 uses commons-logging. If log4j is present in the classpath, it
takes precedence over java.util.logging and you must supply a
log4j.properties file.
Andreas
On Fri, Apr 23, 2010 at 22:32, Demetris wrote:
And I am also getting the following:
lo
Axis2 uses commons-logging. If log4j is present in the classpath, it
takes precedence over java.util.logging and you must supply a
log4j.properties file.
Andreas
On Fri, Apr 23, 2010 at 22:32, Demetris wrote:
>
> And I am also getting the following:
> log4j:WARN No appenders could be found for l
See AXIS2-3851.
Andreas
On Fri, Apr 23, 2010 at 08:57, Vishwal Shah wrote:
> Hi,
> I am trying to generate Stubs for Standalone schema using Axis2 XSD2Java ,
> My Schema does not have a Target Namespace. I get the below error
>
> [echo] Generating code ...
> [java] Exception in thread
And I am also getting the following:
log4j:WARN No appenders could be found for logger
(org.apache.axis2.util.Loader).
log4j:WARN Please initialize the log4j system properly.
The actual client code does not include expilicit calls to the Logger -
does the axis2
baseline need it to be initial
This is an automated response, please do not reply.
Your e-mail message - Re: RE: infinite timeout for WS request has been
successfully delivered.
I will be out of the office starting 04/24/2010 and will not return until
05/03/2010.
I will respond to your message when I return.
Thanks & Reg
First, I think (and I hope others would agree) that it is a bad idea to
use an "infinite" timeout on a web service. Any service that is taking
"forever" to respond is broken (IMO).
If you make your service client's timeout infinite, how do you know when
it failed? Also, you would have to wr
Vish:
I don't have a solution, but I want to confirm that it's not just you.
I ran into the exact same behaviour about 2 months ago. At the end I just gave
up and added a namespace.
Hopefully you'll succeed in figuring it out. Good luck,
--
Dave Cherkassky
VP of Software Development
DJiN
jaxws-guide which will address how to deploy jaxws web-service the snippet
states:
JAX-WS provides the wsgen and wsimport
command-line tools for generating portable artifacts for
JAX-WS Web services. When creating JAX-WS Web services, you
can start with either a WSDL file or an
Please vote for AXIS2-4611 ;-)
Andreas
On Fri, Apr 23, 2010 at 16:23, Dan H wrote:
> I'm trying to deploy a JAX-WS Web Service that uses Hibernate, so I have to
> set the "ServiceTCCL" parameter to "composite". Otherwise the thread context
> classloader can't find org.hibernate.hql.ast.HqlToken.
I'm trying to deploy a JAX-WS Web Service that uses Hibernate, so I have
to set the "ServiceTCCL" parameter to "composite". Otherwise the thread
context classloader can't find org.hibernate.hql.ast.HqlToken.
(unverified if setting ServiceTCCL will actually fix it but it's worth a
try)
It appears t
16 matches
Mail list logo
