Uthaiyashankar wrote:
Hi,
Currently rampart in-handler is called in "PreDispatch" phase in
inflow. Due to that, if a message is having only soap action (no
operation is specified in url or no wsa:action is given, so only
possible way of dispatching is based on soap action) and message is
sec
It is good to follow the Java API. Axiom/C is developed according to the
Java design and it is better to have a similar API for XPath in C. What I
want to mention is that don't go too much into the Java design and
implementation. Please don't take this as I'm saying you are going too much
in to the
On Wed, 2008-05-28 at 14:15 +0530, Manjula Peiris wrote:
> Shankar,
>
> I have tested Rampart/C with a soap action(without addressing) and
> putting the Security phase even before Transport phase and it worked. So
> I think what is happening in this case is that actual dispatching does
> not happ
Shankar,
I have tested Rampart/C with a soap action(without addressing) and
putting the Security phase even before Transport phase and it worked. So
I think what is happening in this case is that actual dispatching does
not happen from soap action phase dispatcher.
-Manjula.
On Wed, 2008-05-2
Hi,
I debug the code. What is happening here is Security phase always
invokes at last even you put it before Transport phase. Since soap
action based dispatcher is in Dispatch phase in this situation when it
comes to Rampart actual dispatching has occurred. So this means Axis2/C
always invoke modu
Hi,
This article [1] written by Samisa explicitly saying we can add user
defined phases only after pre-defined phases in in-flow. I guess it is
added purposely. Then we have to consider some other options to invoke
rampart after soap action based dispatching.
Regards,
Shankar
[1] http://wso
[
https://issues.apache.org/jira/browse/AXIS2C-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600415#action_12600415
]
Supun Kamburugamuva commented on AXIS2C-1142:
-
The patch provided here looks l
Axis2/C does not invoke the phases correctly when there are module defined
phases.
--
Key: AXIS2C-1162
URL: https://issues.apache.org/jira/browse/AXIS2C-1162
Project: Axi
Thanks Manjula for this finding.
Is this a bug or added purposely?
Are there any problems if module defined phases get invoked before the
default phases?
If not definitely need to fix this phase ordering problem in Axis2/C.
Cheers,
Kaushalye
Manjula Peiris wrote:
Hi,
I debug the code. What is
Hi Supun
Thank you very much for the help; please let me know if you see anything
that should be changed at this stage or later.
Thanks
Varuna
On Wed, May 28, 2008 at 2:37 PM, Supun Kamburugamuva <[EMAIL PROTECTED]>
wrote:
> It is good to follow the Java API. Axiom/C is developed according to
rampart doesn't link
Key: AXIS2C-1163
URL: https://issues.apache.org/jira/browse/AXIS2C-1163
Project: Axis2-C
Issue Type: Bug
Components: build system (Unix/Linux)
Affects Versions: Current (Nightly)
[
https://issues.apache.org/jira/browse/AXIS2C-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frederic Heem updated AXIS2C-1163:
--
Attachment: patch-rampart-20080528.diff
Here is a kludge, more work has to be done in
Hello,
I'm playing with axis2/c ws-addressing module (axis2/c 1.3.0 and
1.4.0) and I've noticed something strange with Reference Parameters in
EPR:
I have a message with a like
http://www.w3.org/2005/08/addressing";
xmlns:test="http://example.com/test";>
http://example.com/services/testSvc
On Wed, 2008-05-28 at 15:11 +0530, Uthaiyashankar wrote:
> Hi,
>
> This article [1] written by Samisa explicitly saying we can add user
> defined phases only after pre-defined phases in in-flow. I guess it is
> added purposely. Then we have to consider some other options to invoke
> rampart af
On Wed, 2008-05-28 at 17:50 +0200, Julien Billon wrote:
> Hello,
>
> I'm playing with axis2/c ws-addressing module (axis2/c 1.3.0 and
> 1.4.0) and I've noticed something strange with Reference Parameters in
> EPR:
>
> I have a message with a like
>
> http://www.w3.org/2005/08/addressing";
> xm
We should test this with the interop test suite as well.
AFAICR, we passed all the tests. After fixing these, we should test again.
Samisa...
Manjula Peiris wrote:
On Wed, 2008-05-28 at 17:50 +0200, Julien Billon wrote:
Hello,
I'm playing with axis2/c ws-addressing module (axis2/c 1.3.0 a
Dinesh Premalal wrote:
Hi Varuna and all,
"Supun Kamburugamuva" <[EMAIL PROTECTED]> writes:
So I think it is better to stick to the convention and use those long names.
Also you don't have to put everything in a long format. The only important
thing is the axiom part. You can shorten other
Hi List,
I would like to implement support for IIS 6. At the moment we have an IIS
ISAPI module which is a ISAPI Filter + ISAPI Extension. This is not a good
design for IIS 6 since it doesn't encourage the use of filters. So I thought
of writing a ISAPI Extension for IIS 6 which will connect IIS 6
Hi ,
I have worked with gSOAP. It's good for platforms not supported by AXIS 2C
(ex: Sol 10 when I was using it) where you want to have C++ web services.
Else you are better off with AXIS2C.
gSOAP is more primitive than of AXIS 2C and you'll have to do a lot of hacks
to get things working.
As Sa
[
https://issues.apache.org/jira/browse/AXIS2C-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandika Jayawardana reassigned AXIS2C-884:
--
Assignee: Nandika Jayawardana
> Seg fault in libxml when svc client torn down i
[
https://issues.apache.org/jira/browse/AXIS2C-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600692#action_12600692
]
Nandika Jayawardana commented on AXIS2C-884:
Now Axis2/C uses guththila as the
21 matches
Mail list logo
