hi anil,
Other than for a data binding framework for MTOM, most of the things
are done. There is a sample in the modules/samples/mtom if u wanna
have a look. Axis 2 also provides SwA support...
We have already informed the respective parties about the bugs.
regards,
~Thilina
On 7/19/05, John,
Last week Axis2 MTOM WSE3.0 July CTP succesfully interop for a
simple sample. There were few issues in earlier CTP's with respect to
MIME handling, which they have corrected in the July CTP.
~Thilina
. WS-I has recommended MIME. Is DIME popular among
the vendors other than Microsoft? Does SOAP/WebServices vendors (other than
Microsoft) supports DIME?
For SOAP v1.2, MTOM will be the standard for attachment.
Will MTOM replace MIME and DIME in SOAP 1.2?
thanks,
Naresh
From: Thilina
.
People have to wait for some time till Axis2 gets it's ws-policy
implementation up, to expect Axis2 to be this Smart ;-)
~Thilina
Thanks for any additional insight.
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 26, 2005 9:20 PM
Did u put the wsdl in to the .aar archive. make sure to put is as service.wsdl...On 8/8/05, Anthoni Tom
[EMAIL PROTECTED] wrote:
Hello,
I'm deploying an Axis2 webservice on tomcat. It is
visible in the list 'available services', but I can't reach
my wsdl on the server. When I
Hi Chris,
Fixed the issue...Pls check out the latest svn and try it..
Thanks Regards,
~ThilinaOn 8/9/05, MacKenzie, Christopher C [EMAIL PROTECTED] wrote:
I have run into a problem when using the latest axis2 source implementingthe mtomSample service. I was previously able to run the MTOM
I can't run the build still.. I have a commit wating to do
:((
~ThilinaOn 8/24/05, Eran Chinthaka [EMAIL PROTECTED] wrote:
Hi,
Today I installed maven 1.1-beta-1 and got some errors with the build,
saying can't upload jars. The fix to this was to update to the new
maven
You can also have a look at Axis2 project. Axis2 isbased onStAX parsing and Axis2 supports MTOM.
~Thilina
On 8/26/05, Guy Rixon [EMAIL PROTECTED] wrote:
On Thu, 25 Aug 2005, Scott Goldstein wrote: Does Axis support other SOA protocols besides SOAP over HTTP?
I have an application in which I'm
Hi,
I cannot understand whether this message is a SOAP with Attachements
message or a MTOM message.. Anyway MTOM *spec* does not support the
Content Location based referencing of MIME messages. So that I assume
this is a SwA message.. (Even for SwA *Axis2* does not support the
Content-Location
Also I don't see any point in returning a MIME based message (MTOM or
SwA) in the above mentioned case. This does not contain a binary
attachment. Using of the MIME envelope is a waste of resouces...
This message can be delivered in a plain SOAP envelope without any trouble.On 9/21/05, Thilina
, Thilina Gunarathne [EMAIL PROTECTED] wrote: There's a unlinked mail-transport guide at
http://ws.apache.org/axis2/mail-transport.html. http://ws.apache.org/axis2/mail-configuration.html
I don't know why this is not linked. :( ~Thilina On 9/30/05, vikas kumar [EMAIL PROTECTED] wrote:
Hello everyone
If you are planingto go with the first option, (MTOM with Axis2) then there is a MTOM/image transfer sample in the Samples module. You will be able to grab few tips from it.
Regards,
~Thilina
On 10/11/05, Eran Chinthaka [EMAIL PROTECTED] wrote:
Nice scenario.You have couple of ways to do this.1.
Here's the error...
resultfloat.serializeWithCache((OMOutput) XMLOutputFactory.newInstance().createXMLStreamWriter(writer1));
createXMLStreamWriter returns a XMLStreamWriter... You cannot cast it to am OMOutput. You can construct an OMOutput giving a XMLStreamWriter instance.
BTW lot of things
This is well answered in the followingthread in the dev list. An issue caused due tocross posting..
http://www.opensubscriber.com/message/axis-dev@ws.apache.org/2642402.html
~Thilina
On 11/24/05, Ajith Ranabahu [EMAIL PROTECTED]
wrote:
hi all, Well I'm not sure why nobody seems to answer
Hi,
According to whatI know (Correct me if I'm wrong), Axis2 still does not support WSDL generation.
Inorder to get the wsdl in http://.../myservice?wsdl you have to provide your own wsdl inside the aar file...
If you have the WSDL file corresponding to the Web service, rename it to
Answering your last question...
MTOM sample service can accept SOAP 1.1 and SOAP 1.2 requests.Even though MTOM came with SOAP1.2 and has a close resemblance, there aren't anymention in the spec restricting the use of MTOM with SOAP 1.1
.
Axis2 supports MTOM with SOAP1.1 SOAP1.2 both.
I'm not
It's possible You can use MessageContext injection for that. This is the standard mechanism provided by Axis2 to access MessageContext from service impl's
public void init(MessageContext msgcts) { this.msgcts = msgcts; }
Hope you have already given a look at http://ws.apache.org/axis2/0_94/mtom-guide.html
~Thilina
On 2/28/06, Anne Thomas Manes [EMAIL PROTECTED] wrote:
[same answer I posted on the JAX-WS list]
Florian,There are three choices for attachment protocols:- WS-Attachments over DIME (DIME)- SOAP with
Hi Brian,
See my comments below...
On 3/12/06, Brian Shields [EMAIL PROTECTED] wrote:
Hi all,I am having some trouble sending attachments with axis2 messages. Untilnow I have been sending a large xml string as a parameter of a web
service call. I recently applied security to this and I am getting
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
There was a proposal to improve Data binding for MTOM using ADB.. I
hope it's already implemented in the svn head..
Also Dennis is working on JIBX data binding with MTOM for Axis2...
On 4/7/06, gt1502 [EMAIL PROTECTED] wrote:
2)
In axis 1.x, when I used multipart/related in the binding section
Axis2 MTOM interoperated well with WSE3.0 and WCF.. We did a
succesfull demo at SDWEST-2006 using WSE3.0. We did well with WCF at
the March interop plug fest..
~Thilina
On 4/10/06, Florian Rengers [EMAIL PROTECTED] wrote:
Thanks Bob,
did you definitive reached the MTOM encoded communication
Give it a try with ADB.. ADB has improved efficient support for MTOM..
~Thilina
On 5/2/06, robert lazarski [EMAIL PROTECTED] wrote:
Have you tried defining your complex type like in this example?
http://marc.theaimsgroup.com/?l=axis-userm=114123711724485w=2HTH,Robert
I have fixed the SOAP version issue+ a potential content type issue recently.
Are you using Sun's impl of Java Mail?
Please try with the latest svn heads.. Even the latest Axis2 RC + Axiom RCwould be fine..
~Thilina
On 5/2/06, Stefan Vladov [EMAIL PROTECTED] wrote:
Hi guys,This is probably a
Axis 2 is tested and proven interoprability with .net.
Have a look at the following news item. I was lucky enough to experience it first hand at the interop plug-fest.
http://www.wso2.com/about/news/microsoftinterop/
Except for very few extreme cases WCF and Axis2 demonstrated very good
At first look seems there's a problem with the image utility
classes.. It's better to use the FileDataSource in any case,
since it's the most generic one and it'll make sure to send what ever
the bytes in your original file...
~ThilinaOn 5/10/06, Patric Fornasier [EMAIL PROTECTED] wrote:
Hi,I've
Have you tried with Axis2 1.0.. I fixed a content type issue lately,
but wasn't able to check whether it'll solve the Java Mail issue...
Gerenimo java Mail Sun's Java mail are different implementations
of Java Mail spec. We can't use Sun's Java mail through Maven
repositories due to licensing
May be i can give you a helping handif youu post the generated skeleton as well... I'm not sure wat's the param0. I'm not that familiar with data bounded MTOM skeletons :(...
Problem seems that you are not getting hold of thecorrect textNode with binary data.. Looking at the exception you are
Hi,
I can suggested three ways to access the binary content according to my choice priority.
1. I don't have a much of a knowledge in Data Bounded code. But if the data binding is properly handled for MTOM then there should be a getter for a Data Handler or a Byte[] in your
Aaaha.
Nice finding... Any comments from SOAP1.2 specialists...
Anyway this content type needs to be fixed...
Please log a Jira...
~Thilina
Content-Type: multipart/related;boundary=MIMEBoundaryurn_uuid_26C55753A5E981E64A11479668765601;type=application/xop+xml;
start=0.urn:uuid:[EMAIL
on the server side).
Any ideas? Thanks - really appreciate your help... :)Kind regards,Timo-Original Message-From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]]Sent: 19 May 2006 09:20
To: axis-user@ws.apache.orgSubject: Re: [Axis2] Vanishing MTOM attachmentsYou need to build the elements if you
I'm *not* in touch with the code base :)
-Original Message-
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]] Sent: 19 May 2006 12:50 To: axis-user@ws.apache.org Subject: Re: [Axis2] Vanishing MTOM attachments
Hi, See my comments below Thanks a lot for the response. :) WC..public OMElement mediaTransformation(OMElement element
See my comments below...
On 5/22/06, Laurent CELLA [EMAIL PROTECTED] wrote:
This sample is supposed to return us an instance of class Attachmentslinking to attachments retrieved on mime.
The result is null.When i log the OMElement received by the method, it looks like it is theMTOM way( my
//image/echoImage/soapenv:Body/soapenv:Envelope--MIMEBoundaryurn_uuid_19E43A1912FEAF555111483041641261content-type: image/jpegcontent-transfer-encoding: binary
content-id: 1.urn:uuid:[EMAIL PROTECTED]ÿØÿà
Didn't you had a trailing boundary after this in your message...? Also try using
Moving the conversation over to Axis2-dev list...Please post your replies to dev list..
Hi Laurent and devs,
Currently [1],[2]are the intended behavior. Do you have a use case which makes it mandatory to send the base64 as an attachment, without embedding in the SOAP message...
I'm not sure
Can you post the message snaphots from TCPMON and the exact stack trace .net gave...
Thanks,
~Thilina
On 6/6/06, Jim Collins [EMAIL PROTECTED] wrote:
Hi all,
I have a simple web service for uploading and downloading files that is MTOM enabled. I have used it with no problems from a Java client
the operation and the return object that is null.
Regards
Jim
- Original Message -
From: Thilina Gunarathne
To: axis-user@ws.apache.org
Sent: Tuesday, June 06, 2006 3:15 AM
Subject: Re: Axis2 .NETproblem
Can you post the message snaphots from TCPMON and the exact stack trace .net
Hi,
MTOM sample is designer to work in the OM level.. It takes OMElement as
input and returns OMElement... That's why it uses the
RawXmlMessageReciever.. This will not generate a usable WSDL , but you
should be able to code generate for the given WSDL.. Notice the
following..
xs:element
Hi,
I couldn't detect any probs in your code at the first glance..
Try sending some file other than XML.. I'm just getting the feeling that it might be a bug inAxis2.
If it works then try avoiding the returning of the same file from the server...
Please let us know the progress
Thanks,
+1 indeed..
Its an urgent requirement.. I've seen so many people getting in to trouble with MTOM+WSDL.
One more thing I would like you to consider is writing and packing a WSDL for the MTOM sample :).
Thanks,
~Thilina
On 6/15/06, Eran Chinthaka [EMAIL PROTECTED] wrote:
robert lazarski wrote:
Yes.. You can use MTOM with RawXMLInOutMessageReciever.
I'm not sure about the parameters to use WSDL2Java.IIRC it's possible to generate OM level (RawXML) code using WSDL2Java.
If your WSDL us simply you might be ableto survive without using WSDL2Java.
~Thilina
On 6/16/06, Andrew B [EMAIL
Hi,
You should be able to secure MTOM messages using (engaging andconfiguring) Rampart but you will have to specify the optimizeParts
configuration to MTOM optimize the base64 content after securityprocessing.Note that the original MTOM attachments will appear as base64 text inplace of the
Hi,
Code seems to be corect at firstglance
Can you post the full error trace and the message snapshots...
~Thilina
On 6/30/06, Andrew B [EMAIL PROTECTED] wrote:
Hi,I have a client that needs to get an MTOM attachment as a byte array. The code I came up with is as follows: OMElement
See my comments inline..
On 7/6/06, Tech Savvy [EMAIL PROTECTED] wrote:
Hi,Have two question regarding to MTOM:1. The sample in the guide is using AXIS2 api to code the webservice and client, e.g. OMElements. In such case a wsdl is not present so this is tied to AXIS2, i.e
. a .NET client can't
Receiving binary can happen as either MTOM attachments or as Base64 encoded text.In the case of Base64 user has to explicitly specify that the content is binary, before calling getDataHandler(), getInputStream()
As you can seein this message no MTOM attachments are present in the response,
the setBinary(true) for that OMText and get the dataHandler. If it is defined to take in text, then treat them as text.
Thanks,
~ThilinaThanks.Sunny *
On 7/5/06, Thilina Gunarathne [EMAIL PROTECTED]
wrote:
See my comments inline..
On 7/6/06, Tech Savvy [EMAIL PROTECTED]
wrote:
Hi,Have
Hi,
On 7/6/06, Mancinelli Elodie [EMAIL PROTECTED] wrote:
Hi all,I think it's when I want to get the attachment I should have anOMElement but I have a OMText. But I don't understand why?
Nope... U get an OMText... Binary is represented using an OMText eventhough on the wire it is an element.
Change the problematic part of saveFile() as follows...
OMText child = (OMText) attach.getFirstOMChild(); //Extracting the data and saving DataHandler actualDH; actualDH = (DataHandler) child .getDataHandler();~Thilina
On 7/6/06, Thilina Gunarathne [EMAIL PROTECTED] wrote:
Hi,
On 7/6
Hi Andrew,Axis2 MTOM should work out of the box without much hassel if you have enabled MTOM on client side as follows.options.setProperty(Constants.Configuration.ENABLE_MTOM, Constants.VALUE_TRUE);
The way you are trying to receive the byte[] is correct. Can u post ur messsage snaphots. You can
Andrew,hmmm.. Interesting... Give me some time to look in to this. ~ThilinaOn 7/11/06, Andrew B
[EMAIL PROTECTED] wrote:Thilina,Thanks for the reply. Tried that option, and it didn't make any difference.
The messages are as follows:Request:POST /axis2/services/TTWSServiceService
Hi,
See my comments inline
On 7/19/06, Ben Malek, Hamid [EMAIL PROTECTED] wrote:
I have a big problem making Axis2 work fine with SwA.
1.The first problem is that I could not find any documentation on how to
programmatically construct a SwA SOAP message using AXIOM API only. You can
Hi,
Please see my reply to your earlier mail. Also some comments in line.
On 7/20/06, Ben Malek, Hamid [EMAIL PROTECTED] wrote:
Let me explain why it is important to fully support SwA in Axis2. As you
know, ebMS is heavily built on SwA. The latest version of ebMS (ebMS-3) is
still relying on
Hi Thilina,
On 7/19/06, Ben Malek, Hamid [EMAIL PROTECTED] wrote:
I certainly will be happy to help you guys with this if you need to.
Thanks a lot. You are always welcome to join.
[Hamid]: Thilina, I know very well what the MTOM specification is saying,
and I agree with you that MTOM is
If possible please post the message snapshots. Given stacktrace does
not seem to give much of an idea.
~Thilina
On 8/4/06, Pader, Erwin [EMAIL PROTECTED] wrote:
Hi all,
i've been playing around MTOMService and added functionality that will let
it read a pdf file and subsequently saving it.
Hi,
First of all your message does not contain any MTOM Optimised parts.
Binary attachment has been sent inline with XML payload by base64
encoding. Enable MTOM in the server by adding follwing to the
axis2.xml.
parameter name=enableMTOM locked=falsetrue/parameter
~Thilina
On 8/10/06, Sathija
imagexop:Include xmlns:xop=http://www.w3.org/2004/08/xop/include;
href=cid:1.urn:uuid:[EMAIL PROTECTED]
//image
This means your client is correctly receiving a MTOM optimised
message. Now I wonderhow you got the message snapshot you posted
in your first message. What is the mechanism you
Sithija,
Looking at your ealier posted message snapshot, your client need to
dig one more level in to the OM.
/image
/ns:return
/ns:getDiscrepancyReportResponse
/soapenv:Body
Now it seems your only looking at the children of the return element.
Also it would have been easier to use
hmmm...Strange.
OMElement xop:Include xmlns:xop=http://www.w3.org/2004/08/xop/include;
href=cid:1.urn:uuid:[EMAIL PROTECTED] /
In Axis2 this element automatically gets replaced by an OMText.
Wonder whether this is caused by the data binding stuff you have used
in the client side.
Can you try
See this too...
http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/samples/src/sample/mtom/imagetransfer/
~Thilina
On 8/15/06, Michele Mazzucco [EMAIL PROTECTED] wrote:
Hi Cristopher,
you can use MTOM, http://ws.apache.org/axis2/1_0/mtom-guide.html.
Regards,
Michele
Hi Erwin,
AFAIK it should be the calling thread who is closing the socket upon
sending the response or finishing the message flow.
IMHO you might not be able to avoid that 20 sec delay, cause the file
anyway has to be transfered before closing the socket. You can use an
async client or you can
OMFactory fac = OMAbstractFactory.getOMFactory();
OMText txt = fac.createOMText(axis2);
txt.setOptimize(true);
This string is expected to be a Base64 encoded version of Binary Data.
~Thilina
...
or
byte[] array = axis2.getBytes();
DataSource dataSource = new
There is a slight bug in the code, which prevents this property from
working correct. I've already done the fix in my local repo. Will take
some time to make it to the SVN head. Hopefully by next week.
Will send a mail to this thread when it's commited.
~Thilina
On 8/25/06, Punnoose, Roshan
Hi Jay,
The web site says clients automatically handle MTOM
attachments...
Yes.. It's true.. Client identifies and creates a OMText object in the
place of XOP:Include element... Configuration Dims has mentioned is
usefull when sending MTOM attachements.
What's the data binding framework you
Have a look at how MIME (MTOM/SwA) is handled in Axis2.. Specifically
you can have a look at the following places(IIRC).
1. TransportUtils class in Axis2 Kernel,
2. MIMEOutputUtils and MTOMXMLWriter in AXIOM
3. Whole attachments package in AXIOM, specially the Attachments Class..
HTH,
Try the Axis2 nightly builds..
http://people.apache.org/dist/axis2/nightly/
~Thilina
On 9/13/06, axis2e168 jose [EMAIL PROTECTED] wrote:
I found there is a fix for multiple mtom attachments
problem, the fix number is AXIS2-752. Can any one tell
me how to get the fix?
Thanks.
Yewen
server to see: java.lang.OutOfMemoryError: Java heap space.
Thanks,
Betsy
-Original Message-
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
Sent: Friday, September 15, 2006 11:51 PM
To: axis-user@ws.apache.org
Subject: Re: Axis using more than 256MB for a 9MB file
Try Axis2 with File
Will it be possible for you to show us the WSDL and the message snapshots..
~Thilina
On 9/18/06, Jha, Satyajit [EMAIL PROTECTED] wrote:
Hi,
I am using axis2 generated stub client to render reports from MSRS 2005. I
am getting this org.apache.axiom.om.OMException: Can't find datahandler
/MimeTypeEncodingUnicode
(UTF-8)/EncodingStreamIds
//RenderResponse/soap:Body/soap:Envelope
Thanks,
Satyajit
-Original Message-
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
Sent: Monday, September 18, 2006 8:38 AM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] OMException: Can't find
Hi Yoram,
You can use the OMText.getContentId() to request the content id,
given that OMText object contains the binary attachment you want to
send.
What is you use case..When using MTOM Axis2 will take care of putting
the content-id in to the SOAP request appropriately according to the
parameter name=VerificaLogin locked=falseSimpleService/parameter
Problem seems to be with the above line in you services.xml.
Change it to,
parameter name=ServiceClass
locked=falseagenteservidor.VerificaLogin/parameter
HTH,
Thilina
On 9/20/06, Fabio Alves de Araujo Ebner - DNA
the setConentID for it.
I was just not able to find the equivalent way to do it with Axis2.
Cheers,
Yoram
-Original Message-
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 19, 2006 12:05 PM
To: axis-user@ws.apache.org
Subject: Re: Setting the Content-ID header
Try this...http://people.apache.org/dist/axis2/nightly/axis2.war~ThilinaOn 9/19/06,
Silvio dos Passos Neto [EMAIL PROTECTED] wrote:
Hi everyone,
I downloaded the
last version of axis2 war... I followed de instructions of installation guide,
droping this in the webapps folder (renaming
] 3255-7328
[11] 8308-3835
[EMAIL PROTECTED]
De: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
Enviada em: terça-feira, 19 de setembro de 2006 17:34
Para: axis-user@ws.apache.org
Assunto: Re: Installing Axis2 in Tomcat
Try this...
http://people.apache.org
getElement() method was removed from the stub calss sometime back,
since the generated code no longer uses it.
Please use the latest nightlies to generate your code...
~Thilina
On 9/20/06, Felix Sprick [EMAIL PROTECTED] wrote:
Hi all,
I get the following error message when running the
hmmm... FileDataSource should automatically pick up the MIME type...
Please check whether the message gets delivered using MTOM (using a
MIME package) or with in line base64 string...
Check by enabling MTOM as follows, If MTOM is not enabled.
Options options
Nope.. We are no longer using it..
We use http://www.ibiblio.org/maven2/woodstox/wstx-asl/3.0.1/wstx-asl-3.0.1.jar
as the stax implementation together with stax-api-1.0.1.jar..
~Thilina
On 9/20/06, Z Chen [EMAIL PROTECTED] wrote:
Hi,
I am assuming Axis2 Stax parser is using this class,
but I
-
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 26, 2006 3:42 PM
To: axis-user@ws.apache.org
Subject: Re: Axis PDF trnasmission
Hi,
Please let us know the number of MIME parts in your message..
According to your mail I get a feeling that there is only one...
Please
anyone some idea? Thank
you very much for all ideas.
Vlada
-Original Message-
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 20, 2006 3:29 PM
To: axis-user@ws.apache.org
Subject: Re: Axis PDF trnasmission
hmmm... FileDataSource should
-
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 26, 2006 5:38 PM
To: axis-user@ws.apache.org
Subject: Re: Axis PDF transmision
Your PDF is transmited inline using Base64Encoding.. Anyway that too
needs to work correct.. Please log a Jira for that...
Are you using
Hi Mike,
Have your fingers crossed... We have done some upgrades to the MTOM
sample and we are hoping to get the new sample in with a wsdl.
Hopefully we'll be able to complete and commit it today...
class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ but that
didn't seem to work with the
Axis 2 supports both MTOM SwA...
Use of MTOM or SwA will depend on what your service supports.
MTOM is the better way, but most of the existing SOAP engines do not
have support for that. Only the new generation stacks like Axis2 has
support for that. .
Following is an extract on
According to the XML Schema Part 0[1] default value is
elementFormDefault=unqualified..
~Thilina
[1]http://www.w3.org/TR/xmlschema-0/#UnqualLocals
On 10/2/06, Felix Sprick [EMAIL PROTECTED] wrote:
HI Anne,
Thanks for you reply. Your were right, the elementFormDefault=qualified
worked for
Hi,
Please post your server implementation class...
since I can't copy and paste the soap message from SOAPMonitor, I save the soap
message as
screenshot pictures. please refer them to the attachment. the followings are my
questions:
You can use the http://ws.apache.org/commons/tcpmon/ to
with some simplicity. WDKWSClient.java is client invokation code which produces
a LOT of debug
information redirected to the txt file wdkwsclient.output.
thanks again,
Sam
--- Thilina Gunarathne [EMAIL PROTECTED] wrote:
Hi,
Please post your server implementation class...
since I can't copy
try adding,
as._getServiceClient().getOptions().setAction(urn:traceJob);
to your client code
~Thilina
On 10/3/06, Xia Zhao [EMAIL PROTECTED] wrote:
Hi,
Sorry to bother you guys again. I really need this help to carry on with
rest of my work. Can someone please post me a simple
attached as screenshot pictures in my previous email. the reason why I show you
the debug
information is that I want to know if there is a way to disable those debug
output in the client
side.
thanks,
Sam
--- Thilina Gunarathne [EMAIL PROTECTED] wrote:
Please note the following in your debug
You can use the SimpleAxisServer for this.. Most of the Axis2
integration tests use that...
Following test cases will give you an idea...
http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/engine/EchoRawXMLTest.java?view=markup
a hold of the axis2-test jar? So that I can
get access to the UtilServer? Thanks.
Roshan Punnoose
Phone: 301-497-6039
-Original Message-
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 04, 2006 8:34 AM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] Embedded Axis
We are hoping to do a couple of RC's prior to the much awaited 1.1...
Hopefully you will be able to witness the Axis2 1.1 RC1 by tomorrow..
If we do not find major issues in RC's, we will be able to release the
1.1 in another 2-3 weeks...
~Thilina
On 10/5/06, VF [EMAIL PROTECTED] wrote:
When
see my comments inline..
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder
and in another
This is to handle non-mtom-optimised messages
org.apache.axiom.om.impl.mtom.MTOMStAXSOAPModelBuilder
This is to handle MTOM optimised messages... This builder identifies
the XOP:Include elements
Hi,
But when I traverse the reportElement there is only one child element
i.e the xop:Include element. I can never get to the attachment itself.
This can't be... Axis2 should automatically detect XOP:include and
should create an OMText instead of XOP:Include...
If possible please post your
System.out.println(\n);
omNode.serialize(System.out);
Please let me know the output you get at this point...
OMElement omNode2 = (OMElement) omChildren.next();
if the deserialization is happening correctly you should get a
Are you using the nightly builds... If not please try with Axis2
nightlies available at http://people.apache.org/dist/axis2/nightly/
~Thilina
On 10/6/06, Gnanasekaran Vinayakamurthy
[EMAIL PROTECTED] wrote:
Hi Group,
I have proper functioning Microsoft Sql Server Reporting Services and
IMO xs:anyType should work at this point... Please file a bug report for that...
While above is also correct, you can define the return element by
using the following complex type and it's the better way..
xs:complexType
xs:sequence
xs:element name=image type=xs:base64Binary /
/xs:sequence
the other builder i.e. MTOMStAXSOAPModelBuilder is giving me the
soap message as I expected.
Any suggestions/recommendation are greatly appreciated.
Regards,
Syam
-Original Message-
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 05, 2006 11:57 AM
To: axis-user
Please try the nightly snapshots available at
http://people.apache.org/dist/axis2/nightly/..
~Thilina
On 10/7/06, Yadav, Yogendra (IT) [EMAIL PROTECTED] wrote:
Can anyone help ?
I am using AXIS2 release 1.0. The TCP Client examples do not work. I have
tried MyService example with TCP
Please try with the nightly builds...
You will need to use the WSDL2Java command line versions, since the
eclipse plugin is not included in nightly builds.
Please file a Jira, if it's not working in nighty build as well.
~Thilina
On 10/5/06, falom falom [EMAIL PROTECTED] wrote:
Hi,
While
http://www.wso2.net/kb/232
HTH,
~Thilina
On 10/4/06, Guillem Vidal [EMAIL PROTECTED] wrote:
Hi all,
I have created web services with Axis2 and they work. I would like to
combine those web services with EJBs using the same services code. Some
methods into the same class should be
Axis2 uses StAX parsing, which is also called deferred parsing.. It is
possible for Axis2 to start processing the message before the entire
request has been transmitted. This works even for attachments.. In
Axis2 objects are not made unless a need arises for them. In other
words stream is read
1 - 100 of 585 matches
Mail list logo