On Thu, Mar 11, 2010 at 8:37 PM, Dave Cherkassky wrote:
> Question:
>
> Let's say I have the following in my WSDL:
> type="xs:boolean" />
>
> When I run WSDL2JAVA, I get the following:
> protected boolean localIsSupervisor ;
> protected boolean localIsSupervisorTracker = false ;
> public boo
Hello,
I did finally work it out - so for the benefit of future googlers ...
The following were needed in the log4j.cfg file ...
log4j.rootLogger=INFO, stdout, F
... etc ...
log4j.logger.org.apache.commons=info
log4j.logger.org.apache.axis2=info
log4j.logger.org.apache.axiom=info
#log4j.logger.
Hello,
We've (finally!) connected our client to a SOAP server for the first
time and we are getting thousands of lines of logging similar to ...
2010-03-12 12:01:35,146 [68607 ][pool-6-thread-1] DEBUG Wire wire: >>
"[\r][\n]"
2010-03-12 12:01:35,668 [69129 ][pool-6-thread-1] DEBUG Wire wire: <<
Hey there!
Let's give a try.
Instead of calling 127.0.0.1 specify the DNS of your machine (or computer
name)...
Although I am not having the same problem as you, I also faced a similar
problem and performing this change I was able to get the right IP address of
the client.
Bonne nuit!
On Thu,
Looks like you're .NET WCF Client is using IPv6. 0:0:0:0:0:0:0:1 is the
loopback IP for IPv6, just as 127.0.0.1 is the loopback IP for IPv4.
-Original Message-
From: v2cg4ss [mailto:[email protected]]
Sent: Thursday, March 11, 2010 3:40 PM
To: [email protected]
Subject: Remo
MessageContext msgCtx = MessageContext.getCurrentMessageContext();
if (msgCtx != null)
{
System.out.println(msgCtx.getProperty(MessageContext.REMOTE_ADDR));
}
Works great for a Java client: 127.0.0.1 But for a .NET WCF client I get
0:0:0:0:0:0:0:1
Anyone have any IDEAS
--
View this m
>> [1] - http://axis2m.svn.sourceforge.net/viewvc/axis2m/trunk/axis2m/
>> [2] - http://axis2m.sourceforge.net/axis2m-spring.html
>
> You guys should add junit to your pom as a dependency with scope "test".
Please disregard this. It actually applies to the other project
mentioned in this thread.
On Wed, Mar 10, 2010 at 11:27 PM, Sagara Gunathunga
wrote:
>
> Hi Dave,
>
> As mentioned wsf/spring provides clear idea about how to configure/
> initialize Axis2 using Spring ApplicationContext. If you intent to use
> spring namespace handlers within the ApplicationContext take a look at
> [1]
Hello,
I have a return type for an operation in a wsdl , it can return a choice of
different sequences.
Ex:
operation getNameTypes returns CUSTOMXMLResponse
now in the wsdl schema,
Question:
Let's say I have the following in my WSDL:
When I run WSDL2JAVA, I get the following:
protected boolean localIsSupervisor ;
protected boolean localIsSupervisorTracker = false ;
public boolean getIsSupervisor(){
return localIsSupervisor;
}
public void setIsSupervisor(b
On Thu, Mar 11, 2010 at 2:56 PM, Kim, Ducheol
wrote:
> Thanks Amila.
>
>
>
> It is very helpful for me to keep url.
>
> Actually there is two reasons why I embedded axis2 on my application.
>
>
>
> 1. Keep the wsdl url & SEP.
>
> 2. We don’t’ want to published “Axis2 administration consol
Ducheol:
Here's what we've done:
- simply unzip the entire axis war file on top of your application
- merge axis's web.xml file with your own
- war everything back up together
It seems to be working just fine for us. It might work for you too!
Good luck,
--
Dave Cherkassky
VP of Software Dev
Thanks Amila.
It is very helpful for me to keep url.
Actually there is two reasons why I embedded axis2 on my application.
1. Keep the wsdl url & SEP.
2. We don't' want to published "Axis2 administration console".
Below is solution for 1, but isn't solve 2.
It could be solve it by rema
On Thu, Mar 11, 2010 at 1:29 PM, Kim, Ducheol
wrote:
> Hi there.
>
>
>
> We deploy service using axis. ( Actually we use jBoss WS.)
>
> Sometimes, it raise memory issue, so we are trying to upgrade to axis2.
>
>
>
> Many client already use web service, so we need to upgrade it with backward
> com
Hi there.
We deploy service using axis. ( Actually we use jBoss WS.)
Sometimes, it raise memory issue, so we are trying to upgrade to axis2.
Many client already use web service, so we need to upgrade it with backward
compatible.
I found many articles to make webservice using axis2, but most of
15 matches
Mail list logo