Hi Samisa,
Regarding the JIRA AXIS2C-540 and the Guthilla docs. If you could provide me
some pointers/starting points I'll try to see what I can come up with...
Regarding your comment on the libxml2 memory leaks. Are you planning on
addressing that for the 1.0?
Bye...
--
Feel free - 10 GB
[EMAIL PROTECTED] writes:
Hi Samisa,
Regarding the JIRA AXIS2C-540 and the Guthilla docs. If you could
provide me some pointers/starting points I'll try to see what I can
come up with...
To build with Guththila , you need to configure it as
./configure --enable-guththila=yes [other
+1
thanks,
Dinesh
--
Dinesh Premalal
[EMAIL PROTECTED]
WSO2, Inc.; http://www.wso2.com/
GPG Key ID : A255955C
GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255 955C
-
To unsubscribe, e-mail: [EMAIL
+1 moving rampart.
Are we going to use the Rampart/Java mailing list and for jiras
Rampart/Java jira page ?
Thanks,
-Manjula.
On Thu, 2007-03-22 at 10:49 +0530, Nandika Jayawardana wrote:
+1 for moving rampart.
--Nandika
On 3/22/07, Kaushalye Kapuruge [EMAIL PROTECTED] wrote:
Hi,
I don't think dropping Rampart/C questions in the java list is a good
idea. We need separate mailing list for Rampart/C. Until then we can
use Axis2/C mailing list and JIRA as we used to.
Cheers,
Kaushalye
Manjula Peiris wrote:
+1 moving rampart.
Are we going to use the Rampart/Java
Remove ops and MACROs from Rampart/C and OMXMLSecurity
--
Key: AXIS2C-558
URL: https://issues.apache.org/jira/browse/AXIS2C-558
Project: Axis2-C
Issue Type: Improvement
Kaushalye Kapuruge wrote:
Hi,
I don't think dropping Rampart/C questions in the java list is a good
idea. We need separate mailing list for Rampart/C. Until then we can
use Axis2/C mailing list and JIRA as we used to.
For Sandesha/C, mails go over the same list with a subject prefix.
+1.
Samisa...
Kaushalye Kapuruge wrote:
Hi List,
Since Rampart/C works as a module for Axis2/C and it is not part of
the Axis2/C engine, I propose that we move Rampart/C out of Axis2/C
project and place it under
http://svn.apache.org/repos/asf/webservices/rampart/trunk/c/
This groups
[
https://issues.apache.org/jira/browse/AXIS2-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthiga Rajeevani Ratnam updated AXIS2-2358:
-
Attachment: patch
Inline code level comments for
+1, Welcome
-- Azeez
On 3/20/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote:
Hi All,
I would like to propose Sumedha Rubasinghe as an Apache Axis2/Java
committer. He has contributed Axis2 , AXIOM a lot specially implementing
SAAJ module. In addition to that he is very active in the community
+1
Saminda
On 3/21/07, Supun Kamburugamuva [EMAIL PROTECTED] wrote:
+1
Supun.
On 3/21/07, Isuru Suriarachchi [EMAIL PROTECTED] wrote:
+1 from me too..
Isuru
On 3/20/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote:
Hi All,
I would like to propose Sumedha Rubasinghe as an Apache
+1
Welcome :-)
Best Regards,
Chamil Thanthrimudalige
On Mar 21, 2007, at 10:46 AM, Supun Kamburugamuva wrote:
+1
Supun.
On 3/21/07, Isuru Suriarachchi [EMAIL PROTECTED] wrote:
+1 from me too..
Isuru
On 3/20/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote:
Hi All,
I would like to
Online report :
http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/1511
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed, 21 Mar 2007 07:03:31 +
Finished at: Wed, 21 Mar 2007 07:34:43 +
Total
PERF: AddressingOutHandler.WSAHeaderHandler does not need its own logger
Key: AXIS2-2359
URL: https://issues.apache.org/jira/browse/AXIS2-2359
Project: Axis 2.0 (Axis2)
[
https://issues.apache.org/jira/browse/AXIS2-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Illsley resolved AXIS2-2359.
--
Resolution: Fixed
Fixed in SVN r520799
PERF: AddressingOutHandler.WSAHeaderHandler does not
xmlSchema optional attributes are not handled properly
--
Key: AXIS2-2360
URL: https://issues.apache.org/jira/browse/AXIS2-2360
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Online report :
http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/1514
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed, 21 Mar 2007 08:19:04 +
Finished at: Wed, 21 Mar 2007 08:57:51 +
Total
Hi Asankha !
I couldn't patch the war file but I successfully run the SOAP over JMS
sample under the standalone distribution.
So thanks a lot ! :-)
If you don't mind, I'd like to ask you a question about JMS: actually my
real aim is to create a publisher/subscriber web service allowing a
Hi All;
At the moment we have small issues with the way we handle wsdl files in
the META-INF directory. What we are doing is load all the wsdl inside
the META-INF and then make AxisServices out of them , next read
services.xml and from that pick the required AxisServices (and throw the
remaining
Deepal,
I think we should consider adding the wsdl name in services.xml
instead of trying to do this. If nothing is specified then we do what
we do now scanning the wsdl's. I definitely don't think we should
switch to your proposal at this late juncture.
thanks,
dims
On 3/21/07, Deepal
Sounds like a discussion that should happen in the Axis2-dev list..
-- Forwarded message --
From: Davanum Srinivas [EMAIL PROTECTED]
Date: Mar 21, 2007 4:00 PM
Subject: Re: [Axis2] Axis2 1.2 release prograss
To: axis-user@ws.apache.org
Amila,
Please comment that test out
Those are my 2 cents :)
-- dims
On 3/21/07, Thilina Gunarathne [EMAIL PROTECTED] wrote:
Sounds like a discussion that should happen in the Axis2-dev list..
-- Forwarded message --
From: Davanum Srinivas [EMAIL PROTECTED]
Date: Mar 21, 2007 4:00 PM
Subject: Re: [Axis2] Axis2
Is something broken with the status quo? If its only an inefficiency its
not a huge big deal given its a one-time deployment cost only.
If nothing is broken we should consider these ideas for 1.3, not for 1.2.
Sanjiva.
Davanum Srinivas wrote:
Deepal,
I think we should consider adding the
+1 from me.
Cheers
Brian DePradine
Web Services Development
IBM Hursley
External +44 (0) 1962 816319 Internal 246319
If you can't find the time to do it right the first time, where will you
find the time to do it again?
Deepal Jayasinghe [EMAIL PROTECTED] wrote on 20/03/2007
I agree.
On 3/21/07, Sanjiva Weerawarana [EMAIL PROTECTED] wrote:
Is something broken with the status quo? If its only an inefficiency its
not a huge big deal given its a one-time deployment cost only.
If nothing is broken we should consider these ideas for 1.3, not for 1.2.
Sanjiva.
Davanum
Allow developers and/or deployers deactivate JMX setup
--
Key: AXIS-2643
URL: https://issues.apache.org/jira/browse/AXIS-2643
Project: Axis
Issue Type: Improvement
Components:
Hi Badrys
Firstly, you define the JMS connection factories that the JMS transport
should be listening for messages to Axis2 as follows, on your
axis2.xml. Here you specify the JNDI properties (url, class, and JNDI
name of the actual connection factory) and define a logical 'name' for
this to
[
https://issues.apache.org/jira/browse/AXIS2-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482744
]
Amila Chinthaka Suriarachchi commented on AXIS2-2360:
-
what is the default value for use
[
https://issues.apache.org/jira/browse/AXIS-2643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduardo Costa updated AXIS-2643:
Attachment: axis-2643.patch
Proposed patch. Changes both AxisServlet and ServiceAdmin to allow
What is the status of this effort?
Paul
At 09:03 AM 2007-01-12, Glen Daniels wrote:
Hi Axis-Dev'ers:
As some of you may know, several companies (BEA, IBM, Progress, and
TIBCO) have been working on a formal set of specifications for binding
SOAP to the Java Message Service API. These specs
Online report :
http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/1518
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed, 21 Mar 2007 12:31:40 +
Finished at: Wed, 21 Mar 2007 13:23:59 +
Total
[
https://issues.apache.org/jira/browse/AXIS2-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482757
]
Amila Chinthaka Suriarachchi commented on AXIS2-2292:
-
ok thats great. Please run some sample
Hi Asankha
I think I may have badly described my problem cause that wasn't exactly the
answer to my question. :-(
By the way, I've already configured my axis2.xml and my services.xml just
like you told me.
Here is my question : does the fact of specifying a JMS destination in
services.xml
+1 I think this is a little more intuitive.
-Nick
Davanum Srinivas [EMAIL PROTECTED]
03/21/2007 05:37 AM
Please respond to
axis-dev@ws.apache.org
To
axis-dev@ws.apache.org
cc
Subject
Re: [Axis2] Wsdsl inside service aar file
Deepal,
I think we should consider adding the wsdl name
Hi Dennis,
Please see the notes between Glen and I. I'm investigating this, but it
looks like a deployment change broke JAX-WS.
Regards,
-Nick
Dennis Sosnoski [EMAIL PROTECTED]
03/21/2007 04:22 AM
Please respond to
axis-dev@ws.apache.org
To
axis-dev@ws.apache.org
cc
Subject
Re:
+1 from me
Brian De Pradine [EMAIL PROTECTED]
03/21/2007 05:58 AM
Please respond to
axis-dev@ws.apache.org
To
axis-dev@ws.apache.org
cc
Subject
Re: [Vote][Axis2] Sumedha Rubasinghe as a committer
+1 from me.
Cheers
Brian DePradine
Web Services Development
IBM Hursley
External
[
https://issues.apache.org/jira/browse/AXIS2-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482765
]
Amila Chinthaka Suriarachchi commented on AXIS2-2175:
-
I checked. Now what we do is directly
[
https://issues.apache.org/jira/browse/AXIS2-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2218:
Component/s: jaxws
@HandlerChain annotation is not picked up
[
https://issues.apache.org/jira/browse/AXIS2-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2347:
Component/s: jaxws
When deploying using JAXWSMessageReceiver, the dynamic wsdl (?wsdl)
[
https://issues.apache.org/jira/browse/AXIS2-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas reassigned AXIS2-1729:
---
Assignee: Keith Godwin Chapman (was: Sanka Samaranayake)
Keith,
Do we have a good
oldMsgCtx 'From' does not copied to newMsgCtx 'From' when the MEP is IN_OUT
---
Key: AXIS2-2361
URL: https://issues.apache.org/jira/browse/AXIS2-2361
Project: Axis 2.0 (Axis2)
[
https://issues.apache.org/jira/browse/AXIS2-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas reassigned AXIS2-2361:
---
Assignee: David Illsley (was: Davanum Srinivas)
David,
Any thoughts on how we can
[
https://issues.apache.org/jira/browse/AXIS2-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482776
]
Mariusz Woloncewicz commented on AXIS2-2360:
According to http://www.w3.org/TR/xmlschema-1/ attributes
I came across the latest feature of Axis2 allowing JSON. As I am looking
at building out my site to inculde AJAX I was interested in trying this
out. I was trying JSON with the latest Snapshot of Axis2. I was looking
at trying out the Sample application YahooJSONSearch, however I ran into
the
[
https://issues.apache.org/jira/browse/AXIS2-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482788
]
Antony Bilev commented on AXIS2-2175:
-
Hi Amilia,
I was able to repeat the same problem with the latest Axis2
Online report :
http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/1521
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed, 21 Mar 2007 14:06:10 +
Finished at: Wed, 21 Mar 2007 14:53:13 +
Total
[
https://issues.apache.org/jira/browse/AXIS2-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482814
]
Carmen Checa commented on AXIS2-2292:
-
Test cases ran fine.
Thank you
wsdl2java produces a stub that cannot
Hi Paul
I have been reading through these specs again last weekend and was
preparing to make the enhancements to the current implementation to be
consistent. I also wanted the JMS transport to be able to address the
open issues filed against it.. I hope to embark on this. Would you be
Hi Badrys
does the fact of specifying a JMS destination in
services.xml create a physical Destination (a Java Object that I can access
from a java code) ? and if it's the case can you tell me how to do it ?
Yes, if your JMS provider supports this. (e.g. ActiveMQ) This would
create a JMS
Online report :
http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/1522
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed, 21 Mar 2007 16:06:49 +
Finished at: Wed, 21 Mar 2007 16:48:30 +
Total
Yay!
How about
public void engageModule(String modName) {
engageModule(new QName(modName));
}
Paul
On 3/21/07, Glen Daniels [EMAIL PROTECTED] wrote:
Hi all!
Please note/review this change:
http://svn.apache.org/viewvc?view=revrev=520956
In it I refactored the name of transports (both
The JAXWS tests were broken by the change in rev: 519539. I reverted that
in my sandbox and all is well. Looking at the JAXWS portion now to see
what needs to change.
-Nick
Nicholas L Gallardo/Austin/[EMAIL PROTECTED]
03/21/2007 01:19 AM
Please respond to
axis-dev@ws.apache.org
To
Fixed.
-Nick
Nicholas L Gallardo/Austin/[EMAIL PROTECTED]
03/21/2007 12:27 PM
Please respond to
axis-dev@ws.apache.org
To
axis-dev@ws.apache.org
cc
Subject
Re: [axis2] Continuum build and JAXWS
The JAXWS tests were broken by the change in rev: 519539. I reverted that
in my
Hi Paul!
Yay!
:)
How about
public void engageModule(String modName) {
engageModule(new QName(modName));
}
Funny you should ask... How about I just do the same thing with Module
names (Stringify them) right now and be done with it?
--Glen
Online report :
http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/1524
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed, 21 Mar 2007 18:05:42 +
Finished at: Wed, 21 Mar 2007 18:30:20 +
Total
Hi all!
Please note/review this change:
http://svn.apache.org/viewvc?view=revrev=520956
In it I refactored the name of transports (both in and out) to be a
String instead of a QName, for simplicity and speed. Let me know if
there are any issues with this. I know I still need to change the
Woops, was apparently running without the integration stuff switched on
in m2! Fixing
--G
davidillsley (Continuum) wrote:
Online report :
http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/1524
Build statistics:
State:
Hey David, the download as text link seems to be broken on the latest
continuum builds. I get a 404 after it tries to GET:
http://ws.zones.apache.org:1/continuum/servlet/browse?file=$requestUtil.getParameter('id')/${requestUtil.getParameter('buildId')}.log.txt
Looks like the parameters
I see an entry by Deepal indicating that the bug is resolved in the following
revision. Maybe the patch that was supplied was not added as-is but was
refactored? There seems to be a lot of changes to the file in that revision.
Revision: 498980
Author: deepal
Date: 2:42:35 AM, Tuesday,
Glen
I agree its good overall, but I am a bit concerned about a public API
change if its without deprecation of the previous methods. Synapse can
upgrade our code - but there may be other projects/code outside that may
get broken. Just a concern..
asankha
How about
public void
Hi Asankha:
We can certainly add deprecated methods for the setters and the
constructors, but not for getName() (since it would only differ by
return type). That being the case, I figured just take the hit now
rather than only having the set half of the API continue to work.
Let me know if
Online report :
http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/1526
Build statistics:
State: Ok
Previous State: Failed
Started at: Wed, 21 Mar 2007 20:02:09 +
Finished at: Wed, 21 Mar 2007 20:41:51 +
Total time:
Online report :
http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/1528
Build statistics:
State: Failed
Previous State: Ok
Started at: Wed, 21 Mar 2007 22:01:29 +
Finished at: Wed, 21 Mar 2007 22:21:38 +
Total time:
Given the inability to deprecate smoothly I suggest we take the hit and
put blink tags around this change in the release notes.
Maybe we should put a section titled Backwards Incompatible Changes (and
make sure we explain why they are backwards incompatible).
Big +1 for making both the
I'm +1 on this. Do the deprecated setters and most importantly the
deprecated engageModule(QName).
Paul
On 3/21/07, Glen Daniels [EMAIL PROTECTED] wrote:
Hi Asankha:
We can certainly add deprecated methods for the setters and the
constructors, but not for getName() (since it would only differ
[
https://issues.apache.org/jira/browse/AXIS2-2351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Thaker resolved AXIS2-2351.
--
Resolution: Fixed
revision # 521066
JAXB Marshalling failure for enum types
[
https://issues.apache.org/jira/browse/AXIS2-2351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Thaker closed AXIS2-2351.
JAXB Marshalling failure for enum types
Online report :
http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/1530
Build statistics:
State: Ok
Previous State: Failed
Started at: Thu, 22 Mar 2007 02:01:08 +
Finished at: Thu, 22 Mar 2007 02:32:42 +
Total time:
[
https://issues.apache.org/jira/browse/AXIS2-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482996
]
Keith Godwin Chapman commented on AXIS2-1729:
-
Hi Dims,
We do not have a sample at the moment. I'll
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+1 from me too :)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGAfmEjON2uBzUhh8RAjKPAKC1HPMdYjr1QJMKewoOH+LtO0eMmACfYU3q
HU87T4THatqcyTQ/v66rXRM=
=phcz
-END
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sanjiva Weerawarana wrote:
Deepal Jayasinghe wrote:
- WSDL 2.0 fully support – DONE
(Reading , writing and codegen)
Do we have ?wsdl2 support also? If not that needs to be on the list.
I don't think we can do ?wsdl for WSDL 2.0, as Woden
[
https://issues.apache.org/jira/browse/AXIS2-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483007
]
Lahiru Sandakith commented on AXIS2-2354:
-
Hi Bhagya,
Its seems to me that you are using eclipse wtp based
Online report :
http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/1533
Build statistics:
State: Failed
Previous State: Ok
Started at: Thu, 22 Mar 2007 04:12:32 +
Finished at: Thu, 22 Mar 2007 04:40:09 +
Total time:
+1.
Thanks
Deepal
Sanjiva Weerawarana wrote:
Given the inability to deprecate smoothly I suggest we take the hit
and put blink tags around this change in the release notes.
Maybe we should put a section titled Backwards Incompatible Changes
(and make sure we explain why they are backwards
Inline Code Level Comments
--
Key: AXIS2-2362
URL: https://issues.apache.org/jira/browse/AXIS2-2362
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: documentation
Affects Versions: 1.2
[
https://issues.apache.org/jira/browse/AXIS2-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthiga Rajeevani Ratnam updated AXIS2-2362:
-
Attachment: abstractdispatcher
Modifications to code level comments in
Inline Code Level Comments
--
Key: AXIS2-2363
URL: https://issues.apache.org/jira/browse/AXIS2-2363
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: documentation
Affects Versions: 1.2
[
https://issues.apache.org/jira/browse/AXIS2-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthiga Rajeevani Ratnam updated AXIS2-2363:
-
Attachment: AxisConfiguration
Changes to code level comments in
[
https://issues.apache.org/jira/browse/AXIS2-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthiga Rajeevani Ratnam updated AXIS2-2363:
-
Attachment: AxisConfiguration1
Edits to code level comments
Inline
[
https://issues.apache.org/jira/browse/AXIS2-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483023
]
Karthiga Rajeevani Ratnam commented on AXIS2-2363:
--
Please commit AxisConfiguration1 and not
Online report :
http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/1535
Build statistics:
State: Failed
Previous State: Failed
Started at: Thu, 22 Mar 2007 06:18:57 +
Finished at: Thu, 22 Mar 2007 06:51:43 +
Total
81 matches
Mail list logo
