Hi devs,
As you may have already noticed, I changed the REST URL pattern matching
algorithm while fixing the https://issues.apache.org/jira/browse/AXIS2C-1290
issue and the WSF/PHP issue, https://wso2.org/jira/browse/WSFPHP-347. Since
Apache's principle is to 'Commit first' I committed the code
[
https://issues.apache.org/jira/browse/AXIS2C-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S.Uthaiyashankar reassigned AXIS2C-1292:
Assignee: S.Uthaiyashankar
Improve Configuration Context to Get/Set Properties
[
https://issues.apache.org/jira/browse/AXIS2C-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12649278#action_12649278
]
S.Uthaiyashankar commented on AXIS2C-1292:
--
Patch applied in revision 719171.
[
https://issues.apache.org/jira/browse/AXIS2C-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S.Uthaiyashankar resolved AXIS2C-1292.
--
Resolution: Fixed
Fix Version/s: Current (Nightly)
Improve Configuration
[
https://issues.apache.org/jira/browse/AXIS2C-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S.Uthaiyashankar resolved AXIS2C-1293.
--
Resolution: Fixed
Fix Version/s: Current (Nightly)
Assignee:
Hi Dims
I am not clear on this.. what you are suggesting is to just move the new
code to another maven module only? or to make it available as an option
to someone who wants to use it? If the new implementation has drawbacks
I understand, but if its better, why not just switch? or are we
Asankha et al
The patch was meant as a replacement for the existing implementation. It
is pointless to have two MIME frameworks in Axiom. Just forget about the
patch.
Oleg
-1! I think we should evaluate this patch just like any other. I'm not
clear what Dims is asking I'm afraid, but I
[
https://issues.apache.org/jira/browse/AXIS2-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomohiko HORI updated AXIS2-4136:
-
Issue Type: Bug (was: Wish)
org.apache.axis2.AxisFault:
I am asking for the MIME4J implementation to be an option. Not the
default. Default should be what is in right now.
thanks,
dims
On Wed, Nov 19, 2008 at 5:41 AM, Paul Fremantle [EMAIL PROTECTED] wrote:
Asankha et al
The patch was meant as a replacement for the existing implementation. It
is
org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException:
Unexpected subelement
Key: AXIS2-4136
URL: https://issues.apache.org/jira/browse/AXIS2-4136
Let's please keep it as a parallel optional implementation. just like
we have so many components with specific interfaces and multiple
implementations. If/when we finally see the promised results, all we
need to do is switch the default to the other implementation.
thanks,
dims
On Wed, Nov 19,
[
https://issues.apache.org/jira/browse/AXIS2-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomohiko HORI updated AXIS2-4136:
-
Attachment: KBWebServiceCallbackHandler.java
KBWebServiceStub.java
If we are going to take that approach we should have a clear set of
criteria and tests to decide what should be the default. Dims, can you
help improve the test coverage so we know what this patch is aiming
for?
Thanks
Paul
On Wed, Nov 19, 2008 at 1:39 PM, Davanum Srinivas [EMAIL PROTECTED]
Paul,
I believe changes will be needed in Axis2 trunk as well to support
this. Yes, when we get there, we can pitch in with tests that we can
use to figure out which imple is better under what conditions.
thanks,
dims
On Wed, Nov 19, 2008 at 9:52 AM, Paul Fremantle [EMAIL PROTECTED] wrote:
If
Oleg,
Yes, we need to do exactly what you mention first.
The whole trouble is that Axiom currently does not allow for multiple
implementations of MIME processing as it does not have an abstract API
for that to start with.
-- dims
On Wed, Nov 19, 2008 at 10:16 AM, Oleg Kalnichevski [EMAIL
Oleg,
was not referring to you per se. I meant the promise of super fast
performance if we switch to Mime4j...No, i certainly did not imply
that you are on the hook for that. we would need to look at it and
work on it as a team (all of us).
thanks,
dims
On Wed, Nov 19, 2008 at 10:16 AM, Oleg
Axis2 patch to support transaction configuration in axis2.xml.
-Irantha
In oder to support JTA transactions in synapse, I'm working on
changing axis2 configuration (axis2.xml) to support following new
transaction manager definition.
transactionManager
parameter
Please log a JIRA issue.
thanks,
dims
On Wed, Nov 19, 2008 at 11:00 AM, Irantha [EMAIL PROTECTED] wrote:
Axis2 patch to support transaction configuration in axis2.xml.
-Irantha
In oder to support JTA transactions in synapse, I'm working on changing
axis2 configuration (axis2.xml) to
Irantha
Its worth mentioning that this will also enable transactions in Axis2
(e.g. using the JMS transport and having the JTA transaction passed
through to a service and thence onto a database).
Paul
On Wed, Nov 19, 2008 at 4:04 PM, Davanum Srinivas [EMAIL PROTECTED] wrote:
Please log a JIRA
And possibly for UserTransaction support in the new Sandesha2
persistence module?
David
On Wed, Nov 19, 2008 at 5:49 PM, Paul Fremantle [EMAIL PROTECTED] wrote:
Irantha
Its worth mentioning that this will also enable transactions in Axis2
(e.g. using the JMS transport and having the JTA
Yes indeed!
Paul
On Wed, Nov 19, 2008 at 6:06 PM, David Illsley [EMAIL PROTECTED] wrote:
And possibly for UserTransaction support in the new Sandesha2
persistence module?
David
On Wed, Nov 19, 2008 at 5:49 PM, Paul Fremantle [EMAIL PROTECTED] wrote:
Irantha
Its worth mentioning that this
Let's do #2 and everyone will be happy...
-- dims
On Wed, Nov 19, 2008 at 1:48 PM, Oleg Kalnichevski [EMAIL PROTECTED] wrote:
On Wed, 2008-11-19 at 10:32 -0500, Davanum Srinivas wrote:
Oleg,
Yes, we need to do exactly what you mention first.
The whole trouble is that Axiom currently does
[
https://issues.apache.org/jira/browse/AXIS2-4137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Calvin R Smith updated AXIS2-4137:
--
Attachment: patch-01.txt
getAxisConfiguration cannot be called twice
[
https://issues.apache.org/jira/browse/AXIS2-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12649173#action_12649173
]
Steve Cohen commented on AXIS2-4060:
I wonder why the syntax in Axis 1.1
Wsdl2Java
getAxisConfiguration cannot be called twice
---
Key: AXIS2-4137
URL: https://issues.apache.org/jira/browse/AXIS2-4137
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: deployment
[
https://issues.apache.org/jira/browse/AXIS2-4137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Calvin R Smith updated AXIS2-4137:
--
Description:
It is not possible to call getAxisConfiguration twice since each time after the
[
https://issues.apache.org/jira/browse/AXIS2-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12649228#action_12649228
]
Lien Tran commented on AXIS2-3037:
--
Hello, do you know when this patch will be available?
Irantha,
A small suggestion/improvement. Can you please not add the new parameter to
axisconfig, if no parameter is available in axis2.xml?
OMElement transactionElement =
config_element.getFirstChildWithName(new QName(TAG_TRANSACTION));
if (transactionElement != null) {
Hi Asanka,Hope you've seen the following thread before posting this..
http://markmail.org/message/ayjxurjz2fow7hit
Quoting one of Oleg's mail,
Presently the patch I submitted (WSCOMMONS-387) does not provide support
for the deferred parsing, but it should be relatively trivial to add it.
I'm
Axis2 configuration to support transactions
---
Key: AXIS2-4138
URL: https://issues.apache.org/jira/browse/AXIS2-4138
Project: Axis 2.0 (Axis2)
Issue Type: New Feature
Components: deployment
[
https://issues.apache.org/jira/browse/AXIS2-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
irantha suwandarathna updated AXIS2-4138:
-
Attachment: axis2_transaction.patch
Add JTA transaction configuration to
New JIRA issue AXIS2-4138 is created for this.
-Thanks,
Irantha
Davanum Srinivas wrote:
Please log a JIRA issue.
thanks,
dims
On Wed, Nov 19, 2008 at 11:00 AM, Irantha [EMAIL PROTECTED] wrote:
Axis2 patch to support transaction configuration in axis2.xml.
-Irantha
In oder to
New patch is attached to JIRA issue AXIS2-4138.
-Irantha
Eran Chinthaka wrote:
Irantha,
A small suggestion/improvement. Can you please not add the new
parameter to axisconfig, if no parameter is available in axis2.xml?
OMElement transactionElement =
[
https://issues.apache.org/jira/browse/AXIS2-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
irantha suwandarathna updated AXIS2-4138:
-
Description:
Need to add following JTA transaction related configuration to
34 matches
Mail list logo
