Hi Manjula,
There are some issues
(1) Sample binary location is given as $AXIS2C_HOME/bin/samples in INSTALL
file. It has to be changed according to current folder structure
(2) Folder structure given in section 2.2 (Using Binary Release), 2.3.2
(Compiling the Source) of INSTALL file is not
Hi Supun,
I know the policies does not match, I was testing some error cases like invalid
password.or mismatched policies. But I should not expect to see an access
violation (stack included in my previous message)! It seems that axis2/c code
can not handle the soapFault that the server
I didn't understood your question first time :)
Anyway it seems that the error occurs in the Axiom level. Cannot tell the
actual error by looking at the stack. Did you get the error while processing
the fault or is it occurring at the engine level?
Supun
On Fri, Mar 13, 2009 at 11:13 AM,
Hi Supun,
This is a bug first occured in rampart/c, the soapFault string returned from
rampart/c is NOT a well formed XML, there is a bug filed on rampart/c part. But
AXIS2/c should not generate the ACCESS Violation too. This is another bug needs
to be fixed.
Thanks!
Ray
--- On Fri,
[
https://issues.apache.org/jira/browse/AXIS2-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12681628#action_12681628
]
Nandana Mihindukulasooriya commented on AXIS2-4233:
---
Hi Alexis,
Do we have a compatible Rampart version for testing? There seem to be
some major problems with the handling of WS-SecurityPolicy embedded in
WSDL for 1.4.1, and if we could test 1.5 with a compatible Rampart
version *before* we release 1.5 (rather than the usual approach of
releasing an Axis2
Hi devs,
According to the current design of Axis2, faulty services are detected only
by the relevant deployer. In order improve the faulty services handling, I
need to maintain more information about the faulty services such as, exact
error, axis service object. This information is needed when
[
https://issues.apache.org/jira/browse/AXIS2-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12681651#action_12681651
]
Amila Chinthaka Suriarachchi commented on AXIS2-4233:
-
Can you please
On Fri, Mar 13, 2009 at 2:38 PM, Sameera Jayasoma
sameera.madus...@gmail.com wrote:
Hi devs,
According to the current design of Axis2, faulty services are detected only
by the relevant deployer. In order improve the faulty services handling, I
need to maintain more information about the
Hi All,
I have a service in soapsession scope.
The underlying class implements the org.apache.axis2.engine.LifeCycle class.
When a session starts the init()method is called.
When a session end the destroy() method is called.
So far so good :-)
Now when the session expires (time out) the
hi,
Used the steps given in the URL
http://ws.apache.org/axis2/1_4_1/adv-userguide.html to create a
webservice client to do non blocking invocation.
Steps followed:
1. Created a asynchronous BPEL process.
2. Got the WSDL of the async BPEL process and added the WS-addressing
information to the
[
https://issues.apache.org/jira/browse/AXIS2-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12681730#action_12681730
]
Philip Williams commented on AXIS2-3843:
Looking through the source for 1.4.1, the
I can host a build from the trunk which can be used for testing with Axis2
1.5 but it won't be a RC. I am planning to work on some issues in Rampart
but they are not that affected by changes in Axis2. So policy / dispatching
related issues, we can test that build against Axis2 1.5. I will host a
[
https://issues.apache.org/jira/browse/AXIS2-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12680878#action_12680878
]
Philip Williams edited comment on AXIS2-3843 at 3/13/09 7:34 AM:
[
https://issues.apache.org/jira/browse/AXIS2-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12681811#action_12681811
]
Boris Milanov commented on AXIS2-3843:
--
Hi,
I checked Axis2 trunk, as well as the
[
https://issues.apache.org/jira/browse/AXIS2-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12681812#action_12681812
]
Boris Milanov commented on AXIS2-3843:
--
On the other hand, the hostname parameter is
[
https://issues.apache.org/jira/browse/AXIS2-2633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12681862#action_12681862
]
Mark Stickel commented on AXIS2-2633:
-
The correct configuration in order to get the
[
https://issues.apache.org/jira/browse/AXIS2-4253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12681891#action_12681891
]
Andreas Veithen commented on AXIS2-4253:
Can you please make sure that the code
18 matches
Mail list logo
