yes you can but , wt you have to write is a MessageReciver. You can
write your own message receiver to handle any custom type , so that will
finally become your se/de.
SOA Work wrote:
>Is it possible to write custom serializers or deserializers for axis2? Like in
>axis?
>So that I can use all c
Hi Trevor ;
We dont have Attchement support yet , but it will be there soon :) , but
you can use MTOM and I think that will be a good candidate.
trevor paterson (RI) wrote:
>Thanks
>
>Returning an OMElement is good enough for now - but if I have a very big
>return document it would be nice to z
Title: Deploying Web Services in axis - Custom Deployment
Hi,
I'm trying to deploy a Web Service (Java) in Axis 1.2 using the Custom Deployment method. I have placed the Web Service class in the - /webapps/axis/WEB-INF/classes// folder structure and have placed the corresponding WSDD file a
What is the Mail jar you are using... There is a known problem with
sun's mail jar not being able to decode the content-id generated by
Axis2..
Please try switching to Gerenimo mail & Activation jars if you are
using Sun's impl's...
In the mean time I'll try to get our code working with Sun's imp
I have a small app that uses xmlbean parser and works fine , I wanted to make this a web service that takes an XML as string and deploy it throuh AXIS1.3 . here is my test service public class HelloServer { public String sayHello(String str){ try{ ClientReqDoc doc
Hello Dies,
I got this to work finally. After a decent nights rest I fould a
problem in my "clean" script. I had an extraneous Family.class
file.
Although I used the "--implClass FamilyImpl" argument, for
some reason there was a conflict with that old Family.class file.
I deleted it, recompil
Have a look at this:
Give him This:
_original type def from imported xsd___
_also needed in wsdl file___
type="ns:InvalidDateException"/>
*(in the portType operation definition for a method throwing a fault)*
message="ns:InvalidDateExceptio
Hello All,I am trying implement JDM (JSR-73) Webservices using AXIS 1.3 and have some questions. When i deploy the war containing the webservice and try to view the wsdl using the ?wsdl feature of AXIS, i get an error saying "Bean attribute is of type java.lang.String, which is not a simple type",
Sorry,
I may have simplified the example a bit to much.
On the SOAP communication between B and C in the before mentioned
example, I want to attach SAML headers to the soap message. I'm using
wss4j to achieve this. The problem is however, to configure the
deployment descriptor for the B web se
Rick,
My build hierarchy is something like this:
./src/disney/dis/family
My Family.java and FamilyImpl.java files reside there.
But these files are defined in a Java package disney.dis.family.
So, running the WSDL2Java command in question from this directory
creates the generated files "unde
Hello Anne,
Yes, I compiled both the interface and the implementation file
with -g flag.
Below is the scenario I ran just now. The Java2WSDL execution
produced a family.wsdl file, but the WSDL file still contains
the default "in0", etc. parameter names.
$ javac -version
javac 1.5.0_06
$
$
See, I'm not really sure. The JAX/RPC spec is kinda hazy on how
exceptions are handled, and how the soap fault maps to an exception.
Here's what I'm seeing come back from the server:
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmln
Hello
I need help on the
following problem. I was using axis 1.1 and we are in front of a change in the
wsdl2java generated code.
We have lots of xsd
simple types with string base class and a pattern facet.
With axis 1.1 we had a
java class generated for this purpose.
With axis 1.3 w
Hmmm. Check your SOAP messae. Our problem is that we're sending the
correct data from the server and the error happens during
deserialization. If that's not it, it's a different problem.
Jack Lund wrote:
Thanks! I'd love to hear the workaround - I've tried everything I can.
It looks like the
Ken Campbell wrote:
> Hi Chinthaka,
>
> Now that I understand the problem I just need to refactor my services.
> However, I am a bit confused when you say that you refactored om *after*
> 0.95. Does this mean the refactoring is now *in* 0.95, or does it mean it
> will be in 0.96?
It will be in 0
Thanks! I'd love to hear the workaround - I've tried everything I can.
It looks like the problem is that the server side doesn't really know
how to serialize the exception, even though it should.
-Jack
Thom Hehl wrote:
We had EXACTLY the same problem! We just found it and found a
work-around
Hi,
Not a problem at all. I have done this before. The method in the implementation
class of B just uses the client API to invoke the Web Services on C and A. They
can even be the same Web Service. It's the URL's that are different. Make sure
you call using the correct URL.
Roslan Amir
Quoting K
I deployed the document/literal webserivce in JBOSS
4.0.4RC1 using Axis 1.3. I generated the server/client
from the hand written WSDL. When I'm trying to access from
the client I'm getting the following error. It seems a
common problem when using document/literal. Could any of
you guide me to
Found a solution :
I use a destructor in my web services class : this constructor call the
cleanUpFolders() method described previously.
I imagine that once service execution was done, TOMCAT or AXIS (or whatever)
will destroy the webservice instance : and it seems to work.
After 5 web services
Hi,
I'm using Axis 1.3, and I have a question on how to configure my server.
The setup I want to use Axis to implement is the following two scenarios:
(B is the process that uses Axis)
1)
A sends a message to B,
B forwards the call via Axis using SOAP to C.
2)
C sends a message to B,
B forwards
Did you compile the implClass with debug?On 3/30/06, Rhimbo <[EMAIL PROTECTED]> wrote:
Dies,Ah, sorry to be bothersome... I tried --implClass and it doesn'twork. I also tried -i and it didn't work.I then tried using all "--" long arg names or all "-" short argnames. Nothing worked.
Maybe I should
It's possible that WebSphere is rejecting the invalid URIs. Would you try replacing your current namespace URIs with valid URIs and seeing if you experience the same problem?If not, please send me the WSDL privately, and I'll see if I can figure out what's wrong.
On 3/30/06, Jarmo Doc <[EMAIL PROTE
Hi Anne, I'm not able (allowed) to post the complete WSDL online. I could
email it to a trusted party (for example, to you) but I realize that that's
probably asking too much of you, and goes against the general compact of
newsgroups and this forum.
From: "Anne Thomas Manes" <[EMAIL PROTECT
Hello.
I've been working on this all morning and I'm just not solving this!
I apologise, I know this must have been asked before but none of the
discussions I found solved my problem.
What I'm trying to do is generate a WSDL file from my Java source code. I want
one of the parameters to a meth
When using RPC style, your message parts must reference types rather than elements.AnneOn 3/30/06, Ameet Hasmucrai Amarchande <
[EMAIL PROTECTED]> wrote:Hi Ken,That's what I thought. But when I changed it to "rpc", it gave this error when I was trying to generate the classes:
--
Please provide the complete WSDL so that we can help you identify the problem.On 3/30/06, Jarmo Doc <[EMAIL PROTECTED]
> wrote:Hi Anne, my apologies -- that's one thing that I left out of my original
post. It's hard to separate the wheat from the chaff with WSDL (or moreappropriately with my level
There are other problems with this WSDL besides the wrong qnames in your message parts. (Note that they aren't unqualified because there is a default namespace (the wsdl namespace); but these elements are in the xsd1 namespace.)
When using RPC style, your message parts must reference types, not el
Hi Chinthaka,
Now that I understand the problem I just need to refactor my services.
However, I am a bit confused when you say that you refactored om *after*
0.95. Does this mean the refactoring is now *in* 0.95, or does it mean it
will be in 0.96?
The Eclipse Axis code generator (which I downlo
Hi Anne, my apologies -- that's one thing that I left out of my original
post. It's hard to separate the wheat from the chaff with WSDL (or more
appropriately with my level of knowledge of WSDL).
My 1st schema does indeed have and my 2nd schema
does have . So, I'm stumped.
Note that my na
It's not the WSDL that's wrong, it's the schema. You must add an after line 03. In order to reference an element or type from another namespace, you must both declare the namespace and import it. (I'm assuming that you purposefully left out a bunch of namespace declarations in the element to sav
On 3/30/06, Rhimbo <[EMAIL PROTECTED]> wrote:
> How do I prevent WSDL2Java from overwriting my interface file?
> This command overwrites my Family.java file.
>
> I know I can specify
>-o .
>
> as an option and WSDL2Java will create a disney/dis/family
> hierarchy underneath my current dire
Can you recommend an easily-downloadable validator? The WSDL's not publicly
available so web-sites that offer to validate based upon a URL won't work
for me.
I've run the WSDL through various XML validators and they all report fine.
I don't have a WSDL validator though and haven't been able
We had EXACTLY the same problem! We just found it and found a
work-around, but believe this to be a bug in AXIS that should be fixed.
The guy on our team that found it was going to write something up for
the list. I'll ask him to step this up a bit as it would be of benefit
to you.
Jack Lund
Hi Ken,
Soon after Axis2 0.95 release I did a package name refactoring in OM. So
you will not able to use the latest om with Axis2 0.95.
But if you are only using the jars came with the release, you wouldn't
have got this issue.
Are you saying that you are getting errors even when using the jars
Hi Chinthaka,
I found the solution today: the problems only came about when I dropped a
service into axis2.
I downloaded the axis2 source from http://svn.apache.org/repos/asf to try
and track the problem and discovered that none of that source will build
largely because it uses org.apache.axis2.o
I created WSCOMMONS-5.
tcpmon is not selectable as component in JIRA yet so i chose Utilities.
Best regards
Franz
Ajith Ranabahu schrieb:
Hi Franz,
I was not aware of the bugs that you've posted, I would have tried
fixing it!. BTW I think it is better if you can post a commons Jira so
tha
POST /wstest/NetWebService/SampleService HTTP/1.1
Host: localhost
Content-Type: text/xml; charset=utf-8
Content-Length: length
SOAPAction: "http://tempuri.org/max"
encoding="utf-8"?>
http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema
" xmlns:soap="http://sch
Hello,
I have recently created some web services using TOMCAT 5.5 and AXIS 1.3. The aim
of those web services is to compute some data and to generate ZIP files. Those
ZIP files are returned to client each time he calls the web service.
The thing is that those ZIP files have to be removed from the
Hi Franz,
I was not aware of the bugs that you've posted, I would have tried
fixing it!. BTW I think it is better if you can post a commons Jira so
that the issue is reported in the right place.
Ajith
On 3/30/06, Franz Fehringer <[EMAIL PROTECTED]> wrote:
> I checked and tcpmon still suffers fro
I can now directly provoke, what I said yesterday: WSDL2Java running
smoothly, but the generated coded in an uncompilable state!
To reproduce, take the "Axis2SampleDocLit.wsdl" from the 0.95
distribution, make the error like I did in my own WSDL by removing the
qualification from the message-elem
Thanks
Returning an OMElement is good enough for now - but if I have a very big return
document it would be nice to zip up and transport as a binary attachment - I
can't find any clues how I specify use of SOAP attachments in axis 2 service
deployment.
trevor
-Original Message-
From:
Hello Martin,
I'm glad to hear you found the cause of the error.
Please do not hesitate to open a JIRA bug with your suggestion and a patch.
Regards,
Dies
Martin Atkins wrote:
Dies Koper wrote:
Hello Martin,
Judging from your stacktrace the NPE occurs in the following line:
URL[] u
Dies Koper wrote:
Hello Martin,
Judging from your stacktrace the NPE occurs in the following line:
URL[] urls = new URL[names.length];
"names" is an array of strings that should contain the path entries in
your classpath. I do not know under what circumstances it could be null,
but y
Hi Ken,
That's what I thought. But when I changed it to "rpc", it gave this error when
I was trying to generate the classes:
--
Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.Runtim
I checked and tcpmon still suffers from AXIS-2373 (resend does not
work).
The fix i attached to AXIS-2373 is really simple (although it is
possible in principle that behaviour differs among platforms and JREs).
Can some Axis(2) developer have a look at it?
Should i file a ws-commons issue?
Gre
hi all,
Today I generated a webservice with axis1.3, it was published
successfully, but when I use Eclipse to generated the test client with
JSP, It threw out the Exception "No Such Operation messageDTO1", but
here "messageDTO1" is a element in my wsdl document(see below
content).
I know the situa
Thanks,
I`ll give it a try.
Franz
Ajith Ranabahu schrieb:
Hi Franz,
The TCPMon releases were uploaded to Apache dist but the site is still
not there due to a build problem in the commons base site.
http://www.apache.org/dist/ws/commons/tcpmon/1_0/
I can upload the site but it'll not sho
Hi
I managed to find the reason why polish characters
(with tails) looks so strange in the SOAPEnvelope. The thing is that they are
replaced by numeric character references (NCR) which are defined as &#
; . When I create my DOM Element and
put it on my screen I can see polish characters,
Hi Franz,
The TCPMon releases were uploaded to Apache dist but the site is still
not there due to a build problem in the commons base site.
http://www.apache.org/dist/ws/commons/tcpmon/1_0/
I can upload the site but it'll not show up in the base site! I've not
sent in the release notes yet.
Ajit
49 matches
Mail list logo
