date:20070904

[jira] Commented: (AXIS2-3164) wsdl2java ADB client creates 'staticabstract' instead of 'static abstract'

2007-09-04 Thread Amila Chinthaka Suriarachchi (JIRA)


[ 
https://issues.apache.org/jira/browse/AXIS2-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524980
 ] 

Amila Chinthaka Suriarachchi commented on AXIS2-3164:
-

can you generate the code with -u option and see.

> wsdl2java ADB client creates 'staticabstract' instead of 'static abstract'
> --
>
> Key: AXIS2-3164
> URL: https://issues.apache.org/jira/browse/AXIS2-3164
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: adb, codegen, databinding, wsdl
>Affects Versions: 1.3
> Environment: debian testing, Java 1.5.0_11, eclipse 3.2.1
>Reporter: Petr Kremen
>
> wsdl2java ADB client creates 'staticabstract' instead of 'static abstract'.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Regarding Axis 2 & Axis 1 coexistence

2007-09-04 Thread Amila Suriarachchi

On 9/5/07, Rajesh, Peter (CLAIMS, WIP) <[EMAIL PROTECTED]> wrote:
>
> Thanks. But for example the YearMonth class package is
> org.apache.axis.types in Axis 1 & the package in Axis2 is
> org.apache.axis2.databinding.types
>
> We have used the YearMonth in Axis1 in our source file, so if we copy
> the axis jar file from Axis2 will it not create ambiguity?


I am not getting your problem correctly. But since two classes are in two
different packages
there can  not be any problem.

Amila.

Thanks & Regards,
>
> Peter Rajesh | 860-547-3881
>
> -Original Message-
> From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 04, 2007 3:14 PM
> To: axis-dev@ws.apache.org
> Subject: Re: Regarding Axis 2 & Axis 1 coexistence
>
> Yes, they should work together. Please use the newer version of wsdl4j
> jar in axis2 instead of the one on Axis1.
>
> thanks,
> dims
>
> On 9/4/07, Rajesh, Peter (CLAIMS, WIP) <[EMAIL PROTECTED]>
> wrote:
> >
> >
> >
> > Good Day,
> >
> > This is regarding a doubt we have about the coexistence of the older
> > version of Axis and the Axis2 in the Weblogic server
> >
> > Some application which are deployed in Weblogic server are using old
> > version of Axis like axis1_4, now we are doing an enhancement which
> > needs to use only Axis2. For this purpose we need to copy the Axis2
> > related jar files in the weblogic server.
> >
> > We would like to know will Axis2 affect the existing applications
> > using the older version of Axis?
> >
> > Can older version of Axis and the Axis2 can coexist?
> >
> > Request to clarify my doubts as soon as possible.
> >
> > Thanks & Regards,
> >
> > Peter Rajesh | 860-547-3881
> >
> > **
> > ***  This communication, including attachments, is  for the exclusive
> > use of addressee and may contain proprietary,  confidential and/or
> > privileged information. If you are not the intended  recipient, any
> > use, copying, disclosure, dissemination or distribution is  strictly
> > prohibited. If you are not the intended recipient, please notify  the
> > sender immediately by return e-mail, delete this communication and
> > destroy all copies.
> > **
> > ***
> >
>
>
> --
> Davanum Srinivas :: http://davanum.wordpress.com
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
> *
> This communication, including attachments, is
> for the exclusive use of addressee and may contain proprietary,
> confidential and/or privileged information.  If you are not the intended
> recipient, any use, copying, disclosure, dissemination or distribution is
> strictly prohibited.  If you are not the intended recipient, please notify
> the sender immediately by return e-mail, delete this communication and
> destroy all copies.
> *
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Amila Suriarachchi,
WSO2 Inc.

[jira] Created: (AXIS2-3167) Axis2, GSoap, and Character Sets

2007-09-04 Thread Martin Smith (JIRA)

Axis2, GSoap, and Character Sets


 Key: AXIS2-3167
 URL: https://issues.apache.org/jira/browse/AXIS2-3167
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: transports
Affects Versions: 1.3
Reporter: Martin Smith


Hello Axis folks! I apologize ahead of time if my issue isn't really an Axis 
bug, but one with gSOAP.

Long story short, Axis2-1.3 and HttpClient-3.1 by irself choke on the encoding 
of characters I get back from a gSOAP server. I've detailed some of my analysis 
at http://dev.grub.org/cgi-bin/trac.cgi/ticket/3.

>From what I can tell, this issue came up in the past with Axis 1, but I can't 
>tell how it was fixed: http://issues.apache.org/jira/browse/AXIS-1268

It's also come up directly at gSOAP's issue tracker:
http://sourceforge.net/tracker/index.php?func=detail&aid=1561294&group_id=52781&atid=468021

In 2003, someone suggested using gSOAP's I_PROMISE_TO_USE_REAL_UTF8 flag (not 
the real flag name :): 
http://mail-archives.apache.org/mod_mbox/xml-xalan-c-users/200306.mbox/[EMAIL 
PROTECTED]

Here's a trace from Axis2 minus the authentication header:
[DEBUG] EntityEnclosingMethod - Request body sent
[DEBUG] header - << "HTTP/1.1 200 OK[\r][\n]"
[DEBUG] header - << "Date: Wed, 05 Sep 2007 01:24:27 GMT[\r][\n]"
[DEBUG] header - << "Server: Apache/1.3.28 (Unix)[\r][\n]"
[DEBUG] header - << "Last-Modified: Wed, 05 Sep 2007 01:24:27 GMT[\r][\n]"
[DEBUG] header - << "Content-Length: 281[\r][\n]"
[DEBUG] header - << "Content-Type: text/xml; charset=utf-8[\r][\n]"
[DEBUG] content - << "[0x1f][0x8b][0x8][0x0]"
[DEBUG] content - << 
"[0x0][0x0][0x0][0x0][0x0][0xff][0x95][0x91][0xcd]n[0x83]0[0x10][0x84][0xef]}[\n]"
[DEBUG] content - << 
"[0xcb]wp[0xd2]^*[0x4][0x8e][0xda][0x88][0x9c][0xda][0xa6][0x12]m[0xd5]+[0x82]%[0xb1]d[0xd6][0x96]mBx[0xfb][0x9a][0x10]
 
Q[0xf]io[0xfb]3[0xdf]hG[0x1b][0xaf][0x8e][0xb5]$[0x7]0V(L[0xe8]2\P[0x2]X[0xa8]R[0xe0].[0xa1][0x9f][0x1f][0x9b][0xe0][0x91][0xae][0xf8]][0x9c]m[0x9f][0xde][0x83][0xf4][0xed]+J[0xf1][0x0]Ri
 
[0x9e]C[0x1b][0x8d][0xf3][0x84][0xee][0x9d][0xd3][0x11]c[0xb6][0xd8]C[0x9d][0xdb][0xd0][0xaf][0xad][0xca]u[0xa8][0xcc][0x8e][0xf5][0x5][0x83]3[0xc8][0xe8]5[0xba][0xfe][0xb]:[0x1c]4[0xa1]G+&[EMAIL
 
PROTECTED],`[0xa6][0xca][0xdb][0xd4](F[0x9b][0xd0][0xc6]`T([0xdd]Q>[0xe7]Vew[0xd1]n[0xf2]F:2[0xb5][0xe3][0xa5][0x99][0xeb]$[0xfc]'[0x18][0x8f][0xab][0xde][0xc9][0xb7][0xc0]'[0xb7][0xb5][0x14][0x80].f[0xf3]jPYg<[0xc4]S,[0x89][0xaa]H%$[0x10]e[0x8]*"P7."[[\r]&w[0xfe][0xa1]~[0xe0][0xc0][0x98]F;({[0x89][0x13]u_4[0xa3][0xe7][0xd9](f[0xd7]y.[0x7]C^[0xf6][0xeb][0xff][0xfc][0x7][\r][0xbc][0x9a]_:[0x2][0x0][0x0]"
Exception in thread "main" org.apache.axis2.AxisFault: Invalid UTF-8 start byte 
0x8b (at char #2, byte #-1)
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
at 
org.apache.axis2.builder.SOAPBuilder.processDocument(SOAPBuilder.java:63)
at 
org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:160)
at 
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:111)
at 
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:87)
at 
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:326)
at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389)
at 
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
at 
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at 
org.grub.schema.grubd.GrubServiceStub.GrubService2(GrubServiceStub.java:384)
at org.mbs3.grub.GrubTest.main(GrubTest.java:42)
Caused by: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 start byte 0x8b (at 
char #2, byte #-1)
at 
com.ctc.wstx.stax.WstxInputFactory.doCreateSR(WstxInputFactory.java:548)
at 
com.ctc.wstx.stax.WstxInputFactory.createSR(WstxInputFactory.java:604)
at 
com.ctc.wstx.stax.WstxInputFactory.createSR(WstxInputFactory.java:629)
at 
com.ctc.wstx.stax.WstxInputFactory.createXMLStreamReader(WstxInputFactory.java:324)
at 
org.apache.axiom.om.util.StAXUtils.createXMLStreamReader(StAXUtils.java:175)
at 
org.apache.axis2.builder.SOAPBuilder.processDocument(SOAPBuilder.java:51)
... 9 more
Caused by: java.io.CharConversionException: Invalid UTF-8 start byte 0x8b (at 
char #2, byte #-1)
at com.ctc.wstx.io.UTF8Reader.reportInvalidInitial(UTF8Reader.java:299)
at com.ctc.wstx.io.UTF8Reader.read(UTF8Reader.java:185)
at 
com.ctc.wstx.io.ReaderBootstrapper.initialLoad(ReaderBootstrapper.java:245)
at 
com.ctc.wstx.io.ReaderBootstrapper.bootstrapInput(ReaderBootstrapper.java:132)
at 
com.ctc.wstx.stax.WstxInputFactory.doCreateSR(WstxInputFactory.java:543)
... 14 more


I tried going the dir

Re: [AXIS2] : Help required : getting a zip file using AXIS2 + AXIOM

2007-09-04 Thread Thilina Gunarathne

Hi,
AFAIKS the problem lies in the code where you are trying to create the
byte[]. Also make sure that the zip file is created correctly in he
file system of your server.

I would recommend you to use the FileDataSource directly rather than
using a ByteArrayDataSource. With that you'll be able to create the
data source straight out from the file without creating byte[].

Also if you are planning to transfer large data, make sure to enable
MTOM in the server side.

~Thilina


On 9/4/07, Sushil Dodake <[EMAIL PROTECTED]> wrote:
>
>
> -- Forwarded message --
> From: Sushil Dodake <[EMAIL PROTECTED]>
> Date: Sep 4, 2007 6:47 PM
> Subject: Re: Help required : getting a zip file using AXIS2 + AXIOM
> To: Thilina Gunarathne <[EMAIL PROTECTED]>
>
>
> Hi,
> Thanks you very much for a very prompt reply..
> I have also sent this mail to the group you told me.
> As i need to fix this issue ASAP i am also sending this presonally.
> The code snippet on the server side is as below.
>
> Breife description -->
> 1. Take the JPEG files data in byte array format from the Documentum server
> and store it in a List
> 2. Generate a Zip file and store it on the HDD
> 3. get the zip file as input stream, Convert it in to binary array
> 4. send it using a data handler.
>
>
> private OMElement createZipData(List ObjectList) throws ContentFault{
>
>
>
> ZipOutputStream ZipOutStream;
>
> OMFactory factory = OMAbstractFactory.getOMFactory();
>
> OMNamespace payloadNs= factory.createOMNamespace(XML_NAMESPACE,
> XML_NAMESPACE_PREFIX );
>
> OMElement zipContent = factory.createOMElement("ZipContent", payloadNs);
>
>
>
> try {
>
> String zipPath = this.zipFilePath;
>
> Date currentDate = new Date();
>
> long time = currentDate.getTime();
>
> //Create a local Zip File to add all the Images (binary data)
>
> zipPath = zipPath + "\\file"+ String.valueOf(time)+ ".zip" ;
>
> System.out.println("Zip Path " + zipPath);
>
>
>
> ZipOutStream = new ZipOutputStream(new FileOutputStream(zipPath));
>
> int totalObjects = ObjectList.size();
>
> for(int i = 0; i < totalObjects; i++){
>
> DCTMObject nextObject = (DCTMObject)ObjectList.get(i);
>
> List contentList = nextObject.getContentList();
>
>
>
> if(contentList != null){
>
> int contentListSize = contentList.size();
>
>
>
> for(int j = 0; j < contentListSize; j++){
>
> //Get the binary content of the image data
>
> ObjectContent content = (ObjectContent)contentList.get(j);
>
>
>
> if(content != null){
>
> byte []byteContent = content.getContent();
>
> ZipEntry fileName = new ZipEntry(content.getName());
>
> ZipOutStream.putNextEntry(fileName);
>
> byte []tempArray = new byte [4096];
>
> int flag;
>
> BufferedInputStream bi = new BufferedInputStream(new
> ByteArrayInputStream(byteContent));
>
>
>
> while ((flag = bi.read(tempArray, 0, 4096)) != -1) {
>
> ZipOutStream.write(tempArray, 0, flag);
>
> }
>
>
>
> ZipOutStream.closeEntry();
>
> }
>
> }
>
> }
>
> }
>
> //Local Zip File created
>
> ZipOutStream.close();
>
>
>
> //Read the zip Loacl zip file and convert it in the byte array
>
> ZipInputStream zipInStream = new ZipInputStream(new BufferedInputStream( new
> FileInputStream(zipPath)));
>
> byte [] zipByte = new byte [zipInStream.available()];
>
> System.out.println("Getting Zipped Data Total Size =" +
> zipInStream.available ());
>
> zipInStream.read(zipByte, 0, zipInStream.available());
>
> ByteArrayDataSource byteData = new ByteArrayDataSource(zipByte);
>
>
>
> //Use a data handler to send the binary data (byte array)
>
> DataHandler handler = new DataHandler(byteData);
>
>
>
> OMText fileData = factory.createOMText(handler, true);
>
> zipContent.addChild(fileData);
>
> //objContent.addChild(fileContent);
>
>
>
> } catch (IOException e) {
>
> System.out.println("In the createZipData Catch");
>
> e.printStackTrace();
>
> throw new ContentFault("In the createZipData Catch" );
>
> }
>
> System.out.println("Response Zip Conmtent" + zipContent.toString ());
>
> return zipContent;
>
> }
>
>
>
>
>
> On 9/4/07, Thilina Gunarathne <[EMAIL PROTECTED] > wrote:
> > Hi,
> > >   AA==
> > >
> > What you have got above  is the base64 representation of the data you
> > have attached in your server side. There is a possibility that data is
> > not correctly attached in the server side.
> >
> > Are you using any data binding mechanisms. If so what... Also post me
> > the WSDL if it's possible..
> >
> > I also would like to see how you are attaching the data at the server
> side..
> >
> > Also you can post your Axis2 related questions to axis-user list
> > ( http://ws.apache.org/axis2/mail-lists.html ) with
> [Axis2] prefix in
> > the subject. In there you'll find more people to answer your questions
> > and more people will benefit from the answers you are getting.. FYI: I
> > frequently checks that list..
> >
> > thanks,
> > Thilina
> >
> > On 9/4/07, Sushil Dodake <[EMAIL PROTECTED] > wrote:
> > > Hi Thilina,
> > > I got your mail address from the link.
> > >
> http://archives.devshed.com/fo

AXIS2 : Help required : getting a zip file using AXIS2 + AXIOM

2007-09-04 Thread Sushil Dodake

-- Forwarded message --
From: Sushil Dodake <[EMAIL PROTECTED]>
Date: Sep 4, 2007 6:47 PM
Subject: Re: Help required : getting a zip file using AXIS2 + AXIOM
To: Thilina Gunarathne <[EMAIL PROTECTED]>

Hi,
Thanks you very much for a very prompt reply..
I have also sent this mail to the group you told me.
As i need to fix this issue ASAP i am also sending this presonally.
The code snippet on the server side is as below.
**
*Breife description --> *
*1. Take the JPEG files data in byte array format from the Documentum server
and store it in a List *
*2. Generate a Zip file and store it on the HDD*
*3. get the zip file as input stream, Convert it in to binary array*
*4. send it using a data handler.*

*private* OMElement createZipData(List ObjectList) *throws* ContentFault{

ZipOutputStream ZipOutStream;

OMFactory factory = OMAbstractFactory.*getOMFactory*();

OMNamespace payloadNs= factory.createOMNamespace(
*XML_NAMESPACE*, *XML_NAMESPACE_PREFIX* );

OMElement zipContent = factory.createOMElement(
"ZipContent", payloadNs);

*try* {

String zipPath =
*this*.zipFilePath;

Date currentDate =
*new* Date();

*long* time = currentDate.getTime();

//Create a local Zip File to add all the Images (binary data)

zipPath = zipPath +
"\\file"+ String.*valueOf*(time)+ ".zip" ;

System.
*out*.println("Zip Path " + zipPath);

ZipOutStream =
*new* ZipOutputStream(*new* FileOutputStream(zipPath));

*int* totalObjects = ObjectList.size();

*for*(*int* i = 0; i < totalObjects; i++){

DCTMObject nextObject = (DCTMObject)ObjectList.get(i);

List contentList = nextObject.getContentList();

*if*(contentList != *null*){

*int* contentListSize = contentList.size();

*for*(*int* j = 0; j < contentListSize; j++){

//Get the binary content of the image data

ObjectContent content = (ObjectContent)contentList.get(j);

*if*(content != *null*){

*byte* []byteContent = content.getContent();

ZipEntry fileName =
*new* ZipEntry(content.getName());

ZipOutStream.putNextEntry(fileName);

*byte* []tempArray = *new* *byte *[4096];

*int* flag;

BufferedInputStream bi =
*new* BufferedInputStream(*new* ByteArrayInputStream(byteContent));

*while* ((flag = bi.read(tempArray, 0, 4096)) != -1) {

ZipOutStream.write(tempArray, 0, flag);

}

ZipOutStream.closeEntry();

}

}

}

}

//Local Zip File created

ZipOutStream.close();

//Read the zip Loacl zip file and convert it in the byte array

ZipInputStream zipInStream =
*new* ZipInputStream(*new* BufferedInputStream(
*new*FileInputStream(zipPath)));

*byte* [] zipByte = *new* *byte *[zipInStream.available()];

System.
*out*.println("Getting Zipped Data Total Size =" + zipInStream.available());

zipInStream.read(zipByte, 0, zipInStream.available());

ByteArrayDataSource byteData =
*new* ByteArrayDataSource(zipByte);

//Use a data handler to send the binary data (byte array)

DataHandler handler =
*new* DataHandler(byteData);

OMText fileData = factory.createOMText(handler,
*true*);

zipContent.addChild(fileData);

//objContent.addChild(fileContent);

}
*catch* (IOException e) {

System.
*out*.println("In the createZipData Catch");

e.printStackTrace();

*throw* *new* ContentFault("In the createZipData Catch" );

}

System.
*out*.println("Response Zip Conmtent" + zipContent.toString ());

*return* zipContent;

}




On 9/4/07, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:
>
> Hi,
> >   AA==
> >
> What you have got above  is the base64 representation of the data you
> have attached in your server side. There is a possibility that data is
> not correctly attached in the server side.
>
> Are you using any data binding mechanisms. If so what... Also post me
> the WSDL if it's possible..
>
> I also would like to see how you are attaching the data at the server
> side..
>
> Also you can post your Axis2 related questions to axis-user list
> (http://ws.apache.org/axis2/mail-lists.html ) with [Axis2] prefix in
> the subject. In there you'll find more people to answer your questions
> and more people will benefit from the answers you are getting.. FYI: I
> frequently checks that list..
>
> thanks,
> Thilina
>
> On 9/4/07, Sushil Dodake <[EMAIL PROTECTED]> wrote:
> > Hi Thilina,
> > I got your mail address from the link.
> >
> http://archives.devshed.com/forums/apache-92/axis2-contentid-is-null-using-mtom-1880965.html
> > i have a problem in sending a zip file using AXIS2 + AXIOM
> > when i send  a zip file then @ the client side i get
> >
> >
> >  > xmlns:tns="http://content.dctm.service.toro.com";>
> >
> >   AA==
> >
> > 
> >
> > but the actual zip file conteains 2 jpeg images...
> >
> > i have absolutely no idea as in how to retrieve the jpeg files from the
> > received presentation of the zip file.
> >
> > i tried using the folowing snippet to retrieve the data
> >
> >
> >
> > OMElement zipFile = result.getFirstChildWithName(new QName("ZipContent"
> ));
> >
> > OMText zipData = (OMText)( result.getFirstElement()).getFirstOMChild();
> >
> > zipData.setOptimize(true);
> >
> > DataHandler

Fwd: AXIS2 : Help required : getting a zip file using AXIS2 + AXIOM

2007-09-04 Thread Sushil Dodake

-- Forwarded message --
From: Sushil Dodake <[EMAIL PROTECTED]>
Date: Sep 4, 2007 6:49 PM
Subject: AXIS2 : Help required : getting a zip file using AXIS2 + AXIOM
To: axis-dev@ws.apache.org



-- Forwarded message --
From: Sushil Dodake <[EMAIL PROTECTED]>
Date: Sep 4, 2007 6:47 PM
Subject: Re: Help required : getting a zip file using AXIS2 + AXIOM
To: Thilina Gunarathne <[EMAIL PROTECTED]>

Hi,
Thanks you very much for a very prompt reply..
I have also sent this mail to the group you told me.
As i need to fix this issue ASAP i am also sending this presonally.
The code snippet on the server side is as below.
**
*Breife description --> *
*1. Take the JPEG files data in byte array format from the Documentum server
and store it in a List *
*2. Generate a Zip file and store it on the HDD*
*3. get the zip file as input stream, Convert it in to binary array*
*4. send it using a data handler.*

*private* OMElement createZipData(List ObjectList) *throws* ContentFault{

ZipOutputStream ZipOutStream;

OMFactory factory = OMAbstractFactory.*getOMFactory*();

OMNamespace payloadNs= factory.createOMNamespace(
*XML_NAMESPACE*, *XML_NAMESPACE_PREFIX* );

OMElement zipContent = factory.createOMElement(
"ZipContent", payloadNs);

*try* {

String zipPath =
*this*.zipFilePath;

Date currentDate =
*new* Date();

*long* time = currentDate.getTime();

//Create a local Zip File to add all the Images (binary data)

zipPath = zipPath +
"\\file"+ String.*valueOf*(time)+ ".zip" ;

System.
*out*.println("Zip Path " + zipPath);

ZipOutStream =
*new* ZipOutputStream(*new* FileOutputStream(zipPath));

*int* totalObjects = ObjectList.size();

*for*(*int* i = 0; i < totalObjects; i++){

DCTMObject nextObject = (DCTMObject)ObjectList.get(i);

List contentList = nextObject.getContentList();

*if*(contentList != *null*){

*int* contentListSize = contentList.size();

*for*(*int* j = 0; j < contentListSize; j++){

//Get the binary content of the image data

ObjectContent content = (ObjectContent)contentList.get(j);

*if*(content != *null*){

*byte* []byteContent = content.getContent();

ZipEntry fileName =
*new* ZipEntry(content.getName());

ZipOutStream.putNextEntry(fileName);

*byte* []tempArray = *new* *byte *[4096];

*int* flag;

BufferedInputStream bi =
*new* BufferedInputStream(*new* ByteArrayInputStream(byteContent));

*while* ((flag = bi.read(tempArray, 0, 4096)) != -1) {

ZipOutStream.write(tempArray, 0, flag);

}

ZipOutStream.closeEntry();

}

}

}

}

//Local Zip File created

ZipOutStream.close();

//Read the zip Loacl zip file and convert it in the byte array

ZipInputStream zipInStream =
*new* ZipInputStream(*new* BufferedInputStream(
*new*FileInputStream(zipPath)));

*byte* [] zipByte = *new* *byte *[zipInStream.available()];

System.
*out*.println("Getting Zipped Data Total Size =" + zipInStream.available());

zipInStream.read(zipByte, 0, zipInStream.available());

ByteArrayDataSource byteData =
*new* ByteArrayDataSource(zipByte);

//Use a data handler to send the binary data (byte array)

DataHandler handler =
*new* DataHandler(byteData);

OMText fileData = factory.createOMText(handler,
*true*);

zipContent.addChild(fileData);

//objContent.addChild(fileContent);

}
*catch* (IOException e) {

System.
*out*.println("In the createZipData Catch");

e.printStackTrace();

*throw* *new* ContentFault("In the createZipData Catch" );

}

System.
*out*.println("Response Zip Conmtent" + zipContent.toString ());

*return* zipContent;

}




On 9/4/07, Thilina Gunarathne <[EMAIL PROTECTED] > wrote:
>
> Hi,
> >   AA==
> >
> What you have got above  is the base64 representation of the data you
> have attached in your server side. There is a possibility that data is
> not correctly attached in the server side.
>
> Are you using any data binding mechanisms. If so what... Also post me
> the WSDL if it's possible..
>
> I also would like to see how you are attaching the data at the server
> side..
>
> Also you can post your Axis2 related questions to axis-user list
> ( http://ws.apache.org/axis2/mail-lists.html ) with [Axis2] prefix in
> the subject. In there you'll find more people to answer your questions
> and more people will benefit from the answers you are getting.. FYI: I
> frequently checks that list..
>
> thanks,
> Thilina
>
> On 9/4/07, Sushil Dodake <[EMAIL PROTECTED] > wrote:
> > Hi Thilina,
> > I got your mail address from the link.
> >
> http://archives.devshed.com/forums/apache-92/axis2-contentid-is-null-using-mtom-1880965.html
> > i have a problem in sending a zip file using AXIS2 + AXIOM
> > when i send  a zip file then @ the client side i get
> >
> >
> >  > xmlns:tns="http://content.dctm.service.toro.com ">
> >
> >   AA==
> >
> > 
> >
> > but the actual zip file conteains 2 jpeg images...
> >
> > i have absolutely no idea as in how to retrieve the jpeg files from the
> > received presentation of the zip file.
> >
> > i tried using the folowing snippet to retrieve the data
> >
> >
> >
> > O

Re: Transactional JMS.

2007-09-04 Thread Rajith Attapattu

On 9/4/07, Maciej Szefler <[EMAIL PROTECTED]> wrote:
>
> Rajith,
>
> Your take appears to be based on the assumption that AXIS is communicating
> with the JMS provider directly (that is outside of a managed environment).
> In a managed environment the connection/session creation would not be an
> issue since these would  be pooled objects, with automatic transaction
> association. In this (managed) case sending message in JTA would be only a
> matter of a) providing a way to specify JNDI location of a JMS connection
> factory, and b) making sure that the session is started with the transacted
> flag set to false. In this context, the message consumption is problematic
> since it would need to involve either MDBs or some unsightly polling scheme.
>

Yes, my assumption was based on communicating with a JMS provider directly.

So assuming direct communication to the JMS provider (and no "magic" help
> from the JMS provider) , I generally agree with your comments. Certainly
> creating a connection for each connection is not acceptable (this is true
> for the non-JTA case as well).

Yes, this comment was in general for both transacted and non transacted
case. Connections are expensive and we need to reuse where it make sense.

The naming scheme that you describe would work perfectly well for us, but it
> may quickly turn into a JCA-lite project; perhaps there is some way to make
> this pluggable (a simple interface for providing a JMS connection to AXIS).
> As for reusing sessions,I think it is more trouble than its worth, and in my
> experience there is very little performance overhead here.

For Receiving we use the same session, but for sending we create a new
connection and a session.
Well Sessions are light weight, but in the case where we have a high volume
of web service invocations we will be creating and destroying a lot of
sessions unnecessarily. Setting up a session and then destroying on the
broker side does take some resources all though comparatively less than a
connection.
I agree that reusing sessions are tricky and may not be worth all the time -
but it does make sense for certain situations. For example if you have a
Service with scope='application' or scope='soap-session' that does frequent
message sending then it makse sense to maintain a session per service
instance. Here the life time of the service instance is tied to it's axis2
defined scope. We already have a session per receiver. Also if we have
several services with scope='request' and sending frequent messages then it
make sense to share a session(s) btw these services to improve performance.
Remember that, at the least creating and destroying a session involves IO
and network round trip for two calls on the broker. Now think about a
situation where you send 50,000 msg/sec.

I think with careful thought and planning we can optimize the JMS transport
without screwing up the common cases.

Also session-per-service would necessitate serializing access (since an
> XASession can only be associated with one JTA transaction), which in many
> cases would not be desirable.

Sorry if I was not clear enough. When I said session per service, I meant
session per service instance (where it make sense). So no need to serialize
access.
Ex. If you have a service with scope='soap-session' and there are two
clients talking to it, then you would have two instances of the service and
would be using two JMS sessions (or two XA sessions). So each web service
instance can run transactions independently of the other.

In the use case where services with scope='request' sharing sessions
underneath, a given JMS session will only be used by one and only one
service instance at a given time. (This will be tricky to implement, and
only be worth if there is a high traffic scenario).

Going direct, we still have a problem with receving messages. As far I know,
> it is not possible to do a JTA receive using the async MessageListener
> interface. One would need to either poll, or  use the MessageConsumer
> interfaces.

Async or sync message receive is orthogonal to the transactions. Can you
elaborate a bit more

In either case there is the issue of who begins and commits the JTA
> transaction (AXIS2 or the service), and if its the service, it is not clear
> how that interaction would look.
>
I'm more inclined toward an  MDB-like model, where AXIS starts the TX, calls
> the service, and then barring some indication to the contrary, attempts to
> commit.

IMO Axis2 should not commit or rollback automatically. Commits or rollbacks
can happen based on business decisions as well as system errors.
And in the case of a distributed transaction the decision to commit or
rollback will come from the distributed transaction manager.

If there are any system(axis2) hiccups then axis2 will/should always throw a
fault and the service author will be notified instead of axis2 doing
rollback.
In the case of a local transaction the service author may rollback and in a
distributed

RE: Regarding Axis 2 & Axis 1 coexistence

2007-09-04 Thread Rajesh, Peter (CLAIMS, WIP)

Thanks. But for example the YearMonth class package is
org.apache.axis.types in Axis 1 & the package in Axis2 is
org.apache.axis2.databinding.types

We have used the YearMonth in Axis1 in our source file, so if we copy
the axis jar file from Axis2 will it not create ambiguity?

Thanks & Regards,

Peter Rajesh | 860-547-3881

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, September 04, 2007 3:14 PM
To: axis-dev@ws.apache.org
Subject: Re: Regarding Axis 2 & Axis 1 coexistence

Yes, they should work together. Please use the newer version of wsdl4j
jar in axis2 instead of the one on Axis1.

thanks,
dims

On 9/4/07, Rajesh, Peter (CLAIMS, WIP) <[EMAIL PROTECTED]>
wrote:
>
>
>
> Good Day,
>
> This is regarding a doubt we have about the coexistence of the older 
> version of Axis and the Axis2 in the Weblogic server
>
> Some application which are deployed in Weblogic server are using old 
> version of Axis like axis1_4, now we are doing an enhancement which 
> needs to use only Axis2. For this purpose we need to copy the Axis2 
> related jar files in the weblogic server.
>
> We would like to know will Axis2 affect the existing applications 
> using the older version of Axis?
>
> Can older version of Axis and the Axis2 can coexist?
>
> Request to clarify my doubts as soon as possible.
>
> Thanks & Regards,
>
> Peter Rajesh | 860-547-3881
>
> **
> ***  This communication, including attachments, is  for the exclusive 
> use of addressee and may contain proprietary,  confidential and/or 
> privileged information. If you are not the intended  recipient, any 
> use, copying, disclosure, dissemination or distribution is  strictly 
> prohibited. If you are not the intended recipient, please notify  the 
> sender immediately by return e-mail, delete this communication and  
> destroy all copies.
> **
> ***
>

--
Davanum Srinivas :: http://davanum.wordpress.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

*
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information.  If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited.  If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Transactional JMS.

2007-09-04 Thread Maciej Szefler

Rajith,

Your take appears to be based on the assumption that AXIS is communicating
with the JMS provider directly (that is outside of a managed environment).
In a managed environment the connection/session creation would not be an
issue since these would  be pooled objects, with automatic transaction
association. In this (managed) case sending message in JTA would be only a
matter of a) providing a way to specify JNDI location of a JMS connection
factory, and b) making sure that the session is started with the transacted
flag set to false. In this context, the message consumption is problematic
since it would need to involve either MDBs or some unsightly polling scheme.

So assuming direct communication to the JMS provider (and no "magic" help
from the JMS provider) , I generally agree with your comments. Certainly
creating a connection for each connection is not acceptable (this is true
for the non-JTA case as well). The naming scheme that you describe would
work perfectly well for us, but it may quickly turn into a JCA-lite project;
perhaps there is some way to make this pluggable (a simple interface for
providing a JMS connection to AXIS). As for reusing sessions,I think it is
more trouble than its worth, and in my experience there is very little
performance overhead here. Also session-per-service would necessitate
serializing access (since an XASession can only be associated with one JTA
transaction), which in many cases would not be desirable.

Going direct, we still have a problem with receving messages. As far I know,
it is not possible to do a JTA receive using the async MessageListener
interface. One would need to either poll, or  use the MessageConsumer
interfaces. In either case there is the issue of who begins and commits the
JTA transaction (AXIS2 or the service), and if its the service, it is not
clear how that interaction would look. I'm more inclined toward an  MDB-like
model, where AXIS starts the TX, calls the service, and then barring some
indication to the contrary, attempts to commit.

-mbs

On 9/4/07, Rajith Attapattu <[EMAIL PROTECTED]> wrote:
>
> Maciej,
>
> Currently there are a few problems with doing this. Lets identify the
> issues
> a) We create a new connection for each invocation (sending messages)
> b) Hence we create a new session for each invocation.
> c) When creating a session for receiving as well as sending transacted is
> set to true - no way to configure this.
> d) We currently don't expose the session outside for both transport
> sender/receiver, hence you cannot call commit or rollback on it.
> e) Since u are using JTA I assume it's a distributed transaction. So we
> need to create an XASession instead of a normal session.
>
> This can be done and here are some ideas. I spoke with Asankha briefly on
> this topic once.
>
> a) Asankha pointed out a new connection is created for each invocation as
> each service could have different connection params. (different provider,
> username,..etc)
> The downside of this is that creating new connections is an expensive
> operation. Especially if the same service sends frequent messages it will
> keep recreating connections. We should make this behaviour configurable.
> I would like if we could reuse connections where we can. Also in most
> cases a deployment would use a single provider and we can definitely
> optimize for this case.
> For this case we can get away with a single connection per axis2 instance
> and session per service (one for sending and one for listening).
>
> If we can name connections then we could reuse them when defining
> services. This way we can check if an existing connection by that name
> exists and reuse it, if not create one.
>
> When we reuse connections there will be keep alive issues. Most providers
> have convenient and cheap ways of sending ping/pongs to keep the connection
> alive.
> So in a case where the service sends messages frequently this will help.
> If the service sends messages rarely and the cost of keep alive is greater
> than the occasional connection creation then the user can disable the reuse
> option.
>
> b) Creating a new session for each invocation is not optimal. Since the
> context hierarchy determines the scope of services and is independent of the
> transport session it's ok to reuse a JMS session underneath where ever it
> makes sense. If we introduce some thing similar to scope="transport-session"
> in HTTP for JMS, then we can allow users to directly use the underlying JMS
> transport similar to the way HTTP session is used.
>
> c) We can make the transacted property configurable. By default it will be
> false.
> 
> Ex: true
>
> d) We need to expose the JMS session. Can we put the JMS session somewhere
> in the context hierarchy?
> I also see a getSessionContext in

Re: Regarding Axis 2 & Axis 1 coexistence

2007-09-04 Thread Davanum Srinivas

Yes, they should work together. Please use the newer version of wsdl4j
jar in axis2 instead of the one on Axis1.

thanks,
dims

On 9/4/07, Rajesh, Peter (CLAIMS, WIP) <[EMAIL PROTECTED]> wrote:
>
>
>
> Good Day,
>
> This is regarding a doubt we have about the coexistence of the older version
> of Axis and the Axis2 in the Weblogic server
>
> Some application which are deployed in Weblogic server are using old version
> of Axis like axis1_4, now we are doing an enhancement which needs to use
> only Axis2. For this purpose we need to copy the Axis2 related jar files in
> the weblogic server.
>
> We would like to know will Axis2 affect the existing applications using the
> older version of Axis?
>
> Can older version of Axis and the Axis2 can coexist?
>
> Request to clarify my doubts as soon as possible.
>
> Thanks & Regards,
>
> Peter Rajesh | 860-547-3881
>
> *
>  This communication, including attachments, is
>  for the exclusive use of addressee and may contain proprietary,
>  confidential and/or privileged information. If you are not the intended
>  recipient, any use, copying, disclosure, dissemination or distribution is
>  strictly prohibited. If you are not the intended recipient, please notify
>  the sender immediately by return e-mail, delete this communication and
>  destroy all copies.
> *
>


-- 
Davanum Srinivas :: http://davanum.wordpress.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Regarding Axis 2 & Axis 1 coexistence

2007-09-04 Thread Rajesh, Peter (CLAIMS, WIP)

> Good Day,
> 
> This is regarding a doubt we have about the coexistence of the older
> version of Axis and the Axis2 in the Weblogic server
> 
> Some application which are deployed in Weblogic server are using old
> version of Axis like axis1_4, now we are doing an enhancement which
> needs to use only Axis2. For this purpose we need to copy the Axis2
> related jar files in the weblogic server.
> 
> We would like to know will Axis2 affect the existing applications
> using the older version of Axis?
> 
> Can older version of Axis and the Axis2 can coexist?
> 
> Request to clarify my doubts as soon as possible.
> 
> Thanks & Regards,
> 
> Peter Rajesh | 860-547-3881
> 


*
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information.  If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited.  If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*

Re: axis-castor : unable to find fieldDescriptor

2007-09-04 Thread WJ Krpelan

Hi
Generally, only standard xml-schema-data types are
being provided out of the box. The easy way to do it
is to break it up into standard data types. Else I'm
sure IBM is selling some serializing support for its
special data types.
Cheers

--- Thomas Beaujard <[EMAIL PROTECTED]> wrote:

> Hello
> 
> I am trying the example from this link : 
>
http://www.ibm.com/developerworks/webservices/library/ws-castor/
> 
> And I get the following error :
> org.xml.sax.SAXException:
> Unable to marshall between XML and Castor Objects
> :unable to find
> FieldDescriptor for 'DOC_ID' in ClassDescriptor of
> GMDSREQCT
> 
> I
> have seen thread where people had the same problem
> as me. One person
> said that we have to modify the CastorSerializer
> class as explained in
> this link:
>
http://www.mail-archive.com/[EMAIL PROTECTED]/msg15150.html
> 
> However, I cannot access this link. Does anyone have
> a solution?
> 
> Cheers
> 
> Thom
> 
> 
> 
> 
> 
> 
> 
>   
> 
> 
> 
>  
>
_
> 
> Ne gardez plus qu'une seule adresse mail ! Copiez
> vos mails vers Yahoo! Mail 



  

Park yourself in front of a world of choices in alternative vehicles. Visit the 
Yahoo! Auto Green Center.
http://autos.yahoo.com/green_center/ 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re : Re : Tr : Axis problem returning byteArray

2007-09-04 Thread WJ Krpelan

Hello,
As it works with me, I'd suspect there is something
wrong with your xsd-File or your WSDL-File
Can I have a look at the WSDL?
Cheers

--- Thomas Beaujard <[EMAIL PROTECTED]> wrote:

> Hi
> 
> Here is the SOAP-trace:
> 
> HTTP/1.1 200 OK Content-Type: text/xml;charset=utf-8
> Date: Tue, 04 Sep 2007 11:10:43 GMT Server:
> Apache-Coyote/1.1 Connection: close  
> 
> 
> 
> 37
> 80
> 68
> 70
> 45
> 49 ..
> 13
> 
> 
> 
> As you can see the tag CONTENT appears many times
> with a type byte, whereas it should only appear once
> with the type base64binary.
> I cannot use the xs:string workaround... do you have
> any other idea?
> 
> Thanks for your help
> 
> Thom
> 
> - Message d'origine 
> De : WJ Krpelan <[EMAIL PROTECTED]>
> À : axis-dev@ws.apache.org
> Envoyé le : Vendredi, 31 Août 2007, 12h24mn 28s
> Objet : Re: Re : Tr : Axis problem returning
> byteArray
> 
> Hi
> Could you provice a SOAP-Trace (TCPMon)? Would it
> look
> similar to the one below?
> A less than satisfactory workaround, if you control
> both sides of the wire, would be to change type to
> xs:string and do the conversion within java.
> Cheers
> 
> POST /axis/CalcArr.jws HTTP/1.0
> Content-Type: text/xml; charset=utf-8
> Accept: application/soap+xml, application/dime,
> multipart/related, text/*
> User-Agent: Axis/1.4
> Host: 127.0.0.1:8088
> Cache-Control: no-cache
> Pragma: no-cache
> SOAPAction: ""
> Content-Length: 334
> 
> 
>
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";;
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";;
>
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";;>
>   
>  http://tempuri.org/";;>
> ITAMWA==
> FxdiAg==
>  
>   
>
> 
> 
> HTTP/1.1 200 OK
> Server: Apache-Coyote/1.1
> Set-Cookie:
> JSESSIONID=887A1E5E02B52B88387CAD9B3FEA7F6C;
> Path=/axis
> Content-Type: text/xml;charset=utf-8
> Date: Fri, 31 Aug 2007 10:16:54 GMT
> Connection: close
> 
> 
>
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";;
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";;
>
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";;>
>   
>  
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";;
> xmlns:ns1="http://tempuri.org/";;>
>  xsi:type="xsd:base64Binary">OEduWg==
>  
>   
>
> 
> 
> --- Thomas Beaujard <[EMAIL PROTECTED]> wrote:
> 
> > Thanks for your answer, I will try to explain my
> > problem more precisely:
> > In fact, I generated my code from WSDL2java with a
> > wsdl file and a xsd file as input. In the xsd file
> I
> > defined the response as being xsd:base64binary.
> > Here is the service definition in my
> > server-config.wsdd:
> >   > style="document" use="literal">
> >qname="getDocument"
> > returnQName="ns1:GMDSRESPCT"
> > returnType="ns1:GMDSRESPCT" soapAction=""
> > xmlns:ns1="...">
> > > type="ns1:GMDSREQCT"/>
> > > qname="ns1:GMDSERRCT" type="ns1:GMDSERRCT"/>
> >   
> >> value="getDocument"/>
> >value="1.2"/>
> >> value="DocContent"/>
> >>
>
value="com.webservice.GetDocumentSoapBindingImpl"/>
> >> value="DocContent"/>
> >> value=""/>
> >> value="DocContentService"/>
> >> value=".."/>
> >>
>
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
> > encodingStyle="" qname="ns2:>GMDSREQCT"
> >
>
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
> > type="java:com..messages.GMDSREQCT"
> > xmlns:ns2="."/>
> >>
>
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
> > encodingStyle="" qname="ns3:>GMDSRESPCT"
> >
>
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
> > type="java:com.messages.GMDSRESPCT"
> > xmlns:ns3="."/>
> >>
>
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
> > encodingStyle="" qname="ns4:>GMDSERRCT"
> >
>
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
> > type="java:commessages.GMDSERRCT"
> > xmlns:ns4="..."/>
> >  
> > 
> > Here is the class corresponding to the response :
> >  public class GMDSRESPCT implements Serializable {
> > private byte[] CONTENT;
> > private 
> > public GMDSRESPCT() {
> > }
> > 
> > public GMDSRESPCT(byte[] CONTENT) {
> >this.CONTENT = CONTENT;
> > }
> > 
> > public byte[] getCONTENT() {
> > return CONTENT;
> > }
> > 
> > So the web service should return an object
> > GMDSRESPCT. But I get the error and when I use
> > tcpmon to see the messages exchanged, I notice
> that
> > the response include  tag for every
> single
> > byte instead of having the array of byte within
> the
> > tag .
> > 
> > Hope it's not too messy.
> > 
> > Cheers
> > 
> > Thom
> > 
> > 
> > - Message d'origine 
> > De : WJ Krpelan <[EMAIL PROTECTED]>
> > À : axis-dev@ws.apache.org
> > Envoyé le : Jeudi, 30 Août 2007, 17h18mn 03s
> > Objet : Re: Tr : Axis problem returning byteArray
> > 
> > 
> 
=== message truncated ===

Re: Transactional JMS.

2007-09-04 Thread Rajith Attapattu

Maciej,

Currently there are a few problems with doing this. Lets identify the issues
a) We create a new connection for each invocation (sending messages)
b) Hence we create a new session for each invocation.
c) When creating a session for receiving as well as sending transacted is
set to true - no way to configure this.
d) We currently don't expose the session outside for both transport
sender/receiver, hence you cannot call commit or rollback on it.
e) Since u are using JTA I assume it's a distributed transaction. So we need
to create an XASession instead of a normal session.

This can be done and here are some ideas. I spoke with Asankha briefly on
this topic once.

a) Asankha pointed out a new connection is created for each invocation as
each service could have different connection params. (different provider,
username,..etc)
The downside of this is that creating new connections is an expensive
operation. Especially if the same service sends frequent messages it will
keep recreating connections. We should make this behaviour configurable.
I would like if we could reuse connections where we can. Also in most cases
a deployment would use a single provider and we can definitely optimize for
this case.
For this case we can get away with a single connection per axis2 instance
and session per service (one for sending and one for listening).

If we can name connections then we could reuse them when defining services.
This way we can check if an existing connection by that name exists and
reuse it, if not create one.

When we reuse connections there will be keep alive issues. Most providers
have convenient and cheap ways of sending ping/pongs to keep the connection
alive.
So in a case where the service sends messages frequently this will help. If
the service sends messages rarely and the cost of keep alive is greater than
the occasional connection creation then the user can disable the reuse
option.

b) Creating a new session for each invocation is not optimal. Since the
context hierarchy determines the scope of services and is independent of the
transport session it's ok to reuse a JMS session underneath where ever it
makes sense. If we introduce some thing similar to scope="transport-session"
in HTTP for JMS, then we can allow users to directly use the underlying JMS
transport similar to the way HTTP session is used.

c) We can make the transacted property configurable. By default it will be
false.

Ex: true

d) We need to expose the JMS session. Can we put the JMS session somewhere
in the context hierarchy?
I also see a getSessionContext in TransportListener interface, However
SessionContext is written with HTTP in mind and is not generic enough.
If we put it in the content hierarchy then the service author can retrieve
it and call commit, rollback etc.

e) We can create an XASession  instead of a normal session based on
configuration, provided the JMS provider supports it.
Ex. true

Comments are very much appreciated.

Regards,

Rajith

On 9/4/07, Maciej Szefler <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I've been unable to find anything on the topic in Nabble, so I thought I'd
> ping you all, and Asankha in particular regarding transactions in the JMS
> transport implementation.
> In ODE we'd like to be able to consume/send messages through AXIS' JMS
> transport. That in itself is not a problem. However, we'd like the
> send/receive to be in enrolled in a JTA transaction. Any pointers on how
> this can be done?
>
> -Maciej
>

Re: [Axis2] Test Failure

2007-09-04 Thread Brian De Pradine

Thanks, it's fixed now.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Deepal jayasinghe <[EMAIL PROTECTED]> wrote on 04/09/2007 12:10:02:

> Yes , I am also getting the same exception
> 
> Thanks
> Deepal
> >
> > Hello Amila,
> >
> > Sorry, but this still doesn't work. I get the same error as before, as
> > shown below. I think there may be an
> > extra slash before the drive letter, F: in this case, that probably
> > shouldn't be there.
> >
> > Running org.apache.axis2.xmlbeans.WSDL2Java1Test
> > Retrieving schema at 'wsat.xsd', relative to
> > 'file:*/F:/Drivers/axis2/modules/xml*
> > *beans/test-resources/'.*
> > 04-Sep-2007 11:38:03
> > org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2Entity
> > Resolver resolveEntity
> > INFO: Resolving schema with publicId [null] and systemId [wsat.xsd]
> > org.apache.axis2.wsdl.codegen.CodeGenerationException:
> > org.apache.axis2.wsdl.cod
> > egen.CodeGenerationException: java.lang.RuntimeException: Schema
> > writing failed!
> > at
> > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.
> generate(CodeGenerationEngine.java:265)
> >
> > at
> > org.apache.axis2.xmlbeans.WSDL2JavaSuccessTestBase.
> codeGenerate(WSDL2JavaSuccessTestBase.java:172)
> >
> > at
> > org.apache.axis2.xmlbeans.WSDL2JavaSuccessTestBase.
> generateAndCompile(WSDL2JavaSuccessTestBase.java:157)
> >
> > at
> > org.apache.axis2.xmlbeans.WSDL2JavaSuccessTestBase.
> testWSDLFile(WSDL2JavaSuccessTestBase.java:104)
> >
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> > sun.reflect.NativeMethodAccessorImpl.
> invoke(NativeMethodAccessorImpl.java:39)
> >
> > at
> > sun.reflect.DelegatingMethodAccessorImpl.
> invoke(DelegatingMethodAccessorImpl.java:25)
> >
> > at java.lang.reflect.Method.invoke(Method.java:585)
> > at junit.framework.TestCase.runTest(TestCase.java:168)
> > at junit.framework.TestCase.runBare(TestCase.java:134)
> > at junit.framework.TestResult$1.protect(TestResult.java:110)
> > at 
junit.framework.TestResult.runProtected(TestResult.java:128)
> > at junit.framework.TestResult.run(TestResult.java:113)
> > at junit.framework.TestCase.run(TestCase.java:124)
> > at junit.framework.TestSuite.runTest(TestSuite.java:232)
> > at junit.framework.TestSuite.run(TestSuite.java:227)
> > at
> > org.junit.internal.runners.OldTestClassRunner.
> run(OldTestClassRunner.java:76)
> >
> > at
> > org.apache.maven.surefire.junit4.JUnit4TestSet.
> execute(JUnit4TestSet.java:62)
> >
> > at
> > org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.
> executeTestSet(AbstractDirectoryTestSuite.java:138)
> >
> > at
> > org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.
> execute(AbstractDirectoryTestSuite.java:125)
> >
> > at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> > sun.reflect.NativeMethodAccessorImpl.
> invoke(NativeMethodAccessorImpl.java:39)
> >
> > at
> > sun.reflect.DelegatingMethodAccessorImpl.
> invoke(DelegatingMethodAccessorImpl.java:25)
> >
> > at java.lang.reflect.Method.invoke(Method.java:585)
> > at
> > org.apache.maven.surefire.booter.SurefireBooter.
> runSuitesInProcess(SurefireBooter.java:290)
> >
> > at
> > org.apache.maven.surefire.booter.SurefireBooter.
> main(SurefireBooter.java:818)
> >
> > Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException:
> > java.lang.RuntimeException: Schema writing failed!
> > at
> > org.apache.axis2.wsdl.codegen.emitter.
> AxisServiceBasedMultiLanguageEmitter.
> emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1371)
> >
> > at
> > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.
> generate(CodeGenerationEngine.java:247)
> >
> > ... 26 more
> > Caused by: java.lang.RuntimeException: Schema writing failed!
> > at
> > org.apache.axis2.wsdl.codegen.writer.SchemaWriter.
> writeSchema(SchemaWriter.java:59)
> >
> > at
> > org.apache.axis2.wsdl.codegen.emitter.
> AxisServiceBasedMultiLanguageEmitter.
> writeWSDLFiles(AxisServiceBasedMultiLanguageEmitter.java:1411)
> >
> > at
> > org.apache.axis2.wsdl.codegen.emitter.
> AxisServiceBasedMultiLanguageEmitter.
> emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1342)
> >
> > ... 27 more
> > Caused by: java.io.FileNotFoundException:
> > F:\Drivers\axis2\modules\xmlbeans\out_
> > put_classes\test1\resources\file:*\F:
> \Drivers\axis2\modules\xmlbeans\test-resources\wsat.xsd*
> > (The filename, directory name, or volume label syntax is incorrect)
> > at java.io.FileOutputStream.open(Native Method)
> > at java.io.Fi

Transactional JMS.

2007-09-04 Thread Maciej Szefler

Hi,

I've been unable to find anything on the topic in Nabble, so I thought I'd
ping you all, and Asankha in particular regarding transactions in the JMS
transport implementation.
In ODE we'd like to be able to consume/send messages through AXIS' JMS
transport. That in itself is not a problem. However, we'd like the
send/receive to be in enrolled in a JTA transaction. Any pointers on how
this can be done?

-Maciej

[jira] Commented: (AXIS2-1820) javax.xml.stream.XMLStreamException: problem accessing the parser when using NTLM and stubs generated by xmlbeans

2007-09-04 Thread Patrik Nordwall (JIRA)


[ 
https://issues.apache.org/jira/browse/AXIS2-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524713
 ] 

Patrik Nordwall commented on AXIS2-1820:


setAllowedRetry doesn't work for me with basic auth and xmlbeans.

I have found this solution:
http://www.nabble.com/http-authentication-with-Axis2-tf3436522.html#a9581568

ArrayList authSchemes = new ArrayList(); 
authSchemes.add(HttpTransportProperties.Authenticator.BASIC); 

HttpTransportProperties.Authenticator auth = new 
HttpTransportProperties.Authenticator(); 

auth.setPreemptiveAuthentication(true); 
auth.setAuthSchemes(authSchemes); 
auth.setUsername(username); 
auth.setPassword(password); 

client.getOptions().setProperty(HTTPConstants.AUTHENTICATE, auth);   


> javax.xml.stream.XMLStreamException: problem accessing the parser when using 
> NTLM and stubs generated by xmlbeans
> -
>
> Key: AXIS2-1820
> URL: https://issues.apache.org/jira/browse/AXIS2-1820
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>Affects Versions: 1.1
> Environment: jdk 1.5.0_8. Windows xp servicepack 2
>Reporter: Tor Jonsson
>Assignee: Deepal Jayasinghe
>Priority: Critical
> Attachments: SendPageClient.java
>
>
> When generating a java client with xmlbeans NTLM authentication breaks:
> WSDL (Test.wsdl):
> 
> http://schemas.xmlsoap.org/wsdl/soap/"; 
> xmlns:tns="http://www.example.org/Test/"; 
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; 
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; name="Test" 
> targetNamespace="http://www.example.org/Test/";>
> 
> http://www.example.org/Test/";>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  transport="http://schemas.xmlsoap.org/soap/http"/>
> 
> http://www.example.org/Test/NewOperation"/>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> http://www.host.com/Services.asmx"/>
> 
> 
> 
> Command to generate Java cllient stubs:
> wsdl2java -uri Test.wsdl -d xmlbeans
> ClientTest.java
> package com.volvo.ums.test;
> import java.rmi.RemoteException;
> import java.util.ArrayList;
> import java.util.List;
> import org.apache.axis2.client.Options;
> import org.apache.axis2.transport.http.HTTPConstants;
> import org.apache.axis2.transport.http.HttpTransportProperties;
> import org.example.www.test.NewOperationDocument;
> import org.example.www.test.NewOperationResponseDocument;
> import org.example.www.test.TestStub;
> import org.example.www.test.NewOperationDocument.NewOperation;
> public class ClientTest {
>   public static void main(String[] args) {
>   ClientTest cli = new ClientTest();
>   
>   try {
>   cli.doTest();
>   } catch (RemoteException e) {
>   e.printStackTrace();
>   }
>   }
>   public void doTest( )throws RemoteException
>   {
>   TestStub stub = new TestStub( 
> "http://www.host.com/Services.asmx"; );
>   Options opts = stub._getServiceClient().getOptions();
>   HttpTransportProperties.Authenticator auth = 
> getAuthProperties();
>   opts.setProperty(HTTPConstants.AUTHENTICATE, auth );
>   NewOperationDocument doc = 
> NewOperationDocument.Factory.newInstance();
>   NewOperation operation = doc.addNewNewOperation();
>   operation.setIn( "Hello" );
>   NewOperationResponseDocument resp = stub.NewOperation( doc );
>   }
>   /**
>* generates the properties needed for NTLM authentication 
>* 
>*/
>   public HttpTransportProperties.Authenticator getAuthProperties()
>   {
>   HttpTransportProperties.Authenticator auth = new 
> HttpTransportProperties.Authenticator();
>   List l = new ArrayList();
>   l.add( HttpTransportProperties.Authenticator.NTLM );
>   auth.setAuthSchemes(l);
>   auth.setUsername( "username" );
>   auth.setPassword("password");
>   auth.setDomain( "domain" );
>   auth.setHost( "www.host.com" );
>   auth.setPort( 80 );
>   return auth;
>   }
> }
> StackTrace:
> org.apache.axis2.AxisFault: problem accessing the parser. Parser already 
> accessed!; nested exception is: 
>   javax.xml.stream.XMLStreamException: problem accessing the parser. 
> Parser already accessed!; nested exception is: 
>   org.apache.axis2.AxisFault: problem accessing the parser. Parser 
> already accessed!; nested exception is: 
>   javax.xml.stream.XMLStreamException: problem accessing the parser. 
> Parser already accessed!; nested exception is: 
>   org.apache

[jira] Commented: (AXIS2-3164) wsdl2java ADB client creates 'staticabstract' instead of 'static abstract'

2007-09-04 Thread Nikolaus Krismer (JIRA)


[ 
https://issues.apache.org/jira/browse/AXIS2-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524705
 ] 

Nikolaus Krismer commented on AXIS2-3164:
-

same problem here
...i run the wsdl2java operation using ANT:














It seems to only happen in wsdl-fault definitions that are static. generated 
code looks like the following (MyFault is declared in a seperat .xsd file using 
abstract="true"):

public staticabstract class MyFault
implements org.apache.axis2.databinding.ADBBean{


Hope this helps a little...

> wsdl2java ADB client creates 'staticabstract' instead of 'static abstract'
> --
>
> Key: AXIS2-3164
> URL: https://issues.apache.org/jira/browse/AXIS2-3164
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: adb, codegen, databinding, wsdl
>Affects Versions: 1.3
> Environment: debian testing, Java 1.5.0_11, eclipse 3.2.1
>Reporter: Petr Kremen
>
> wsdl2java ADB client creates 'staticabstract' instead of 'static abstract'.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

axis-castor : unable to find fieldDescriptor

2007-09-04 Thread Thomas Beaujard

Hello

I am trying the example from this link : 
http://www.ibm.com/developerworks/webservices/library/ws-castor/

And I get the following error :
org.xml.sax.SAXException:
Unable to marshall between XML and Castor Objects :unable to find
FieldDescriptor for 'DOC_ID' in ClassDescriptor of GMDSREQCT

I
have seen thread where people had the same problem as me. One person
said that we have to modify the CastorSerializer class as explained in
this link:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg15150.html

However, I cannot access this link. Does anyone have a solution?

Cheers

Thom







  



  
_ 
Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail

Re : Re : Tr : Axis problem returning byteArray

2007-09-04 Thread Thomas Beaujard

Hi

Here is the SOAP-trace:

HTTP/1.1 200 OK Content-Type: text/xml;charset=utf-8 Date: Tue, 04 Sep 2007 
11:10:43 GMT Server: Apache-Coyote/1.1 Connection: close  



37
80
68
70
45
4913



As you can see the tag CONTENT appears many times with a type byte, whereas it 
should only appear once with the type base64binary.
I cannot use the xs:string workaround... do you have any other idea?

Thanks for your help

Thom

- Message d'origine 
De : WJ Krpelan <[EMAIL PROTECTED]>
À : axis-dev@ws.apache.org
Envoyé le : Vendredi, 31 Août 2007, 12h24mn 28s
Objet : Re: Re : Tr : Axis problem returning byteArray

Hi
Could you provice a SOAP-Trace (TCPMon)? Would it look
similar to the one below?
A less than satisfactory workaround, if you control
both sides of the wire, would be to change type to
xs:string and do the conversion within java.
Cheers

POST /axis/CalcArr.jws HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime,
multipart/related, text/*
User-Agent: Axis/1.4
Host: 127.0.0.1:8088
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: ""
Content-Length: 334


   http://schemas.xmlsoap.org/soap/envelope/";;
xmlns:xsd="http://www.w3.org/2001/XMLSchema";;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";;>
  
 http://tempuri.org/";;>
ITAMWA==
FxdiAg==
 
  
   


HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Set-Cookie:
JSESSIONID=887A1E5E02B52B88387CAD9B3FEA7F6C;
Path=/axis
Content-Type: text/xml;charset=utf-8
Date: Fri, 31 Aug 2007 10:16:54 GMT
Connection: close


   http://schemas.xmlsoap.org/soap/envelope/";;
xmlns:xsd="http://www.w3.org/2001/XMLSchema";;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";;>
  
 http://schemas.xmlsoap.org/soap/encoding/";;
xmlns:ns1="http://tempuri.org/";;>
OEduWg==
 
  
   


--- Thomas Beaujard <[EMAIL PROTECTED]> wrote:

> Thanks for your answer, I will try to explain my
> problem more precisely:
> In fact, I generated my code from WSDL2java with a
> wsdl file and a xsd file as input. In the xsd file I
> defined the response as being xsd:base64binary.
> Here is the service definition in my
> server-config.wsdd:
>   style="document" use="literal">
>returnQName="ns1:GMDSRESPCT"
> returnType="ns1:GMDSRESPCT" soapAction=""
> xmlns:ns1="...">
> type="ns1:GMDSREQCT"/>
> qname="ns1:GMDSERRCT" type="ns1:GMDSERRCT"/>
>   
>value="getDocument"/>
>   
>value="DocContent"/>
>   
value="com.webservice.GetDocumentSoapBindingImpl"/>
>value="DocContent"/>
>value=""/>
>value="DocContentService"/>
>value=".."/>
>   
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
> encodingStyle="" qname="ns2:>GMDSREQCT"
>
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
> type="java:com..messages.GMDSREQCT"
> xmlns:ns2="."/>
>   
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
> encodingStyle="" qname="ns3:>GMDSRESPCT"
>
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
> type="java:com.messages.GMDSRESPCT"
> xmlns:ns3="."/>
>   
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
> encodingStyle="" qname="ns4:>GMDSERRCT"
>
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
> type="java:commessages.GMDSERRCT"
> xmlns:ns4="..."/>
>  
> 
> Here is the class corresponding to the response :
>  public class GMDSRESPCT implements Serializable {
> private byte[] CONTENT;
> private 
> public GMDSRESPCT() {
> }
> 
> public GMDSRESPCT(byte[] CONTENT) {
>this.CONTENT = CONTENT;
> }
> 
> public byte[] getCONTENT() {
> return CONTENT;
> }
> 
> So the web service should return an object
> GMDSRESPCT. But I get the error and when I use
> tcpmon to see the messages exchanged, I notice that
> the response include  tag for every single
> byte instead of having the array of byte within the
> tag .
> 
> Hope it's not too messy.
> 
> Cheers
> 
> Thom
> 
> 
> - Message d'origine 
> De : WJ Krpelan <[EMAIL PROTECTED]>
> À : axis-dev@ws.apache.org
> Envoyé le : Jeudi, 30 Août 2007, 17h18mn 03s
> Objet : Re: Tr : Axis problem returning byteArray
> 
> 
> Hello 
> you can't simply send binary data as on the
> transport
> level its converted to xml, which is basically plain
> text.
> 
> One simple possibility would be to use datatype
> base64binary
> Cheers,
> 
> --- Thomas Beaujard <[EMAIL PROTECTED]> wrote:
> 
> > Hello,
> >  
> > I'm using Axis 1.4.
> > I have a document style web service which returns
> a
> > byteArray (actually a pdf file).
> > When I invoke the web service, I get the following
> > error:
> >  
> > org.apache.axis.encoding.ser.BeanPropertyTarget
> set
> > Could not convert java.lang.Byte to bean field
> > 'CONTENT', type [B
> >  
> > Does anyone have encounter similar problem?
> >  
> > Thanks in advance,
> >  
> > Thom
> > 
> > 
> > 
> > 
> > 
> > 
> >

Re: [Axis2] Test Failure

2007-09-04 Thread Deepal jayasinghe

Yes , I am also getting the same exception

Thanks
Deepal
>
> Hello Amila,
>
> Sorry, but this still doesn't work. I get the same error as before, as
> shown below. I think there may be an
> extra slash before the drive letter, F: in this case, that probably
> shouldn't be there.
>
> Running org.apache.axis2.xmlbeans.WSDL2Java1Test
> Retrieving schema at 'wsat.xsd', relative to
> 'file:*/F:/Drivers/axis2/modules/xml*
> *beans/test-resources/'.*
> 04-Sep-2007 11:38:03
> org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2Entity
> Resolver resolveEntity
> INFO: Resolving schema with publicId [null] and systemId [wsat.xsd]
> org.apache.axis2.wsdl.codegen.CodeGenerationException:
> org.apache.axis2.wsdl.cod
> egen.CodeGenerationException: java.lang.RuntimeException: Schema
> writing failed!
> at
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:265)
>
> at
> org.apache.axis2.xmlbeans.WSDL2JavaSuccessTestBase.codeGenerate(WSDL2JavaSuccessTestBase.java:172)
>
> at
> org.apache.axis2.xmlbeans.WSDL2JavaSuccessTestBase.generateAndCompile(WSDL2JavaSuccessTestBase.java:157)
>
> at
> org.apache.axis2.xmlbeans.WSDL2JavaSuccessTestBase.testWSDLFile(WSDL2JavaSuccessTestBase.java:104)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:585)
> at junit.framework.TestCase.runTest(TestCase.java:168)
> at junit.framework.TestCase.runBare(TestCase.java:134)
> at junit.framework.TestResult$1.protect(TestResult.java:110)
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.framework.TestResult.run(TestResult.java:113)
> at junit.framework.TestCase.run(TestCase.java:124)
> at junit.framework.TestSuite.runTest(TestSuite.java:232)
> at junit.framework.TestSuite.run(TestSuite.java:227)
> at
> org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.java:76)
>
> at
> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
>
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
>
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
>
> at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290)
>
> at
> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818)
>
> Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException:
> java.lang.RuntimeException: Schema writing failed!
> at
> org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1371)
>
> at
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:247)
>
> ... 26 more
> Caused by: java.lang.RuntimeException: Schema writing failed!
> at
> org.apache.axis2.wsdl.codegen.writer.SchemaWriter.writeSchema(SchemaWriter.java:59)
>
> at
> org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.writeWSDLFiles(AxisServiceBasedMultiLanguageEmitter.java:1411)
>
> at
> org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1342)
>
> ... 27 more
> Caused by: java.io.FileNotFoundException:
> F:\Drivers\axis2\modules\xmlbeans\out_
> put_classes\test1\resources\file:*\F:\Drivers\axis2\modules\xmlbeans\test-resources\wsat.xsd*
> (The filename, directory name, or volume label syntax is incorrect)
> at java.io.FileOutputStream.open(Native Method)
> at java.io.FileOutputStream.(FileOutputStream.java:179)
> at java.io.FileOutputStream.(FileOutputStream.java:131)
> at
> org.apache.axis2.wsdl.codegen.writer.SchemaWriter.writeSchema(SchemaWriter.java:50)
>
> ... 29 more
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 6.89
> sec <<< FAILURE!
>
> Cheers
>
> Brian DePradine
> Web Services Development
> IBM Hursley
> External  +44 (0) 1962 816319 Internal 246319
>
> If you can't find the time to do it right the first time, where will
> you find the time to do it again?
>
>
> "Amila Suriarachchi" <[EMAIL PR

Re: [Axis2] Test Failure

2007-09-04 Thread Brian De Pradine

Hello Amila,

Sorry, but this still doesn't work. I get the same error as before, as 
shown below. I think there may be an
extra slash before the drive letter, F: in this case, that probably 
shouldn't be there.

Running org.apache.axis2.xmlbeans.WSDL2Java1Test
Retrieving schema at 'wsat.xsd', relative to 'file:
/F:/Drivers/axis2/modules/xml
beans/test-resources/'.
04-Sep-2007 11:38:03 
org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2Entity
Resolver resolveEntity
INFO: Resolving schema with publicId [null] and systemId [wsat.xsd]
org.apache.axis2.wsdl.codegen.CodeGenerationException: 
org.apache.axis2.wsdl.cod
egen.CodeGenerationException: java.lang.RuntimeException: Schema writing 
failed!
at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:265)
at 
org.apache.axis2.xmlbeans.WSDL2JavaSuccessTestBase.codeGenerate(WSDL2JavaSuccessTestBase.java:172)
at 
org.apache.axis2.xmlbeans.WSDL2JavaSuccessTestBase.generateAndCompile(WSDL2JavaSuccessTestBase.java:157)
at 
org.apache.axis2.xmlbeans.WSDL2JavaSuccessTestBase.testWSDLFile(WSDL2JavaSuccessTestBase.java:104)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at 
org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.java:76)
at 
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at 
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290)
at 
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818)
Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: 
java.lang.RuntimeException: Schema writing failed!
at 
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1371)
at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:247)
... 26 more
Caused by: java.lang.RuntimeException: Schema writing failed!
at 
org.apache.axis2.wsdl.codegen.writer.SchemaWriter.writeSchema(SchemaWriter.java:59)
at 
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.writeWSDLFiles(AxisServiceBasedMultiLanguageEmitter.java:1411)
at 
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:1342)
... 27 more
Caused by: java.io.FileNotFoundException: 
F:\Drivers\axis2\modules\xmlbeans\out_
put_classes\test1\resources\file:
\F:\Drivers\axis2\modules\xmlbeans\test-resources\wsat.xsd (The filename, 
directory name, or volume label syntax is incorrect)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.(FileOutputStream.java:179)
at java.io.FileOutputStream.(FileOutputStream.java:131)
at 
org.apache.axis2.wsdl.codegen.writer.SchemaWriter.writeSchema(SchemaWriter.java:50)
... 29 more
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 6.89 sec 
<<< FAILURE!

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


"Amila Suriarachchi" <[EMAIL PROTECTED]> wrote on 04/09/2007 
05:58:32:

> I am working on linux and had set the file seperator as "/"
> now I replace it with  File.separator. please try it now.

> If you can't find the time to do it right the first time, where will
> you find the time to do it ag

[jira] Commented: (AXIS2-2996) CORBA module for Axis2

2007-09-04 Thread Deepal Jayasinghe (JIRA)


[ 
https://issues.apache.org/jira/browse/AXIS2-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524670
 ] 

Deepal Jayasinghe commented on AXIS2-2996:
--

Thx for the patch I will apply that today , once Amila fix the build problem

> CORBA module for Axis2
> --
>
> Key: AXIS2-2996
> URL: https://issues.apache.org/jira/browse/AXIS2-2996
> Project: Axis 2.0 (Axis2)
>  Issue Type: New Feature
>  Components: modules
>Affects Versions: nightly
> Environment: CORBA, Linux, Windows, Java 5
>Reporter: Eranga Jayasundera
>Assignee: Deepal Jayasinghe
>Priority: Minor
> Attachments: corba.2.tar.gz, corba.odt, corba.patch.zip
>
>
> I have developed a CORBA module for Axis2. It is based on pluggable deployer 
> architecture. This module can act as a bridge between a CORBA server and a 
> web service client. The patch against the latest trunk and a user guide is 
> attached.
> This module uses Apache Yoko as the default CORBA implementation in RUNTIME. 
> (can be overridden) Since Yoko is not yet available in maven2 remote 
> repositories I have commented them from pom.xml file. Yoko requires JDK 1.5.
> This module depends on Antlr also. The classes in 
> org.apache.axis2.corba.idl.parser were generated by Antlr using idl.g. Please 
> refer the attached guide for more information.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (AXIS2-2996) CORBA module for Axis2

2007-09-04 Thread Eranga Jayasundera (JIRA)


 [ 
https://issues.apache.org/jira/browse/AXIS2-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eranga Jayasundera updated AXIS2-2996:
--

Attachment: corba.2.tar.gz

Since the first patch seems to be outdated I have attached a new patch 
(corba.2.tar.gz) based on the latest Axis2 source code.

The idl.g file available in the patch is based on the IDL grammar file prepared 
by Jim Coker and Gary Duzan (http://www.antlr.org/grammar/1072891676218/idl.g). 
I hope there are no license issues. (Apache Yoko project is also uses the same 
grammar file)


> CORBA module for Axis2
> --
>
> Key: AXIS2-2996
> URL: https://issues.apache.org/jira/browse/AXIS2-2996
> Project: Axis 2.0 (Axis2)
>  Issue Type: New Feature
>  Components: modules
>Affects Versions: nightly
> Environment: CORBA, Linux, Windows, Java 5
>Reporter: Eranga Jayasundera
>Assignee: Deepal Jayasinghe
>Priority: Minor
> Attachments: corba.2.tar.gz, corba.odt, corba.patch.zip
>
>
> I have developed a CORBA module for Axis2. It is based on pluggable deployer 
> architecture. This module can act as a bridge between a CORBA server and a 
> web service client. The patch against the latest trunk and a user guide is 
> attached.
> This module uses Apache Yoko as the default CORBA implementation in RUNTIME. 
> (can be overridden) Since Yoko is not yet available in maven2 remote 
> repositories I have commented them from pom.xml file. Yoko requires JDK 1.5.
> This module depends on Antlr also. The classes in 
> org.apache.axis2.corba.idl.parser were generated by Antlr using idl.g. Please 
> refer the attached guide for more information.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (AXIS2-3164) wsdl2java ADB client creates 'staticabstract' instead of 'static abstract'

Re: Regarding Axis 2 & Axis 1 coexistence

[jira] Created: (AXIS2-3167) Axis2, GSoap, and Character Sets

Re: [AXIS2] : Help required : getting a zip file using AXIS2 + AXIOM

AXIS2 : Help required : getting a zip file using AXIS2 + AXIOM

Fwd: AXIS2 : Help required : getting a zip file using AXIS2 + AXIOM

Re: Transactional JMS.

RE: Regarding Axis 2 & Axis 1 coexistence

Re: Transactional JMS.

Re: Regarding Axis 2 & Axis 1 coexistence

Regarding Axis 2 & Axis 1 coexistence

Re: axis-castor : unable to find fieldDescriptor

Re: Re : Re : Tr : Axis problem returning byteArray

Re: Transactional JMS.

Re: [Axis2] Test Failure

Transactional JMS.

[jira] Commented: (AXIS2-1820) javax.xml.stream.XMLStreamException: problem accessing the parser when using NTLM and stubs generated by xmlbeans

[jira] Commented: (AXIS2-3164) wsdl2java ADB client creates 'staticabstract' instead of 'static abstract'

axis-castor : unable to find fieldDescriptor

Re : Re : Tr : Axis problem returning byteArray

Re: [Axis2] Test Failure

Re: [Axis2] Test Failure

[jira] Commented: (AXIS2-2996) CORBA module for Axis2

[jira] Updated: (AXIS2-2996) CORBA module for Axis2

24 matches

Site Navigation

Mail list logo

Footer information