Hi,
I've added an option to the messagecontext to control the cookie policy on
http Request. This can be set as follows
options.setProperty(HTTPConstants.COOKIE_POLICY, CookiePolicy.IGNORE_COOKIES
);
Valid values for cookie policy are
public static final java.lang.String BROWSER_COMPATIBILI
+1 ... I also believe we should be able to have module define/arrange
phases without
having to edit the axis2.xml file and the handlers themselves can take
care of fault processing.
Even in Rampart we use the same handler in the fault flows and we do
the fault handling internally
without really che
sources unavailable in the maven repository.
Key: AXIS2-3404
URL: https://issues.apache.org/jira/browse/AXIS2-3404
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: samples,
Asankha and all synapse-devs,
It seems like the axis2 community is neutral about this. AFAIK, axis2
does not display anything if you browse to the exact service path
using a browser (GET request on service path), and their also having a
?info filter and it displays the service information.
I thin
[
https://issues.apache.org/jira/browse/AXIS2-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Godwin Chapman resolved AXIS2-3394.
-
Resolution: Fixed
Fixed in revision 603805. Aplied modified version of the patch
[
https://issues.apache.org/jira/browse/AXIS2-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Godwin Chapman reassigned AXIS2-3394:
---
Assignee: Keith Godwin Chapman
> multipart/form-data problem at the RESTFul S
[
https://issues.apache.org/jira/browse/AXIS2-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551007
]
Daniele Fiorellino commented on AXIS2-2883:
---
Hi.
I've same problem.
Environment: Operating System : Linu
[
https://issues.apache.org/jira/browse/AXIS2-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550997
]
Nick Gallardo commented on AXIS2-3305:
--
Roy, there is already a set of context properties available for the WSDL
[
https://issues.apache.org/jira/browse/AXIS2-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Gallardo updated AXIS2-3403:
-
Attachment: patch.txt
A patch for this issue.
> JAX-WS BasicAuth client config should allow no p
JAX-WS BasicAuth client config should allow no password
---
Key: AXIS2-3403
URL: https://issues.apache.org/jira/browse/AXIS2-3403
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Compone
[
https://issues.apache.org/jira/browse/AXIS2-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Gallardo updated AXIS2-3402:
-
Attachment: patch.txt
A patch for the issue.
> Nested swaRef attachments not sent in message
> -
Nested swaRef attachments not sent in message
-
Key: AXIS2-3402
URL: https://issues.apache.org/jira/browse/AXIS2-3402
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: jaxws
Affec
hi glen,
I am agreeing with you for the two features you have mentioned. And also As
I remember these two features
were there in the list that came up after last Apache Con hacathon. So there
were no objections for this
features.
But for the moment since axis2 do not have these features the only
Keith,
I'm looking into these now...
Thanks,
Dustin Amrhein
keith chapman <[EMAIL PROTECTED]> wrote:
Hi,
There are some test failures
http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm?view=ProjectBuild&buildId=3476&id=61
namely
Results :
Failed tests:
Hi Nandana!
Nandana Mihindukulasooriya wrote:
Hi Devs,
Rampart is in the process of providing security in the fault
flows. In order to do that,
we need to introduce security phase in to out fault flow. It is already
there in the in fault flow.
so the axis2.xml have to modified to incl
Hi Devs,
Rampart is in the process of providing security in the fault flows.
In order to do that,
we need to introduce security phase in to out fault flow. It is already
there in the in fault flow.
so the axis2.xml have to modified to include,
Hi Devs,
Rampart is in the process of providing security in the fault flows.
In order to do that,
we need to introduce security phase in to out fault flow. It is already
there in the in fault flow.
so the axis2.xml have to modified to include,
[
https://issues.apache.org/jira/browse/AXIS2-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christoph Ludwig updated AXIS2-3401:
Attachment: axis2-issue-3401.zip
Test service and client using the ADB binding generated fo
[
https://issues.apache.org/jira/browse/AXIS2-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christoph Ludwig updated AXIS2-3401:
Attachment: axis2test.wsdl
WSDL file that triggers the described bug.
> choice of sequence
choice of sequence of union causes infinite loop in generated ADB binding
-
Key: AXIS2-3401
URL: https://issues.apache.org/jira/browse/AXIS2-3401
Project: Axis 2.0 (Axis2)
Hi,
There are some test failures
http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm?view=ProjectBuild&buildId=3476&id=61
namely
Results :
Failed tests:
testLoadWSDLImpl(org.apache.axis2.jaxws.description.AnnotationServiceImplWithDBCTests)
testLoadWSDLSEI(
Hi Nick ,
This is really strange, when I get an update now and run all the build with
test cases that include my fix, all the test passes and when it was removed
these two tests fails,
Failed tests:
testLoadWSDLImpl(
org.apache.axis2.jaxws.description.AnnotationServiceImplWithDBCTests)
testLo
22 matches
Mail list logo
