Axis c++ calculator compiling error, Admin Client
Hi all, i have some problems with the Axis c++ calculator-example. I build my Client with g++ c.cpp -I$AXISCPP_HOME/include -I$AXISCPP_HOME/lib -ldl -laxiscpp_client -o calculator and i get the error: cannot find laxiscpp_client. I search in the mailing list for this problem and change my command to: g++ c.cpp -I$AXISCPP_HOME/include -I$AXISCPP_HOME/lib -ldl -LPathToTheLibrarylaxis_client.so -o calculator Now i think it finds the library but i get the error undefined reference to 'Calculator::Calculator()' I have search in the mailing list but all tipps don´t solve this problem. I use Open Suse 10.3,compiler version 4.2.1 and try it with KDE/KDevelop too, but it produces the same error. I think i have set the LD_LIBRARY_PATH correctly. Maybe there is a conflict with 32 and 64 bit processor. Can anybody help me please? After i can´t solve this problem i go on with the server guide. I run the simle Axis Server with: ./simple_axis_server 8080 and then deploy the service with: java org.apache.axis.client.AdminClient -Lhttp://localhost:8080/axis/Services/AdminService deploy.wsdd I get the message: Porcessing file deploy.wsdd Was the deploying successful or not? By checking the deploying configuration in the user server guide:Open a browser and enter the link http://localhost/axis I can´t open the link. Why it doesn´t work?? I hope there is somebody who can help me in some questions... -- View this message in context: http://www.nabble.com/Axis-c%2B%2B-calculator-compiling-error%2C-Admin-Client-tp18998976p18998976.html Sent from the Axis - C++ - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Axis c++ calculator compiling error, Admin Client
I don't know if we're talking about the same sample (under
samples/server/Calculator):
I had to make changes in both the client and server implementations of the
Calculator sample.
I develop in win32.
Here are the main changes I made:
For the Client:
- I recreated the stubs from wsdl2c using the wsdl in
samples/server/Calculator.wsdl
- I reimplemented the 'test_calculator.c' file to set the parameters on the
request object based on the
Actual names of the parameters in the wsdl (they were out of sync):
stub = axis2_stub_create_Calculator(env, client_home, endpoint_uri);
/* create the struct */
add_req = adb_add_create(env);
adb_add_set_param_1(add_req, env, val1); ==
adb_add_set_param_2(add_req, env, val2); ==
/* invoke the web service method */
add_res = axis2_stub_op_Calculator_add(stub, env, add_req);
if (!add_res)
{
printf(Error: response NULL\n);
return -1;
}
/* return the output params using databinding */
ret_val = adb_addResponse_get_result(add_res, env);
printf(finally: add (%d %d ) = %d\n, val1, val2, ret_val);
return 0
- I added the build target axis2_client_calculator into the makefile in
build\win32\makefile (just use another client example)
For the Server, I found the code was out of sync as well from the wsdl. The
following are the main changes I made:
- Code diff is below. Essentially 2 changes, -
1. the object model in calc.c was deeper than the wsdl indicated, so I
eliminated
Several of the lines to match the actual SOAP object:
2. the response object was different from what was expected based on the wsdl
and the client code.
*** calc.c Tue Aug 05 16:31:14 2008
--- calc.c.bak Thu Jul 10 17:54:18 2008
***
*** 34,54
axis2_char_t *param2_str = NULL;
long int param2 = 0;
if (!node)
{
AXIS2_ERROR_SET(env-error, AXIS2_ERROR_SVC_SKEL_INPUT_OM_NODE_NULL,
AXIS2_FAILURE);
printf(Calculator client request ERROR: input parameter NULL\n);
return NULL;
}
! param1_node = axiom_node_get_first_child(node, env);
if (!param1_node)
{
AXIS2_ERROR_SET(env-error,
AXIS2_ERROR_SVC_SKEL_INVALID_XML_FORMAT_IN_REQUEST,
AXIS2_FAILURE);
printf(Calculator service ERROR: invalid XML in request\n);
return NULL;
}
param1_text_node = axiom_node_get_first_child(param1_node, env);
if (!param1_text_node)
--- 34,73
axis2_char_t *param2_str = NULL;
long int param2 = 0;
if (!node)
{
AXIS2_ERROR_SET(env-error, AXIS2_ERROR_SVC_SKEL_INPUT_OM_NODE_NULL,
AXIS2_FAILURE);
printf(Calculator client request ERROR: input parameter NULL\n);
return NULL;
}
! complex_node = axiom_node_get_first_child(node, env);
! if (!complex_node)
! {
! AXIS2_ERROR_SET(env-error,
! AXIS2_ERROR_SVC_SKEL_INVALID_XML_FORMAT_IN_REQUEST,
! AXIS2_FAILURE);
! printf(Calculator service ERROR: invalid XML in request\n);
! return NULL;
! }
! seq_node = axiom_node_get_first_child(complex_node, env);
! if (!seq_node)
! {
! AXIS2_ERROR_SET(env-error,
! AXIS2_ERROR_SVC_SKEL_INVALID_XML_FORMAT_IN_REQUEST,
! AXIS2_FAILURE);
! printf(Calculator service ERROR: invalid XML in request\n);
! return NULL;
! }
!
! param1_node = axiom_node_get_first_child(seq_node, env);
if (!param1_node)
{
AXIS2_ERROR_SET(env-error,
AXIS2_ERROR_SVC_SKEL_INVALID_XML_FORMAT_IN_REQUEST,
AXIS2_FAILURE);
printf(Calculator service ERROR: invalid XML in request\n);
return NULL;
}
param1_text_node = axiom_node_get_first_child(param1_node, env);
if (!param1_text_node)
***
*** 113,146
return NULL;
}
if (param1_str param2_str)
{
long int result = 0;
axis2_char_t result_str[255];
axiom_element_t *ele1 = NULL;
axiom_node_t *node1 = NULL,
! *node2 = NULL, *node3 = NULL;
axiom_namespace_t *ns1 = NULL;
axiom_text_t *text1 = NULL;
param1 = strtol(param1_str, NULL, 10);
param2 = strtol(param2_str, NULL, 10);
result = param1 + param2;
sprintf(result_str, %ld, result);
ns1 = axiom_namespace_create(env,
!
http://ws.apache.org/axis2/services/Calculator/types;, ns1);
! ele1 = axiom_element_create(env, NULL, addResponse, ns1,
node1);
! ele1 = axiom_element_create(env, node1, result, NULL, node2);
! text1 = axiom_text_create(env, node2, result_str, node3);
Web Service error
Hi all,
I created a WSDL file.using java2wsdl and got the following WSDL
(attached for reference). I see the WSDL deployed on
http://localhost:8080/axis/services/Bingo?wsdl.
When I write a client , I get the folllowing error.. What could be the
reason and also , please let me know if the WSDL is created properly... I
have a doubt on the WSDL creation
AxisFault
faultCode: {
*http://schemas.xmlsoap.org/soap/envelope/}Server.userExceptionhttp://schemas.xmlsoap.org/soap/envelope/%7DServer.userException
*
faultSubcode:
faultString:
*java.lang.reflect.InvocationTargetException*
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:buildshttp://xml.apache.org/axis/%7Dhostname:builds
*
java.lang.reflect.InvocationTargetException
*
at org.apache.axis.message.SOAPFaultBuilder.createFault(
*SOAPFaultBuilder.java:222*)
at org.apache.axis.message.SOAPFaultBuilder.endElement(
*SOAPFaultBuilder.java:129*)
at org.apache.axis.encoding.DeserializationCo
Any help gr8ly appreciated.
Regards,
Sarika
?xml version=1.0 encoding=UTF-8?
wsdl:definitions targetNamespace=urn:com.fci.healthcheck.service xmlns:apachesoap=http://xml.apache.org/xml-soap; xmlns:impl=urn:com.fci.healthcheck.service xmlns:intf=urn:com.fci.healthcheck.service xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:xsd=http://www.w3.org/2001/XMLSchema;
!--WSDL created by Apache Axis version: 1.4
Built on Apr 22, 2006 (06:55:48 PDT)--
wsdl:types
schema targetNamespace=urn:com.fci.healthcheck.service xmlns=http://www.w3.org/2001/XMLSchema;
import namespace=http://schemas.xmlsoap.org/soap/encoding//
complexType name=ClientInfo
sequence
element name=ficoScore type=xsd:int/
/sequence
/complexType
/schema
/wsdl:types
wsdl:message name=getHealthCheckResponse
wsdl:part name=getHealthCheckReturn type=soapenc:string/
/wsdl:message
wsdl:message name=getHealthCheckRequest
wsdl:part name=in0 type=impl:ClientInfo/
/wsdl:message
wsdl:portType name=FCIPlannerEndPoint
wsdl:operation name=getHealthCheck parameterOrder=in0
wsdl:input message=impl:getHealthCheckRequest name=getHealthCheckRequest/
wsdl:output message=impl:getHealthCheckResponse name=getHealthCheckResponse/
/wsdl:operation
/wsdl:portType
wsdl:binding name=Bingo2SoapBinding type=impl:FCIPlannerEndPoint
wsdlsoap:binding style=rpc transport=http://schemas.xmlsoap.org/soap/http/
wsdl:operation name=getHealthCheck
wsdlsoap:operation soapAction=/
wsdl:input name=getHealthCheckRequest
wsdlsoap:body encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; namespace=urn:com.fci.healthcheck.service use=encoded/
/wsdl:input
wsdl:output name=getHealthCheckResponse
wsdlsoap:body encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; namespace=urn:com.fci.healthcheck.service use=encoded/
/wsdl:output
/wsdl:operation
/wsdl:binding
wsdl:service name=FCIPlannerEndPointService
wsdl:port binding=impl:Bingo2SoapBinding name=Bingo2
wsdlsoap:address location=http://localhost:8080/axis/services/Bingo2/
/wsdl:port
/wsdl:service
/wsdl:definitions
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: AXIS2 WS-Security
Hi Pradeep, I don't think it really matters if the service uses Rampart since Rampart merely implements WS-Security standards. It is the open source implementation of WS-Security standards. So as long as both the service and the client supports WS-Security standards, it shouldn't matter what the web service implementation stack is. You could look at the wsdl of the service and find out the requirements of the service by looking at the policy side of things. Cheers. Regards Sanjay -Original Message- From: Deep455 [mailto:[EMAIL PROTECTED] Sent: 14 August 2008 12:39 To: axis-user@ws.apache.org Subject: Re: AXIS2 WS-Security Thanks for the information. Iam not sure whether rampart is used on the webservice server side. I want to consume these services so is it possible for me to set the security token w/o using rampart. Incase rampart has to be used, my client is java based(not a web application). I have generated the client stubs using wsdl2java from Axis2-1.3. Please let me know what do i need to do? Regards Pradeep Nunny wrote: You can you Apache Rampart [1], Axis2 security module. These two tutorials may also help. http://www.wso2.org/library/3190 http://www.wso2.org/library/3415 thanks, nandana [1] - http://ws.apache.org/rampart/ On Thu, Aug 14, 2008 at 3:22 PM, Deep455 [EMAIL PROTECTED] wrote: I have created a client for a web service(with ws-securtiy). How do I pass the security token in the soap header? -- View this message in context: http://www.nabble.com/AXIS2-WS-Security-tp18978756p18978756.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Nandana Mihindukulasooriya WSO2 inc. http://nandana83.blogspot.com/ http://www.wso2.org -- View this message in context: http://www.nabble.com/AXIS2-WS-Security-tp18978756p18979919.html Sent from the Axis - User mailing list archive at Nabble.com. - 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 WS-Security
Thanks Sanjay Iam able to run the stanalone client using rampart libraries and mar file. Currently Iam using axis2 configuration file for username and password. Can I do this programatically with out using teh configuration file ? I have used outflowconfiguration below and its working fine. OutflowConfiguration ofc = new OutflowConfiguration(); ofc.setActionItems(UsernameToken); ofc.setPasswordType(WSConstants.PW_TEXT); ofc.setUser(UserName); options.setProperty(WSSHandlerConstants.OUTFLOW_SECURITY,ofc.getProperty()); PWCBHandler myCallback=new PWCBHandler(); myCallback.setUser(userName); myCallback.setPass(Password); options.setProperty(WSHandlerConstants.PW_CALLBACK_REF, myCallback); BUt Outflowconfiguration seems to be depracted with rampart 1.3. How do I do this using RampartConfig class? -- View this message in context: http://www.nabble.com/AXIS2-WS-Security-tp18978756p18995269.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
wsdd files and axis configuration
Hi, today I have a questoin about th eold wsdd files from axis1. Can we use them in axis2 ? and, precisely, the parameter: parameter name=sendXsiTypes value=*boolean*/ is there any possibility to explain to axis2 to not put th exsi:types in the soap messages in the configuration ? or have a module to do that ? any ideas are welcome again :) thks Pierre
RE: AXIS2 WS-Security
Yes, you can do this programatically by using the policy based approach to implement Rampart enabled services. There's a good tutorial on the topic at [1]. Cheers. 1 - http://wso2.org/library/3190 Regards Sanjay -Original Message- From: Deep455 [mailto:[EMAIL PROTECTED] Sent: 15 August 2008 09:09 To: axis-user@ws.apache.org Subject: RE: AXIS2 WS-Security Thanks Sanjay Iam able to run the stanalone client using rampart libraries and mar file. Currently Iam using axis2 configuration file for username and password. Can I do this programatically with out using teh configuration file ? I have used outflowconfiguration below and its working fine. OutflowConfiguration ofc = new OutflowConfiguration(); ofc.setActionItems(UsernameToken); ofc.setPasswordType(WSConstants.PW_TEXT); ofc.setUser(UserName); options.setProperty(WSSHandlerConstants.OUTFLOW_SECURITY,ofc.ge tProperty()); PWCBHandler myCallback=new PWCBHandler(); myCallback.setUser(userName); myCallback.setPass(Password); options.setProperty(WSHandlerConstants.PW_CALLBACK_REF, myCallback); BUt Outflowconfiguration seems to be depracted with rampart 1.3. How do I do this using RampartConfig class? -- View this message in context: http://www.nabble.com/AXIS2-WS-Security-tp18978756p18995269.html Sent from the Axis - User mailing list archive at Nabble.com. - 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 Client Error - Part content ID cannot be blank for non root MIME parts
My WebService Client are crashed. My command prompt display like Part content ID cannot be blank for non root MIME parts Why ? Thanks for interesting
AW: SOAP-Session management; terminate session.
Hi group,
I've found this old message in the mailing list about a topic which I also have
to think about again.
Is there a nicer, maybe standard, way to end a soapsession? What is the best
way to destroy a session and all related resources, like eg. licenses?
Hoping for your help,
Matthias.
Von: LIE Jorund [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 2. April 2008 17:07
An: axis-user@ws.apache.org
Betreff: RE: SOAP-Session management; terminate session.
I found a workaround for (2.) by setting the lastTouchedTime for the service
group context to 0, the next cleanup will then destroy the session context. In
the service class there is a method like this:
public void endSession()
{
ServiceGroupContext serviceGroupContext =
MessageContext.getCurrentMessageContext().getServiceGroupContext();
serviceGroupContext.setLastTouchedTime(0);
}
This seems to do the trick, although I do not feel that the solution is very
clean.
Jørund
From: LIE Jorund
Sent: Tuesday, April 01, 2008 11:12 AM
To: axis-user@ws.apache.org
Subject: SOAP-Session management; terminate session.
I would need to use the SOAP session management facilities in Axis2-1.3, and I
have a question about terminating a session.
Following the description for session management I have prepared a small
prototype web service that initiates the session, returns the service group ID
for the session to the client, and receives subsequent requests using the
session ID. If there are no requests for a session-ID during a context timeout
interval (set to 30 sec) the session becomes inactive. So far so good, this
works fine, but I have 2 questions tough.
1. From tracing the destroy() method of my web service class I see that the
object instance is not destroyed immediately after the context timeout. It
seems like the session becomes stale, and that the object instance
corresponding to stale sessions are destroyed after any new request to the web
service. Is this correct?
2. I would like to find a way to terminate the sessions triggered by a certain
operation (e.g. by a logout), not by the inactivity timeout. How can this be
achieved in a clean way?
Thanks and Regards.
Jørund Lie
Multiple packages in the same Namespace
Hi, Is it possible to write XSD / WSDL to use only one namespace but that will generate into Java packages? So say I have 20 XSDs, 10 package package1 and 10 in package2, but I wish to keep them in the one namespace? Is this possible? Thanks -- View this message in context: http://www.nabble.com/Multiple-packages-in-the-same-Namespace-tp18996577p18996577.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Binary Data, http and jms, WebSphere 6.x
Currently using MTOM with ADB running through Axis2 http transport web service in WebSphere 6.x - works great! Thanks. Need to support MQ interface running same service, cannot use Axis2 JMS because running in J2EE WebSphere Container (the ole' setMessageListener() problem that app server vendors imposed on the J2EE specification). So, ADB and MTOM appear to be out for this interface. You guys got any idea how to do this? 1) Have done XMLBeans with XOP from MQ (in 2 passes) before without Axis2. Could do this, but the folks I work for want the same business code to be run for both http and mq transports - novel idea. 2) Cannot figure out how to get XMLBeans to do XOP running through Axis2, it keeps making the binary data Base64 encoded instead of XOP - anyone solved this. Looking for some directions/ideas at this point and thanks for your replies. Damin -- View this message in context: http://www.nabble.com/Binary-Data%2C-http-and-jms%2C-WebSphere-6.x-tp18997365p18997365.html 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 and MTOM
Hi, I don't know how you captured the message (response.txt). The message seems to be corrupt with its MIME headers (there is no line delimiter in the first few lines). I don't know if there is some interoperability problem in the Axis 1.4 implementation. Is it also not working if your client is talking to the Axis 1.4 server talking MTOM? We have some MTOM scenarios with Axis 1.4. Regards, Aki 2008/8/14 [EMAIL PROTECTED]: Hi group, I am currently trying to implement an axis 1.4 web service (with a client) with attachments using MTOM. Somewhere it was said, that this is also possible with axis 1.4. But unfortunately I don't get it working. I'm sending the attachments from the server side via MTOM, but I can't receive them on the client. The problem seems to be on the client side. On the client I get this error: [#text: Error in parsing mime data stream: null I included the stacktrace and the response message as attachments. My questions: · Is it possible to implement a Web Service with Attachments using MTOM and Axis 1.4? · Do I have to tell the client somehow that MTOM is being used? · Can you provide some help to my issue? The future plan is to migrate to axis2, but this would take too long for my current issue. Hopefully waiting for your answers. Matthias. - 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 and MTOM
your webapp's pom.xml build script should have this dependency
dependency
groupIdorg.apache.axis2/groupId
artifactIdaxis2-mtompolicy/artifactId
version${version}/version
/dependency
startup axis2.xml
parameter name=enableMTOMtrue/parameter
$AXIS_HOME/lib should contain
axis2-mtompolicy-1.4.jar
from $AXIS_HOME/samples/mtom folloe these instructions from readme.txt
Prerequisites
=
Apache Ant 1.6.2 or later
Running the Sample:
===
1. Use ant generate.service or just the ant command alone in the
Axis2_HOME/sample/mtom/ to build the service.
2. Generated service gets copied to the AXIS2_HOME/repository/services
automatically.
3. Run the AXIS2_HOME/bin/axis2server.{sh/bat} to start the standalone axis2
server. (Alternatively
you can drop the sample into the services directory of a Axis2 server running
in a servlet container)
4. Use ant generate.client to build the client.
5. Use ant run.client -Dfile file to be sent -Ddest destination file name
to run the client.
Note
==
Sometimes, if you're having trouble running the client successfully,
It may be necessary to clean the services repository before you generate the
service, deploy it
and run the client. (i.e. delete services created from previous samples.)
HTH/
Martin
__
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official business
of Sender. This transmission is of a confidential nature and Sender does not
endorse distribution to any party other than intended recipient. Sender does
not necessarily endorse content contained within this transmission.
Date: Fri, 15 Aug 2008 14:53:44 +0200
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Axis 1.4 and MTOM
CC: axis-user@ws.apache.org
Hi,
I don't know how you captured the message (response.txt).
The message seems to be corrupt with its MIME headers (there is no
line delimiter in the first few lines).
I don't know if there is some interoperability problem in the Axis 1.4
implementation.
Is it also not working if your client is talking to the Axis 1.4
server talking MTOM?
We have some MTOM scenarios with Axis 1.4.
Regards, Aki
2008/8/14 [EMAIL PROTECTED]:
Hi group,
I am currently trying to implement an axis 1.4 web service (with a client)
with attachments using MTOM.
Somewhere it was said, that this is also possible with axis 1.4. But
unfortunately I don't get it working. I'm sending the attachments from the
server side via MTOM, but I can't receive them on the client.
The problem seems to be on the client side. On the client I get this error:
[#text: Error in parsing mime data stream: null
I included the stacktrace and the response message as attachments.
My questions:
· Is it possible to implement a Web Service with Attachments using
MTOM and Axis 1.4?
· Do I have to tell the client somehow that MTOM is being used?
· Can you provide some help to my issue?
The future plan is to migrate to axis2, but this would take too long for my
current issue.
Hopefully waiting for your answers.
Matthias.
-
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]
_
Talk to your Yahoo! Friends via Windows Live Messenger. Find out how.
http://www.windowslive.com/explore/messenger?ocid=TXT_TAGLM_WL_messenger_yahoo_082008
Controlling Java2WSDL
Is there a handle to control WSDL generation with various options (like Java2WSDL utility) on the fly? We need to include -xc parameter for including additional subtypes. We have the service class exposed in services.xml from which WSDL is auto generated. Any quick pointers will be really helpful. Balaji -- View this message in context: http://www.nabble.com/Controlling-Java2WSDL-tp18999035p18999035.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Axis 1.4 and MTOM
Hi Aki, I am using Axis 1.4 (not Axis2) for the client and the server and I am wondering if it is possible at all to implement the scenario to transmit attachments using MTOM? You said you have some scenarios.. could you point me to them? I don't know how you captured the message (response.txt). The message seems to be corrupt with its MIME headers (there is no line delimiter in the first few lines). I captured the message using a TCP-monitor tool and I agree that the HTTP/MIME headers look quite odd. Is it also not working if your client is talking to the Axis 1.4 server talking MTOM? I did not really get that question. It is working when I transmit the attachments via MIME, but it does not work when I switch to MTOM on the server side. Is there maybe an option to switch the client to MTOM as well? Thanks for your help, Matthias. -Ursprüngliche Nachricht- Von: Akitoshi Yoshida [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 15. August 2008 14:54 An: Gaiser, Matthias Cc: axis-user@ws.apache.org Betreff: Re: Axis 1.4 and MTOM Hi, I don't know how you captured the message (response.txt). The message seems to be corrupt with its MIME headers (there is no line delimiter in the first few lines). I don't know if there is some interoperability problem in the Axis 1.4 implementation. Is it also not working if your client is talking to the Axis 1.4 server talking MTOM? We have some MTOM scenarios with Axis 1.4. Regards, Aki 2008/8/14 [EMAIL PROTECTED]: Hi group, I am currently trying to implement an axis 1.4 web service (with a client) with attachments using MTOM. Somewhere it was said, that this is also possible with axis 1.4. But unfortunately I don't get it working. I'm sending the attachments from the server side via MTOM, but I can't receive them on the client. The problem seems to be on the client side. On the client I get this error: [#text: Error in parsing mime data stream: null I included the stacktrace and the response message as attachments. My questions: · Is it possible to implement a Web Service with Attachments using MTOM and Axis 1.4? · Do I have to tell the client somehow that MTOM is being used? · Can you provide some help to my issue? The future plan is to migrate to axis2, but this would take too long for my current issue. Hopefully waiting for your answers. Matthias. - 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]
Unexpected subelement error
Hi all,
I'm trying to generate a SOAP service server from an existing WSDL file.
I have generated all necessary class using the following command:
wsdl2java.sh -t -o server/title_edition/ -uri wsdl/Webs_TitelEdition.wsdl -p
nl.kabisa.sanoma.webservices.server -d adb -s -wv 1.2 -ss -sd -ssi
I have also created a simple client. Unfortunately when I run the client I
get the following exception:
Exception in thread main org.apache.axis2.AxisFault:
org.apache.axis2.databinding.ADBException: Unexpected subelement Edition
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:512)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:370)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at
nl.kabisa.sanoma.webservices.Webs_TitelEditionStub.TitelEdition_new(Webs_TitelEditionStub.java:186)
at
nl.kabisa.sanoma.webservices.TitleEditionTestClient.main(TitleEditionTestClient.java:48)
Java Result: 1
I don't know why, because it seems my message is correct according to the
XML schema provided.
I have been trying to resolve this now for the past two days, but
unfortunately I'm still stuck.
Can somebody please tell me what it is I'm doing wrong here?
Here is my code including the WSDL:
client: -
package nl.kabisa.sanoma.webservices;
import java.math.BigInteger;
import java.util.Date;
/**
*
* @author harm
*/
public class TitleEditionTestClient {
public static void main(String[] args) throws Exception {
Webs_TitelEditionStub stub =
new Webs_TitelEditionStub(
http://localhost:9090/axis2/services/Webs_TitelEdition;);
Webs_TitelEditionStub.TitelEdition_new titleEdition =
new Webs_TitelEditionStub.TitelEdition_new();
Webs_TitelEditionStub.Editions_type0 editions =
new Webs_TitelEditionStub.Editions_type0();
Webs_TitelEditionStub.Edition_type0 edition =
new Webs_TitelEditionStub.Edition_type0();
edition.setTitleId(2);
edition.setTitleName(Test title);
edition.setEditionId(1);
edition.setEditionDescription(Test);
edition.setPublicationDate(new Date());
edition.setLatestMatDelivDate(new Date());
editions.addEdition(edition);
editions.setCreateDate(new Date());
editions.setRecords(BigInteger.ONE);
titleEdition.setEditions(editions);
stub.TitelEdition_new(titleEdition);
}
}
---
Using TCPMon I see the following message being sent to the server:
-- soap message -
POST /axis2/services/Webs_TitelEdition HTTP/1.1
Content-Type: application/soap+xml; charset=UTF-8; action=
http://schemas.sanoma-uitgevers.nl/advportal/Webs_TitelEdition/TitelEdition_new
User-Agent: Axis2
Host: localhost:9090
Transfer-Encoding: chunked
209
?xml version='1.0' encoding='UTF-8'?
soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
soapenv:Body
ns3:TitelEdition_new xmlns:ns3=
http://schemas.sanoma-uitgevers.nl/advportal/Webs_TitelEdition;
Editions xmlns=
http://schemas.sanoma-uitgevers.nl/advportal/Webs_TitelEdition/TitelEdition_new;
createDate=2008-08-15+01:00 records=1
Edition[EMAIL PROTECTED]
/Edition
/Editions
/ns3:TitelEdition_new
/soapenv:Body
/soapenv:Envelope
0
---
-- WSDL-
?xml version=1.0 encoding=utf-8?
wsdl:definitions xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:tm=http://microsoft.com/wsdl/mime/textMatching/; xmlns:soapenc=
http://schemas.xmlsoap.org/soap/encoding/; xmlns:mime=
http://schemas.xmlsoap.org/wsdl/mime/; xmlns:tns=
http://schemas.sanoma-uitgevers.nl/advportal/Webs_TitelEdition; xmlns:s1=
http://schemas.sanoma-uitgevers.nl/advportal/Webs_TitelEdition/TitelEdition_new;
xmlns:s=http://www.w3.org/2001/XMLSchema; xmlns:s2=
http://schemas.sanoma-uitgevers.nl/AdvPortal/Defaults/SchemaReturnMessage;
xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/; xmlns:http=
http://schemas.xmlsoap.org/wsdl/http/; targetNamespace=
http://schemas.sanoma-uitgevers.nl/advportal/Webs_TitelEdition; xmlns:wsdl=
http://schemas.xmlsoap.org/wsdl/;
wsdl:types
s:schema elementFormDefault=qualified targetNamespace=
http://schemas.sanoma-uitgevers.nl/advportal/Webs_TitelEdition;
s:import namespace=
http://schemas.sanoma-uitgevers.nl/advportal/Webs_TitelEdition/TitelEdition_new;
/
s:import namespace=
http://schemas.sanoma-uitgevers.nl/AdvPortal/Defaults/SchemaReturnMessage;
/
s:element name=TitelEdition_new
s:complexType
s:sequence
s:element minOccurs=0 maxOccurs=1 ref=s1:Editions /
/s:sequence
working with weblogic
im trying to get axis to work with weblogic, im getting the famous class loader issues when i package it into an ear file. i found in the documentation that i have to add this to the configuration dependency groupIdxerces/groupId artifactIdxerces/artifactId version2.8.1/version /dependency dependency groupIdxalan/groupId artifactIdxalan/artifactId version2.7.0/version /dependency dependency groupIdxml-apis/groupId artifactIdxml-apis/artifactId version1.3.03/version /dependency dependency groupIdstax-api/groupId artifactIdstax-api/artifactId version1.0.1/version /dependency would someone please tell me what file thats supposed to go in? thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unexpected subelement error
Hi,
Are you using Axis2 1.4 ?
I tried your wsdl on Axis2 1.4 using following command:
wsdl2java -t -o server/title_edition/ -uri wsdl/Webs_TitelEdition.wsdl -p
nl.kabisa.sanoma.webservices.server -d adb
And the generated code contains two repeating classes:
1. There is Edition_type0 and Edition_type1
2. There is Editions and Editions_type0
The Editions_type0 class by me contains an addEdition(Edition_type*1*),
rather than addEdition(Edition_type*0*)
And I just used Edition_type1 instance and got the following request which
seems OK:
soapenv:Body
ns3:TitelEdition_new xmlns:ns3=
http://schemas.sanoma-uitgevers.nl/advportal/Webs_TitelEdition;
Editions xmlns=
http://schemas.sanoma-uitgevers.nl/advportal/Webs_TitelEdition/TitelEdition_new;
createDate=2008-08-15+02:00 records=1
Edition
titleId2/titleId
titleNameTest title/titleName
editionId1/editionId
editionDescriptionTest/editionDescription
publicationDate2008-08-15+02:00/publicationDate
latestMatDelivDate2008-08-15+02:00/latestMatDelivDate
/Edition
/Editions
/ns3:TitelEdition_new
/soapenv:Body
But I wonder why there 2 similiar classes generated and not just one of
them, can somebody explain this?
On Fri, Aug 15, 2008 at 5:04 PM, Harm de Laat [EMAIL PROTECTED] wrote:
Hi all,
I'm trying to generate a SOAP service server from an existing WSDL file.
I have generated all necessary class using the following command:
wsdl2java.sh -t -o server/title_edition/ -uri wsdl/Webs_TitelEdition.wsdl
-p nl.kabisa.sanoma.webservices.server -d adb -s -wv 1.2 -ss -sd -ssi
I have also created a simple client. Unfortunately when I run the client I
get the following exception:
Exception in thread main org.apache.axis2.AxisFault:
org.apache.axis2.databinding.ADBException: Unexpected subelement Edition
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:512)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:370)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at
nl.kabisa.sanoma.webservices.Webs_TitelEditionStub.TitelEdition_new(Webs_TitelEditionStub.java:186)
at
nl.kabisa.sanoma.webservices.TitleEditionTestClient.main(TitleEditionTestClient.java:48)
Java Result: 1
I don't know why, because it seems my message is correct according to the
XML schema provided.
I have been trying to resolve this now for the past two days, but
unfortunately I'm still stuck.
Can somebody please tell me what it is I'm doing wrong here?
Here is my code including the WSDL:
client: -
package nl.kabisa.sanoma.webservices;
import java.math.BigInteger;
import java.util.Date;
/**
*
* @author harm
*/
public class TitleEditionTestClient {
public static void main(String[] args) throws Exception {
Webs_TitelEditionStub stub =
new Webs_TitelEditionStub(
http://localhost:9090/axis2/services/Webs_TitelEdition;);
Webs_TitelEditionStub.TitelEdition_new titleEdition =
new Webs_TitelEditionStub.TitelEdition_new();
Webs_TitelEditionStub.Editions_type0 editions =
new Webs_TitelEditionStub.Editions_type0();
Webs_TitelEditionStub.Edition_type0 edition =
new Webs_TitelEditionStub.Edition_type0();
edition.setTitleId(2);
edition.setTitleName(Test title);
edition.setEditionId(1);
edition.setEditionDescription(Test);
edition.setPublicationDate(new Date());
edition.setLatestMatDelivDate(new Date());
editions.addEdition(edition);
editions.setCreateDate(new Date());
editions.setRecords(BigInteger.ONE);
titleEdition.setEditions(editions);
stub.TitelEdition_new(titleEdition);
}
}
---
Using TCPMon I see the following message being sent to the server:
-- soap message -
POST /axis2/services/Webs_TitelEdition HTTP/1.1
Content-Type: application/soap+xml; charset=UTF-8; action=
http://schemas.sanoma-uitgevers.nl/advportal/Webs_TitelEdition/TitelEdition_new
User-Agent: Axis2
Host: localhost:9090
Transfer-Encoding: chunked
209
?xml version='1.0' encoding='UTF-8'?
soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
soapenv:Body
ns3:TitelEdition_new xmlns:ns3=
http://schemas.sanoma-uitgevers.nl/advportal/Webs_TitelEdition;
Editions xmlns=
http://schemas.sanoma-uitgevers.nl/advportal/Webs_TitelEdition/TitelEdition_new;
RE: AXIS2 WS-Security
Here is RampartConfig which configures the client authenticator to use keystores (services.xml) Service name=test messageReceiver class=org.apache.rahas.STSMessageReceiver/ !-- Action mapping to accept SCT requests -- actionMappinghttp://schemas.xmlsoap.org/ws/2005/02/trust/RST/SCT/actionMapping actionMappinghttp://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue/actionMapping actionMappinghttp://schemas.xmlsoap.org/ws/2005/02/trust/RST/Renew/actionMapping actionMappinghttp://schemas.xmlsoap.org/ws/2005/02/trust/RST/Cancel/actionMapping actionMappinghttp://schemas.xmlsoap.org/ws/2005/02/trust/RST/SCT/Cancel/actionMapping actionMappinghttp://schemas.xmlsoap.org/ws/2005/02/trust/RST/Validate/actionMapping /operation !-- Using the config file -- parameter name=token-dispatcher-configuration-fileMETA-INF/token-dispatcher-configuration.xml/parameter !-- Configure Rampart to authenticate clients -- wsp:Policy wsu:Id=SigOnly xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd; xmlns:wsp=http://schemas.xmlsoap.org/ws/2004/09/policy; wsp:ExactlyOne wsp:All ramp:RampartConfig xmlns:ramp=http://ws.apache.org/rampart/policy; ramp:userip/ramp:user ramp:encryptionUseruseReqSigCert/ramp:encryptionUser ramp:passwordCallbackClassPWCBHandler/ramp:passwordCallbackClass ramp:signatureCrypto ramp:crypto provider=org.apache.ws.security.components.crypto.Merlin ramp:property name=org.apache.ws.security.crypto.merlin.keystore.typeJKS/ramp:property ramp:property name=org.apache.ws.security.crypto.merlin.fileMETA-INF/rahas-sts.jks/ramp:property ramp:property name=org.apache.ws.security.crypto.merlin.keystore.passwordpassword/ramp:property /ramp:crypto /ramp:signatureCrypto /ramp:RampartConfig Martin Gainty __ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Date: Fri, 15 Aug 2008 09:14:16 +0100 Subject: RE: AXIS2 WS-Security Yes, you can do this programatically by using the policy based approach to implement Rampart enabled services. There's a good tutorial on the topic at [1]. Cheers. 1 - http://wso2.org/library/3190 Regards Sanjay -Original Message- From: Deep455 [mailto:[EMAIL PROTECTED] Sent: 15 August 2008 09:09 To: axis-user@ws.apache.org Subject: RE: AXIS2 WS-Security Thanks Sanjay Iam able to run the stanalone client using rampart libraries and mar file. Currently Iam using axis2 configuration file for username and password. Can I do this programatically with out using teh configuration file ? I have used outflowconfiguration below and its working fine. OutflowConfiguration ofc = new OutflowConfiguration(); ofc.setActionItems(UsernameToken); ofc.setPasswordType(WSConstants.PW_TEXT); ofc.setUser(UserName); options.setProperty(WSSHandlerConstants.OUTFLOW_SECURITY,ofc.ge tProperty()); PWCBHandler myCallback=new PWCBHandler(); myCallback.setUser(userName); myCallback.setPass(Password); options.setProperty(WSHandlerConstants.PW_CALLBACK_REF, myCallback); BUt Outflowconfiguration seems to be depracted with rampart 1.3. How do I do this using RampartConfig class? -- View this message in context: http://www.nabble.com/AXIS2-WS-Security-tp18978756p18995269.html Sent from the Axis - User mailing list archive at Nabble.com. - 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] _ See what people are saying about Windows Live. Check out featured posts. http://www.windowslive.com/connect?ocid=TXT_TAGLM_WL_connect2_082008
Re: JMS timeout
Thanks Asankha! But I did try that before and it did not work. Where should I put it exactly? in the Receiver or Sender? can you please give me an example of axis2.xml with the modification just to make sure I am doing the correct thing? Thanks again On Tue, Aug 12, 2008 at 9:48 AM, Asankha C. Perera [EMAIL PROTECTED] wrote: Hi Ihab Please set the message context property JMS_WAIT_REPLY to what you desire (in ms). This will override the default timeout asankha Ihab EL-ALAMI wrote: Thanks for your prompt reply, But actually I am not doing that programmatically. Is there a way to specify that statically from the axis2.xml file for instance? Ihab EL ALAMI Process Expert Intalio, The Open Source BPMS Company Date: Tue, 12 Aug 2008 08:13:21 -0700 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Subject: JMS timeout Hi everybody, I have set up my JMS transport, and I would like now to call a service via JMS. The problem is this service needs more than 20 seconds to answer back, and the timeout for this transport is set to 3ms. How can I modify the timeout? Thanks in advance Ihab -- Get more from your digital life. Find out how.http://www.windowslive.com/default.html?ocid=TXT_TAGLM_WL_Home2_082008 -- Asankha C. Perera WSO2 - http://wso2.org http://esbmagic.blogspot.com
RE: JMS timeout
config the JMS_WAIT_REPLY parameter for JMSSender in the axis2.xml configuration file e.g. transportSender name=jms class=org.apache.axis2.transport.jms.JMSSender/ parameter name=JMS_WAIT_REPLY1000/parameter /transportSender Martin __ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. Date: Fri, 15 Aug 2008 16:49:57 -0700 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Subject: Re: JMS timeout Thanks Asankha! But I did try that before and it did not work. Where should I put it exactly? in the Receiver or Sender? can you please give me an example of axis2.xml with the modification just to make sure I am doing the correct thing? Thanks again On Tue, Aug 12, 2008 at 9:48 AM, Asankha C. Perera [EMAIL PROTECTED] wrote: Hi Ihab Please set the message context property JMS_WAIT_REPLY to what you desire (in ms). This will override the default timeout asankha Ihab EL-ALAMI wrote: Thanks for your prompt reply, But actually I am not doing that programmatically. Is there a way to specify that statically from the axis2.xml file for instance? Ihab EL ALAMI Process Expert Intalio, The Open Source BPMS Company Date: Tue, 12 Aug 2008 08:13:21 -0700 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Subject: JMS timeout Hi everybody, I have set up my JMS transport, and I would like now to call a service via JMS. The problem is this service needs more than 20 seconds to answer back, and the timeout for this transport is set to 3ms. How can I modify the timeout? Thanks in advance Ihab Get more from your digital life. Find out how. -- Asankha C. Perera WSO2 - http://wso2.org http://esbmagic.blogspot.com _ Talk to your Yahoo! Friends via Windows Live Messenger. Find out how. http://www.windowslive.com/explore/messenger?ocid=TXT_TAGLM_WL_messenger_yahoo_082008
Axis 2 - JMS durable subscriptions
Hi, I have done some modifications to the Axis 2 JMS transport so that web services running over JMS can use durable subscriptions to messaging servers. This means that if your web service is down, when it comes back up, the messaging server will pass it any messages it missed out on while it was inactive. My mods are for Axis 2 version 1.3, and I have been running them live in an enterprise production environment for 4 months without any problems. The Axis 2 JMS classe asnd details of how to use them can be found on my blog at: http://thejavamonkey.blogspot.com/2008/08/modding-axis-2-durable-subscriptions.html I'm happy to help anyone through any problems if they encounter them while using these changes. -- 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 - 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]
Axis 2 - JMS over Websphere MQ
While using JMS enabled Axis2 web services in a Websphere MQ environment, I encountered a bug with JNDI resource leakage when using the Axis 2 JMS Sender to post to WebSphere MQ - the bug causes the Axis 2 client to use up all of the WebSphere MQ servers client connections, and after a while nothing can connect to it anymore. If anyone else is having similar issues with Axis 2 over WebSphere MQ, I've created a patch/fix for Axis 2 version 1.3 that cleans up the JNDI contexts correctly when sending messages. The patch and details are at: http://thejavamonkey.blogspot.com/2008/08/modding-axis-2-jms-transportweb-sphere.html cheers, Ants. -- 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 - 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]
RE: Code generation and camelback notation
This is not spam.
Thanks,
... Greg ...
-Original Message-
From: balaji hari [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 14, 2008 1:36 PM
To: axis-user@ws.apache.org
Subject: Re: Code generation and camelback notation
Surprised by what the follow up message I got on this issue?
Is this a spam?
Hutchinson, Greg wrote:
When generating a client for synchronous and asynchronous invocations of a
web service, I get the following methods created.
public void createCustomer() {
...
}
public void startcreateCustomer() { //lowercase (c)reate
...
}
where I was expecting to get
public void startCreateCustomer() { //Proper camelback notation
...
}
Is there any plans to fix this, or is there some option to turn on?
Thanks,
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/NullPointerException-org.apache.axis2.databinding.typemapping.SimpleTypeMapper-tp18985650p18988234.html
Sent from the Axis - User mailing list archive at Nabble.com.
-
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]
