Hi,
Rampart documentation states that the Rampart supports SAML.
Does Rampart also support XACML ?
Which version of SAML (and XACML if it does) is supported by Rampart ?
Gul
Hi,
Looks like when we use HTTPS/SSL to communicate with a web service
running on Linux,
the keystore is used is the one under where JAVA_HOME environment
variable points to
(%JAVA_HOME%/jre/lib/security/cacerts).
Is there a way to configure axis2 to use default keystore (~/.keystore)
on
Hi,
I am using RawXMLINOnlyMessageReceiver for my in-only operations. I
tried the following signatures in my in-only methods,
but my client doesn't seem to get any exception. How do I get my client
receive exception for in-only methods ? Do I need to
set a configuration parameter somewhere ?
that with in-only. You have to use robust-in-only MEP.
http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803/
Regards,
Jorge Fernández
Gul Onural [EMAIL PROTECTED] escribió:
Hi,
I am using
Programming a client using the client stubs (using xmlbean option)
generated with wsdl2java requires the following files (at least most of
them, not sure you can further reduce the list below) :
axiom-api-1.2.4.jar
axiom-impl-1.2.4.jar
axis2-kernel-1.2.jar
stax-api-1.0.1.jar
Hi,
I noticed that the SOAPMonitor is not protected with userId/password. If
somebody knows the url of the service,
he can then launch the SOAPMonitor and see the messages coming back and
forth.
Is there a way to password protect the SOAPMonitor, or we just have to
take it out from our
implement it
as its pretty easy once you know how to do it.
Robert
On 6/20/07, Gul Onural [EMAIL PROTECTED] wrote:
Hi,
I noticed that the SOAPMonitor is not protected with
userId/password. If somebody knows the url of the service,
he can then launch
Hi,
- How does the two CONNECTION_TIMEOUT and SO_TIMEOUT relates to each
other ?
What effect will get if I set these two to 30 minutes (180
millis) ? I know
the impact of SO_TIMEOUT, but I am not sure about the interpretation
of the CONNECTION_TIMEOUT.
- Should I set them both in the
How do I reset AxisServlet For Socket timeout ?
Gul
Martin Gainty wrote :
set Socket timeout and Connection timeout in axis2.xml and reset
AxisServlet For Socket timeout:
parameter name=SO_TIMEOUT locked=falsesome_int_value/parameter
For Connection timeout:
parameter name=CONNECTION_TIMEOUT
What value we should set if we want SO_TIMEOUT and CONNECTION_TIMEOUT to
be indefinite, (i.e. never time out value) ?
Gul
-Original Message-
From: Martin Gainty [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 05, 2007 7:27 PM
To: axis-user@ws.apache.org
Subject: Re:
I know how to retrieve caller's IP Address from the message context in
Axis2 (via property keyed by MessageContext.REMOTE_ADDR).
Is there a similar way of retrieving caller's port number from the
current message context ?
@ws.apache.org
Subject: Re: Retrieving caller's port number from current message
context
Nope. AFAIK. Is it available in a typical servlet?
thanks,
dims
On 5/31/07, Gul Onural [EMAIL PROTECTED] wrote:
I know how to retrieve caller's IP Address from the message context in
Axis2 (via property keyed
it into
REMOTE_ADDRESS. if you can log a jira with some code to get the port
from HttpServletRequest's. we'd certainly entertain a enhancement
request.
thanks,
dims
On 5/31/07, Gul Onural [EMAIL PROTECTED] wrote:
A standard HTTP request has the port number and IPAddress. Would it be
possible
a getServerPort() method which returns the
port number.
Thanks
Raghu
-Original Message-
From: Gul Onural [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 31, 2007 12:13 PM
To: [EMAIL PROTECTED]
Cc: axis-user@ws.apache.org
Subject: RE: Retrieving caller's port number from current message
I see init and destroy functions implemented in one of the samples
(servicelifecycle) in Axis2 distro.
public void init(ServiceContext serviceContext)
public void destroy(ServiceContext serviceContext) throws AxisFault
When are these functions get invoked for a service that is deployed as
In the wsdl, what is the difference between soapAction and wsaAction ?
Gul
major difference is the wsaAction is transport neutral. If you use
JMS to execute a web service, the soapAction would not available without
some intermediary router logic. As long as you are using WS-Addressing,
the wsaAction will always be available.
Ted
From: Gul
Recently we have migrated our web service to Axis2 1.2. Since then I see
The endpoint reference (EPR) for the Operation not found exception...
when I invoke
one of our web service operations, consistently. I have created an
example web service and
an example test client to reproduce the
The release 1.2 wsdl2 java generates incorrect stub functions for the
operations that has header part only, no payload.
This was correctly done with version axis2 1.1.1. Something changed in
between the two releases in this area is causing the problem.
For example, operation and message are
https://issues.apache.org/jira/browse/AXIS2-2609 is the JIRA along with
the samples to simulatethe issue.
_
From: Onural, Gul (CAR:QT00)
Sent: Monday, April 30, 2007 12:59 PM
To: axis-user@ws.apache.org
Subject: Axis2 :
Well, I found a JIRA (actually opened by me...in January and based on
the JIRA notes, a fixed has been submitted in March. I will need to
upgrade to
nightly to re-test the case.
Gul
From: Onural, Gul (CAR:QT00)
Sent: Sunday, April 08, 2007 2:49 AM
To:
Hi,
I have used xmlbeans databinding to generate client stubs. I am trying
to understand how to get soap fault using the client stubs.
One of my methods on the web service either returns an error (soap
fault) or a piece of information if the result is successful.
In the case of successful
More specifically I am looking for a way to get faultstring on the
client side using the xmlbeans generated stubs.
I can get tns:errorId (below), but I don't see any method on the
exception to allow me to retrieve faultstring.
?xml version='1.0' encoding='utf-8'?
soapenv:Envelope
Hi Gul,
Here is the corret SVN URL for Savan.
https://svn.apache.org/repos/asf/webservices/savan/trunk/java/
The new home page is http://ws.apache.org/savan/ (but this is not fully
complete yet).
Chamikara
On 4/2/07, Gul Onural [EMAIL PROTECTED] wrote:
Looks like both Savan and Muse
Is there any way to force the wsdl2java to override generated files even
if they are already exists ?
Hi,
I just wanted to ask how people are distributing the web services stubs.
For example, let say you generated your stubs using xmlbeans databinding
option.
The wsdl2java tool generates the following files/directories for a web
service :
- src
- resources
- build.xml
What is the common
Using wsdl2java -d xmlbeans option, and building the generated code
(using ant) creates two jar
files :
- web-service-name-test-client.jar and
- XBeans-packaged.jar
My question is :
- When you build a client application using the xmlbeans based stubs, I
can see that
the
Is there a WS-Notification implementation module for Axis2 ?
If not is there a way to integrate a custom event notification system
into Axis2, so that
ws clients can subscribe to events published by my web services that is
implemented using
Axis2?
Gul
Apache Muse implements quite a bit number of WS- specs
(WS-MetadataExchange (WSX),WS-ResourceFramework (WSRF), WS-Notification
(WSN), WS-DistributedManagement (WSDM)...)
What I want to accomplish is to have event driven communication between
our web service (which is implemented using axis2) and
I have the same issue as Gilbert. We don't just want unblocking API,
but real async. API.
I took a quick look into Sandesha2 and I am trying to understand your
comments (reply to Gilbert) on Sandesha2.
You say the behavior we want can be achieved using Sandesha2. But I am
not sure I truly
I have an OMElement response coming from my web services written in
Axis2.
?xml version=1.0 encoding=UTF-8?
tns:XResponse xmlns:tns=mynamespace
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
tns:myObject xsi:type=tns:Type1_T
tns:nameaName/tns:name
/tns:myObject
/tns:XResponse
I have a question about the async. Invocation of the web service
interfaces with Axis2.
My understanding from the existing documentation
(http://today.java.net/pub/a/today/2006/12/13/invoking-web-services-usin
g-apache-axis2.html),
Axis2 definition of the async. invocation refers to the pattern
as nonAnonymous and Microsoft as
Duplex). See here:
http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/ws-addr-wsdl.html
?content-type=text/html;%20charset=utf-8#wspolicyanonresponses
Paul
On 3/7/07, Gul Onural [EMAIL PROTECTED] wrote:
I have a question about the async. Invocation of the web
Hot update seems to be somewhat unreliable. See the following JIRA.
http://issues.apache.org/jira/browse/AXIS2-1596
-Original Message-
From: Tobias Wolf [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 14, 2007 8:50 AM
To: axis-user@ws.apache.org
Subject: Re: Hot Update of Web
I have created JIRA AXIS2-2066
(https://issues.apache.org/jira/browse/AXIS2-2066)
for this issue.
Gul
-Original Message-
From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 30, 2007 11:59 PM
To: axis-user@ws.apache.org
Subject: Re: Axis2 : Namespace is incorrectly
Hi,
ServiceClient sendRobust throws null pointer exception (see below) when
web service reports fault,
if addressing module is engaged with the client. If I don't engage
addressing module, the sendRobust works fine
when web service reports a fault.
I have created a JIRA
I am seeing very strange behavior in Axis2 with the namespace in the
responses.
My web service uses RawXMLINOutMessageReceiver and
RawXMLINOnlyMessageReceiver
message receivers. My service methods (actions) look like :
public OMElement method1(OMElement inputMsg) throws AxisFault {
XMLSpy (enterprise) allows you to generate wsdl documentation in html
and word formats.
Gul
From: John Eapen [mailto:[EMAIL PROTECTED]
Sent: Monday, January 22, 2007 2:18 PM
To: axis-user
Subject: Tool to derive documentation from wsdl/xsd ?
Does anyone know
copy axis2-soapmonitor-1.1.jar to a temp directory and do :
jar -xf axis2-soapmonitor-1.1.jar
This jar file is normally located under axis2-version\lib
as part of the axis2 distro.
Then remove axis2-soapmonitor-1.1.jar from the temp directory.
List of files under the temp directory should
Have you defined AXIS_HOME environment variable pointing to your axis2
installation ?
From: Garth Keesler [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 10, 2007 4:23 PM
To: Axis User
Subject: WSDL2Java Question
The examples below are straight from
To: axis-user@ws.apache.org
Subject: Re: WSDL2Java Question
Yes, both AXIS_HOME and JAVA_HOME point to their correct directories.
However they are defined in /etc/profile and not in my local profile.
Could that be it?
Thanx
Gul Onural wrote:
Have you defined AXIS_HOME environment
I am looking for similar capability too... For the production, it is not
desirable to have hard-coded repository path...
Gul
From: Rishi krish [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 09, 2007 10:45 AM
To: axis-user@ws.apache.org
Subject: axis2
I am trying to get the https access running for axis2 in tomcat, using
Axis1.1 nightly build of Jan. 2, 2007.
I have uncommented SSL HTTP/1/1 Connector entry in
$CATALINA_HOME/conf/server.xml.
Also created a certificate keystore using keytool.
https://localhost:8443/ correctly displays Tomcat
I have spent some time to get https working for my web service using
Axis2 1.1 release and nightly builds
without any luck.
I was wondering if anyone was able to do this successfully. If yes, do
you mind sharing the details ?
What I am looking for is Axis2 specifics of using https to get
I have downloaded the December 20, axis2 nightly build axis2.war and
installed in tomcat.
When I try to access axis2 admin page (http://localhost:8080/axis2/)
from a web browser I get
following jsp exception.
Gul
HTTP Status 500 -
type Exception report
message
description The server
I have downloaded the December 20, axis2 nightly build axis2.war and
installed in tomcat.
When I try to access axis2 admin page (http://localhost:8080/axis2/)
from a web browser I get
following jsp exception.
Gul
HTTP Status 500 -
type Exception report
message
description The
Hi,
I have followed tomcat https/ssl configuration document under
http://tomcat.apache.org/tomcat-5.5-doc/ssl-howto.html
to configure tomcat for https/ssl.
Then I have created a certificate using keytool and imported it into
client's truststore.
I have added the following two properties to my
, nous vous signalons qu'il est strictement interdit
de le diffuser, de le distribuer ou de le reproduire.
- Original Message -
From: Gul Onural mailto:[EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Tuesday, December 19, 2006 3:22 PM
Subject
Hi,
I am trying to setup https access to Axis2 in tomcat. I have configured
the tomcat to use https on port 8443.
I can get access to the list of services using
https://localhost:8443/axis2/services/listServices.
I can see version in the list of available services, but when I click
the version I
Thanks Deepal. I have filed a JIRA for this issue
(http://issues.apache.org/jira/browse/AXIS2-1810).
I think this will be a very important thing to have in Axis2 framework.
Without a solid versioning
strategy, developing commercial products with Axis2 will be very
challenging. I believe
Sounds like the easiest approach for you is to use
RawXMLMessageReceivers for your operations :
OMElemenet myOperation1(OMElement inputXmlDocument) {
...
}
OMElement basically is an XMLInfoset, so you might be able to use your
existing operation implementation code
with some straight forward
I have found a parameter in axis2.xml to change the service path and
changed the service path
to point to the directory that I want my service to be deployed.
However using Axis2 admin web page, looks like my service is still
deployed to the services directory,
not under services/0.1 directory
I want to be able to support multiple versions of my service on the same
system.
The pattern I am trying to use is :
- Keep the service name the same
- Change wsdl namespace url to reflect the change in the wsdl
- Change the location (target EPR) of the service fro the new version
deployment
For
://www.wso2.net/kb/90
Robert
On 12/2/06, Gul Onural [EMAIL PROTECTED] wrote:
I have created a new directory called v0.1 under axis2's services
directory and trying to deploy my service under this directory:
/tomcat_inst_dir/webapps/axis2/WEB-INF/services/v0.1
I have changed my service's
I am trying to extract data from SOAP message header, using axis2 raw
xml message receivers.
My SOAP envelope look like :
?xml version='1.0' encoding='utf-8'?
soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
soapenv:Header
tns:UserId
Using RawXMLMessageReceiver, my service receives and OMElement as input
message.
OMElement children has namespace prefix :
myPrefix:nameXXX/myPrefix:name
Is there a way to remove the namespace prefix from OMElement and all its
children, programmatically ?
Quick question about the SOAP message :
I don't see wsa:To, wsa:ReplyTo, wsa:Address, wsa:MessageID in my SOAP
message headers.
Using SOAP 1.1, WSDL 1.1, Axis 1.2, and RawXML message receiver. What do
I need to do
to see them in the SOAP message? The messaging is still working without
those
, 2006 10:25 AM
To: axis-user@ws.apache.org
Subject: Re: wsa:To, wsa:ReplyTo
Hi Gul,
are you sure the WS-addressing module is engaged? And what about the
dual-channel option (options.setUseSeparateListener(true))?
Michele
On 23 Nov 2006, at 14:29, Gul Onural wrote:
Quick question about the SOAP
it to hide the wsdl or just return nothing to the
user if somebody request the url:
http://myid/axis2/service/myService?wsdl
Is this possible?
On 11/10/06, Gul Onural [EMAIL PROTECTED] wrote:
Hi Holy,
You need to add useOriginalwsdl parameter to your services.xml
file
Well, I had a JIRA opened for this (or very very similar) problem
http://issues.apache.org/jira/browse/AXIS2-1625?page=all, but it has
been closed with the explanation which didn't make to much sense to me.
Take a look if you are interested in.
Gul
From:
I have Axis2 deployed with hotupdate property set to true in the
axis2.xml :
parameter name=hotupdate locked=falsetrue/parameter
If I add a simple log to my service and re-deploy the service, I don't
see this new log displayed.
The only way to see the new log is to restart tomcat.
With
?
On 11/16/06, Gul Onural [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
wrote:
Why would you want to hide the wsdl ? The wsdl is the foundation
of the web services. It is your contract.
Gul
From: [EMAIL PROTECTED] [mailto:[EMAIL
Thanks Rainer, the JIRA you have opened (AXIS2-1596) captures issues I
am seeing w.r.t the hotupdate.
Gul
-Original Message-
From: Rainer Menzner [mailto:[EMAIL PROTECTED]
Sent: Friday, November 17, 2006 1:43 AM
To: axis-user@ws.apache.org
Subject: Re: Is hotupdate working ?
Gul
Hi Michele,
You will need to introduce a class (say MyServiceLifeCycleClass) which
implements ServiceLifeCycle interface. In service.xml you need to
declare this class :
service name=MyService class=MyServiceLifeCycleClass
scope=application
messageReceivers
...
To: axis-user@ws.apache.org
Subject: Re: [axis2] module lifecycle management
Hi Gul,
thanks for your reply, but I'm speaking of *modules*, not services. Does
this apply to modules as well?
Michele
Gul Onural wrote:
Hi Michele,
You will need to introduce a class (say MyServiceLifeCycleClass
So far, Axis1.1's basic functionality worked for me. I don't use
wsdl2java, databinding, etcJust raw xml...
Gul
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 15, 2006 2:13 PM
To: axis-user@ws.apache.org
Cc: Axis developer list
,
Can you please create a JIRA issue from this and assigned to me. Will
fix this after 1.1
Thanks,
Chinthaka
Gul Onural wrote:
I am using following AxisFault constructor in Axis2 :
* public * AxisFault(QName faultCode, String faultReason, String
faultNode, String faultRole, OMElement
Axis2 supports hot deployment only. It doesn't support hot update.
You will need to restart the application container to get your updated
.aar in effect.
Gul
-Original Message-
From: Niklas Saers [mailto:[EMAIL PROTECTED]
Sent: Sunday, November 12, 2006 11:15 AM
To:
://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA
+1-425-296-6194 - Wellington, NZ +64-4-298-6117
Gul Onural wrote:
Axis2 supports hot deployment only. It doesn't support hot update.
You will need to restart the application container to get your
updated .aar in effect.
Gul
-Original
Title: null AxisFault reason
I am using following AxisFault constructor in Axis2 :
public AxisFault(QName faultCode, String faultReason, String faultNode, String faultRole, OMElement faultDetail);
And throwing AxisFault with following code on the Server side :
throw new AxisFault(new
Title: Using standard wsdl:fault with extended faultcodes
Hi,
I am trying to use wsdl standard (WSDL 1.1, SOAP 1.1) fault in my wsdl as it is defined in http://www.w3.org/TR/2000/NOTE-SOAP-2508/#_Toc478383507.
faultcode
faultstring
faultactor
detail
There are small set of
Title: Plans for Axis2 release 1.1 ?
What is the latest plan for the Axis2 1.1 release ? Can somebody comment on this ?
Cheers,
Gul
When you upload an .aar file it gets put under
apache-tomcat-root-directory\webapps\axis2\WEB-INF\services (assuming
you use apache tomcat)
Gul
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 08, 2006 1:59 PM
To: axis-user@ws.apache.org
Title: Re: [Axis2] Help using AXIOMXPath
Brian,
Similar to the following code worked for me. Please give it a try. Note that I am using Axis2 RC1.1 nightly, but you need to try to see if it makes any difference. If it does then you may need to upgrade to nightly:
AXIOMXPath xpathExp =
Add useOriginalwsdl parameter to services.xml file and
set it to true.
service
name="XXX"
messageReceivers parameter name="ServiceClass"
locked="false"Your Service
Class/parameter
parameter
name="useOriginalwsdl"true/parameter
operation name="..."/
...
/service
From: S Pole
Sorry, there was a typo in my posting. The
useOriginalwsdl parameter description should be placed after the closing tag of
the messageReceivers.
Gul
service name="XXX"
messageReceivers
...
/messageReceivers
parameter
name="ServiceClass" locked="false"Your
Service Class/parameter
.
On 11/7/06, Gul
Onural [EMAIL PROTECTED]
wrote:
Add useOriginalwsdl
parameter to services.xml file and set it to true.
service
name="XXX"
messageReceivers parameter name="ServiceClass"
locked="false"Your Service
Class/parameter
para
Title: Axiom jars in axis2 rc2 1.1-nightly
Is there anyone successfully able to use axiom apis in axis2 1.1rc2 - nightly (for example any November nightly), like OMElement iteration or AxiomXPath ?
I am having problems with OMElement iteration and AxiomXPath navigation. There are two JIRAs
Title: Axis2 OMElement issues in nightly
No it didn't actually. In order to send the e-mail I have changed my
original code (i.e. changed the namespace and method names for simplicity) and
when I was crafting my e-mail I made a typo in the namespace. The original code
(I have double checked
Title: AxisFault and fault definition in the wsdl
- If I want my service implementation methods (operations in wsdl terms) to throw AxisFault
how do I define this in the wsdl ? Do I need to use wsdl:fault ? Is there such an example ?
- If my service methods throw AxisFault, and if my
Sadik Kumlali [mailto:[EMAIL PROTECTED]
Sent: Monday, November 06, 2006 10:50 AM
To: axis-user@ws.apache.org
Subject: Re: AxisFault and fault definition in the wsdl
Gul,
Please see my comments inline.
Regards,
Ali Sadik Kumlali
- Original Message
From: Gul Onural [EMAIL PROTECTED
Title: Axis2 OMElement issues in nightly
Filed a JIRA for this issue (AXIS2-1625).
Gul
From: Onural, Gul (CAR:SI12) Sent:
Monday, November 06, 2006 4:31 PMTo:
axis-user@ws.apache.orgSubject: Axis2 OMElement issues in
nightly
I am thinking that the Axiom in nightly Axis2 (RC1.1)
is
,
Robert
On 11/3/06, Gul Onural [EMAIL PROTECTED] wrote:
Soap monitor seems to have problems with the axis2 rc2 (see the
exception
below). It doesn't work even for the localhost.
Does anyone else see this problem ?
Gul
org.apache.axis2.AxisFault: localhost ; nested exception
Title: soapmonitor exception in axis2 rc2
Soap monitor seems to have problems with the axis2 rc2 (see the exception below). It doesn't work even for the localhost.
Does anyone else see this problem ?
Gul
org.apache.axis2.AxisFault: localhost ; nested exception is:
: Gul Onural
Priority: Blocker
Attachments: ws.zip
The attachement ws.zip can be used to reproduce the issue explained
below.
Gul
I am getting org.apache.axis2.deployment.DeploymentException (entire
exception stack trace is down below in the e-mail) from the service I am
Title: RE: Service Group deployment problems
Opened a JIRA for this issue (AXIS2-1587) and marked it as a blocking issue.
Gul
_
From: Onural, Gul (CAR:SI12)
Sent: Wednesday, November 01, 2006 4:24 PM
To: axis-user@ws.apache.org
Title: Service Group deployment problems
I have a wsdl file containing multiple services. When I deploy the .aar file to Tomcat, I am getting following
exception, which is really bizarre
I am using nightly (Oct-31). Is deployment of the service group broken ?
Error:
URL: http://issues.apache.org/jira/browse/AXIS2-1556
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Affects Versions: 1.1
Environment: Axis2 1.1 (Oct. 30 nightly build) Tomcat version
5.5.17 Java 1.5 Linux Redhat
Reporter: Gul Onural
Title: What axis2 class to use for robust-in-only mep ?
I can see the AbstractRobustInMessageReceiver in the axis2 src repository, but I don't see
any concrete message receiver class defined that extends the AbstractRobustInMessageReceiver.
Is it something planned for the 1.1 ?
What I am
Use http://ws.zones.apache.org/dist/axis2/nightly/.
Gul
-Original Message-
From: Nirmit Desai [mailto:[EMAIL PROTECTED]
Sent: Monday, October 30, 2006 10:21 AM
To: axis-user@ws.apache.org
Subject: [Axis2] download question
Hi,
I am using an old nightly and thought of upgrading. I
Title: Axis2 org.apache.axis2.deployment.DeploymentException with nightly
I am getting org.apache.axis2.deployment.DeploymentException (entire exception stack trace is down below in the e-mail) from the service I am trying to deploy to Tomcat version 5.5.17, using the Axis2 nightly (Oct
.deployment.DeploymentException with
nightly
Gul,
Jira please and upload your AAR as well.
thanks,
dims
On 10/30/06, Gul Onural [EMAIL PROTECTED] wrote:
I am getting
org.apache.axis2.deployment.DeploymentException (entire exception
stack trace is down below in the e-mail) from the service I am
Title: What axis2 class to map robust-in-only mep ?
Hi,
I can see the AbstractRobustInMessageReceiver in the axis2 src repository, but I don't see
any new concrete message receiver defined that extends the AbstractRobustInMessageReceiver.
Is it something planned for the 1.1 ?
What I
Title: RE: What axis2 class to map robust-in-only mep ?
There was a typo in my previous e-mail. Resending it :
Hi,
I can see the AbstractRobustInMessageReceiver in the axis2 src repository, but I don't see
any new concrete message receiver defined that extends the
Title: Looking for xml schema for services.xml
I want to see the xsd for the services xml to have a better understanding of it (information about it
is all over the place and hard to get the full picture for usage of advance features).
I checked the nightly src distr. and couldn't find a
Title: WS client (other than axis2 client api based impl.) for axis2 based-web services
There a quite a bit of number of features in Axis2 server side which require Axis2 client
API to be used on the client side.
Also there are some configuration options which can be used on the
should be one
eventually, if for no other reason than tooling/users being able to validate
it.
Brennan Spies
Sr. Programmer Analyst
Shared Application
Services
-Original
Message-From: Gul Onural
[mailto:[EMAIL PROTECTED] Sent: Thursday, October 26,
2006 6:49
AMTo: axis-user
I am also interested in the same subject if anyone can comment on...
Gul
-Original Message-
From: Frans Thamura @ FB - Meruvian [mailto:[EMAIL PROTECTED]
Sent: Monday, October 23, 2006 6:31 AM
To: axis-user@ws.apache.org
Subject: SOAP and Session
Hi All,
I just got input from my
. Programmer Analyst
Shared Application Services
-Original Message-
From: Gul Onural [mailto:[EMAIL PROTECTED]
Sent: Monday, October 23, 2006 12:23 PM
To: axis-user@ws.apache.org
Subject: RE: SOAP and Session
I am also interested in the same subject if anyone can comment on...
Gul
-Original
state in between server shutdowns etc, nor does it have
anything AFAIK that allows the user the contol the session without a
handler. Some single sign-on ideas like CAS can do that, but the link
shows somthing much simpler. Just an idea - feel free to ignore it.
Robert
On 10/23/06, Gul Onural [EMAIL
1 - 100 of 139 matches
Mail list logo
