Antwort: Re: problems with ws and corba call in one client

[Juergen Haeussler]

Hi there,

we recently found the problem:

In util/src/network_handler.c - lines 239-240 the default behaviour of
socket creation through windows API gets changed:

setsockopt(INVALID_SOCKET, SOL_SOCKET, SO_OPENTYPE, (char *)sock_opt,
  sizeof(sock_opt));

As you can find in the MSDN documentation for SOL_SOCKET Socket Options,
one should not use this options:

(Embedded image moved to file: pic18467.jpg)
(Have a look at http://msdn2.microsoft.com/en-us/library/ms740532.aspx)

As we did comment out this two lines, everything worked correctly: the WS
call and subsequent Corba calls did work correctly.

Does anybody know whom to contact for a change request?

Regards,

Jürgen Häußler (IT/Hae)

--

IF - Fertigungsleitsysteme, Anwendungsintegration, Web-Anwendungen

Tel.: +49 (0)731 944-6118
--


   
 Samisa Abeysinghe 
 samisa.abeysingh 
 [EMAIL PROTECTED]   
An 
 Apache AXIS C User List   
 19.06.2007 11:45axis-c-user@ws.apache.org   
 Kopie 
   
  Bitte antwortenThema 
an   Re: problems with ws and  
  Apache AXIS C corba call in one client  
User List 
 [EMAIL PROTECTED] 
pache.org 
   
   
   




Juergen Haeussler wrote:
 Do we have to free anything else or to close any connections to the
server
 or something like that?
 (If we have a look at our network connections via netstat, we se that the
 connection to the jboss remains opened.)

There is no need to close any connections. Please have a look at
src/core/transport/http/sender/http_sender.c line number 259.
The block of code:
axutil_property_set_scope(property, env, AXIS2_SCOPE_REQUEST);
axutil_property_set_free_func(property, env,
axis2_http_client_free_void_arg);
axutil_property_set_value(property, env, sender-client);
axis2_msg_ctx_set_property(msg_ctx, env, AXIS2_HTTP_CLIENT, property);
Is supposed to free the connection to server.
 Is there anybody who can imagine what could conflict with corba calls out
 of the same client application?

Could it be something that the JBoss server is doing, with session
management or something like that?

Samisa...
 Thanks,

 Jürgen Häußler (IT/Hae)


--


 IF - Fertigungsleitsysteme, Anwendungsintegration, Web-Anwendungen

 Tel.: +49 (0)731 944-6118

--


 
 Wieland-Werke Aktiengesellschaft
 Vorstand:
 Harald Kroener, Sprecher
 Dr. Jörg Hanisch
 Werner T. Traa
 Dr. Ulrich Hartmann

 Vorsitzender des Aufsichtsrats:
 Dr.-Ing. Wolfgang Eychmüller
 Sitz der Gesellschaft: Ulm

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





--
Samisa Abeysinghe : http://www.bloglines.com/blog/samisa


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


Wieland-Werke Aktiengesellschaft
Vorstand:
Harald Kroener, Sprecher
Dr. Jörg Hanisch
Werner T. Traa
Dr. Ulrich Hartmann

Vorsitzender des Aufsichtsrats:
Dr.-Ing. Wolfgang Eychmüller
Sitz der Gesellschaft: Ulm
attachment: pic18467.jpg-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[AXIS2C] Operation Not Found

[Mark Nüßler]

hello users,

when i'm trying to request my generated c service,
i alway get the fault 'Operation Not Found'.

i am using latest c-svn, build myself
and latest java-nightly.

when does this occurs ?
what i am doing wrong ?
why the breakpoints i set in dll-project doesn't work ?

any suggestions ?

mfg derMark




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

|AXIS2] [AXIS2C] c-stubs: memset in axis2_TYPE_create missing

[Dr. Florian Steinborn]

Hi group,

I guess I found a problem in generated sources. I try to get in touch with  
Axis and play around with all the things... I have a service that returns  
an array of structures that contain all possible datatypes - also float  
and double.


I used this class for generating the wsdl:


public class Dat{
public long l;
public shorts;
public int  i;
public String   str;
public floatfl;
public double   dl;
}

The generated wsdl shows

xs:element name=Dat type=ns:Dat /
xs:complexType name=Dat
xs:sequence
xs:element name=dl type=xs:double /
xs:element name=fl type=xs:float /
xs:element name=i type=xs:int /
xs:element name=str nillable=true type=xs:string /
xs:element name=l type=xs:long /
xs:element name=s type=xs:short /
/xs:sequence
/xs:complexType

When you generate C-Server stubs the constructor function
shows:

AXIS2_EXTERN axis2_Dat_t* AXIS2_CALL
axis2_Dat_create(
const axutil_env_t *env )
{
axis2_Dat_t *Dat = NULL;

AXIS2_ENV_CHECK(env, NULL);

Dat = (axis2_Dat_t *) AXIS2_MALLOC(env-
allocator, sizeof(axis2_Dat_t));

/*  missing
 * memset( Dat, 0, sizeof(axis2_Dat_t));
 * *
 */

if(NULL == Dat)
{
AXIS2_ERROR_SET(env-error, AXIS2_ERROR_NO_MEMORY, AXIS2_FAILURE);
return NULL;
}
return Dat;
}

For more safety it would be desirable if the generation would add the  
memset() call. I did not initialize every field of the structure before  
returning it and the service crashed (with the server), when it tried to  
return the values. In that the generated function axis2_Date_serialize()  
is called. This function has a problem, as it tries to print (with  
sprintf()) all the numeric members of the Dat-struct into 64-bytes memory  
blocks. Printing a double with sprintf() this way into a 64-byte array  
will most likely crash, especially with uninitialized memory, as the  
resulting string will be longer than 64 bytes.


Unfortunately the user cannot call the memset himself after calling the  
constructor as the real length of the type is hidden in the module. I  
myself now know that I have to call the setter method for each member of a  
new struct.


Thanks,
Flori.

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

Re: Re: problems with ws and corba call in one client

[Dinesh Premalal]

Hi Juergen,
   Please find my comments inline.

On 6/21/07, Juergen Haeussler [EMAIL PROTECTED] wrote:



Hi there,

we recently found the problem:

In util/src/network_handler.c - lines 239-240 the default behaviour of
socket creation through windows API gets changed:

setsockopt(INVALID_SOCKET, SOL_SOCKET, SO_OPENTYPE, (char *)sock_opt,
  sizeof(sock_opt));

As you can find in the MSDN documentation for SOL_SOCKET Socket Options,
one should not use this options:

(Embedded image moved to file: pic18467.jpg)
(Have a look at http://msdn2.microsoft.com/en-us/library/ms740532.aspx)

As we did comment out this two lines, everything worked correctly: the WS
call and subsequent Corba calls did work correctly.

Does anybody know whom to contact for a change request?



Please create a Jira issue and attach your patch there. We may be able to
ship it with next release.

thanks,
Dinesh

--
http://xydinesh.wordpress.com/
GPG Key ID : A255955C
GPG Key Finger Print : C481 E5D4 C27E DC34 9257  0229 4F44 266E A255 955C

is Axis2 C ready for production environment ?

[Radoslav Dorcik]

Hello,

i'm trying to search some opensource lib for SOAP client communication in
C/C++.
I have been using for testing Axis C++ but it seems that it is not very
stable and not ready for production use (observed non-standard behavior,
segmentation faults). Is Axis C++ still developed ?

What is the status of Axis2 C ? Is version 1.0.0 stable and can be used in
production environment ?

Thanks,
Radoslav

Re: is Axis2 C ready for production environment ?

[Samisa Abeysinghe]

Radoslav Dorcik wrote:

Hello,

i'm trying to search some opensource lib for SOAP client communication 
in C/C++.
I have been using for testing Axis C++ but it seems that it is not 
very stable and not ready for production use (observed non-standard 
behavior, segmentation faults). Is Axis C++ still developed ?

Yes, I think Nadir is working on Axis C++ with few others. It is alive.


What is the status of Axis2 C ? Is version 1.0.0 stable and can be 
used in production environment ?
Well, as a developer of Axis2/C, I am tempted to say yes it is 
production ready. :) However, it would be best if you could test. If 
you have any problems, I hope the community would be happy to help.


Samisa...


Thanks,
Radoslav



--
Samisa Abeysinghe : http://www.wso2.org/ (WSO2 Oxygen Tank - Web Services 
Developers' Portal)


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

Regarding Article by Deepal Jaysinghe

[smitha.aldrin]

Hi

 

I read the article written by Deepal Jaysinghe

http://wso2.org/library/406 regarding service with out-only mep in
axis2.

 

It's written that

There are two main ways of writing an active service in Axis2:

 

1.Implementing service life cycle interface and starting the thread
inside the startUp method 

2.Deploying service in application scope and writing the thread
initialization code inside the init method of the service implementation
class

Article continues with the first one.

 

It is helpful If somebody can tell me which is the best way to go ahead

 

Thanks And Regards

Smitha Aldrin




The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email.
 
www.wipro.com

axis 1.4 IllegalArgumentException got in response

[Roman Heinrich]

Hi all,

i`m using oracle oc4j 10.1.3 with axis 1.4 bundled in my application. I 
have problem with running web service. Axis is not recognizing correctly 
arguments passed in soap request message.


SoapUi generated this soap request, which is not working:

soapenv:Envelope 
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; 
xmlns:ops=http://ishop.orange.iway.sk/OPSTypes/;

  soapenv:Header/
  soapenv:Body
 ops:Endpoint21/ops:Endpoint2
 ops:CId21/ops:CId2
  /soapenv:Body
/soapenv:Envelope

and i`ve got this response from axis:

soapenv:Envelope 
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:Body
 soapenv:Fault
faultcodesoapenv:Server.generalException/faultcode
faultstringTried to invoke method public 
sk.iway.orange.ishop.catalog.ProductRecordType 
sk.iway.orange.ishop.ProductSynchroServiceImpl.getProductNextRecord(long,long) 
throws 
java.rmi.RemoteException,sk.iway.orange.ishop.exceptions.TimeoutException,sk.iway.orange.ishop.exceptions.ServiceException,sk.iway.orange.ishop.exceptions.DatabaseException 
with arguments java.lang.Long,null.  The arguments do not match the 
signature.; nested exception is:

   java.lang.IllegalArgumentException/faultstring
detail
   ns1:hostname 
xmlns:ns1=http://xml.apache.org/axis/;AMD64x5/ns1:hostname

/detail
 /soapenv:Fault
  /soapenv:Body
/soapenv:Envelope

It seems, that axis is not recognising ops:CId2 argument.

My wsdl for service:

 ?xml version=1.0 encoding=UTF-8 ?
- # wsdl:definitions targetNamespace=*http://ishop.orange.iway.sk*; 
xmlns:tns3=*http://ishop.orange.iway.sk/catalog/*; 
xmlns:impl=*http://ishop.orange.iway.sk*; 
xmlns:intf=*http://ishop.orange.iway.sk*; 
xmlns:apachesoap=*http://xml.apache.org/xml-soap*; 
xmlns:wsdlsoap=*http://schemas.xmlsoap.org/wsdl/soap/*; 
xmlns:xsd=*http://www.w3.org/2001/XMLSchema*; 
xmlns:tns2=*http://ishop.orange.iway.sk/exceptions*; 
xmlns:tns1=*http://ishop.orange.iway.sk/OPSTypes/*; 
xmlns:wsdl=*http://schemas.xmlsoap.org/wsdl/*;

- # !--

WSDL created by Apache Axis version: 1.4
Built on Apr 22, 2006 (06:55:48 PDT)

 --
- # wsdl:types
- # schema xmlns=*http://www.w3.org/2001/XMLSchema*; 
targetNamespace=*http://ishop.orange.iway.sk/OPSTypes/*;

 import namespace=*http://ishop.orange.iway.sk/catalog/*; /
 import namespace=*http://ishop.orange.iway.sk/exceptions*; /
 element name=*Endpoint1* type=*xsd:long* /
 element name=*CId1* type=*xsd:long* /
 element name=*Endpoint2* type=*xsd:long* /
 element name=*CId2* type=*xsd:long* /
 element name=*OutProductRecord1* type=*tns3:productRecordType* /
 element name=*Endpoint3* type=*xsd:long* /
 element name=*ProductRecord1* type=*tns3:productRecordType* /
 element name=*OutProductRecord2* type=*tns3:productRecordType* /
 element name=*Endpoint4* type=*xsd:long* /
 element name=*CId3* type=*xsd:long* /
 element name=*ProductRecord2* type=*tns3:productRecordType* /
 element name=*CId4* type=*xsd:long* /
 element name=*Endpoint5* type=*xsd:long* /
 element name=*CId5* type=*xsd:long* /
 element name=*ProductRecord3* type=*tns3:productRecordType* /
 element name=*OutProductRecord3* type=*tns3:productRecordType* /
 element name=*ProductRecord4* type=*tns3:productRecordType* /
 element name=*Endpoint6* type=*xsd:long* /
 /schema
- # schema xmlns=*http://www.w3.org/2001/XMLSchema*; 
targetNamespace=*http://ishop.orange.iway.sk/exceptions*;

 import namespace=*http://ishop.orange.iway.sk/catalog/*; /
- # complexType name=*timeoutException*
- # sequence
 element name=*ExceptionCode* type=*xsd:int* /
 element name=*ExceptionMessage* nillable=*true* 
type=*xsd:string* /

 /sequence
 /complexType
 element name=*timeoutException* type=*tns2:timeoutException* /
- # complexType name=*serviceException*
- # sequence
 element name=*ExceptionMessage* nillable=*true* 
type=*xsd:string* /
 element name=*NestedExceptionStackTrace* nillable=*true* 
type=*xsd:string* /

 /sequence
 /complexType
 element name=*serviceException* type=*tns2:serviceException* /
- # complexType name=*databaseException*
- # sequence
 element name=*ExceptionCode* type=*xsd:int* /
 element name=*ExceptionMessage* nillable=*true* 
type=*xsd:string* /

 /sequence
 /complexType
 element name=*databaseException* type=*tns2:databaseException* /
- # complexType name=*implementedException*
- # sequence
 element name=*ExceptionCode* type=*xsd:int* /
 element name=*ExceptionMessage* nillable=*true* 
type=*xsd:string* /

 /sequence
 /complexType
 element name=*implementedException* 
type=*tns2:implementedException* /

 /schema
- # schema xmlns=*http://www.w3.org/2001/XMLSchema*; 
targetNamespace=*http://ishop.orange.iway.sk/catalog/*; 
elementFormDefault=*qualified*

 import namespace=*http://ishop.orange.iway.sk/exceptions*; /
- # complexType name=*productIdentifierType*
- # sequence
 element name=*productPartNumber* nillable=*true* 
type=*xsd:string* 

Re: Deploy simple service class

[Alexey Zavizionov]

Thanks, I have read that.
You can deploy a service by simply taking this hierarchy of files and
copying it to the webapps directory of your servlet engine. This is
known as the exploded format. You can also compress your documents
into an *.aar file, similar to a *.jar file, and place the *.aar file
directly in the servlet engine's webapps directory.

If I want to compile services as jar and put it into
application_server_lib directory and within some war ( e.g.
portal.war) just change web.inf to add axises' servlets, so how will
be service deployed ?

Alexey

On 6/20/07, Chad DeBauch [EMAIL PROTECTED] wrote:

Take a look at the quick start guide.
http://ws.apache.org/axis2/1_2/quickstartguide.html

Chad

On 6/20/07, Alexey Zavizionov
[EMAIL PROTECTED] wrote:
 How can i do to deploy simple java class (within jar file) as axis2
service?


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






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

Re: [Axis 2] Minimal set of Jars for client application.

[Ognjen Blagojevic]

Hi Jakub,

I am trying to put together an Axis2 1.2 client application that uses 
ADB. Can anybody tell me what the minimal set of jar files is? I want to 
avoid putting in the whole distribution.


Try this thread:

http://mail-archives.apache.org/mod_mbox/ws-axis-user/200702.mbox/[EMAIL 
PROTECTED]

Regards,
Ognjen

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

Re: axis 1.4 IllegalArgumentException got in response

[omatzura]

Hi Roman,

thanks.. this is a bit strange, your operations input message has defined
several parts but it is not used with a RPC soap-binding, you will probably
either need to change the style for the binding from document to rpc
(probably just a setting somewhere), or refactor the input message to
contain one root element/argument which holds the other two
elements/arguments..

hope this makes sense :-)

regards!

/Ole
eviware.com


Roman Heinrich-2 wrote:
 
 Hi all,
 
 i`m using oracle oc4j 10.1.3 with axis 1.4 bundled in my application. I 
 have problem with running web service. Axis is not recognizing correctly 
 arguments passed in soap request message.
 
 SoapUi generated this soap request, which is not working:
 
 soapenv:Envelope 
 xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; 
 xmlns:ops=http://ishop.orange.iway.sk/OPSTypes/;
soapenv:Header/
soapenv:Body
   ops:Endpoint21/ops:Endpoint2
   ops:CId21/ops:CId2
/soapenv:Body
 /soapenv:Envelope
 
 and i`ve got this response from axis:
 
 soapenv:Envelope 
 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:Body
   soapenv:Fault
  faultcodesoapenv:Server.generalException/faultcode
  faultstringTried to invoke method public 
 sk.iway.orange.ishop.catalog.ProductRecordType 
 sk.iway.orange.ishop.ProductSynchroServiceImpl.getProductNextRecord(long,long)
  
 throws 
 java.rmi.RemoteException,sk.iway.orange.ishop.exceptions.TimeoutException,sk.iway.orange.ishop.exceptions.ServiceException,sk.iway.orange.ishop.exceptions.DatabaseException
  
 with arguments java.lang.Long,null.  The arguments do not match the 
 signature.; nested exception is:
 java.lang.IllegalArgumentException/faultstring
  detail
 ns1:hostname 
 xmlns:ns1=http://xml.apache.org/axis/;AMD64x5/ns1:hostname
  /detail
   /soapenv:Fault
/soapenv:Body
 /soapenv:Envelope
 
 It seems, that axis is not recognising ops:CId2 argument.
 
 My wsdl for service:
 
   ?xml version=1.0 encoding=UTF-8 ?
 - # wsdl:definitions targetNamespace=*http://ishop.orange.iway.sk*; 
 xmlns:tns3=*http://ishop.orange.iway.sk/catalog/*; 
 xmlns:impl=*http://ishop.orange.iway.sk*; 
 xmlns:intf=*http://ishop.orange.iway.sk*; 
 xmlns:apachesoap=*http://xml.apache.org/xml-soap*; 
 xmlns:wsdlsoap=*http://schemas.xmlsoap.org/wsdl/soap/*; 
 xmlns:xsd=*http://www.w3.org/2001/XMLSchema*; 
 xmlns:tns2=*http://ishop.orange.iway.sk/exceptions*; 
 xmlns:tns1=*http://ishop.orange.iway.sk/OPSTypes/*; 
 xmlns:wsdl=*http://schemas.xmlsoap.org/wsdl/*;
 - # !--
 
 WSDL created by Apache Axis version: 1.4
 Built on Apr 22, 2006 (06:55:48 PDT)
 
   --
 - # wsdl:types
 - # schema xmlns=*http://www.w3.org/2001/XMLSchema*; 
 targetNamespace=*http://ishop.orange.iway.sk/OPSTypes/*;
   import namespace=*http://ishop.orange.iway.sk/catalog/*; /
   import namespace=*http://ishop.orange.iway.sk/exceptions*; /
   element name=*Endpoint1* type=*xsd:long* /
   element name=*CId1* type=*xsd:long* /
   element name=*Endpoint2* type=*xsd:long* /
   element name=*CId2* type=*xsd:long* /
   element name=*OutProductRecord1* type=*tns3:productRecordType* /
   element name=*Endpoint3* type=*xsd:long* /
   element name=*ProductRecord1* type=*tns3:productRecordType* /
   element name=*OutProductRecord2* type=*tns3:productRecordType* /
   element name=*Endpoint4* type=*xsd:long* /
   element name=*CId3* type=*xsd:long* /
   element name=*ProductRecord2* type=*tns3:productRecordType* /
   element name=*CId4* type=*xsd:long* /
   element name=*Endpoint5* type=*xsd:long* /
   element name=*CId5* type=*xsd:long* /
   element name=*ProductRecord3* type=*tns3:productRecordType* /
   element name=*OutProductRecord3* type=*tns3:productRecordType* /
   element name=*ProductRecord4* type=*tns3:productRecordType* /
   element name=*Endpoint6* type=*xsd:long* /
   /schema
 - # schema xmlns=*http://www.w3.org/2001/XMLSchema*; 
 targetNamespace=*http://ishop.orange.iway.sk/exceptions*;
   import namespace=*http://ishop.orange.iway.sk/catalog/*; /
 - # complexType name=*timeoutException*
 - # sequence
   element name=*ExceptionCode* type=*xsd:int* /
   element name=*ExceptionMessage* nillable=*true* 
 type=*xsd:string* /
   /sequence
   /complexType
   element name=*timeoutException* type=*tns2:timeoutException* /
 - # complexType name=*serviceException*
 - # sequence
   element name=*ExceptionMessage* nillable=*true* 
 type=*xsd:string* /
   element name=*NestedExceptionStackTrace* nillable=*true* 
 type=*xsd:string* /
   /sequence
   /complexType
   element name=*serviceException* type=*tns2:serviceException* /
 - # complexType name=*databaseException*
 - # sequence
   element name=*ExceptionCode* type=*xsd:int* /
   element name=*ExceptionMessage* nillable=*true* 
 type=*xsd:string* /
   /sequence
   /complexType
   element name=*databaseException* 

Re: axis2 Calendar convertToDateTime

[zvika]

Thanks for the replay , it was very helpful

but,
there is no way to configure the Adb to replace the converter to some other
custom one , or the favorite one ,to fix the problem and change that in the
ADB ,so the fix will be a permanent and will not require to change the
Convertor in every new version of axis that i will use.

thanks again ,
Zvika.



Jon Diprose wrote:
 
 Hi,
 
 Hit exactly the same problem recently. Detailed reading of the spec seems
 to 
 indicate that adb implements the minimum required by the spec, though
 perhaps 
 falls short in the requirement to properly document this.
 
 I spent a while rewriting convertToDateTime myself before I discovered
 that 
 (apologies for wrapping):
 
 
 import
 com.sun.org.apache.xerces.internal.jaxp.datatype.XMLGregorianCalendarImpl;
 
 [snip]
 
 public static Calendar convertToDateTime(String source) {
  return XMLGregorianCalendarImpl.parse(source).toGregorianCalendar();
 }
 
 seemed to do a much more through job. Xerces and xml-apis.jar are in the 
 classpath, so why not? This implementation rounds fractional seconds to
 the 
 nearest millisecond, deals with BCE dates and year   and provides a
 pure 
 Gregorian calendar as per the spec. The only other major difference seems
 to 
 be that it throws IllegalArgumentExceptions where the original threw 
 NumberFormatExceptions. Might be nice to have the option of throwing an 
 exception if there is loss of precision but it does what I needed it to
 do.
 
 Unfortunately, the same class is too clever to reliably return an 
 xsd:dateTime-formatted string for convertToString(...) - it gives any of
 the 
 other xsd date/time formats depending on which fields are set in the
 calendar 
 - see javadocs. I ended up with:
 
 public static String convertToString(Calendar value) {
 
  // Set BCE flag if appropriate
  String era = ;
  if (GregorianCalendar.BC == value.get(Calendar.ERA)) {
  era = -;
  }
 
  // Build an appropriate SimpleDateFormat for the Zulu timezone
  // SimpleDateFormat seems to handle the variable length year itself
  // Spec indicates it should be pure Greogian
  SimpleDateFormat zulu = new SimpleDateFormat(era + 
 -MM-dd'T'HH:mm:ss.SSS'Z');
  GregorianCalendar c = new GregorianCalendar();
  c.setGregorianChange(new Date(Long.MIN_VALUE));
  c.setTimeZone(TimeZone.getTimeZone(GMT));
  zulu.setCalendar(c);
 
  // Sun JDK bug 
 http://developer.java.sun.com/developer/bugParade/bugs/4229798.html
  // Has been fixed since 1.4?
  return zulu.format(value.getTime());
 
 }
 
 Of course, you could just ensure that all the fields are set first and use 
 XMLGregorianCalendarImpl again.
 
 I've got updated test cases and a rebuilt axis2-adb-1.2.jar somewhere as
 well, 
 but its built for java5 so I think not strictly speaking correct.
 
 Sorry, don't have the source checked out or maven set up or anything. I'm 
 happy to send my source files to someone who does, if anyone wants them?
 
 Jon
 
 
 
 
 zvika wrote:
 hi!
 
 we started to make use of a webservice with generating an Apache Axis2
 ADB
 webservice client stub. 
 the webservice itself is provided by .NET on a IIS server.
 
 the problem we have is that when the webservice serialize a DateTime
 Object
 in a format of -MM-dd'T'HH:mm:ss.ss'Z'   ss - dynamic
 positions
 for the fractional seconds
 but the ADB (org.apache.axis2.databinding.utils.ConvertorUtil ) that used
 by
 Axis2 expect to format like -MM-dd'T'HH:mm:ss.sss'Z' when the
 fractional
 seconds no more then a three positions
 
 we understands from the webservice suppliers that the format is as define
 in
 W3 specification 
 http://www.w3.org/TR/xmlschema-2/#dateTime
 http://www.w3.org/TR/xmlschema-2/#dateTime 
 
 some samples that we get in invoking the  webservice 
 2007-06-20T17:00:37.8380863GMT+02:00
 2007-06-20T17:00:45.3GMT+02:00
 
 
 java.lang.RuntimeException: java.lang.NumberFormatException: Unparseable
 date: 2007-06-20T17:00:37.8380863GMT+02:00
  at
 com.orbograph.www.orboservice.OrboServiceStub.fromOM(OrboServiceStub.java:9400)
  at
 com.orbograph.www.orboservice.OrboServiceStub.GetServerTime(OrboServiceStub.java:777)
 
 
 
 
 Thanks,
 zvika.
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/axis2-Calendar-convertToDateTime-tf3952614.html#a11229001
Sent from the Axis - User mailing list archive at Nabble.com.


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

Re: axis 1.4 IllegalArgumentException got in response

[Roman Heinrich]

Hi Ole,

that means, if i want to use document/literal, then i should change for 
instance this message:


 wsdl:message name=*getProductNextRecordRequest*
 wsdl:part name=*Endpoint2* element=*tns1:Endpoint2* /
 wsdl:part name=*CId2* element=*tns1:CId2* /
 /wsdl:message

to one element, which will be defined as one parameter, which will hold 
Endpoint2 and CId2 in itself ?


That means, for document/literal, every function can have only one input 
message ?


Regards,
Roman.

omatzura wrote:

Hi Roman,

thanks.. this is a bit strange, your operations input message has defined
several parts but it is not used with a RPC soap-binding, you will probably
either need to change the style for the binding from document to rpc
(probably just a setting somewhere), or refactor the input message to
contain one root element/argument which holds the other two
elements/arguments..

hope this makes sense :-)

regards!

/Ole
eviware.com


Roman Heinrich-2 wrote:
  

Hi all,

i`m using oracle oc4j 10.1.3 with axis 1.4 bundled in my application. I 
have problem with running web service. Axis is not recognizing correctly 
arguments passed in soap request message.


SoapUi generated this soap request, which is not working:

soapenv:Envelope 
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; 
xmlns:ops=http://ishop.orange.iway.sk/OPSTypes/;

   soapenv:Header/
   soapenv:Body
  ops:Endpoint21/ops:Endpoint2
  ops:CId21/ops:CId2
   /soapenv:Body
/soapenv:Envelope

and i`ve got this response from axis:

soapenv:Envelope 
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:Body
  soapenv:Fault
 faultcodesoapenv:Server.generalException/faultcode
 faultstringTried to invoke method public 
sk.iway.orange.ishop.catalog.ProductRecordType 
sk.iway.orange.ishop.ProductSynchroServiceImpl.getProductNextRecord(long,long) 
throws 
java.rmi.RemoteException,sk.iway.orange.ishop.exceptions.TimeoutException,sk.iway.orange.ishop.exceptions.ServiceException,sk.iway.orange.ishop.exceptions.DatabaseException 
with arguments java.lang.Long,null.  The arguments do not match the 
signature.; nested exception is:

java.lang.IllegalArgumentException/faultstring
 detail
ns1:hostname 
xmlns:ns1=http://xml.apache.org/axis/;AMD64x5/ns1:hostname

 /detail
  /soapenv:Fault
   /soapenv:Body
/soapenv:Envelope

It seems, that axis is not recognising ops:CId2 argument.

My wsdl for service:

  ?xml version=1.0 encoding=UTF-8 ?
- # wsdl:definitions targetNamespace=*http://ishop.orange.iway.sk*; 
xmlns:tns3=*http://ishop.orange.iway.sk/catalog/*; 
xmlns:impl=*http://ishop.orange.iway.sk*; 
xmlns:intf=*http://ishop.orange.iway.sk*; 
xmlns:apachesoap=*http://xml.apache.org/xml-soap*; 
xmlns:wsdlsoap=*http://schemas.xmlsoap.org/wsdl/soap/*; 
xmlns:xsd=*http://www.w3.org/2001/XMLSchema*; 
xmlns:tns2=*http://ishop.orange.iway.sk/exceptions*; 
xmlns:tns1=*http://ishop.orange.iway.sk/OPSTypes/*; 
xmlns:wsdl=*http://schemas.xmlsoap.org/wsdl/*;

- # !--

WSDL created by Apache Axis version: 1.4
Built on Apr 22, 2006 (06:55:48 PDT)

  --
- # wsdl:types
- # schema xmlns=*http://www.w3.org/2001/XMLSchema*; 
targetNamespace=*http://ishop.orange.iway.sk/OPSTypes/*;

  import namespace=*http://ishop.orange.iway.sk/catalog/*; /
  import namespace=*http://ishop.orange.iway.sk/exceptions*; /
  element name=*Endpoint1* type=*xsd:long* /
  element name=*CId1* type=*xsd:long* /
  element name=*Endpoint2* type=*xsd:long* /
  element name=*CId2* type=*xsd:long* /
  element name=*OutProductRecord1* type=*tns3:productRecordType* /
  element name=*Endpoint3* type=*xsd:long* /
  element name=*ProductRecord1* type=*tns3:productRecordType* /
  element name=*OutProductRecord2* type=*tns3:productRecordType* /
  element name=*Endpoint4* type=*xsd:long* /
  element name=*CId3* type=*xsd:long* /
  element name=*ProductRecord2* type=*tns3:productRecordType* /
  element name=*CId4* type=*xsd:long* /
  element name=*Endpoint5* type=*xsd:long* /
  element name=*CId5* type=*xsd:long* /
  element name=*ProductRecord3* type=*tns3:productRecordType* /
  element name=*OutProductRecord3* type=*tns3:productRecordType* /
  element name=*ProductRecord4* type=*tns3:productRecordType* /
  element name=*Endpoint6* type=*xsd:long* /
  /schema
- # schema xmlns=*http://www.w3.org/2001/XMLSchema*; 
targetNamespace=*http://ishop.orange.iway.sk/exceptions*;

  import namespace=*http://ishop.orange.iway.sk/catalog/*; /
- # complexType name=*timeoutException*
- # sequence
  element name=*ExceptionCode* type=*xsd:int* /
  element name=*ExceptionMessage* nillable=*true* 
type=*xsd:string* /

  /sequence
  /complexType
  element name=*timeoutException* type=*tns2:timeoutException* /
- # complexType name=*serviceException*
- # sequence
  element name=*ExceptionMessage* nillable=*true* 
type=*xsd:string* /
  element 

Re: [Axis2] Using Axis2 for SOAP handling, without administration web app for deployment

[Nicholas Hogg]

Hi Deepal,

Thanks very much for your reply.

Regard,
Nick

Deepal Jayasinghe wrote:

Hi Nicholas ,
If you look at axis2 web.xml there you can find a commented parameter as
follows, please uncomment that and give a valid path name for that (it
should be an absolute path). Or you can create a file called conf under
WEB-INF directory and drop your axis2.xml there.

!--param-nameaxis2.xml.path/param-name--

Wsdl file should go as marked below;


Hi,

I have a legacy web application that I deploy straight into the
webapps dir of my container (Jetty).   I build with maven2 and have
axis2 as a dependency, and use it to handle the SOAP interaction.  I
don't use the Axis2 administration web application.  So directory
layout is different than if deployed using the axis2 web app:
{container}/webapps/{webappname}/
 -wsdl
 |- Command.wsdl
 -META-INF
 -WEB-INF

| conf
 | axis2.xml

|- web.xml
|- classes
|- lib
|- services
|- Command
  |- META-INF
 |- services.xml

  | myWsdl.wsdl

Two questions:
1.  Where would I put an axis2.xml in this layout?  I want to
configure the SOAPMonitor.
2.  Where should the wsdl file go.  The web service is working, but
the ?wsdl query is not.

Regards,
Nick







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



--
Nicholas Hogg   
KE Software (Australia)
www.kesoftware.com

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

axis2 command ns2p

[Alexey Zavizionov]

Hello

Does axis2 have option like -ns2p with arg file, file which contains
ns1=pkg1,ns2=pkg2?
In axis1 it was NStoPkg.properties

Thanks,
Alexey

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

Axis2 migrating from Axis1 for WSRP

[Alexey Zavizionov]

I'm new to axis2

We are migrating from Axis1 to Axis2.

I have problems with generation WSDL2Code for wsdl file
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_service.wsdl
which import bindings from
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_bindings.wsdl
which import interfaces from
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_interfaces.wsdl

Command line arguments  -s -ss -sd -ssi -g -d adb -t -p org.wsdl -uri
wsrp_service.wsdl
-o ${src.gen.dir}
-ns2p urn:oasis:names:tc:wsrp:v1:intf=org.intf,
urn:oasis:names:tc:wsrp:v1:types=org.type,
urn:oasis:names:tc:wsrp:v1:bind=org.bind,
urn:oasis:names:tc:wsrp:v1:wsdl=org.wsdl

While using axis1 we have got files:
in the generated dir bind
WSRP_v1_Markup_Binding_SOAPStub.java
WSRP_v1_PortletManagement_Binding_SOAPStub.java
WSRP_v1_Registration_Binding_SOAPStub.java
WSRP_v1_ServiceDescription_Binding_SOAPStub.java

in the generated dir intf
WSRP_v1_Markup_PortType.java
WSRP_v1_PortletManagement_PortType.java
WSRP_v1_Registration_PortType.java
WSRP_v1_ServiceDescription_PortType.java

But, now we have
in intf
ExtensionMapper.java
in wsdl
WSRPServiceMessageReceiverInOut.java
WSRPServiceSkeleton.java
WSRPServiceSkeletonInterface.java
WSRPServiceStub.java

Does axis2 correct generate source?

I'm really want to use axis2 for wsrp

Thanks in advance
Alexey

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

Re: Axis2 migrating from Axis1 for WSRP

[José Antonio Sánchez]

Do not use ADB to implement WS-* specifications since they usually use
very complex schemas and ADB doesn't have good support for complex
schemas. Consider using XmlBeans while ADB matures.
Axis2 uses a completely different service implementation schema. In
that case,  you have to implement your service completing the
WSRPServiceSkeleton.java class that must have one operation per
service operation provided in the WSDL.

Read this for details about migration from Axis1 to Axis2:

http://ws.apache.org/axis2/1_2/migration.html

On 6/21/07, Alexey Zavizionov [EMAIL PROTECTED] wrote:

I'm new to axis2

We are migrating from Axis1 to Axis2.

I have problems with generation WSDL2Code for wsdl file
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_service.wsdl
which import bindings from
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_bindings.wsdl
which import interfaces from
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_interfaces.wsdl

Command line arguments  -s -ss -sd -ssi -g -d adb -t -p org.wsdl -uri
wsrp_service.wsdl
-o ${src.gen.dir}
-ns2p urn:oasis:names:tc:wsrp:v1:intf=org.intf,
urn:oasis:names:tc:wsrp:v1:types=org.type,
urn:oasis:names:tc:wsrp:v1:bind=org.bind,
urn:oasis:names:tc:wsrp:v1:wsdl=org.wsdl

While using axis1 we have got files:
 in the generated dir bind
WSRP_v1_Markup_Binding_SOAPStub.java
WSRP_v1_PortletManagement_Binding_SOAPStub.java
WSRP_v1_Registration_Binding_SOAPStub.java
WSRP_v1_ServiceDescription_Binding_SOAPStub.java

 in the generated dir intf
WSRP_v1_Markup_PortType.java
WSRP_v1_PortletManagement_PortType.java
WSRP_v1_Registration_PortType.java
WSRP_v1_ServiceDescription_PortType.java

But, now we have
in intf
ExtensionMapper.java
in wsdl
WSRPServiceMessageReceiverInOut.java
WSRPServiceSkeleton.java
WSRPServiceSkeletonInterface.java
WSRPServiceStub.java

Does axis2 correct generate source?

I'm really want to use axis2 for wsrp

Thanks in advance
Alexey

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





--
Saludos.
José Antonio Sánchez

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

Re: Axis2 migrating from Axis1 for WSRP

[Alexey Zavizionov]

Thanks,

I have seen that migration manifest before send mail.
I tried to use xmlbeans databinding. It generates lots of files, and
same as I send
in wsdl
WSRPServiceMessageReceiverInOut.java
WSRPServiceSkeleton.java
WSRPServiceSkeletonInterface.java
WSRPServiceStub.java
:(

BTW, WSRPServiceSkeleton class has only methods which described in
WSRP_v1_PortletManagement_PortType. Looks like he generates one of
four intefaces. Does it a bug?

Regards,
Alexey

On 6/21/07, José Antonio Sánchez [EMAIL PROTECTED] wrote:

Do not use ADB to implement WS-* specifications since they usually use
very complex schemas and ADB doesn't have good support for complex
schemas. Consider using XmlBeans while ADB matures.
Axis2 uses a completely different service implementation schema. In
that case,  you have to implement your service completing the
WSRPServiceSkeleton.java class that must have one operation per
service operation provided in the WSDL.

Read this for details about migration from Axis1 to Axis2:

http://ws.apache.org/axis2/1_2/migration.html

On 6/21/07, Alexey Zavizionov [EMAIL PROTECTED] wrote:
 I'm new to axis2

 We are migrating from Axis1 to Axis2.

 I have problems with generation WSDL2Code for wsdl file
 
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_service.wsdl
 which import bindings from
 
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_bindings.wsdl
 which import interfaces from
 
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_interfaces.wsdl

 Command line arguments  -s -ss -sd -ssi -g -d adb -t -p org.wsdl -uri
 wsrp_service.wsdl
 -o ${src.gen.dir}
 -ns2p urn:oasis:names:tc:wsrp:v1:intf=org.intf,
 urn:oasis:names:tc:wsrp:v1:types=org.type,
 urn:oasis:names:tc:wsrp:v1:bind=org.bind,
 urn:oasis:names:tc:wsrp:v1:wsdl=org.wsdl

 While using axis1 we have got files:
  in the generated dir bind
 WSRP_v1_Markup_Binding_SOAPStub.java
 WSRP_v1_PortletManagement_Binding_SOAPStub.java
 WSRP_v1_Registration_Binding_SOAPStub.java
 WSRP_v1_ServiceDescription_Binding_SOAPStub.java

  in the generated dir intf
 WSRP_v1_Markup_PortType.java
 WSRP_v1_PortletManagement_PortType.java
 WSRP_v1_Registration_PortType.java
 WSRP_v1_ServiceDescription_PortType.java

 But, now we have
 in intf
 ExtensionMapper.java
 in wsdl
 WSRPServiceMessageReceiverInOut.java
 WSRPServiceSkeleton.java
 WSRPServiceSkeletonInterface.java
 WSRPServiceStub.java

 Does axis2 correct generate source?

 I'm really want to use axis2 for wsrp

 Thanks in advance
 Alexey

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




--
Saludos.
José Antonio Sánchez

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




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

Re: Axis2 migrating from Axis1 for WSRP

[José Antonio Sánchez]

I don't know if it's a bug or a feature but for multi-port services it
seems to generate only the first port. If you are using Axis2 1.2 try
to put one service per port and then generate the code. You should get
some other skeleton classes to fill.

On 6/21/07, Alexey Zavizionov [EMAIL PROTECTED] wrote:

Thanks,

I have seen that migration manifest before send mail.
I tried to use xmlbeans databinding. It generates lots of files, and
same as I send
in wsdl
WSRPServiceMessageReceiverInOut.java
WSRPServiceSkeleton.java
WSRPServiceSkeletonInterface.java
WSRPServiceStub.java
:(

BTW, WSRPServiceSkeleton class has only methods which described in
WSRP_v1_PortletManagement_PortType. Looks like he generates one of
four intefaces. Does it a bug?

Regards,
Alexey

On 6/21/07, José Antonio Sánchez [EMAIL PROTECTED] wrote:
 Do not use ADB to implement WS-* specifications since they usually use
 very complex schemas and ADB doesn't have good support for complex
 schemas. Consider using XmlBeans while ADB matures.
 Axis2 uses a completely different service implementation schema. In
 that case,  you have to implement your service completing the
 WSRPServiceSkeleton.java class that must have one operation per
 service operation provided in the WSDL.

 Read this for details about migration from Axis1 to Axis2:

 http://ws.apache.org/axis2/1_2/migration.html

 On 6/21/07, Alexey Zavizionov [EMAIL PROTECTED] wrote:
  I'm new to axis2
 
  We are migrating from Axis1 to Axis2.
 
  I have problems with generation WSDL2Code for wsdl file
  
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_service.wsdl
  which import bindings from
  
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_bindings.wsdl
  which import interfaces from
  
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_interfaces.wsdl
 
  Command line arguments  -s -ss -sd -ssi -g -d adb -t -p org.wsdl -uri
  wsrp_service.wsdl
  -o ${src.gen.dir}
  -ns2p urn:oasis:names:tc:wsrp:v1:intf=org.intf,
  urn:oasis:names:tc:wsrp:v1:types=org.type,
  urn:oasis:names:tc:wsrp:v1:bind=org.bind,
  urn:oasis:names:tc:wsrp:v1:wsdl=org.wsdl
 
  While using axis1 we have got files:
   in the generated dir bind
  WSRP_v1_Markup_Binding_SOAPStub.java
  WSRP_v1_PortletManagement_Binding_SOAPStub.java
  WSRP_v1_Registration_Binding_SOAPStub.java
  WSRP_v1_ServiceDescription_Binding_SOAPStub.java
 
   in the generated dir intf
  WSRP_v1_Markup_PortType.java
  WSRP_v1_PortletManagement_PortType.java
  WSRP_v1_Registration_PortType.java
  WSRP_v1_ServiceDescription_PortType.java
 
  But, now we have
  in intf
  ExtensionMapper.java
  in wsdl
  WSRPServiceMessageReceiverInOut.java
  WSRPServiceSkeleton.java
  WSRPServiceSkeletonInterface.java
  WSRPServiceStub.java
 
  Does axis2 correct generate source?
 
  I'm really want to use axis2 for wsrp
 
  Thanks in advance
  Alexey
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 


 --
 Saludos.
 José Antonio Sánchez

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



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





--
Saludos.
José Antonio Sánchez

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

RE: SOAP response

[Walker, Jeff]

Hi Demetris,
I'm using Axis 1.3, but these are the HTTP headers that my requests tend
to have:

POST /axis/services/ExampleAxisService HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related,
text/*
User-Agent: Axis/1.3
Host: 127.0.0.1:1234
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: 
Content-Length: 445

?xml version=1.0 encoding=UTF-8?soapenv:Envelope ...

And these are the ones on the response:
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=09876Jeffrey; Domain=pag; Expires=Thu,
21-Jun-2007 15:31:07 GMT
Content-Type: text/xml;charset=utf-8
Date: Thu, 21 Jun 2007 12:44:27 GMT
Connection: close

?xml version=1.0 encoding=utf-8?soapenv:Envelope ...


Obviously, you can change the SOAPAction and a few of the others, but
the answer I believe is yes, the HTTP headers do matter in web services
that go over the http protocol.
-jeff



 

-Original Message-
From: Demetris G [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, June 20, 2007 8:00 PM
To: Demetris G
Cc: axis-user@ws.apache.org
Subject: Re: SOAP response


Hi again,

I didn't get a response for the simple issue below so I am trying 
again. I intercept the
response from a legitimate SOAP call to a remote Axis container and I 
return it back
to the client by simply feeding it into the socket that the client wrote

the HTTP bundle
to. Shouldn't this work ? what I am missing ? Is the client side 
excepting to see HTTP
headers etc and not just the SOAP response ? I will appreciate any ideas

on this.

Thanks

Demetris G wrote:

 Hi all,

I am manually feeding the following SOAP response into an Axis 
 engine that requested
 this through a SOAP message and Axis responds with a 
 java.lang.NumberFormatException
 For input string quot;version=quot;1.0quot; etc.

Shouldn't the msg below be accepted with no issues from the engine 
 ?? What is it missing?

 Thanks much



 ?xml version=1.0 encoding=UTF-8?soapenv:Envelope 
 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:Bodyns1
:getBundlesResponse 
 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 

xmlns:ns1=http://soapobject.bundle.knopflerfish.org;getBundlesReturn 
 soapenc:arrayType=xsd:long[24] xsi:type=soapenc:Array 

xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;getBundlesRet
urn 
 href=#id0/getBundlesReturn href=#id1/getBundlesReturn 
 href=#id2/getBundlesReturn href=#id3/getBundlesReturn 
 href=#id4/getBundlesReturn href=#id5/getBundlesReturn 
 href=#id6/getBundlesReturn href=#id7/getBundlesReturn 
 href=#id8/getBundlesReturn href=#id9/getBundlesReturn 
 href=#id10/getBundlesReturn href=#id11/getBundlesReturn 
 href=#id12/getBundlesReturn href=#id13/getBundlesReturn 
 href=#id14/getBundlesReturn href=#id15/getBundlesReturn 
 href=#id16/getBundlesReturn href=#id17/getBundlesReturn 
 href=#id18/getBundlesReturn href=#id19/getBundlesReturn 
 href=#id20/getBundlesReturn href=#id21/getBundlesReturn 
 href=#id22/getBundlesReturn 
 href=#id23//getBundlesReturn/ns1:getBundlesResponsemultiRef 
 id=id12 soapenc:root=0 
 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
 xsi:type=xsd:long 

xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;18/multiRef
multiRef 
 id=id22 soapenc:root=0 
 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
 xsi:type=xsd:long 

xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;22/multiRef
multiRef 
 id=id17 soapenc:root=0 
 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
 xsi:type=xsd:long 

xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;23/multiRef
multiRef 
 id=id14 soapenc:root=0 
 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
 xsi:type=xsd:long 

xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;13/multiRef
multiRef 
 id=id18 soapenc:root=0 
 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
 xsi:type=xsd:long 

xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;17/multiRef
multiRef 
 id=id16 soapenc:root=0 
 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
 xsi:type=xsd:long 

xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;12/multiRef
multiRef 
 id=id20 soapenc:root=0 
 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
 xsi:type=xsd:long 

xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;6/multiRefm
ultiRef 
 id=id9 soapenc:root=0 
 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
 xsi:type=xsd:long 

xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;20/multiRef
multiRef 
 id=id23 soapenc:root=0 
 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
 xsi:type=xsd:long 

xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;3/multiRefm
ultiRef 
 id=id3 soapenc:root=0 
 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
 

RE: service classpath

[Michael Lepine]

That makes sense. Thank you for the response.

 



From: Chad DeBauch [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, June 20, 2007 8:45 PM
To: axis-user@ws.apache.org
Subject: Re: service classpath

 

Each aar file that you deploy has its own ClassLoader.  If there is code
in your service that needs to get resources such as xml files you need
to pass it the ClassLoader for that service.  For example if you have
this iBatis method in your service Resources.getResourceAsReader(String
resource), you must use this one instead
Resources.getResourceAsReader(ClassLoader classLoader, String resource).
You can get access to the ClassLoader for that service by calling

MessageContext.getCurrentMessageContext().getAxisService().getClassLoade
r();

If you are not able to change the code that gets the resources, then you
have to put the resources in the WEB-INF/classes directory or if it is
bundled in a jar put it in WEB-INF/lib directory. 

Chad

On 6/20/07, Michael Lepine [EMAIL PROTECTED] wrote:

Hello all. I still have classpath issues with my deployed aar archive
file and am hoping for some guidance. (My original post is below and
mentions log4j configuration as part of my issue, but that a side effect
of my classpath issue.)  I've reviewed the docs, faqs and wiki entries
on the Axis2 site and cannot find any topics on this, so I probably am
just missing something.

 

There are XML configuration files that my service needs access to when
deployed; however, with the aar configuration below, it does not find
them on the classpath once deployed. 

 

How do I deploy my service with configuration files so that it can find
and access those resources? Do I need to deploy the service differently?

 

Any guidance (and your time) is appreciated. Thank you.

 

 



From: Michael Lepine [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 19, 2007 10:23 AM
To: axis-user@ws.apache.org
Subject: service classpath

 

I'm not overly familiar with web services, but I've created a POJO-based
web service and am having difficultly logging from the service. The aar
archive has the following top-level directory structure:

 

com - class files under the com.xxx.xxx... package

META-INF - folder containing the services.xml

lib - folder containing library (jar/zip) files for service

commons-logging.properties - property file for logging configuration

log4j.properties - property file for log4j configuration

other.xml - other xml files that need to be accessible via the classpath

 

I'm deploying the aar file to the following folder under the tomcat
(version 5.0.28) installation directory:

 

[TOMCAT_HOME]\webapps\axis\WEB-INF\services

 

The service is being deployed correctly and appears to be working.

 

So, should my properties and xml files be accessible via the classpath
or am I doing something wrong?

 

Any guidance is appreciated. Thank you.

 

- Mike

 

[Axis2] Using rampart to consume WCF service

[Thomas Jaehnig]

Hello,

i want to access a WCF Service which uses WS-Security (WSHttpBinding
with Username Token).

Have someone accomplished this?

When I try to use wsdl2java to generate a client class, it fails with
the following error:

Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException:
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException: can't serialize the policy ..
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener
ationEngine.java:256)
...

So i've used a Stub generated from the same service configured without
any security and tried to configure the client behavior in the axis
config file.

Is there an easy way to consume a secure WCF service with Axis2 and Rampart.

If so, can anyone post the configuration he used to get this working.

Thanks in advance

Thomas

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

[ANNOUNCEMENT] WSRM 1.1 is now an OASIS Standard

[Paul Fremantle]

http://www.oasis-open.org/news/oasis-news-2007-06-21.php

Boston, MA, USA; 21 June 2007 -- OASIS, the international open
standards consortium, today announced that its members have approved
Web Services Reliable Messaging (WS-ReliableMessaging) version 1.1 as
an OASIS Standard, a status that signifies the highest level of
ratification. WS-ReliableMessaging allows messages to be transferred
reliably despite failures in software components, systems, or
networks. It enables a broad range of reliability features, including
ordered delivery, duplicate elimination, and guaranteed receipt.

Reliable messaging is one of the features customers demand most as
they move to electronic business. The problem is that messages can be
lost, repeated, or reordered, and host systems can fail, explained
Paul Fremantle of WSO2, co-chair of the OASIS Web Services Reliable
Exchange (WS-RX) Technical Committee. WS-ReliableMessaging addresses
all these risks by providing a modular mechanism that identifies,
tracks, and manages the reliable transfer of messages between a source
and a destination.

Sanjay Patil of SAP, co-chair of the OASIS WS-RX Technical Committee,
added, WS-ReliableMessaging delivers a key element in the openness of
an enterprise service-oriented architecture (SOA) and provides a
critical building block that can be used in conjunction with other
specifications and application-specific protocols to reliably handle a
wide variety of SOA requirements and scenarios.

The extensible nature of WS-ReliableMessaging allows additional
functionality, such as security, to be tightly integrated. It
incorporates a SOAP binding for interoperability and allows additional
bindings to be defined. The protocol can be implemented with a variety
of robustness characteristics ranging from in-memory persistence
scoped to a single process lifetime, to replicated durable storage
that is recoverable in the most extreme circumstances.

OASIS president and CEO, Patrick Gannon, noted, WS-ReliableMessaging
integrates with and complements the WS-Security OASIS Standard as well
as other Web services specifications. Combining these standards offers
companies many reliable, secure messaging options.

The WS-ReliableMessaging OASIS Standard was developed by
representatives of Adobe, BEA Systems, Fujitsu, Hitachi, IBM, Intel,
IONA, Microsoft, NEC, Nortel, Novell, Oracle, Progress Software, Red
Hat, SAP, Sun Microsystems, TIBCO, webMethods, and others. The
WS-ReliableMessaging OASIS Standard and the archives of the OASIS
WS-RX Technical Committee work are publicly accessible. OASIS hosts
the ws-reliablemessaging-dev mailing list for exchanging information
on implementing the standard.

Support for WS-ReliableMessaging OASIS Standard
ACORD
On behalf of ACORD, we welcome the official release of the
WS-ReliableMessaging OASIS Standard. ACORD is committed to Web
services standards as part of its Service Oriented Architecture
strategy and has been working for several years with its members on a
profile for Web service protocols based on insurance industry use
cases. WS-ReliableMessaging is a piece of the puzzle we have been
critically expecting in support of robust message exchange, flexible
deployment of services, and mass transit on the Internet. We are
strongly encouraging the implementation of this set of protocols in
software libraries and tools, in support of Web services deployment in
the insurance industry, said Lloyd Chumbley, Assistant Vice President
of Standards, ACORD.

Adobe
Interoperable reliable messaging is a critical component in enabling
real-world distributed Service Oriented Architectures (SOA).
WS-ReliableMessaging provides a framework for reliable and robust
exchange of business information as part of Web services and SOA,
enabling the enterprise to realize reliable integration and
collaborative business processes leveraging disparate applications,
said Charlton Barreto, Senior Computer Scientist and Architect, Adobe
Systems.

BEA Systems
The acceptance of WS-ReliableMessaging as an OASIS Standard
represents an important milestone in the development of reliable,
secure services that can leverage today's heterogeneous
infrastructures. Ensuring that messages are delivered, eliminating
duplicate messages, and delivering messages in the order they are sent
are fundamental capabilities for building flexible, SOA-based
applications. With the standardization of WS-ReliableMessaging, BEA
Systems plans to continue its commitment to and leadership in Web
services standards, said Gilbert Pilz, Sr. Principal Technologist,
Office of the CTO, BEA Systems, Inc.

Hitachi
Enterprise systems are nothing if they are not reliable, and no Web
service that employed intermediaries could be reliable until now.
WS-ReliableMessaging is widely adopted. Platform users can now have
high confidence that this core functionality will be available to them
on a variety of platforms from most enterprise vendors. We thank the
committee for all of its work in 

Soap viewer or sniffer

[Alexey Zavizionov]

Hello,

Which tools are you using for debugging web services and viewing soap messages?
Does anybody use http sniffer for it?

Thanks in advance,
Alexey

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

Re: Axis2 migrating from Axis1 for WSRP

[Alexey Zavizionov]

I got wsdl files from oasis specification, there are 4 ports for one
service. I shouldn't change it.
Does any more know this issue?
Does axis2 useful for implements wsrp services?

Спасибо за помощь,
Alexey

On 6/21/07, José Antonio Sánchez [EMAIL PROTECTED] wrote:

I don't know if it's a bug or a feature but for multi-port services it
seems to generate only the first port. If you are using Axis2 1.2 try
to put one service per port and then generate the code. You should get
some other skeleton classes to fill.

On 6/21/07, Alexey Zavizionov [EMAIL PROTECTED] wrote:
 Thanks,

 I have seen that migration manifest before send mail.
 I tried to use xmlbeans databinding. It generates lots of files, and
 same as I send
 in wsdl
 WSRPServiceMessageReceiverInOut.java
 WSRPServiceSkeleton.java
 WSRPServiceSkeletonInterface.java
 WSRPServiceStub.java
 :(

 BTW, WSRPServiceSkeleton class has only methods which described in
 WSRP_v1_PortletManagement_PortType. Looks like he generates one of
 four intefaces. Does it a bug?

 Regards,
 Alexey

 On 6/21/07, José Antonio Sánchez [EMAIL PROTECTED] wrote:
  Do not use ADB to implement WS-* specifications since they usually use
  very complex schemas and ADB doesn't have good support for complex
  schemas. Consider using XmlBeans while ADB matures.
  Axis2 uses a completely different service implementation schema. In
  that case,  you have to implement your service completing the
  WSRPServiceSkeleton.java class that must have one operation per
  service operation provided in the WSDL.
 
  Read this for details about migration from Axis1 to Axis2:
 
  http://ws.apache.org/axis2/1_2/migration.html
 
  On 6/21/07, Alexey Zavizionov [EMAIL PROTECTED] wrote:
   I'm new to axis2
  
   We are migrating from Axis1 to Axis2.
  
   I have problems with generation WSDL2Code for wsdl file
   
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_service.wsdl
   which import bindings from
   
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_bindings.wsdl
   which import interfaces from
   
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_interfaces.wsdl
  
   Command line arguments  -s -ss -sd -ssi -g -d adb -t -p org.wsdl -uri
   wsrp_service.wsdl
   -o ${src.gen.dir}
   -ns2p urn:oasis:names:tc:wsrp:v1:intf=org.intf,
   urn:oasis:names:tc:wsrp:v1:types=org.type,
   urn:oasis:names:tc:wsrp:v1:bind=org.bind,
   urn:oasis:names:tc:wsrp:v1:wsdl=org.wsdl
  
   While using axis1 we have got files:
in the generated dir bind
   WSRP_v1_Markup_Binding_SOAPStub.java
   WSRP_v1_PortletManagement_Binding_SOAPStub.java
   WSRP_v1_Registration_Binding_SOAPStub.java
   WSRP_v1_ServiceDescription_Binding_SOAPStub.java
  
in the generated dir intf
   WSRP_v1_Markup_PortType.java
   WSRP_v1_PortletManagement_PortType.java
   WSRP_v1_Registration_PortType.java
   WSRP_v1_ServiceDescription_PortType.java
  
   But, now we have
   in intf
   ExtensionMapper.java
   in wsdl
   WSRPServiceMessageReceiverInOut.java
   WSRPServiceSkeleton.java
   WSRPServiceSkeletonInterface.java
   WSRPServiceStub.java
  
   Does axis2 correct generate source?
  
   I'm really want to use axis2 for wsrp
  
   Thanks in advance
   Alexey
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 
 
  --
  Saludos.
  José Antonio Sánchez
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 

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




--
Saludos.
José Antonio Sánchez

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

Re: Soap viewer or sniffer

[Thomas Jaehnig]

Hi,

i prefer wireshark. This tool has a nice function called Follow TCP
Stream. Using this you can see the whole conversation between the
parties.

regard

Thomas

On Thu, 2007-06-21 at 16:23 +0300, Alexey Zavizionov wrote:
 Hello,
 
 Which tools are you using for debugging web services and viewing soap 
 messages?
 Does anybody use http sniffer for it?
 
 Thanks in advance,
 Alexey
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


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

Re: problem with axis generated wsdl files, related to schema address

[legolas]

Any comment?



legolas wrote:
 
 Hi
 Thank you for reading my post
 I have a problem with axis generated wsdl files regarded to xsd urls.
 for example :
 
 xsd:import namespace=http://wsp/; schemaLocation=calc?xsd=xsd0/
 
 
 The above is a part of a wsdl generated by axis and this wsdl is not
 suitable for my case.
 I need it to generate the wsdl with full address of schema, something
 like:
 
 xsd:import namespace=http://wsp/;
 schemaLocation=http://192.168.100.1:9000/soap/calc?xsd=xsd0/
 
 
 is it possible or i should  edit the wsdl files to make them like that?
 
 thanks.
 
 

-- 
View this message in context: 
http://www.nabble.com/problem-with-axis-generated-wsdl-files%2C-related-to-schema-address-tf3949495.html#a11233007
Sent from the Axis - User mailing list archive at Nabble.com.


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

Re: axis2 Calendar convertToDateTime

[Jon Diprose]

Ideally I'd get my changes committed to the source tree. I just haven't 
figured out how to make that happen yet!


I'm guessing creating a bug report and attaching fix...

Jon

zvika wrote:

Thanks for the replay , it was very helpful

but,
there is no way to configure the Adb to replace the converter to some other
custom one , or the favorite one ,to fix the problem and change that in the
ADB ,so the fix will be a permanent and will not require to change the
Convertor in every new version of axis that i will use.

thanks again ,
Zvika.



Jon Diprose wrote:

Hi,

Hit exactly the same problem recently. Detailed reading of the spec seems
to 
indicate that adb implements the minimum required by the spec, though
perhaps 
falls short in the requirement to properly document this.


I spent a while rewriting convertToDateTime myself before I discovered
that 
(apologies for wrapping):



import
com.sun.org.apache.xerces.internal.jaxp.datatype.XMLGregorianCalendarImpl;

[snip]

public static Calendar convertToDateTime(String source) {
 return XMLGregorianCalendarImpl.parse(source).toGregorianCalendar();
}

seemed to do a much more through job. Xerces and xml-apis.jar are in the 
classpath, so why not? This implementation rounds fractional seconds to
the 
nearest millisecond, deals with BCE dates and year   and provides a
pure 
Gregorian calendar as per the spec. The only other major difference seems
to 
be that it throws IllegalArgumentExceptions where the original threw 
NumberFormatExceptions. Might be nice to have the option of throwing an 
exception if there is loss of precision but it does what I needed it to

do.

Unfortunately, the same class is too clever to reliably return an 
xsd:dateTime-formatted string for convertToString(...) - it gives any of
the 
other xsd date/time formats depending on which fields are set in the
calendar 
- see javadocs. I ended up with:


public static String convertToString(Calendar value) {

 // Set BCE flag if appropriate
 String era = ;
 if (GregorianCalendar.BC == value.get(Calendar.ERA)) {
 era = -;
 }

 // Build an appropriate SimpleDateFormat for the Zulu timezone
 // SimpleDateFormat seems to handle the variable length year itself
 // Spec indicates it should be pure Greogian
 SimpleDateFormat zulu = new SimpleDateFormat(era + 
-MM-dd'T'HH:mm:ss.SSS'Z');

 GregorianCalendar c = new GregorianCalendar();
 c.setGregorianChange(new Date(Long.MIN_VALUE));
 c.setTimeZone(TimeZone.getTimeZone(GMT));
 zulu.setCalendar(c);

 // Sun JDK bug 
http://developer.java.sun.com/developer/bugParade/bugs/4229798.html

 // Has been fixed since 1.4?
 return zulu.format(value.getTime());

}

Of course, you could just ensure that all the fields are set first and use 
XMLGregorianCalendarImpl again.


I've got updated test cases and a rebuilt axis2-adb-1.2.jar somewhere as
well, 
but its built for java5 so I think not strictly speaking correct.


Sorry, don't have the source checked out or maven set up or anything. I'm 
happy to send my source files to someone who does, if anyone wants them?


Jon




zvika wrote:

hi!

we started to make use of a webservice with generating an Apache Axis2
ADB
webservice client stub. 
the webservice itself is provided by .NET on a IIS server.


the problem we have is that when the webservice serialize a DateTime
Object
in a format of -MM-dd'T'HH:mm:ss.ss'Z'   ss - dynamic
positions
for the fractional seconds
but the ADB (org.apache.axis2.databinding.utils.ConvertorUtil ) that used
by
Axis2 expect to format like -MM-dd'T'HH:mm:ss.sss'Z' when the
fractional
seconds no more then a three positions

we understands from the webservice suppliers that the format is as define
in
W3 specification 
http://www.w3.org/TR/xmlschema-2/#dateTime
http://www.w3.org/TR/xmlschema-2/#dateTime 

some samples that we get in invoking the  webservice 
2007-06-20T17:00:37.8380863GMT+02:00

2007-06-20T17:00:45.3GMT+02:00


java.lang.RuntimeException: java.lang.NumberFormatException: Unparseable
date: 2007-06-20T17:00:37.8380863GMT+02:00
at
com.orbograph.www.orboservice.OrboServiceStub.fromOM(OrboServiceStub.java:9400)
at
com.orbograph.www.orboservice.OrboServiceStub.GetServerTime(OrboServiceStub.java:777)




Thanks,
zvika.

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







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

[Axis2] Enabling MTOM partially duplicates message

[Tammy Dugan]

Here is what the response message from by Axis2 service looks like with 
MTOM disabled:


?xml version='1.0' encoding='UTF-8'?soapenv:Envelope 
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Bodyr:queryDatasetReturnResponse 
xmlns:r=http://spin.regenstrief.org/query;.../rawData/r:queryDatasetReturnResponse/soapenv:Body/soapenv:Envelope


This is what the message looks like with MTOM enabled:

--MIMEBoundaryurn_uuid_2BE039143DB2744D651182431292012
Content-Type: application/xop+xml; charset=UTF-8; type=text/xml
Content-Transfer-Encoding: binary
Content-ID: 0.urn:uuid:[EMAIL PROTECTED]

?xml version='1.0' encoding='UTF-8'?soapenv:Envelope 
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Bodyr:queryDatasetReturnResponse 
xmlns:r=http://spin.regenstrief.org/query;.../rawData

--MIMEBoundaryurn_uuid_2BE039143DB2744D651182431292012MIMEBoundaryurn_uuid_2BE039143DB2744D651182431292012
Content-Type: application/xop+xml; charset=UTF-8; type=text/xml
Content-Transfer-Encoding: binary
Content-ID: 0.urn:uuid:[EMAIL PROTECTED]

?xml version='1.0' encoding='UTF-8'?soapenv:Envelope 
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Bodyr:queryDatasetReturnResponse 
xmlns:r=http://spin.regenstrief.org/query;.../rawData/r:queryDatasetReturnResponse/soapenv:Body/soapenv:Envelope

--MIMEBoundaryurn_uuid_2BE039143DB2744D651182431292012--

As you can see, almost the entire message is repeated twice. The first 
time the end of the message is truncated. This really looks like a bug 
to me. Any thoughts? I am running the latest released version of Axis2. 
Here is the code I am running to make this message:


   OMFactory fact = OMAbstractFactory.getOMFactory();
   OMNamespace ns = 
fact.createOMNamespace(http://spin.regenstrief.org/query;, r);
   OMElement resultXML = 
fact.createOMElement(queryDatasetReturnResponse, ns);
   Connection con = db.openConnection(); // create a dedicated 
connection for streaming from database

   OMElement datasetElement = null;

   InputStream inputStream = readDataSetXMLToInputStream(con, 1, 
VARIABLE_DATA_SET); //string of xml from database


   if (inputStream != null)
   {
   ns = new OMNamespaceImpl(, );
   OMDataSource dataSource = new CustomDataSource(inputStream);
   datasetElement = new OMSourcedElementImpl(rawData, ns, 
fact, dataSource);

   }

   resultXML.addChild(datasetElement);

class CustomDataSource implements OMDataSource
   {
   private final InputStream data;

   public CustomDataSource(InputStream data)
   {
   this.data = data;
   }

   public void serialize(XMLStreamWriter xmlWriter) throws 
XMLStreamException

   {
   XMLStreamReader reader = null;

   try
   {
   StreamingOMSerializer serializer = new 
StreamingOMSerializer();

   reader = getReader();
   serializer.serialize(reader, xmlWriter);
   xmlWriter.flush();
   } catch (Throwable e)
   {
   }
   }

   public XMLStreamReader getReader() throws XMLStreamException
   {
   XMLStreamReader reader = null;

   try
   {
   reader = StAXUtils.createXMLStreamReader(this.data);
   } catch (Exception e)
   {
   }

   return reader;
   }
   ...
   }


Tammy

--
Tammy Dugan
Computer Programmer

Regenstrief Institute, Inc.
Medical Informatics
Health Information and Translational Sciences (HITS) Building
410 West 10th Street, Suite 2000
Indianapolis, IN 46202
Main: 317.423.5500
Fax: 317.423.5695
IU campus mail address: HS, 2000

(317) 423 - 5541

Confidentiality Notice: The contents of this message and any files transmitted 
with it may contain confidential and/or privileged information and are intended 
solely for the use of the named addressee(s). Additionally, the information 
contained herein may have been disclosed to you from medical records with 
confidentiality protected by federal and state laws. Federal regulations and 
State laws prohibit you from making further disclosure of such information 
without the specific written consent of the person to whom the information 
pertains or as otherwise permitted by such regulations. A general authorization 
for the release of medical or other information is not sufficient for this 
purpose.

If you have received this message in error, please notify the sender by return 
e-mail and delete the original message. Any retention, disclosure, copying, 
distribution or use of this information by anyone other than the intended 
recipient is strictly prohibited.



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

Re: Error: java.io.IOException: Server returned HTTP response code: 500 for URL: http://localhost:8080/axis/services/LogCollector?wsdl at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unk

[Roland Piazzi]

yuhu :-), i've found the error:

the destination package of WSDL2Java should exist, if not exists it gives me 
the error.

thanks again
roland
- Original Message - 
From: Roland Piazzi [EMAIL PROTECTED]

To: Walker, Jeff [EMAIL PROTECTED]; axis-user@ws.apache.org
Sent: Thursday, June 21, 2007 2:51 AM
Subject: Re: Error: java.io.IOException: Server returned HTTP response code: 
500 for URL: http://localhost:8080/axis/services/LogCollector?wsdl at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)




what you mean with

edit your wsdl


edit the class that represents the webservice?

Both PC's where hosting the webservice and acting as client.

Yes this is the problem: I really edited the class to the point that i had 
only one simple Method that returned a String but it didn't work...seems 
to be some ghost in there :-)...


roland
- Original Message - 
From: Walker, Jeff [EMAIL PROTECTED]

To: axis-user@ws.apache.org; Roland Piazzi [EMAIL PROTECTED]
Sent: Wednesday, June 20, 2007 11:33 PM
Subject: RE: Error: java.io.IOException: Server returned HTTP response 
code: 500 for URL: http://localhost:8080/axis/services/LogCollector?wsdl 
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown 
Source)



I guess what I was implying is,
that I would edit your wsdl to comment out all of the methods except a
simple ping() method, that takes say, an integer, and returns an
integer. Something ridiculously simple. Then generate your classes from
it. Then deploy the web service.
Then get your client to successfully call that ping() method. This tells
you the wsdl (and the generated classes) are healthy.

Then start to edit the wsdl again, bring in one actual business method,
preferrably the simplest business method you have, and try to call that.

I'm not sure what you mean when you say you got it to work on one PC but
not the other. Were both of these PC's acting as clients, or were they
hosting the web service?

One final point of confusion I have; if you removed all of the methods,
then there is no web service to speak of, so there would be no web
service methods to call from your client, and so how could you still get
the error?
I don't understand.
-jeff





-Original Message-
From: Roland Piazzi [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 20, 2007 5:00 PM
To: axis-user@ws.apache.org
Subject: Re: Error: java.io.IOException: Server returned HTTP response
code: 500 for URL: http://localhost:8080/axis/services/LogCollector?wsdl
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
Source)

I copied some old implementation instead of that and it worked, but only

with one pc, with the other it didn't work, also if i removed all
methods,
still the error was. If you have other advices how to try please tell me

because at the time i don't know how to go on trying.

roland
- Original Message - 
From: Walker, Jeff [EMAIL PROTECTED]

To: axis-user@ws.apache.org; Roland Piazzi [EMAIL PROTECTED]
Sent: Wednesday, June 20, 2007 7:31 PM
Subject: RE: Error: java.io.IOException: Server returned HTTP response
code:
500 for URL: http://localhost:8080/axis/services/LogCollector?wsdl at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
Source)


Yeah,
The service is reachable, but the server failed to complete your
request.
A). Check that the request going out to the url is also correct.
B). Check your web service implementation. Do you even reach your web
service methods? (Put some old-fashioned debug statements into your web
service method, to see if tose statements get hit).
C). I'd also pick the simplest method on the web service and call that

from your client, to help narrow down the error. Then move onto the

next
most complicated method, etc.

There are many thing to try, but concentrate on your web service
debugging.
-jeff


-Original Message-
From: Roland Piazzi [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 20, 2007 11:31 AM
To: axis-user@ws.apache.org
Subject: Error: java.io.IOException: Server returned HTTP response code:
500 for URL: http://localhost:8080/axis/services/LogCollector?wsdl at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
Source)

Hi!

I try to generate WSDL2Java classes but receive the following error (the

service is reachable at this endpoint) :

java.io.IOException: Server returned HTTP response code: 500 for URL:
http://localhost:8080/axis/services/LogCollector?wsdl at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEnt
ity(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocV
ersion(Unknown
Source)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuratioin.parse(Unk
nown
Source)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuratioin.parse(Unk
nown
Source)
at 

Re: Soap viewer or sniffer

[Alexey Zavizionov]

Hi, Thomas

Thanks, I'll try it!
I use the HTTPLook, but it's some times doesn't work.

Regards,
Alexey

On 6/21/07, Thomas Jaehnig [EMAIL PROTECTED] wrote:

Hi,

i prefer wireshark. This tool has a nice function called Follow TCP
Stream. Using this you can see the whole conversation between the
parties.

regard

Thomas

On Thu, 2007-06-21 at 16:23 +0300, Alexey Zavizionov wrote:
 Hello,

 Which tools are you using for debugging web services and viewing soap 
messages?
 Does anybody use http sniffer for it?

 Thanks in advance,
 Alexey

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



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




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

Get the username from UsernameTokens in Skeleton class

[Chad DeBauch]

How do I get the username that was in the SOAP UsernameToken from my
skeleton class?  Is there a way to retrieve it from the MessageContext?  I
am using Rampart to validate the UsernameTokens using a PWCallback class.

Thanks,

Chad

Re: Soap viewer or sniffer

[Alexey Zavizionov]

Look like HTTPLook better than Wireshark.
Did you use HTTPLook?

Alexey

On 6/21/07, Alexey Zavizionov [EMAIL PROTECTED] wrote:

Hi, Thomas

Thanks, I'll try it!
I use the HTTPLook, but it's some times doesn't work.

Regards,
Alexey

On 6/21/07, Thomas Jaehnig [EMAIL PROTECTED] wrote:
 Hi,

 i prefer wireshark. This tool has a nice function called Follow TCP
 Stream. Using this you can see the whole conversation between the
 parties.

 regard

 Thomas

 On Thu, 2007-06-21 at 16:23 +0300, Alexey Zavizionov wrote:
  Hello,
 
  Which tools are you using for debugging web services and viewing soap 
messages?
  Does anybody use http sniffer for it?
 
  Thanks in advance,
  Alexey
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 


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





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

Re: Soap viewer or sniffer

[Thomas Jaehnig]

No. I didn't know HTTPLook before.

I use Wireshark for many things. Not only for watching HTTP sessions.
It's very adjustable using filters. And it runs on many plattforms :D 

Maybe, HTTPLook is better for analyzing HTTP sessions. I will give it a
try.

Thomas

On Thu, 2007-06-21 at 18:01 +0300, Alexey Zavizionov wrote:
 Look like HTTPLook better than Wireshark.
 Did you use HTTPLook?
 
 Alexey
 
 On 6/21/07, Alexey Zavizionov [EMAIL PROTECTED] wrote:
  Hi, Thomas
 
  Thanks, I'll try it!
  I use the HTTPLook, but it's some times doesn't work.
 
  Regards,
  Alexey
 
  On 6/21/07, Thomas Jaehnig [EMAIL PROTECTED] wrote:
   Hi,
  
   i prefer wireshark. This tool has a nice function called Follow TCP
   Stream. Using this you can see the whole conversation between the
   parties.
  
   regard
  
   Thomas
  
   On Thu, 2007-06-21 at 16:23 +0300, Alexey Zavizionov wrote:
Hello,
   
Which tools are you using for debugging web services and viewing soap 
messages?
Does anybody use http sniffer for it?
   
Thanks in advance,
Alexey
   
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   
  
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


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

Re: axis 1.4 IllegalArgumentException got in response

[Martin Gainty]

Good Morning Roman --

I ran a few quick tests and found

!--This xmlns:wsdl declaration does not work--
!-- ?xml version=1.0 encoding=UTF-8? --
!-- wsdl:definitions targetNamespace=*http://ishop.orange.iway.sk*;
xmlns:wsdl=*http://schemas.xmlsoap.org/wsdl/*;
xmlns:apachesoap=*http://xml.apache.org/xml-soap*;
xmlns:tns=http://example;
xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
/wsdl:definitions --

!-- THIS xmlns:wsdl declaration WORKS!! --
?xml version=1.0 encoding=UTF-8?
wsdl:definitions targetNamespace=*http://ishop.orange.iway.sk*;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
xmlns:apachesoap=*http://xml.apache.org/xml-soap*;
xmlns:tns=http://example;
xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
/wsdl:definitions

HTH
Martin--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.

- Original Message - 
From: Roman Heinrich [EMAIL PROTECTED]

To: axis-user@ws.apache.org
Sent: Thursday, June 21, 2007 4:59 AM
Subject: Re: axis 1.4 IllegalArgumentException got in response



Hi Ole,

that means, if i want to use document/literal, then i should change for 
instance this message:


 wsdl:message name=*getProductNextRecordRequest*
 wsdl:part name=*Endpoint2* element=*tns1:Endpoint2* /
 wsdl:part name=*CId2* element=*tns1:CId2* /
 /wsdl:message

to one element, which will be defined as one parameter, which will hold 
Endpoint2 and CId2 in itself ?


That means, for document/literal, every function can have only one input 
message ?


Regards,
Roman.

omatzura wrote:

Hi Roman,

thanks.. this is a bit strange, your operations input message has defined
several parts but it is not used with a RPC soap-binding, you will 
probably

either need to change the style for the binding from document to rpc
(probably just a setting somewhere), or refactor the input message to
contain one root element/argument which holds the other two
elements/arguments..

hope this makes sense :-)

regards!

/Ole
eviware.com


Roman Heinrich-2 wrote:


Hi all,

i`m using oracle oc4j 10.1.3 with axis 1.4 bundled in my application. I 
have problem with running web service. Axis is not recognizing correctly 
arguments passed in soap request message.


SoapUi generated this soap request, which is not working:

soapenv:Envelope 
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; 
xmlns:ops=http://ishop.orange.iway.sk/OPSTypes/;

   soapenv:Header/
   soapenv:Body
  ops:Endpoint21/ops:Endpoint2
  ops:CId21/ops:CId2
   /soapenv:Body
/soapenv:Envelope

and i`ve got this response from axis:

soapenv:Envelope 
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:Body
  soapenv:Fault
 faultcodesoapenv:Server.generalException/faultcode
 faultstringTried to invoke method public 
sk.iway.orange.ishop.catalog.ProductRecordType 
sk.iway.orange.ishop.ProductSynchroServiceImpl.getProductNextRecord(long,long) 
throws 
java.rmi.RemoteException,sk.iway.orange.ishop.exceptions.TimeoutException,sk.iway.orange.ishop.exceptions.ServiceException,sk.iway.orange.ishop.exceptions.DatabaseException 
with arguments java.lang.Long,null.  The arguments do not match the 
signature.; nested exception is:

java.lang.IllegalArgumentException/faultstring
 detail
ns1:hostname 
xmlns:ns1=http://xml.apache.org/axis/;AMD64x5/ns1:hostname

 /detail
  /soapenv:Fault
   /soapenv:Body
/soapenv:Envelope

It seems, that axis is not recognising ops:CId2 argument.

My wsdl for service:

  ?xml version=1.0 encoding=UTF-8 ?
- # wsdl:definitions targetNamespace=*http://ishop.orange.iway.sk*; 
xmlns:tns3=*http://ishop.orange.iway.sk/catalog/*; 
xmlns:impl=*http://ishop.orange.iway.sk*; 
xmlns:intf=*http://ishop.orange.iway.sk*; 
xmlns:apachesoap=*http://xml.apache.org/xml-soap*; 
xmlns:wsdlsoap=*http://schemas.xmlsoap.org/wsdl/soap/*; 
xmlns:xsd=*http://www.w3.org/2001/XMLSchema*; 
xmlns:tns2=*http://ishop.orange.iway.sk/exceptions*; 
xmlns:tns1=*http://ishop.orange.iway.sk/OPSTypes/*; 
xmlns:wsdl=*http://schemas.xmlsoap.org/wsdl/*;

- # !--

WSDL created by Apache Axis version: 1.4
Built on Apr 22, 2006 (06:55:48 PDT)

  --
- # wsdl:types
- # schema xmlns=*http://www.w3.org/2001/XMLSchema*; 
targetNamespace=*http://ishop.orange.iway.sk/OPSTypes/*;

  import namespace=*http://ishop.orange.iway.sk/catalog/*; /
  import namespace=*http://ishop.orange.iway.sk/exceptions*; /
  element name=*Endpoint1* type=*xsd:long* /
  element name=*CId1* type=*xsd:long* /
  element name=*Endpoint2* type=*xsd:long* /
  element 

Re: Soap viewer or sniffer

[Alexey Zavizionov]

Does Wireshark can show soap body as here on the picture
http://bp0.blogger.com/_aEfX-L_3RIQ/RcwbginwePI/AAs/X42ssmlnP5s/s1600-h/httplook_screen.JPG
?
I have noticed many snifers, if it will be useful for you look at
http://zavizionov.blogspot.com/2007/02/http-sniffers.html

Regards,
Alexey

On 6/21/07, Thomas Jaehnig [EMAIL PROTECTED] wrote:

No. I didn't know HTTPLook before.

I use Wireshark for many things. Not only for watching HTTP sessions.
It's very adjustable using filters. And it runs on many plattforms :D

Maybe, HTTPLook is better for analyzing HTTP sessions. I will give it a
try.

Thomas

On Thu, 2007-06-21 at 18:01 +0300, Alexey Zavizionov wrote:
 Look like HTTPLook better than Wireshark.
 Did you use HTTPLook?

 Alexey

 On 6/21/07, Alexey Zavizionov [EMAIL PROTECTED] wrote:
  Hi, Thomas
 
  Thanks, I'll try it!
  I use the HTTPLook, but it's some times doesn't work.
 
  Regards,
  Alexey
 
  On 6/21/07, Thomas Jaehnig [EMAIL PROTECTED] wrote:
   Hi,
  
   i prefer wireshark. This tool has a nice function called Follow TCP
   Stream. Using this you can see the whole conversation between the
   parties.
  
   regard
  
   Thomas
  
   On Thu, 2007-06-21 at 16:23 +0300, Alexey Zavizionov wrote:
Hello,
   
Which tools are you using for debugging web services and viewing soap 
messages?
Does anybody use http sniffer for it?
   
Thanks in advance,
Alexey
   
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   
  
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 

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



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




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

Fw: [Axis2] SOAPMonitorApplet.class not found

[Martin Gainty]

Good Morning Oliver

Have you compiled SOAPMonitorApplet.java and copied the requisite classes to 
axis2 ROOT folder?


cp SOAPMonitorApplet$ServiceFilterPanel.class into 
$CATALINA_HOME/webapps/axis2 folder ?
cp SOAPMonitorApplet$SOAPMonitorData.class into $CATALINA_HOME/webapps/axis2 
folder ?
cp SOAPMonitorApplet$SOAPMonitorFilter.class into 
$CATALINA_HOME/webapps/axis2 folder ?
cp SOAPMonitorApplet$SOAPMonitorPage.class into $CATALINA_HOME/webapps/axis2 
folder ?
cp SOAPMonitorApplet$SOAPMonitorTableModel.class into 
$CATALINA_HOME/webapps/axis2 folder ?
cp SOAPMonitorApplet$SOAPMonitorTextArea.class into 
$CATALINA_HOME/webapps/axis2 folder ?
cp SOAPMonitorApplet$SOAPMonitorApplet.class into 
$CATALINA_HOME/webapps/axis2 folder ?


also make sure 
org.apache.axis2.soapmonitor.servlet.SOAPMonitorConstants.class is located 
in $CATALINA_HOME/webapps/axis2/org/apache/axis2/soapmonitor/servlet


Also make sure your Socket connections have requisite connect and resolve 
permission on Applet on Port 5001 AND

class files have read/write/execute access in axis2 folder e.g.

vi $CATALINA_HOME/conf/catalina.policy e.g.

grant codeBase file:${catalina.home}/webapps/axis2/- {
   permission java.security.AllPermission;
   permission java.net.SocketPermission localhost:5001, accept,connect, 
listen, resolve;

 };

HTH
Martin--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.


- Original Message - 
From: Oliver Hirschi [EMAIL PROTECTED]

To: axis-user@ws.apache.org
Sent: Tuesday, June 19, 2007 10:53 AM
Subject: [Axis2] SOAPMonitorApplet.class not found



Hi there

I have just installed Axis2 (Version 1.2) and I try to run the 
SOAPMonitor-Applet.

Unfortunately I am not able to run it.

What I have done:
1.) Add 'module ref=soapmonitor/' to axis2.xml of the 
axis2\WEB-INF\conf\ folder.
2.) Add the servlet and servlet-mapping to web.xml of the 
axis2\WEB-INF\ folder.

3.) Restart Tomcat.
There is a axis2-soapmonitor-1.2.jar in the axis2\WEB-INF\lib\ 
directory.


Now, when I call http://localhost:8080/axis2/SOAPMonitor there comes the 
message Applet SOAPMonitorApplet notinited in the browser statusbar.

The Java console shows:

Laden: Klasse SOAPMonitorApplet.class nicht gefunden
java.lang.ClassNotFoundException: SOAPMonitorApplet.class
at sun.applet.AppletClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.applet.AppletClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.applet.AppletClassLoader.loadCode(Unknown Source)
at sun.applet.AppletPanel.createApplet(Unknown Source)
at sun.plugin.AppletViewer.createApplet(Unknown Source)
at sun.applet.AppletPanel.runLoader(Unknown Source)
at sun.applet.AppletPanel.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException: open HTTP connection failed.
at sun.applet.AppletClassLoader.getBytes(Unknown Source)
at sun.applet.AppletClassLoader.access$100(Unknown Source)
at sun.applet.AppletClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
... 10 more


It seems like a classpath-problem, but I don't know where to solve.
I also tried to copy the axis2-soapmonitor-1.2.jar to the 
apache-tomcat-6.0.13\lib\ directory, but it does not help.


Could anyone help me on this problem?

Great thanks.
--
Oliver Hirschi
http://www.FamilyHirschi.ch



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





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

Rampart question and Custom header

[masi]

Hi all,

I'm trying to develop an Identity Provider that uses WS-Trust to issue
SAML 2.0 assertions.

I am using axis2, following the guidelines from the IBM developerworks:
https://www6.software.ibm.com/developerworks/education/ws-understand-web-ser=
vices4/

Do you know any other document regarding the use of rampart?

I put in the services.xml the following:

service name=3DTianiSTS
 description
 Tiani Spirit SecureTokenService
 /description
 parameter =20
name=3DServiceClasscom.spirit.sts.TokenManagerService/parameter
  parameter name=3DInflowSecurity
action
 itemsTimestamp/items
/action
 /parameter

 parameter name=3DOutflowSecurity
action
 itemsTimestamp/items
/action
 /parameter
 operation name=3DRequestTokenIssue
 messageReceiver =20
class=3Dorg.apache.axis2.receivers.RawXMLINOutMessageReceiver/
 /operation

/service

Everything works, the client sends the message with the right headers and
rampart does its checks.

In the client I create the WS-Trust elements requesting the SAML token.

 From the server I take the remainings headers (wstrust) I check them and
if everythings is OK I create the OMElement SAMLAssertion (I do not =20
use OpenSAML2 is I don't know how to write code: examples from =20
internet2 wiki don't work).

First question: How can I add the SAMLAssertion header in the SOAP Response?
I use the MessageContext.getCurrentMessageContext() to get the SOAP =20
Request header, but how can I do it with the response?

Second question: Is rahas capable to issue SAML 2.0 tokens? It uses =20
opensaml1, as I can see.

Third question: In the response message, the Timestamp is not present. =20
Have you idea why?

Thank you,


Massimiliano Masi




This message was sent using IMP, the Internet Messaging Program.



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

Re: Soap viewer or sniffer

[Thomas Jaehnig]

Yes. It also shows the HTTP header and the SOAP body. 
But the body isn't formatted like shown on the picture. 
Wireshark doesn't line wrap, and so it becomes unclear when the soap
body is to big.

thanks for your advice

Thomas

On Thu, 2007-06-21 at 18:18 +0300, Alexey Zavizionov wrote:
 Does Wireshark can show soap body as here on the picture
 http://bp0.blogger.com/_aEfX-L_3RIQ/RcwbginwePI/AAs/X42ssmlnP5s/s1600-h/httplook_screen.JPG
 ?
 I have noticed many snifers, if it will be useful for you look at
 http://zavizionov.blogspot.com/2007/02/http-sniffers.html
 
 Regards,
 Alexey
 
 On 6/21/07, Thomas Jaehnig [EMAIL PROTECTED] wrote:
  No. I didn't know HTTPLook before.
 
  I use Wireshark for many things. Not only for watching HTTP sessions.
  It's very adjustable using filters. And it runs on many plattforms :D
 
  Maybe, HTTPLook is better for analyzing HTTP sessions. I will give it a
  try.
 
  Thomas
 
  On Thu, 2007-06-21 at 18:01 +0300, Alexey Zavizionov wrote:
   Look like HTTPLook better than Wireshark.
   Did you use HTTPLook?
  
   Alexey
  
   On 6/21/07, Alexey Zavizionov [EMAIL PROTECTED] wrote:
Hi, Thomas
   
Thanks, I'll try it!
I use the HTTPLook, but it's some times doesn't work.
   
Regards,
Alexey
   
On 6/21/07, Thomas Jaehnig [EMAIL PROTECTED] wrote:
 Hi,

 i prefer wireshark. This tool has a nice function called Follow TCP
 Stream. Using this you can see the whole conversation between the
 parties.

 regard

 Thomas

 On Thu, 2007-06-21 at 16:23 +0300, Alexey Zavizionov wrote:
  Hello,
 
  Which tools are you using for debugging web services and viewing 
  soap messages?
  Does anybody use http sniffer for it?
 
  Thanks in advance,
  Alexey
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 


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


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


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

docs for wss4j

[Richard DeGrande]

Hi

I'm trying to write a WS client to a secure service using axis 1.4 and wss4j.  
I am having some difficulty finding information on the use of wss4j.  Does 
anyone know of any links that could help me out ?

thanks in advance


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

Re: SOAP response

[Demetris G]

Hi Jeff,

   yes you are absolutely right - I took a look at the 
axis.transport.http.HTTPSender
and the code expects the headers. So on the server side I got the header 
from the
post object and fed them back into the client engine. That took care of 
the number
format issue - now it is just stalling without complaining. Hmm .. I 
wonder what else

it needs.

Thanks again man

Walker, Jeff wrote:

Hi Demetris,
I'm using Axis 1.3, but these are the HTTP headers that my requests tend
to have:

POST /axis/services/ExampleAxisService HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related,
text/*
User-Agent: Axis/1.3
Host: 127.0.0.1:1234
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: 
Content-Length: 445

?xml version=1.0 encoding=UTF-8?soapenv:Envelope ...

And these are the ones on the response:
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=09876Jeffrey; Domain=pag; Expires=Thu,
21-Jun-2007 15:31:07 GMT
Content-Type: text/xml;charset=utf-8
Date: Thu, 21 Jun 2007 12:44:27 GMT
Connection: close

?xml version=1.0 encoding=utf-8?soapenv:Envelope ...


Obviously, you can change the SOAPAction and a few of the others, but
the answer I believe is yes, the HTTP headers do matter in web services
that go over the http protocol.
-jeff



 


-Original Message-
From: Demetris G [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, June 20, 2007 8:00 PM

To: Demetris G
Cc: axis-user@ws.apache.org
Subject: Re: SOAP response


Hi again,

I didn't get a response for the simple issue below so I am trying 
again. I intercept the
response from a legitimate SOAP call to a remote Axis container and I 
return it back

to the client by simply feeding it into the socket that the client wrote

the HTTP bundle
to. Shouldn't this work ? what I am missing ? Is the client side 
excepting to see HTTP

headers etc and not just the SOAP response ? I will appreciate any ideas

on this.

Thanks

Demetris G wrote:
  

Hi all,

   I am manually feeding the following SOAP response into an Axis 
engine that requested
this through a SOAP message and Axis responds with a 
java.lang.NumberFormatException

For input string quot;version=quot;1.0quot; etc.

   Shouldn't the msg below be accepted with no issues from the engine 
?? What is it missing?


Thanks much



?xml version=1.0 encoding=UTF-8?soapenv:Envelope 
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:Bodyns1
:getBundlesResponse 
  
soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 


xmlns:ns1=http://soapobject.bundle.knopflerfish.org;getBundlesReturn 
  
soapenc:arrayType=xsd:long[24] xsi:type=soapenc:Array 



xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;getBundlesRet
urn 
  
href=#id0/getBundlesReturn href=#id1/getBundlesReturn 
href=#id2/getBundlesReturn href=#id3/getBundlesReturn 
href=#id4/getBundlesReturn href=#id5/getBundlesReturn 
href=#id6/getBundlesReturn href=#id7/getBundlesReturn 
href=#id8/getBundlesReturn href=#id9/getBundlesReturn 
href=#id10/getBundlesReturn href=#id11/getBundlesReturn 
href=#id12/getBundlesReturn href=#id13/getBundlesReturn 
href=#id14/getBundlesReturn href=#id15/getBundlesReturn 
href=#id16/getBundlesReturn href=#id17/getBundlesReturn 
href=#id18/getBundlesReturn href=#id19/getBundlesReturn 
href=#id20/getBundlesReturn href=#id21/getBundlesReturn 
href=#id22/getBundlesReturn 
href=#id23//getBundlesReturn/ns1:getBundlesResponsemultiRef 
id=id12 soapenc:root=0 
soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
xsi:type=xsd:long 



xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;18/multiRef
multiRef 
  
id=id22 soapenc:root=0 
soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
xsi:type=xsd:long 



xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;22/multiRef
multiRef 
  
id=id17 soapenc:root=0 
soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
xsi:type=xsd:long 



xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;23/multiRef
multiRef 
  
id=id14 soapenc:root=0 
soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
xsi:type=xsd:long 



xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;13/multiRef
multiRef 
  
id=id18 soapenc:root=0 
soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
xsi:type=xsd:long 



xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;17/multiRef
multiRef 
  
id=id16 soapenc:root=0 
soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
xsi:type=xsd:long 



xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;12/multiRef
multiRef 
  
id=id20 soapenc:root=0 
soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
xsi:type=xsd:long 



xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;6/multiRefm
ultiRef 
  
id=id9 soapenc:root=0 

RE: Array in axis 2

[Raghu Upadhyayula]

Hi Chris,

 

Try changing your wsdl as shown below in blue

 

Thanks

Raghu

 



From: Chris Shah [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, June 20, 2007 7:33 PM
To: axis-user@ws.apache.org
Subject: Array in axis 2

 

I am writing a doc literal wsdl. I have an issue with creating an array
of objects. I have an element 'a' and another element 'b' which is an
array of objects 'a'. WSDL2JAVA gives me 

 

WARNING: Type {http://sample.com/}a missing!

 

Here are the wsdl snippets:

 

xsd:element name=a
xsd:complexType name=a
xsd:sequence
xsd:element minOccurs=0 name=str
type=xsd:string /
xsd:element minOccurs=0 name=num
type=xsd:int /
/xsd:sequence
/xsd:complexType
/xsd:element

 

   xsd:element name=b
   xsd:complexType
   xsd:sequence
 xsd:element minOccurs=0 maxOccurs=unbounded name=p
type=ns1:a/
  /xsd:sequence
   /xsd:complexType
   /xsd:element

 

ns1 is defined in the definitions as xmlns:ns1=http://mysample.com/;

 

If I specify type=a, that doesn't work either and I get the same
warning. 

 

ANy help will be appreciated.

 

TIA

Cris 

 

 

 

  



Fussy? Opinionated? Impossible to please? Perfect. Join Yahoo!'s user
panel
http://us.rd.yahoo.com/evt=48516/*http:/surveylink.yahoo.com/gmrs/yahoo
_panel_invite.asp?a=7%20  and lay it on us. 

Re: [Axis2] wsdl2java code generation errors with jaxb and soap header

[andreas netter]

Hi,
has nobody a comment on this?
i think it is no good idea to fix errors in the generated code manually.

greets,
andi

[EMAIL PROTECTED] schrieb:
 Hello,

 I generate client code out of a wsdl with axis2 (v. 1.2) wsdl2java and 
 jaxbri(v. 2.0.2) databinding.
 the wsdl not only defines request and reply messages but also the header 
 element of the soap message.

 i have the following problems with the generated code:
 1) The generated code for the client stub doesn't compile because of a 
 parameter error in the toOM-Method for the Header.
 2) When i fix the error, the invocation of toOM fails because of incorrect/ 
 missing values when creating the OMElement for the Header
 3) When i fix this error too by filling in the correct values for the 
 HeaderType, the client code works. 

 I think the wsdl is correct because generated code with adb binding out of 
 this wsdl works fine.

 It seems that axis2 code generation doesn't generate correct code with jaxb 
 binding when you have defined a soap header in the wsdl. 
 Does someone have a similiar problem (or fixed it)?

 greetings from sunny munich :)
 andi

 some code snippets from the generated stub:

 toOM-Method call. mMS150_Display0 represents the request data type, 
 mws1 the header data type.
 1)--
 **snip**
 env = toEnvelope(getFactory(
   _operationClient.getOptions().getSoapVersionURI()), 
   mMS150_Display0, 
   optimizeContent(new javax.xml.namespace.QName(, MMS150_Display)));
 env.build();
 // add the children only if the parameter is not null
 if (mws1!=null){
   env.getHeader().addChild(
   toOM(mws1, optimizeContent(new javax.xml.namespace.QName(, 
 MMS150_Display;
 }
 **snap**

 toOM-Method for the header:
 2)--
 **snip**
 private org.apache.axiom.om.OMElement toOM(net.company.mws.mws2.HeaderType 
 param, org.apache.axiom.soap.SOAPFactory factory, boolean optimizeContent) {
 try {
 javax.xml.bind.JAXBContext context = net_company_mws_mws2_HeaderType;
 javax.xml.bind.Marshaller marshaller = context.createMarshaller();
 marshaller.setProperty(javax.xml.bind.Marshaller.JAXB_FRAGMENT, 
 Boolean.TRUE);

 JaxbRIDataSource source = new JaxbRIDataSource( 
 net.company.mws.mws2.HeaderType.class,
 param,
 marshaller,
 ,
 );
 org.apache.axiom.om.OMNamespace namespace = 
 factory.createOMNamespace(,
null);
 return factory.createOMElement(source, , namespace);
 } catch (javax.xml.bind.JAXBException bex){
 throw new RuntimeException(bex);
 }
 }

 **snap**

 the call of the toOM-Method (with Parameters HeaderType, boolean) doesn't 
 fit with the signature of the toOm-Method (HeaderType, SOAPFactory, boolean)
 i can correct this error by adding 
 getFactory(_operationClient.getOptions().getSoapVersionURI()) to the 
 toOM-Method call in the generated stub.
 then i run into the second error i mentioned above. 

 The following code snippet shows the correct values for in the toOM-Method:
 3)--
 **snip**
 JaxbRIDataSource source = new JaxbRIDataSource( 
 net.company.mws.mws2.HeaderType.class,
 param,
 marshaller,
 http://mws.company.net/mws2;,
 mws);
 org.apache.axiom.om.OMNamespace namespace = factory.createOMNamespace(,
null);
 return factory.createOMElement(source, mws, namespace);
 **snap**

 the wsdl:
 --
 **snip**
 ?xml version=1.0 encoding=UTF-8?
 wsdl:definitions xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; 
   xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; 
   xmlns:mws=http://mws.company.net/mws2; 
   xmlns:tns=http://schemas.company.com/KKTEST2; 
   
 xmlns:mms150_display=http://schemas.company.com/KKTEST2/MMS150_Display; 
   name=KKTEST2 targetNamespace=http://schemas.company.com/KKTEST2;
   wsdl:types
 xsd:schema xmlns:xsd=http://www.w3.org/2001/XMLSchema; 
 targetNamespace=http://schemas.company.com/KKTEST2/MMS150_Display; 
 elementFormDefault=qualified
   xsd:element name=MMS150_Display 
 type=mms150_display:MMS150_DisplayType /
   xsd:complexType name=MMS150_DisplayType
 xsd:sequence
   xsd:element name=MMS150 type=mms150_display:ct_0 /
 /xsd:sequence
   /xsd:complexType
   xsd:complexType name=ct_0
 xsd:sequence
   xsd:element name=User nillable=true maxOccurs=1 
 

RE: SOAP response

[Walker, Jeff]

Is it the client that is stalling?
Then I would guess it is waiting for the correct terminating character.
(Is there some terminator that the http protocol uses to end a
response??) When I emailed the request/response http headers, I used
tcpmon to capture them, and that may have stripped off any terminating
character, so I can't see it.

Can you turn on your debugger and step through the code and see if the
client is stalled waiting for the response to complete?
-jeff


 

-Original Message-
From: Demetris G [mailto:[EMAIL PROTECTED] 
Sent: Thursday, June 21, 2007 1:51 PM
To: axis-user@ws.apache.org
Subject: Re: SOAP response


Hi Jeff,

yes you are absolutely right - I took a look at the 
axis.transport.http.HTTPSender
and the code expects the headers. So on the server side I got the header

from the
post object and fed them back into the client engine. That took care of 
the number
format issue - now it is just stalling without complaining. Hmm .. I 
wonder what else
it needs.

Thanks again man

Walker, Jeff wrote:
 Hi Demetris,
 I'm using Axis 1.3, but these are the HTTP headers that my requests
tend
 to have:

 POST /axis/services/ExampleAxisService HTTP/1.0
 Content-Type: text/xml; charset=utf-8
 Accept: application/soap+xml, application/dime, multipart/related,
 text/*
 User-Agent: Axis/1.3
 Host: 127.0.0.1:1234
 Cache-Control: no-cache
 Pragma: no-cache
 SOAPAction: 
 Content-Length: 445

 ?xml version=1.0 encoding=UTF-8?soapenv:Envelope ...

 And these are the ones on the response:
 HTTP/1.1 200 OK
 Server: Apache-Coyote/1.1
 Set-Cookie: JSESSIONID=09876Jeffrey; Domain=pag; Expires=Thu,
 21-Jun-2007 15:31:07 GMT
 Content-Type: text/xml;charset=utf-8
 Date: Thu, 21 Jun 2007 12:44:27 GMT
 Connection: close

 ?xml version=1.0 encoding=utf-8?soapenv:Envelope ...


 Obviously, you can change the SOAPAction and a few of the others, but
 the answer I believe is yes, the HTTP headers do matter in web
services
 that go over the http protocol.
 -jeff



  

 -Original Message-
 From: Demetris G [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, June 20, 2007 8:00 PM
 To: Demetris G
 Cc: axis-user@ws.apache.org
 Subject: Re: SOAP response


 Hi again,

 I didn't get a response for the simple issue below so I am trying 
 again. I intercept the
 response from a legitimate SOAP call to a remote Axis container and I 
 return it back
 to the client by simply feeding it into the socket that the client
wrote

 the HTTP bundle
 to. Shouldn't this work ? what I am missing ? Is the client side 
 excepting to see HTTP
 headers etc and not just the SOAP response ? I will appreciate any
ideas

 on this.

 Thanks

 Demetris G wrote:
   
 Hi all,

I am manually feeding the following SOAP response into an Axis 
 engine that requested
 this through a SOAP message and Axis responds with a 
 java.lang.NumberFormatException
 For input string quot;version=quot;1.0quot; etc.

Shouldn't the msg below be accepted with no issues from the engine

 ?? What is it missing?

 Thanks much



 ?xml version=1.0 encoding=UTF-8?soapenv:Envelope 
 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:Bodyns1
 :getBundlesResponse 
   
 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 

 

xmlns:ns1=http://soapobject.bundle.knopflerfish.org;getBundlesReturn 
   
 soapenc:arrayType=xsd:long[24] xsi:type=soapenc:Array 

 

xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;getBundlesRet
 urn 
   
 href=#id0/getBundlesReturn href=#id1/getBundlesReturn 
 href=#id2/getBundlesReturn href=#id3/getBundlesReturn 
 href=#id4/getBundlesReturn href=#id5/getBundlesReturn 
 href=#id6/getBundlesReturn href=#id7/getBundlesReturn 
 href=#id8/getBundlesReturn href=#id9/getBundlesReturn 
 href=#id10/getBundlesReturn href=#id11/getBundlesReturn 
 href=#id12/getBundlesReturn href=#id13/getBundlesReturn 
 href=#id14/getBundlesReturn href=#id15/getBundlesReturn 
 href=#id16/getBundlesReturn href=#id17/getBundlesReturn 
 href=#id18/getBundlesReturn href=#id19/getBundlesReturn 
 href=#id20/getBundlesReturn href=#id21/getBundlesReturn 
 href=#id22/getBundlesReturn 
 href=#id23//getBundlesReturn/ns1:getBundlesResponsemultiRef 
 id=id12 soapenc:root=0 
 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
 xsi:type=xsd:long 

 

xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;18/multiRef
 multiRef 
   
 id=id22 soapenc:root=0 
 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
 xsi:type=xsd:long 

 

xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;22/multiRef
 multiRef 
   
 id=id17 soapenc:root=0 
 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
 xsi:type=xsd:long 

 

xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;23/multiRef
 multiRef 
   
 id=id14 soapenc:root=0 
 

Re: SOAP response

[Demetris G]

Hey Jeff,

   I am working on that now. I am going to step through it to see what 
the story is. But
I think you may have a good point there cause I am sending it all that 
it needs. I will

let you know.

Thanks

Walker, Jeff wrote:

Is it the client that is stalling?
Then I would guess it is waiting for the correct terminating character.
(Is there some terminator that the http protocol uses to end a
response??) When I emailed the request/response http headers, I used
tcpmon to capture them, and that may have stripped off any terminating
character, so I can't see it.

Can you turn on your debugger and step through the code and see if the
client is stalled waiting for the response to complete?
-jeff


 


-Original Message-
From: Demetris G [mailto:[EMAIL PROTECTED] 
Sent: Thursday, June 21, 2007 1:51 PM

To: axis-user@ws.apache.org
Subject: Re: SOAP response


Hi Jeff,

yes you are absolutely right - I took a look at the 
axis.transport.http.HTTPSender

and the code expects the headers. So on the server side I got the header

from the
post object and fed them back into the client engine. That took care of 
the number
format issue - now it is just stalling without complaining. Hmm .. I 
wonder what else

it needs.

Thanks again man

Walker, Jeff wrote:
  

Hi Demetris,
I'm using Axis 1.3, but these are the HTTP headers that my requests


tend
  

to have:

POST /axis/services/ExampleAxisService HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related,
text/*
User-Agent: Axis/1.3
Host: 127.0.0.1:1234
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: 
Content-Length: 445

?xml version=1.0 encoding=UTF-8?soapenv:Envelope ...

And these are the ones on the response:
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=09876Jeffrey; Domain=pag; Expires=Thu,
21-Jun-2007 15:31:07 GMT
Content-Type: text/xml;charset=utf-8
Date: Thu, 21 Jun 2007 12:44:27 GMT
Connection: close

?xml version=1.0 encoding=utf-8?soapenv:Envelope ...


Obviously, you can change the SOAPAction and a few of the others, but
the answer I believe is yes, the HTTP headers do matter in web


services
  

that go over the http protocol.
-jeff



 


-Original Message-
From: Demetris G [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, June 20, 2007 8:00 PM

To: Demetris G
Cc: axis-user@ws.apache.org
Subject: Re: SOAP response


Hi again,

I didn't get a response for the simple issue below so I am trying 
again. I intercept the
response from a legitimate SOAP call to a remote Axis container and I 
return it back

to the client by simply feeding it into the socket that the client


wrote
  

the HTTP bundle
to. Shouldn't this work ? what I am missing ? Is the client side 
excepting to see HTTP

headers etc and not just the SOAP response ? I will appreciate any


ideas
  

on this.

Thanks

Demetris G wrote:
  


Hi all,

   I am manually feeding the following SOAP response into an Axis 
engine that requested
this through a SOAP message and Axis responds with a 
java.lang.NumberFormatException

For input string quot;version=quot;1.0quot; etc.

   Shouldn't the msg below be accepted with no issues from the engine
  


  

?? What is it missing?

Thanks much



?xml version=1.0 encoding=UTF-8?soapenv:Envelope 
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:Bodyns1
  
:getBundlesResponse 
  

soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 


  
xmlns:ns1=http://soapobject.bundle.knopflerfish.org;getBundlesReturn 
  
  

soapenc:arrayType=xsd:long[24] xsi:type=soapenc:Array 


  

xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;getBundlesRet
  
urn 
  

href=#id0/getBundlesReturn href=#id1/getBundlesReturn 
href=#id2/getBundlesReturn href=#id3/getBundlesReturn 
href=#id4/getBundlesReturn href=#id5/getBundlesReturn 
href=#id6/getBundlesReturn href=#id7/getBundlesReturn 
href=#id8/getBundlesReturn href=#id9/getBundlesReturn 
href=#id10/getBundlesReturn href=#id11/getBundlesReturn 
href=#id12/getBundlesReturn href=#id13/getBundlesReturn 
href=#id14/getBundlesReturn href=#id15/getBundlesReturn 
href=#id16/getBundlesReturn href=#id17/getBundlesReturn 
href=#id18/getBundlesReturn href=#id19/getBundlesReturn 
href=#id20/getBundlesReturn href=#id21/getBundlesReturn 
href=#id22/getBundlesReturn 
href=#id23//getBundlesReturn/ns1:getBundlesResponsemultiRef 
id=id12 soapenc:root=0 
soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
xsi:type=xsd:long 


  

xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;18/multiRef
  
multiRef 
  

id=id22 soapenc:root=0 
soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
xsi:type=xsd:long 


  

xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;22/multiRef
  
multiRef 
  
  

[Axis2] Streaming dynamically generated large sized content

[Shalab Goel]

Hello Everyone,

 

I am looking for some assistance with streaming large sized dynamically
generated content.

 

I have defined an 'echoString' operation, which takes two request
arguments a string to repeat, and count of number of times to repeat.
This is a service which replicates somewhat the requirement I am working
on - to be able to stream dynamically generated content (size in order
of 50 to 200 MBs). 

 

public OMElement echoString (String echo, String count)
throws Exception

{

PipedInputStream inStream = new
PipedInputStream();

PipedOutputStream outStream = new
PipedOutputStream(inStream);

 

DataHandler dh = new DataHandler(inStream,
text/plain);

 

MessageContext inCtx =
MessageContext.getCurrentMessageContext();

   OperationContext operationContext =
inCtx.getOperationContext();

   MessageContext outCtx = operationContext

 
.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);



String attachmentID = outCtx.addAttachment(dh);

 

OMFactory fac =
OMAbstractFactory.getOMFactory();

OMNamespace omNs = fac.createOMNamespace(

 
http://service.soapwithattachments.sample/xsd;, swa);

OMElement echoStringOp =
fac.createOMElement(echoStringResponse, omNs);

OMElement idEle =
fac.createOMElement(attchmentID, omNs);

idEle.addAttribute(href,
cid:+attachmentID,null);

echoStringOp.addChild(idEle);

 

byte bytes[] = strArg.getBytes();

try

{

  for (int i=0; i  cntArg; i++)

  outStream.write(bytes);

  outStream.flush();

  outStream.close();

}

catch (Exception e) {};

 

return echoStringOp;

}

 

In the services.xml, I have added parameter for enabling SWA

 

 parameter name=enableSwAtrue/parameter

 

 

When I run my client code, I get the following exception trace:

 

contentID 0.urn:uuid:[EMAIL PROTECTED]

Exception in thread main java.io.IOException: eosBeforeMarker

  at
org.apache.axiom.attachments.BoundaryDelimitedStream.read(BoundaryDelimi
tedStream.java:300)

  at
org.apache.axiom.attachments.IncomingAttachmentInputStream.read(Incoming
AttachmentInputStream.java:121)

  at
sample.soapwithattachments.client.SWAClient.callEchoManyTimes(SWAClient.
java:212)

  at
sample.soapwithattachments.client.SWAClient.main(SWAClient.java:59)

 

 

Following is how the attachment is being accessed in client code:

 

MessageContext response = mepClient

 
.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);

Attachments attachments =
response.getAttachmentMap();

IncomingAttachmentStreams streams =
attachments.getIncomingAttachmentStreams();

IncomingAttachmentInputStream inStream = null;

if (streams != null)

{

inStream = streams.getNextStream();

System.out.println(contentID  +
inStream.getContentId());

}

 

Following is the SOAP request (in TCPMonitor):

-  

 

POST /axis2/services/SWASampleService HTTP/1.1

Content-Type: multipart/related;
boundary=MIMEBoundaryurn_uuid_C2F2DEF18072BF88741182450074533;
type=text/xml;
start=0.urn:uuid:[EMAIL PROTECTED];
charset=UTF-8

SOAPAction: urn:echoString

User-Agent: Axis2

Host: 127.0.0.1:8081

Transfer-Encoding: chunked

 

231

--MIMEBoundaryurn_uuid_C2F2DEF18072BF88741182450074533

Content-Type: text/xml; charset=UTF-8

Content-Transfer-Encoding: 8bit

Content-ID: 0.urn:uuid:[EMAIL PROTECTED]

   ?xml version='1.0' encoding='UTF-8'?

  soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;

 soapenv:Body

swa:echoString
xmlns:swa=http://service.soapwithattachments.sample/xsd;

   swa:echohowdy/swa:echo

   swa:count45/swa:count

/swa:echoString

 /soapenv:Body

 
/soapenv:Envelope--MIMEBoundaryurn_uuid_C2F2DEF18072BF8874118245007453
3-0

 

 

Following is the SOAP response (showing Fault)

--


 

HTTP/1.1 200 OK

Server: Apache-Coyote/1.1

Content-Type: multipart/related;
boundary=MIMEBoundaryurn_uuid_DFCA23517587D8F2141182450081761;
type=text/xml;
start=0.urn:uuid:[EMAIL PROTECTED];charset=
UTF-8Transfer-Encoding: chunkedDate: Thu, 

[AXIS2]: How to have a client tunnel through a proxy server

[Masin, Valerie]

We need to do firewall tunneling via a proxy server. This means we need
to tell the client what the proxy address is, in addition to the actual
server endpoint. We can't set it on the jvm because we need to change it
dynamically at runtime.
Does anyone know how to do this using Axis?
Thanks, Valerie

HTTP/1.1 400 Bad Request

[Jorge Fernandez]

Hi again,

I was trying to get some information on this problem but I couldn't know what 
is happening so I'm trying again.

Does anybody know anything about how can I fix this???

Thanks a lot,

Jorge Fernández

Jorge Fernandez [EMAIL PROTECTED] escribió: Hi all,

I'm having problems only when throwing exceptions. I'm getting bad request. 
This problem appeared since I moved to axis2 1.2, using it with Tomcat. If I 
use axis as standalone server there's no problem. 

The messages are apparently the same except for some minimal changes in the 
order of HTTP header, the prefix for the description element namespace and that 
the final character after envelope in one case appears in the following line. 
This are the messages:

The correct one with standalone axis:

HTTP/1.1 500 Internal server error
Date: Wed, 13 Jun 2007 08:22:37 GMT
Content-Type: application/soap+xml; 
action=http://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault;
Server: Simple-Server/1.1
Transfer-Encoding: chunked
Connection: Close

3a2
?xml version='1.0' encoding='UTF-8'?
   soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing;  
xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
  soapenv:Header
 
wsa:Actionhttp://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault/wsa:Action
 wsa:RelatesTourn:uuid:B2AFE74A4124DE7BFF1181722957402/wsa:RelatesTo
  /soapenv:Header
  soapenv:Body
 soapenv:Fault
soapenv:Code
   soapenv:Valuesoapenv:Sender/soapenv:Value
 /soapenv:Code
soapenv:Reason
   soapenv:Text 
xml:lang=en-USValidationFaultException/soapenv:Text
/soapenv:Reason
soapenv:Detail
   ns4:ValidationException 
xmlns:ns4=http://op_messages.medici_link/xsd;
  ns4:ValidationFault
 s2:description 
xmlns:s2=http://faults.medici_link/xsd;User not validated. You  must validate 
before invoking a method./s2:description
  /ns4:ValidationFault
   /ns4:ValidationException
/soapenv:Detail
 /soapenv:Fault
  /soapenv:Body
   /soapenv:Envelope0


The bad one with tomcat:

HTTP/1.1 400 Petición incorrecta
Server: Apache-Coyote/1.1
Content-Type: application/soap+xml; 
action=http://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault;charset=UTF-8
Transfer-Encoding: chunked
Date: Wed, 13 Jun 2007 08:12:50 GMT
Connection: close

3a2
?xml version='1.0'  encoding='UTF-8'?
   soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; 
xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
  soapenv:Header
 
wsa:Actionhttp://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault/wsa:Action
 wsa:RelatesTourn:uuid:61931C3AAB6FF83F181181722371001/wsa:RelatesTo
  /soapenv:Header
  soapenv:Body
 soapenv:Fault
soapenv:Code
soapenv:Valuesoapenv:Sender/soapenv:Value
/soapenv:Code
soapenv:Reason
   soapenv:Text 
xml:lang=en-USValidationFaultException/soapenv:Text
/soapenv:Reason
soapenv:Detail
   ns4:ValidationException 
xmlns:ns4=http://op_messages.medici_link/xsd;
   ns4:ValidationFault
 s1:description 
xmlns:s1=http://faults.medici_link/xsd;User not validated. You must validate 
before invoking a method./s1:description
  /ns4:ValidationFault
   /ns4:ValidationException
/soapenv:Detail
 /soapenv:Fault
  /soapenv:Body
   /soapenv:Envelope
0








-

LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com

   
-

¡Descubre una nueva forma de obtener respuestas a tus preguntas!
Entra en Yahoo! Respuestas.

Re: HTTP/1.1 400 Bad Request

[Martin Gainty]

undecipherable characters (specifically 3a2) is being introduced before the 
beginning xml tag which neither the servlet or the client stub can interpret
I have seen this happen with Chunked encoding

try to disable parameter name=Transfer-Encoding (commenting out the 
parameter name=Transfer-Encoding from axis2.xml)
and re-deploy

Saludos
M--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.

  - Original Message - 
  From: Jorge Fernandez 
  To: axis-user@ws.apache.org 
  Sent: Thursday, June 21, 2007 3:40 PM
  Subject: HTTP/1.1 400 Bad Request


  Hi again,

  I was trying to get some information on this problem but I couldn't know what 
is happening so I'm trying again.

  Does anybody know anything about how can I fix this???

  Thanks a lot,

  Jorge Fernández

  Jorge Fernandez [EMAIL PROTECTED] escribió:
Hi all,

I'm having problems only when throwing exceptions. I'm getting bad 
request. This problem appeared since I moved to axis2 1.2, using it with 
Tomcat. If I use axis as standalone server there's no problem. 

The messages are apparently the same except for some minimal changes in the 
order of HTTP header, the prefix for the description element namespace and that 
the final character after envelope in one case appears in the following line. 
This are the messages:

The correct one with standalone axis:

HTTP/1.1 500 Internal server error
Date: Wed, 13 Jun 2007 08:22:37 GMT
Content-Type: application/soap+xml; 
action=http://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault;
Server: Simple-Server/1.1
Transfer-Encoding: chunked
Connection: Close

3a2
?xml version='1.0' encoding='UTF-8'?
   soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; 
xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
  soapenv:Header
 
wsa:Actionhttp://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault/wsa:Action
 
wsa:RelatesTourn:uuid:B2AFE74A4124DE7BFF1181722957402/wsa:RelatesTo
  /soapenv:Header
  soapenv:Body
 soapenv:Fault
soapenv:Code
   soapenv:Valuesoapenv:Sender/soapenv:Value
/soapenv:Code
soapenv:Reason
   soapenv:Text 
xml:lang=en-USValidationFaultException/soapenv:Text
/soapenv:Reason
soapenv:Detail
   ns4:ValidationException 
xmlns:ns4=http://op_messages.medici_link/xsd;
  ns4:ValidationFault
 s2:description 
xmlns:s2=http://faults.medici_link/xsd;User not validated. You must validate 
before invoking a method./s2:description
  /ns4:ValidationFault
   /ns4:ValidationException
/soapenv:Detail
 /soapenv:Fault
  /soapenv:Body
   /soapenv:Envelope0


The bad one with tomcat:

HTTP/1.1 400 Petición incorrecta
Server: Apache-Coyote/1.1
Content-Type: application/soap+xml; 
action=http://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault;charset=UTF-8
Transfer-Encoding: chunked
Date: Wed, 13 Jun 2007 08:12:50 GMT
Connection: close

3a2
?xml version='1.0' encoding='UTF-8'?
   soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; 
xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
  soapenv:Header
 
wsa:Actionhttp://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault/wsa:Action
 
wsa:RelatesTourn:uuid:61931C3AAB6FF83F181181722371001/wsa:RelatesTo
  /soapenv:Header
  soapenv:Body
 soapenv:Fault
soapenv:Code
   soapenv:Valuesoapenv:Sender/soapenv:Value
/soapenv:Code
soapenv:Reason
   soapenv:Text 
xml:lang=en-USValidationFaultException/soapenv:Text
/soapenv:Reason
soapenv:Detail
   ns4:ValidationException 
xmlns:ns4=http://op_messages.medici_link/xsd;
  ns4:ValidationFault
 s1:description 
xmlns:s1=http://faults.medici_link/xsd;User not validated. You must validate 
before invoking a method./s1:description
  /ns4:ValidationFault
   /ns4:ValidationException
/soapenv:Detail
 /soapenv:Fault
  /soapenv:Body
   /soapenv:Envelope
0










LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.

Re: HTTP/1.1 400 Bad Request

[Jorge Fernandez]

Hola Martin:

I tried what you said but the problem is the same. Furthermore, those 
characters remain appearing even commenting every Transfer-Encoding parameter.

 I think that it's something related to Tomcat because the code 400 on HTTP 
header only appears when deploying Axis2 under Tomcat. 

Saludos y muchas gracias again,

Jorge Fernandez


Martin Gainty [EMAIL PROTECTED] escribió:   undecipherable characters 
(specifically 3a2)  is being introduced before the beginning xml tag which 
neither the servlet or  the client stub can interpret
 I have seen this happen with Chunked  encoding
 
try to disable parameter  name=Transfer-Encoding (commenting out the 
parameter  name=Transfer-Encoding from axis2.xml)
and re-deploy
  
 Saludos
 M--
 This email message and any files transmitted with it contain  confidential
information intended only for the person(s) to whom this email  message is
addressed.  If you have received this email message in error,  please notify
the sender immediately by telephone or email and destroy the  original
message without making a copy.  Thank you.

- Original Message - 
   From:Jorge Fernandez 
   To: axis-user@ws.apache.org 
   Sent: Thursday, June 21, 2007 3:40PM
   Subject: HTTP/1.1 400 Bad Request
   

Hi again,

I was trying to get some information on thisproblem but I couldn't know 
what is happening so I'm trying again.

Doesanybody know anything about how can I fix this???

Thanks alot,

Jorge Fernández

Jorge Fernandez [EMAIL PROTECTED]escribió:   Hi  all,

I'm having problems only when throwing exceptions. I'm getting  bad 
request. This problem appeared since I moved to axis2 1.2, using it  with 
Tomcat. If I use axis as standalone server there's no problem.  

The messages are apparently the same except for some minimal changes  in 
the order of HTTP header, the prefix for the description element  namespace 
and that the final character after envelope in one case appears in  the 
following line. This are the messages:

The correct one with  standalone axis:

HTTP/1.1 500 Internal server error
Date: Wed, 13  Jun 2007 08:22:37 GMT
Content-Type: application/soap+xml;  
action=http://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault;
Server:  Simple-Server/1.1
Transfer-Encoding: chunked
Connection:  Close

3a2
?xml version='1.0'  encoding='UTF-8'?
   soapenv:Envelope  xmlns:wsa=http://www.w3.org/2005/08/addressing;  
xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
   soapenv:Header
  
wsa:Actionhttp://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault/wsa:Action
  
wsa:RelatesTourn:uuid:B2AFE74A4124DE7BFF1181722957402/wsa:RelatesTo
   /soapenv:Header
   soapenv:Body
  soapenv:Fault
 soapenv:Code
soapenv:Valuesoapenv:Sender/soapenv:Value
 /soapenv:Code
 soapenv:Reason
soapenv:Text  
xml:lang=en-USValidationFaultException/soapenv:Text
 /soapenv:Reason
 soapenv:Detail
ns4:ValidationException  
xmlns:ns4=http://op_messages.medici_link/xsd;
   ns4:ValidationFault
  s2:description 
xmlns:s2=http://faults.medici_link/xsd;User not  validated. You must 
validate before invoking a  method./s2:description
   /ns4:ValidationFault
/ns4:ValidationException
 /soapenv:Detail
  /soapenv:Fault
   /soapenv:Body
/soapenv:Envelope0


The bad one with  tomcat:

HTTP/1.1 400 Petición incorrecta
Server:  Apache-Coyote/1.1
Content-Type: application/soap+xml;  
action=http://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault;charset=UTF-8
Transfer-Encoding:  chunked
Date: Wed, 13 Jun 2007 08:12:50 GMT
Connection:  close

3a2
?xml version='1.0'  encoding='UTF-8'?
   soapenv:Envelope  xmlns:wsa=http://www.w3.org/2005/08/addressing;  
xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
   soapenv:Header
  
wsa:Actionhttp://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault/wsa:Action
  
wsa:RelatesTourn:uuid:61931C3AAB6FF83F181181722371001/wsa:RelatesTo
   /soapenv:Header
   soapenv:Body
  soapenv:Fault
 soapenv:Code
soapenv:Valuesoapenv:Sender/soapenv:Value
 /soapenv:Code
 soapenv:Reason
soapenv:Text  
xml:lang=en-USValidationFaultException/soapenv:Text
 /soapenv:Reason
 soapenv:Detail
ns4:ValidationException  
xmlns:ns4=http://op_messages.medici_link/xsd;
   ns4:ValidationFault
  s1:description 

Re: SOAP response

[Demetris G]

I am sending the message out as a string with (first) and then without 
LF/CR and
either way it is stuck. I am not sure what else it needs since this 
should be
straight forward - the Axis server gives this, then we feed it back into 
the client

socket. What am I missing ? Any Axis developers have any ideas ? I am using
Axis 1.4.

One interesting thing that I noticed is that the generated client SOAP 
message

is HTTP/1.0 and the SOAP response is HTTP/1.1. These are the same engines
for crying out loud, so why would the HTTP versions be different ? Is the
WSDL2Java the issue ?

Thanks much

Walker, Jeff wrote:

Is it the client that is stalling?
Then I would guess it is waiting for the correct terminating character.
(Is there some terminator that the http protocol uses to end a
response??) When I emailed the request/response http headers, I used
tcpmon to capture them, and that may have stripped off any terminating
character, so I can't see it.

Can you turn on your debugger and step through the code and see if the
client is stalled waiting for the response to complete?
-jeff


 


-Original Message-
From: Demetris G [mailto:[EMAIL PROTECTED] 
Sent: Thursday, June 21, 2007 1:51 PM

To: axis-user@ws.apache.org
Subject: Re: SOAP response


Hi Jeff,

yes you are absolutely right - I took a look at the 
axis.transport.http.HTTPSender

and the code expects the headers. So on the server side I got the header

from the
post object and fed them back into the client engine. That took care of 
the number
format issue - now it is just stalling without complaining. Hmm .. I 
wonder what else

it needs.

Thanks again man

Walker, Jeff wrote:
  

Hi Demetris,
I'm using Axis 1.3, but these are the HTTP headers that my requests


tend
  

to have:

POST /axis/services/ExampleAxisService HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related,
text/*
User-Agent: Axis/1.3
Host: 127.0.0.1:1234
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: 
Content-Length: 445

?xml version=1.0 encoding=UTF-8?soapenv:Envelope ...

And these are the ones on the response:
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=09876Jeffrey; Domain=pag; Expires=Thu,
21-Jun-2007 15:31:07 GMT
Content-Type: text/xml;charset=utf-8
Date: Thu, 21 Jun 2007 12:44:27 GMT
Connection: close

?xml version=1.0 encoding=utf-8?soapenv:Envelope ...


Obviously, you can change the SOAPAction and a few of the others, but
the answer I believe is yes, the HTTP headers do matter in web


services
  

that go over the http protocol.
-jeff



 


-Original Message-
From: Demetris G [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, June 20, 2007 8:00 PM

To: Demetris G
Cc: axis-user@ws.apache.org
Subject: Re: SOAP response


Hi again,

I didn't get a response for the simple issue below so I am trying 
again. I intercept the
response from a legitimate SOAP call to a remote Axis container and I 
return it back

to the client by simply feeding it into the socket that the client


wrote
  

the HTTP bundle
to. Shouldn't this work ? what I am missing ? Is the client side 
excepting to see HTTP

headers etc and not just the SOAP response ? I will appreciate any


ideas
  

on this.

Thanks

Demetris G wrote:
  


Hi all,

   I am manually feeding the following SOAP response into an Axis 
engine that requested
this through a SOAP message and Axis responds with a 
java.lang.NumberFormatException

For input string quot;version=quot;1.0quot; etc.

   Shouldn't the msg below be accepted with no issues from the engine
  


  

?? What is it missing?

Thanks much



?xml version=1.0 encoding=UTF-8?soapenv:Envelope 
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:Bodyns1
  
:getBundlesResponse 
  

soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 


  
xmlns:ns1=http://soapobject.bundle.knopflerfish.org;getBundlesReturn 
  
  

soapenc:arrayType=xsd:long[24] xsi:type=soapenc:Array 


  

xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;getBundlesRet
  
urn 
  

href=#id0/getBundlesReturn href=#id1/getBundlesReturn 
href=#id2/getBundlesReturn href=#id3/getBundlesReturn 
href=#id4/getBundlesReturn href=#id5/getBundlesReturn 
href=#id6/getBundlesReturn href=#id7/getBundlesReturn 
href=#id8/getBundlesReturn href=#id9/getBundlesReturn 
href=#id10/getBundlesReturn href=#id11/getBundlesReturn 
href=#id12/getBundlesReturn href=#id13/getBundlesReturn 
href=#id14/getBundlesReturn href=#id15/getBundlesReturn 
href=#id16/getBundlesReturn href=#id17/getBundlesReturn 
href=#id18/getBundlesReturn href=#id19/getBundlesReturn 
href=#id20/getBundlesReturn href=#id21/getBundlesReturn 
href=#id22/getBundlesReturn 
href=#id23//getBundlesReturn/ns1:getBundlesResponsemultiRef 
id=id12 soapenc:root=0 

Re: HTTP/1.1 400 Bad Request

[Martin Gainty]

Buenas Dias Jorge

Please post your WSDL

Saludos desde EEUU!

M--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.

  - Original Message - 
  From: Jorge Fernandez 
  To: axis-user@ws.apache.org ; Martin Gainty 
  Sent: Thursday, June 21, 2007 4:41 PM
  Subject: Re: HTTP/1.1 400 Bad Request


  Hola Martin:

  I tried what you said but the problem is the same. Furthermore, those 
characters remain appearing even commenting every Transfer-Encoding parameter.

   I think that it's something related to Tomcat because the code 400 on HTTP 
header only appears when deploying Axis2 under Tomcat. 

  Saludos y muchas gracias again,

  Jorge Fernandez


  Martin Gainty [EMAIL PROTECTED] escribió:
undecipherable characters (specifically 3a2) is being introduced before the 
beginning xml tag which neither the servlet or the client stub can interpret
I have seen this happen with Chunked encoding

try to disable parameter name=Transfer-Encoding (commenting out the 
parameter name=Transfer-Encoding from axis2.xml)
and re-deploy

Saludos
M--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.

  - Original Message - 
  From: Jorge Fernandez 
  To: axis-user@ws.apache.org 
  Sent: Thursday, June 21, 2007 3:40 PM
  Subject: HTTP/1.1 400 Bad Request


  Hi again,

  I was trying to get some information on this problem but I couldn't know 
what is happening so I'm trying again.

  Does anybody know anything about how can I fix this???

  Thanks a lot,

  Jorge Fernández

  Jorge Fernandez [EMAIL PROTECTED] escribió: 
Hi all,

I'm having problems only when throwing exceptions. I'm getting bad 
request. This problem appeared since I moved to axis2 1.2, using it with 
Tomcat. If I use axis as standalone server there's no problem. 

The messages are apparently the same except for some minimal changes in 
the order of HTTP header, the prefix for the description element namespace and 
that the final character after envelope in one case appears in the following 
line. This are the messages:

The correct one with standalone axis:

HTTP/1.1 500 Internal server error
Date: Wed, 13 Jun 2007 08:22:37 GMT
Content-Type: application/soap+xml; 
action=http://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault;
Server: Simple-Server/1.1
Transfer-Encoding: chunked
Connection: Close

3a2
?xml version='1.0' encoding='UTF-8'?
   soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; 
xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
  soapenv:Header
 
wsa:Actionhttp://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault/wsa:Action
 
wsa:RelatesTourn:uuid:B2AFE74A4124DE7BFF1181722957402/wsa:RelatesTo
  /soapenv:Header
  soapenv:Body
 soapenv:Fault
soapenv:Code
   soapenv:Valuesoapenv:Sender/soapenv:Value
/soapenv:Code
soapenv:Reason
   soapenv:Text 
xml:lang=en-USValidationFaultException/soapenv:Text
/soapenv:Reason
soapenv:Detail
   ns4:ValidationException 
xmlns:ns4=http://op_messages.medici_link/xsd;
  ns4:ValidationFault
 s2:description 
xmlns:s2=http://faults.medici_link/xsd;User not validated. You must validate 
before invoking a method./s2:description
  /ns4:ValidationFault
   /ns4:ValidationException
/soapenv:Detail
 /soapenv:Fault
  /soapenv:Body
   /soapenv:Envelope0


The bad one with tomcat:

HTTP/1.1 400 Petición incorrecta
Server: Apache-Coyote/1.1
Content-Type: application/soap+xml; 
action=http://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault;charset=UTF-8
Transfer-Encoding: chunked
Date: Wed, 13 Jun 2007 08:12:50 GMT
Connection: close

3a2
?xml version='1.0' encoding='UTF-8'?
   soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; 
xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
  soapenv:Header
  

RE: Accessing SOAP message from MessageContexts in Handlers

[Kevin TierOne]

Hi Wayne,

We've talked about this but I thought I'd post to see if anyone else can
give us insight.


The original message context of the MySoapReceiverInOut.invokeBusinessLogic()
code stores the incoming soap envelope.  If your skeleton throws an
exception, AxisFault.handleFault() will replace the messageContext's soap
envelope with faultContext.getEnvelope().  If there is no exception in your
code, the setEnvelope() call is not invoked.


The reason why you cannot use
msgContext.getOperationContext().getMessageContext(In)
to get the orignal envelope, is that the getMessage(In) refers to the
original message context (because the hashmap stores a reference to original
message context).  Its envelope was overwritten with the fault envelope
during the fault handling.  Not sure why there is also a getMessage(Fault)
that returns the same envelope.  Perhaps it's a bug or maybe there is a
reason for this.  I don't know enough about the Axis2 code.


Kevin


--
From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Subject: Accessing SOAP message from MessageContexts in Handlers
Date: Wed, 20 Jun 2007 16:09:20 -0400


Using Axis2 1.2.  Is there a way to read the original SOAP message within a
PostDispatch Handler?

I'm invoking a custom handler in the PostDispatch phase.  The handler reads
the uses the MessageContext to get the original soap request message.
Something like this:

 String incomingMsg=msgContext.getOperationContext
().getMessageContext(In).getEnvelope().toString();
 System.out.println(Original SOAPMessage: +incomingMsg);

This works fine in the success case.  The problem is if the Skeleton code
throws an exception, the above code prints the Fault soap message.  For
example, the following code prints exactly the same output:

 String incomingMsg=3DmsgContext.getOperationContext
().getMessageContext(In).getEnvelope().toString();
 System.out.println(SOAPMessage: +incomingMsg);=0A=

 String faultMsg=3DmsgContext.getOperationContext
().getMessageContext(Fault).getEnvelope().toString();
 System.out.println(SOAPMessage: +faultMsg);

Am I doing something incorrectly?  Is there another way to get the original
SOAP message in a Handler?

Thanks,
Wayne

[AXIS2] Weblogic 8.1 ClassLoader problem?

[Mike Ferraro]

Hello,

I have deployed Axis2 to Weblogic 8.1 (we are still on SP2) in the exploded
format and I have included a weblogic.xml file in the WEB-INF directory that
looks like this:

?xml version=1.0 encoding=UTF-8?
!DOCTYPE weblogic-web-app PUBLIC
  -//BEA Systems, Inc.//DTD Web Application 8.1//EN
  http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd;
weblogic-web-app
  container-descriptor
prefer-web-inf-classestrue/prefer-web-inf-classes
  /container-descriptor
/weblogic-web-app

I just deployed a packaged aar service file containing a group of services to
the axis2/WEB-INF/services directory.  The services have a ServiceLifeCycle
class that is attempting to preload some configuration files.

I successfully deployed the StockQuoteService.aar sample, but when I try to
deploy my services I get the exception below.  I have all of the necessary
libraries packaged in my aar file in the lib directory.  I have tried deploying
with the Xerces and Xalan jar files included in my aar lib directory and also
tried deploying without them.  I get the same results in both cases.  Any help
would be much appreciated.

-Mike

Jun 21, 2007 4:26:47 PM org.apache.axis2.deployment.ModuleDeployer deploy
INFO: Deploying module: addressing-1.2
Jun 21, 2007 4:26:47 PM org.apache.axis2.deployment.ModuleDeployer deploy
INFO: Deploying module: soapmonitor-1.2
[JAM] Warning: You are running under a pre-1.5 JDK.  JSR175-style source
annotations will not be available
Jun 21, 2007 4:26:48 PM org.apache.axis2.deployment.ServiceDeployer deploy
INFO: Deploying Web service: version.aar
Jun 21, 2007 4:26:48 PM org.apache.axis2.deployment.ServiceDeployer deploy
INFO: Deploying Web service: StockQuoteService.aar
Jun 21, 2007 4:26:51 PM edu.harvard.cait.cdws.services.CDWSServiceLifeCycle
startUp
INFO:
Jun 21, 2007 4:26:51 PM edu.harvard.cait.cdws.services.CDWSServiceLifeCycle
startUp
INFO: Initializing configuration...
Jun 21, 2007 4:26:51 PM edu.harvard.cait.cdws.services.CDWSServiceLifeCycle
startUp
INFO:
Jun 21, 2007 4:26:52 PM org.apache.axis2.deployment.ServiceDeployer deploy
INFO: The cdws.aar service, which is not valid, caused java.lang.LinkageError:
Class org/xml/sax/InputSource violates loader constraints
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at
weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:476)
at
weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:181)
at
weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:61)
at
weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:46)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at org.apache.commons.digester.Digester.parse(Digester.java:1666)
at
org.apache.commons.configuration.ConfigurationFactory.getConfiguration(ConfigurationFactory.java:165)
at edu.harvard.itis.util.ConfigurationManager.loadConfiguration(Unknown
Source)
at edu.harvard.itis.util.ConfigurationManager.load(Unknown Source)
at edu.harvard.itis.util.ConfigurationManager.load(Unknown Source)
at edu.harvard.itis.util.ConfigurationManager.load(Unknown Source)
at edu.harvard.cait.cdws.services.CDWSServiceLifeCycle.startUp(Unknown
Source)
at
org.apache.axis2.deployment.ServiceBuilder.loadServiceLifeCycleClass(ServiceBuilder.java:454)
at
org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:176)
at
org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:98)
at
org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:106)
at
org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:140)
at
org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:79)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:582)
at
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:201)
at
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:271)
at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:189)
at
org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:110)
at
org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:257)
at

Re: Array in axis 2

[Anne Thomas Manes]

Alternatively, you could define it as (changes in red):

   xsd:element name=a
   xsd:complexType
   xsd:sequence
   xsd:element minOccurs=0 name=str
type=xsd:string /
   xsd:element minOccurs=0 name=num type=xsd:int
/
   /xsd:sequence
   /xsd:complexType
   /xsd:element

  xsd:element name=b
  xsd:complexType
  xsd:sequence
xsd:element minOccurs=0 maxOccurs=unbounded
!--name=p-- ref=ns1:a/
 /xsd:sequence
  /xsd:complexType
  /xsd:element

The problem with your original declaration is that your type reference
pointed to an element rather than a type.
Raghu resolved the problem by converting the a element declaration into a
type definition. I resolved it by changing your type reference into an
element reference.

Anne

On 6/21/07, Raghu Upadhyayula [EMAIL PROTECTED] wrote:


 Hi Chris,



Try changing your wsdl as shown below in blue



Thanks

Raghu


 --

*From:* Chris Shah [mailto:[EMAIL PROTECTED]
*Sent:* Wednesday, June 20, 2007 7:33 PM
*To:* axis-user@ws.apache.org
*Subject:* Array in axis 2



I am writing a doc literal wsdl. I have an issue with creating an array of
objects. I have an element 'a' and another element 'b' which is an array of
objects 'a'. WSDL2JAVA gives me



WARNING: Type {http://sample.com/}a missing!



Here are the wsdl snippets:



xsd:element name=a
xsd:complexType name=a
xsd:sequence
xsd:element minOccurs=0 name=str
type=xsd:string /
xsd:element minOccurs=0 name=num
type=xsd:int /
/xsd:sequence
/xsd:complexType
/xsd:element



   xsd:element name=b
   xsd:complexType
   xsd:sequence
 xsd:element minOccurs=0 maxOccurs=unbounded name=p
type=ns1:a/
  /xsd:sequence
   /xsd:complexType
   /xsd:element



ns1 is defined in the definitions as xmlns:ns1=http://mysample.com/;



If I specify type=a, that doesn't work either and I get the same
warning.



ANy help will be appreciated.



TIA

Cris








 --

Fussy? Opinionated? Impossible to please? Perfect. Join Yahoo!'s user
panelhttp://us.rd.yahoo.com/evt=48516/*http:/surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7%20and
 lay it on us.

JMS/SOAP axis2

[Kang, Kamaljeet K.]

Hi,

I am trying to test a webservice with JMS transport. The service works 
perfectly fine with HTTP but with JMS it gives the following exception during 
unmarshling. Looks like localName is incorrect. Is it a bug?


OMElelment BodyBy the StaxSOAPModelBuilder
1-Jun 15:44:40,552 DEBUG builder.StAXOMBuilder [JMSWorker-1] - START_ELEMENT: {
mf854.v1}notify:notify
1-Jun 15:44:40,552 DEBUG builder.StAXSOAPModelBuilder [JMSWorker-1] - Build the
OMElelment notifyBy the StaxSOAPModelBuilder
1-Jun 15:44:40,552 DEBUG engine.AxisEngine [JMSWorker-1] - [MessageContext: log
D=urn:uuid:4153845C2D42C4D72B1182455081080] receive:null
1-Jun 15:44:40,552 DEBUG addressing.AddressingValidationHandler [JMSWorker-1] -
invoke: IS_ADDR_INFO_ALREADY_PROCESSED=null
1-Jun 15:44:40,552 DEBUG addressing.AddressingValidationHandler [JMSWorker-1] -
checkUsingAddressing: WSAddressingFlag=unspecified
1-Jun 15:51:30,779 DEBUG builder.StAXOMBuilder [JMSWorker-1] - START_ELEMENT: {
mf854.v1}TopicExpression_T:TopicExpression_T (it should be topic)
1-Jun 15:51:30,779 DEBUG builder.StAXSOAPModelBuilder [JMSWorker-1] - Build the
OMElelment TopicExpression_TBy the StaxSOAPModelBuilder
1-Jun 15:52:48,088 ERROR jms.JMSMessageReceiver [JMSWorker-1] - JMS Worker [JMS
orker-1] Encountered an Axis Fault : java.lang.RuntimeException: Unexpected sub
lement TopicExpression_T; nested exception is:
   java.lang.RuntimeException: java.lang.RuntimeException: Unexpected subel
ment TopicExpression_T
rg.apache.axis2.AxisFault: java.lang.RuntimeException: Unexpected subelement To
icExpression_T; nested exception is:
   java.lang.RuntimeException: java.lang.RuntimeException: Unexpected subel
ment TopicExpression_T
   at org.apache.axis2.AxisFault.makeFault(AxisFault.java:367)
   at org.tmforum.tmf854.v1.ws.notif.NotificationConsumerMessageReceiverInO
ly.invokeBusinessLogic(NotificationConsumerMessageReceiverInOnly.java:55)
   at org.apache.axis2.receivers.AbstractInMessageReceiver.receive(Abstract
nMessageReceiver.java:35)
   at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:186)
Kamal 







The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs

Help with sending client side certificates

[Ford, Jennifer M.]

Hello there!

I am working with a new company and attempting to submit data to them
via a secured web service.  I used WSDLtoJava to generate a Java client
in Axis2.  The web service will not only be encrypted via SSL/TLS, but
will also require me as a client to submit a certificate to them.  I see
references on the web that I need only set my system parameters for
trustStore and keyStore, which I've done.  

I believe the Truststore portion is working because I do actually get a
200 response which states Authorization Failure: accessNotAllowed.  

However, I cannot seem to make the keyStore take effect.  When I turn on
debugging via javax.net.debug, there doesn't appear to be a difference
when I specify a keystore versus when I don't.  I tried using
Wireshark/Ethereal on it, and again, no difference with or without
setting the keyStore.

Here's the code, which I placed in the constructor for the generated
stub.   I have printed out the keyStore environment variable before and
after the message is executed, and it appears to be fine.  I also have
tried keytool -list with the path I provided for the keystore and the
results were as expected. 


System.setProperty(
java.protocol.handler.pkgs, com.sun.net.ssl.internal.www.protocol);
Security.addProvider( new
com.sun.net.ssl.internal.ssl.Provider() );

System.setProperty(javax.net.ssl.trustStore,
path);
 
System.setProperty(javax.net.ssl.trustStorePassword,  changeit);

System.setProperty(javax.net.ssl.keyStore,
path);
 
System.setProperty(javax.net.ssl.keyStorePassword,  changeit);
System.setProperty(javax.net.ssl.keyStoreType,
jks);

System.setProperty(javax.net.debug, all);

 I've been working on this for 2 days now, so if anyone can offer some
help, I would appreciate it.

Thanks in advance for your help!
Jennifer Ford

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

Re: Help with sending client side certificates

[Martin Gainty]

All System properties are of type string
System.setProperty(javax.net.ssl.trustStorePassword,  password);
http://forum.springframework.org/archive/index.php/t-28717.html

M--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.

- Original Message - 
From: Ford, Jennifer M. [EMAIL PROTECTED]

To: axis-user@ws.apache.org
Sent: Thursday, June 21, 2007 6:20 PM
Subject: Help with sending client side certificates


Hello there!

I am working with a new company and attempting to submit data to them
via a secured web service.  I used WSDLtoJava to generate a Java client
in Axis2.  The web service will not only be encrypted via SSL/TLS, but
will also require me as a client to submit a certificate to them.  I see
references on the web that I need only set my system parameters for
trustStore and keyStore, which I've done.  


I believe the Truststore portion is working because I do actually get a
200 response which states Authorization Failure: accessNotAllowed.  


However, I cannot seem to make the keyStore take effect.  When I turn on
debugging via javax.net.debug, there doesn't appear to be a difference
when I specify a keystore versus when I don't.  I tried using
Wireshark/Ethereal on it, and again, no difference with or without
setting the keyStore.

Here's the code, which I placed in the constructor for the generated
stub.   I have printed out the keyStore environment variable before and
after the message is executed, and it appears to be fine.  I also have
tried keytool -list with the path I provided for the keystore and the
results were as expected. 



   System.setProperty(
java.protocol.handler.pkgs, com.sun.net.ssl.internal.www.protocol);
   Security.addProvider( new
com.sun.net.ssl.internal.ssl.Provider() );

   System.setProperty(javax.net.ssl.trustStore,
path);

System.setProperty(javax.net.ssl.trustStorePassword,  changeit);
   
   System.setProperty(javax.net.ssl.keyStore,

path);

System.setProperty(javax.net.ssl.keyStorePassword,  changeit);
   System.setProperty(javax.net.ssl.keyStoreType,
jks);

   System.setProperty(javax.net.debug, all);

I've been working on this for 2 days now, so if anyone can offer some
help, I would appreciate it.

Thanks in advance for your help!
Jennifer Ford

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



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

Re: SOAP response

[Demetris G]

One thing I noticed is that if I kill the server response process that 
is forwarding the SOAP
response to the client, the client spits out the message that there was 
a SAX Parser
exception - Content cannot be in trailing section ?? That makes no sense 
- here is the
complete response that is very similar to Jeff's - to make this a bit 
readable I am showing

only part of the soap body:

HTTP/1.1 200 OK
MIME-Version: 1.0
Content-Type: text/xml; charset=utf-8
Server: The Knopflerfish HTTP Server
Connection: Close
Date: Thu, 21 Jun 2007 20:31:44 GMT

?xml version=1.0 encoding=UTF-8?soapenv:Envelope 
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:Bodyns1:getBundlesResponse 
soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
xmlns:ns1=http://soapobject.bundle.knopflerfish.org;getBundlesReturn 
soapenc:arrayType=xsd:long[24] xsi:type=soapenc:Array

...
/soapenv:Body/soapenv:Envelope

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

RE: Help with sending client side certificates

[Ford, Jennifer M.]

 
Yes, I edited out my strings to send them to the group, but what I am sending 
is indeed of String type for all of the system property values I am setting.
 
I guess my question should be: is there anything that I need to do to set 
properties on a generated stub in AXIS2 to get my certificate passed, or should 
the code I have be enough?  AXIS doesn't seem to be using the keyStore at all.

 


From: Martin Gainty [mailto:[EMAIL PROTECTED]
Sent: Thu 6/21/2007 5:31 PM
To: axis-user@ws.apache.org
Subject: Re: Help with sending client side certificates



All System properties are of type string
System.setProperty(javax.net.ssl.trustStorePassword,  password);
http://forum.springframework.org/archive/index.php/t-28717.html

M--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.

- Original Message -
From: Ford, Jennifer M. [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Thursday, June 21, 2007 6:20 PM
Subject: Help with sending client side certificates


Hello there!

I am working with a new company and attempting to submit data to them
via a secured web service.  I used WSDLtoJava to generate a Java client
in Axis2.  The web service will not only be encrypted via SSL/TLS, but
will also require me as a client to submit a certificate to them.  I see
references on the web that I need only set my system parameters for
trustStore and keyStore, which I've done. 

I believe the Truststore portion is working because I do actually get a
200 response which states Authorization Failure: accessNotAllowed. 

However, I cannot seem to make the keyStore take effect.  When I turn on
debugging via javax.net.debug, there doesn't appear to be a difference
when I specify a keystore versus when I don't.  I tried using
Wireshark/Ethereal on it, and again, no difference with or without
setting the keyStore.

Here's the code, which I placed in the constructor for the generated
stub.   I have printed out the keyStore environment variable before and
after the message is executed, and it appears to be fine.  I also have
tried keytool -list with the path I provided for the keystore and the
results were as expected.


System.setProperty(
java.protocol.handler.pkgs, com.sun.net.ssl.internal.www.protocol);
Security.addProvider( new
com.sun.net.ssl.internal.ssl.Provider() );

System.setProperty(javax.net.ssl.trustStore,
path);

System.setProperty(javax.net.ssl.trustStorePassword,  changeit);
   
System.setProperty(javax.net.ssl.keyStore,
path);

System.setProperty(javax.net.ssl.keyStorePassword,  changeit);
System.setProperty(javax.net.ssl.keyStoreType,
jks);

System.setProperty(javax.net.debug, all);

 I've been working on this for 2 days now, so if anyone can offer some
help, I would appreciate it.

Thanks in advance for your help!
Jennifer Ford

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



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




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

Re: NoSuchMethodError error while engagin rampart

[Chad DeBauch]

Some code that is executing is calling the method isEngaged(QName) but with
the latest release of Axis2 if you look at the java docs the only isEngaged
method accepts a String.  Make sure you don't have any code that calls the
method isEngaged(QName) and that you are using the latest 1.2 jars of both
Rampart and Axis2.  You also might want to check that you don't have
duplicate jars, that is an older version is loaded before your newer version
jar.

Chad

On 6/21/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:


Hi Chad,


I made download of the archive however still the error occurs
java.lang.NoSuchMethodError:
org.apache.axis2.context.MessageContext.isEngaged
(Ljavax/xml/namespace/QName;)Z

some idea of as I can decide?

Link download
http://www.apache.org/dist/ws/rampart/1_2/

thanks,

Evandro P. Contato
Curitiba - Paraná - Brasil


Chad DeBauch wrote:

 You need to be using rampart-1.2.mar with axis2-1.2.

 Chad

 On 6/19/07, Shantaram Nadkarni [EMAIL PROTECTED] wrote:

  Hi



   I am trying to engage rampart module. I get the following error



 org.apache.axis2.AxisFault: java.lang.NoSuchMethodError: boolean
 org.apache.axis2.context.MessageContext.isEngaged(
javax.xml.namespace.QN

 ame)

 at

 org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(
Utils.java

 :434)

 at

 org.apache.axis2.description.OutInAxisOperationClient.send
(OutInAxisOper

 ation.java:373)

 at

 org.apache.axis2.description.OutInAxisOperationClient.execute
(OutInAxisO

 peration.java:294)



 I am using rampart-1.1.mar and axis2-1.2



 I have included the module in the service.xml as well as axis2.xml



 Please advice.



 Thanks



 Shantaram





Quoted from:

http://www.nabble.com/NoSuchMethodError-error-while-engagin-rampart-tf3947792.html#a11200135

Re: Get the username from UsernameTokens in Skeleton class

[Chad DeBauch]

I figured out how to do this.  I got the SOAP Envelope from the
MessageContext by calling getEnvelope() and parsing the SOAP Header for the
username.  I was hoping there were some helper methods that would do that
for you but now it is done.

Chad

On 6/21/07, Chad DeBauch [EMAIL PROTECTED] wrote:


How do I get the username that was in the SOAP UsernameToken from my
skeleton class?  Is there a way to retrieve it from the MessageContext?  I
am using Rampart to validate the UsernameTokens using a PWCallback class.

Thanks,

Chad

Re: NoSuchMethodError error while engagin rampart

[Anthony Bull]

I just had this same problem while engaging the addressing module. 

The issue was I was using Axis 1.2 and the Addressing 1.0 module.
Upgraded the addressing to 1.2 and it fixed it.

Chad DeBauch wrote:
Some code that is executing is calling the method
isEngaged(QName) but with the latest release of Axis2 if you look at
the java docs the only isEngaged method accepts a String. Make sure
you don't have any code that calls the method isEngaged(QName) and that
you are using the latest 1.2 jars of both Rampart and Axis2. You also
might want to check that you don't have duplicate jars, that is an
older version is loaded before your newer version jar.
  
Chad
  
  On 6/21/07, [EMAIL PROTECTED]
[EMAIL PROTECTED]
wrote:
  Hi
Chad,


I made download of the archive however still the error occurs
java.lang.NoSuchMethodError:
org.apache.axis2.context.MessageContext.isEngaged(Ljavax/xml/namespace/QName;)Z

some idea of as I can decide?


Link download
http://www.apache.org/dist/ws/rampart/1_2/

thanks,

Evandro P. Contato
Curitiba - Paran - Brasil


Chad DeBauch wrote:


 You need to be using rampart-1.2.mar with axis2-1.2.

 Chad

 On 6/19/07, Shantaram Nadkarni [EMAIL PROTECTED]
wrote:


Hi



 I am trying to engage rampart module. I get the following
error



 org.apache.axis2.AxisFault: java.lang.NoSuchMethodError
: boolean

org.apache.axis2.context.MessageContext.isEngaged(javax.xml.namespace.QN

 ame)

 at

 org.apache.axis2.util.Utils.getInboundFaultFromMessageContext
(Utils.java

 :434)

 at


org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper

 ation.java:373)

 at


org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO

 peration.java:294)



 I am using rampart-1.1.mar and axis2-1.2



 I have included the module in the service.xml as well as
axis2.xml



 Please advice.



 Thanks



 Shantaram





Quoted from:
http://www.nabble.com/NoSuchMethodError-error-while-engagin-rampart-tf3947792.html#a11200135

  
  
  



-- 
Anthony
-
Anthony Bull
Senior Developer
Black Coffee Software Ltd
PO Box 10-192 The Terrace
Wellington, New Zealand

[EMAIL PROTECTED]
Ph  +64 4 472 8818
Fax +64 4 472 8811
Mobile 021 303 692
-
www.bcsoft.co.nz
---
This email may contain confidential or privileged information,
and is intended for use only by the addressee, or addressees.
If you are not the intended recipient please advise the sender
immediately and do not copy, use or disclose the contents to
any other person or organisation.
Black Coffee Software Ltd accepts no responsibility for viruses
received with this email, or to any changes made to the original
content. Any views or opinions expressed in this email may be
personal to the sender and are not necessarily those of Black
Coffee Software Ltd.
---





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

How to send a predefined soap xml message?

[Zhu Zhong]

Hi All,

I'm new to soap and Axis. Hope someone on this mailing
list can help out on understanding Axis.

My Application receives an XML message like:
cwmp:GetParameterValues
  ParameterNames soap:arrayType=xsd:string[1]

stringInternetGatewayDevice.ManagementServer./string
/ParameterNames
/cwmp:GetParameterValues

I'd like to use Axis to send it out, the final soap
message should be like:
soapenv:Envelope 
xmlns:cwmp=urn:dslforum-org:cwmp-1-0
xmlnssi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:soap=http://schemas.xmlsoap.org/soap/encoding/;
xmlnssd=http://www.w3.org/2001/XMLSchema; 
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;

soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;

soapenv:Header
cwmp:ID
soapenv:mustUnderstand=123_THOM_TR69_ID/cwmp:ID
/soapenv:Header

soapenv:Body

cwmp:GetParameterValues
ParameterNames soap:arrayType=xsd:string[1]

stringInternetGatewayDevice.ManagementServer./string
/ParameterNames
/cwmp:GetParameterValues

/soapenv:Body
/soapenv:Envelope

Is there an convinient way in Axis to do that? I hope
I don't need to create SOAPEnvelope,SOAPHeaderElement
and SOAPBodyElement in my code.

Thank you!
Zhu.



  ___ 
抢注雅虎免费邮箱3.5G容量，20M附件！ 
http://cn.mail.yahoo.com

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

persistant TCP connection?

[Zhu Zhong]

I sniffered my HelloWorld Axis program and found that
each time you call invoke() a TCP connection will be
established and then closed.

Is there any way to use a persistance TCP connection
for all the soap transactions within one session. Or
that is the way RPC style should be?

Thanks.


  ___ 
抢注雅虎免费邮箱3.5G容量，20M附件！ 
http://cn.mail.yahoo.com

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

Re: Getting an InvalidClassException in one of the JMS classes when deploying my webservices

[Asankha C. Perera]

Hi Raghu

Although you do not state your environment clearly (its a good practice
to do so in future), from what I can find out through the stack trace,
you are using JBoss JMS? It seems like there is a difference in the JMS
classes (JBoss) used at the Axis2 side and JBoss side.. probably a
different JMS client library which is incompatible with your server.
Can you verify if the client library works fine with a simple test
without using Axis2?

asankha

Raghu Upadhyayula wrote:

  
  
  
  
  Hi,
  
   Im getting
an InvalidClassException (stacktrace
shown below) in one of the JMS classes when deploying my webservices,
any one
has any idea what the problem could be?
  
  Thanks
  Raghu
  
  javax.naming.CommunicationException
[Root exception is
java.io.InvalidClassException:
org.jboss.jms.client.delegate.DelegateSupport;
local class incompatible: stream classdesc serialVersionUID =
-1362079381836473747, local class serialVersionUID =
-1723908125830723356]
   at
org.jnp.interfaces.NamingContext.lookup(NamingContext.java:723)
   at
org.jnp.interfaces.NamingContext.lookup(NamingContext.java:588)
   at
javax.naming.InitialContext.lookup(InitialContext.java:351)
   at
com.rsys.jms.JMSConnectionFactory.internalCreateConnFactory(JMSConnectionFactory.java:242)
   at
com.rsys.jms.JMSConnectionFactory.createConnectionFactory(JMSConnectionFactory.java:179)
   at
com.rsys.jms.JMSConnectionFactory.afterPropertiesSet(JMSConnectionFactory.java:120)
   at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1202)
   at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1172)
   at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:428)
   at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251)
   at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:156)
   at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248)
   at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160)
   at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:287)
   at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:352)
   at
org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:244)
   at
org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:187)
   at
org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:49)
   at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3854)
   at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4359)
   at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:761)
   at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:741)
   at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553)
   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.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297)
   at
org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
   at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
   at
org.apache.catalina.core.StandardContext.init(StandardContext.java:5310)
   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.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297)
   at
org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
   at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
   at
org.jboss.web.tomcat.service.TomcatDeployer.performDeployInternal(TomcatDeployer.java:301)
   at
org.jboss.web.tomcat.service.TomcatDeployer.performDeploy(TomcatDeployer.java:104)
   at
org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:375)
   at
org.jboss.web.WebModule.startModule(WebModule.java:83)
   at
org.jboss.web.WebModule.startService(WebModule.java:61)
   at
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
   at