Hi Ashok,
For the WSDL validation Eclipse WTP has the ability to validate the
WSDL 1.1Please have a look at this
http://wiki.eclipse.org/index.php/WSDL_Validator
and Woden is the option for 2.0 based validation.
Thanks
Lahiru
On 7/23/07, Ashok Kumar Rajendran <[EMAIL PROTECTED] > wrote:
Than
Hi Gail,
I was able to reproduce your issue with tomcat 4.0.3. This should be an
axis2 bug. I think Dims has fixed an issue related to this, So please
get the latest build from trunk and check again. Btw, I reported a JIRA
for tomcat4.0.3 issue. https://issues.apache.org/jira/browse/AXIS2-3014
Petr V. wrote:
> Hi All,
>
> I am having a serious issue when my service is returning objects from
> different namespaces. Let me explain the issue:
>
> 1-I created a service and deployed with Axis 2. Every thing works fine
> except parameters are names as param0 , param1 because my service is
> i
Hi Mark,
In this situation the only option you have is to set the policy in the
Configuration context.
ConfigurationContext configCxt =
serviceClient.getServiceContext().getConfigurationContext();
configCxt.setProperty(RampartMessageData.KEY_RAMPART_POLICY,securityPolicy);
Regards,
Dimuthu.
On
Hi Gail,
What is the Axis2 version you used?
Thanks,
Keith.
On 7/24/07, Gail LaPinsky <[EMAIL PROTECTED]> wrote:
Hello,
I am unable to get the welcome page to display when I deploy the axis2.war
.
I am putting axis2.war in the webapps directory of a Tomcat 4.0.3installation.
Is that too o
I've tried ports 3901, 5001 and 5050. All gave the same result.
robert lazarski <[EMAIL PROTECTED]> wrote: Have you tried changing to another
port in the web.xml?
HTH,
Robert
On 7/24/07, Jack Sprat wrote:
> I've followed the instructions for setting up the SOAP monitor applet here:
> http://
Have you tried changing to another port in the web.xml?
HTH,
Robert
On 7/24/07, Jack Sprat <[EMAIL PROTECTED]> wrote:
I've followed the instructions for setting up the SOAP monitor applet here:
http://ws.apache.org/axis2/1_2/soapmonitor-module.html
Whenever I start my server I get the followin
I've followed the instructions for setting up the SOAP monitor applet here:
http://ws.apache.org/axis2/1_2/soapmonitor-module.html
Whenever I start my server I get the following errors:
2007-07-24 18:18:20,468 ERROR SOAPMonitorService - Unable to open server socket
using port: 5001
2007-07-24 18
Actually I found plenty of low level info on DIME. Check out the
following:
http://msdn.microsoft.com/archive/default.asp?url=/archive/en-us/dnarxml
/html/dimewsattch.asp
http://msdn2.microsoft.com/en-us/library/ms819965.aspx
http://msdn.microsoft.com/msdnmag/issues/02/12/dime/default.aspx#S6
h
2007/7/24, Davanum Srinivas <[EMAIL PROTECTED]>:
Erik,
You are absolutely right!!! we are missing
axis2-ant-plugin-SNAPSHOT.jar from the bin dist. the name changed
after we moved to maven2 based build. I will update the build by
tonight hopefully.
Thanks alot :-)
I actually tried to build axi
Yep.
DIME is fully deprecated by Microsoft now. (It's even hard getting a
good low level description of how it works). It was Microsoft's answer
to SWA (SOAP With Attachments).
Both technologies are obsolete now, and the world has (for better or for
worse) chosen MTOM.
-jeff
-Original Message
Hi,
Done some searching of axis and other lists as well as google searches
and I haven't come up with anything that explained what I am wondering
about. Maybe some kind person will take pity on the confused. :)
I'm posting an xml file containing a soap envelope to a service and I
get back a xml
I configured my WSDL for DIME on the axis side and stubs got generated
fine. But on the .NET client side, WSE2.0 supports DIME but WSE3.0
supports only MTOM - so we need WSE2.0. But WSE2.0 needs Visual Studio
.NET 2003 while we have Visual Studio 2005 - and it seems difficult to
move backto the old
Hi All,
I am having a serious issue when my service is returning objects from different
namespaces. Let me explain the issue:
1-I created a service and deployed with Axis 2. Every thing works fine except
parameters are names as param0 , param1 because my service is implementing
interface.
2-
Hi,
I am getting Null response at C# client (Visual Studio 2005). The Web
Service is
on Axis 1.1. (RAD6)
I am able to see SOAP request and response on the consol at server side
Any help is appreciated.
Thanks,
Srini
-
Boardwalk
Erik,
You are absolutely right!!! we are missing
axis2-ant-plugin-SNAPSHOT.jar from the bin dist. the name changed
after we moved to maven2 based build. I will update the build by
tonight hopefully.
thanks,
dims
On 7/23/07, Erik Bertelsen <[EMAIL PROTECTED]> wrote:
2007/7/20, Deepal Jayasinghe
FWIW, the original bug in this thread has been fixed in latest nightly.
thanks,
dims
On 7/14/07, Chad DeBauch <[EMAIL PROTECTED]> wrote:
Jared...you can just hard code the endpoint and the wsdl instead of having
Axis2 generate it for you. Here's how.
You must make sure that your wsdl is in th
Hello,
I am unable to get the welcome page to display when I deploy the
axis2.war.
I am putting axis2.war in the webapps directory of a Tomcat 4.0.3
installation. Is that too old a version of Tomcat to use with axis2?
The first error I got was a class not found which went away when I took
xml
Thanks Ashok. Woden tries to download the schemas referred to by your WSDL.
You have got this error cause Woden was unable to get the schema online. Its
not a big deal though. Its juat a warning hence it does not effect the
codegenaration process. It fails only on fatal errors.
Thanks,
Keith.
On
Thanks, for the help Dimuthu, but this did not seem to solve the problem.
It seems that since the asynchronous response is being received on a
separate thread, Axis does not have the original ServiceContext; it actually
seems to build everything from the incoming message. It does not tell
Ra
Thanks Jose,
I programatically by-passed the by including the below code. But response on
the
client side it NULL, able to see SOAP request and response on the server side.
Any idea on this Null value at client side?
System.Net.ServicePointManager.ServerCertificateValidationCa
The wsdl and the imported schemas are in the Archive.zip file that was
sent with initial post.
On 7/24/07, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
Please send as the wsdl.
Thank
Deepal
DSL wrote:
> Hello all,
>
> I am getting an error on the wsdl2java generation of my wsdl:
>
> [axis-wsdl
Hi Jonathan,
I also noticed that the ant build seemed to create a directory under my
eclipse area like this:
Repository
|
-- services
|
-- WeatherService.aar
I believe I need to copy that .aar into my tomcat area somewhere ... can
anyone advise?
I always copy the aar file to
$CATALINA_
You will have to update the .NET client to use the new WSDL.
.NET has an easy-to-use utility call wsdl.exe that generates client
stubs for you.
Anne
On 7/23/07, david <[EMAIL PROTECTED]> wrote:
Hello Ann, thanks for the WSDL editor recommendations. I have only one more question
about the WSDL
Hi all,
I have copied the PoJo Weather Sample into my own directory and build it
with ant. I modified the service so that my package is
server.WeatherService and client.WeatherService and the build structure
is located in my Eclipse workspace area. I have attempted to modify the
services.xml fil
Hi guys ...
I got ant working by using ANT_HOME=c:/ap... and JAVA_HOME=c:/Java...
INSTEAD of ANT_HOME=/c/ap... and JAVA_HOME=/c/Java
Something about the way cygwin works. Normally in my cygwin env I use
/c/ for all my paths but because ant was not compiled for cygwin (or
something like that
Georgi Yonchev wrote:
> Thilina Gunarathne wrote:
>
>>> and Deepal, yes works fine, but try it with larger byte[] size,
>>> with larger, in the payload goes array from bytes ?!
>>> not encoded in base64 ..
>>>
>> Not clear what you meant?... Do they go as native binary in the form
>> of a
Thanks a lot, it works !
Just a precision for people who have the same problem : when you implement
onFault, you can get the exception with AxisFault, for example :
msgContext.getResponseMessage().getSOAPBody().getFault().getFaultString()
2007/7/23, cara <[EMAIL PROTECTED]>:
I had the same p
Thilina Gunarathne wrote:
>> and Deepal, yes works fine, but try it with larger byte[] size,
>> with larger, in the payload goes array from bytes ?!
>> not encoded in base64 ..
> Not clear what you meant?... Do they go as native binary in the form
> of an attachment or inside the soap body...
>
> T
and Deepal, yes works fine, but try it with larger byte[] size,
with larger, in the payload goes array from bytes ?!
not encoded in base64 ..
Not clear what you meant?... Do they go as native binary in the form
of an attachment or inside the soap body...
Thanks,
Thilina
Thanks Keith I am really amazed with your efforts . As u mentioned the
environment variable pointed to the old Axis2 1.2 location . I changed the
AXIS2_HOME to point to the latest 1.3 RC2 location and ran wsdl2Java
. Though i got woden warning like
Woden[Warning],0:0,WSDL504,Could not locate the
At the moment we do not have that support but its a trivial thing to do
, so please create a JIRA if the community agree on fixing that I will
fix the for 1.3
Thanks
Deepal
> Hi,
>
> There are functions which share a common
> "library" of data types (classes) and which must be now converted to w
Hello,
Try to use this tool because I think you are having problem with the
accepted format in .net.
http://www.alphaworks.ibm.com/tech/keyman
KeyMan is a tool for managing keys, certificates, certificate revocation
lists (CRLs), and the respective repositories for storing and retrieving
these
Hi,
There are functions which share a common
"library" of data types (classes) and which must be now converted to web
services. When I run java2WSDL for all these services, multiple WSDLs
are generated with the same data types duplicated in all WSDLs. Is there
a way in Java2wsdl , where it can
Deepal jayasinghe wrote:
> Hi Georgi ,
>
> We had that issue in Axis2 1.2 and we have now fixed the issues in Axis2
> 1.3 RC2 [http://ws.apache.org/axis2/download.cgi] please download that
> and see. In the meantime I deploy ur service and invoke it and got the
> following responses.
>
> http://www
Michele
Try these until you upgrade to a later version of Axis2
/etc/sysctl.conf
net.ipv4.ip_local_port_range = 1024 65535
net.ipv4.tcp_fin_timeout = 30
fs.file-max = 2097152
net.ipv4.tcp_tw_recycle = 1
net.ipv4.tcp_tw_reuse = 1
/etc/security/limits.conf
* soft nofile 4096
* hard nofile 65535
Ashok,
I've added the WSDL validation to Axis2 as well. This will be available in
the nightly and also in the 1.3 release.
Thanks,
Keith.
On 7/24/07, keith chapman <[EMAIL PROTECTED]> wrote:
Hi Ashok,
I just downloaded AXIS2 1.3 RC2 and ran wsdl2java on your WSDL with
options -uri and -wv 2,
Glen,
it was clear.
What is now more difficult to achieve, instead, is to handle multiple
MEPs using the same callback since the onComplete() is called n times
(where n is the number of expected responses), while it would be much
better if it was called only once.
Michele
On Mon, 2007-07-23 a
Hi Georgi ,
We had that issue in Axis2 1.2 and we have now fixed the issues in Axis2
1.3 RC2 [http://ws.apache.org/axis2/download.cgi] please download that
and see. In the meantime I deploy ur service and invoke it and got the
following responses.
http://www.w3.org/2003/05/soap-envelope";>
Hi Ashok,
I just downloaded AXIS2 1.3 RC2 and ran wsdl2java on your WSDL with options
-uri and -wv 2, and it worked perfectly. I tested this on both Linux and
windows and on both JDK 1.4 and 1.5. I wonder whether you have an old
AXIS2_HOME. Can you check on this please as I'm not getting any erro
Georgi
You could also try the 1.3 RC2. Its probable this has already been fixed.
http://people.apache.org/~deepal/axis2/1.3-RC2/
Paul
On 7/24/07, Paul Fremantle <[EMAIL PROTECTED]> wrote:
Georgi
Can you change your POJO to use the DataHandler interface?
import javax.activation.DataHandler;
Georgi
Can you change your POJO to use the DataHandler interface?
import javax.activation.DataHandler;
import org.apache.axiom.attachments.ByteArrayDataSource;
DataHandler dh = new DataHandler(new ByteArrayDataSource(bytes));
This might work around the problem.
You should look out for the re
Paul Fremantle wrote:
> Can you post the interface (or the POJO itself) and the services.xml.
> Its not handling the byte[] correctly as a base64binary.
>
> Paul
>
> On 7/24/07, Georgi Yonchev <[EMAIL PROTECTED]> wrote:
>> Paul Fremantle wrote:
>> > George
>> >
>> > Is there any stack trace? How bi
Can you post the interface (or the POJO itself) and the services.xml.
Its not handling the byte[] correctly as a base64binary.
Paul
On 7/24/07, Georgi Yonchev <[EMAIL PROTECTED]> wrote:
Paul Fremantle wrote:
> George
>
> Is there any stack trace? How big is the byte[] before it crashes? Can
> y
Paul Fremantle wrote:
> George
>
> Is there any stack trace? How big is the byte[] before it crashes? Can
> you attach any code you've generated? What kind of databinding are you
> using? Which version of Axis2?
>
> Paul
>
> On 7/24/07, Georgi Yonchev <[EMAIL PROTECTED]> wrote:
>> Hi,
>> i developi
George
Is there any stack trace? How big is the byte[] before it crashes? Can
you attach any code you've generated? What kind of databinding are you
using? Which version of Axis2?
Paul
On 7/24/07, Georgi Yonchev <[EMAIL PROTECTED]> wrote:
Hi,
i developing a web service, based on Axis2,
and the
46 matches
Mail list logo
