[
https://issues.apache.org/jira/browse/WSCOMMONS-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi updated WSCOMMONS-511:
---
Attachment: patch.txt
patch to support above requirement
-511
Project: WS-Commons
Issue Type: Improvement
Reporter: Amila Chinthaka Suriarachchi
Use source address to send a reply with UDP transport if the addressing ReplyTo
is annonymous.
ws-discovery specification[1] requires annonymous reply messages.
This can be
[
https://issues.apache.org/jira/browse/WSCOMMONS-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779305#action_12779305
]
Amila Chinthaka Suriarachchi commented on WSCOMMONS
Type: Bug
Reporter: Amila Chinthaka Suriarachchi
String xmlString = "http://schemas.xmlsoap.org/soap/envelope/\";>\n" +
" \n" +
" \n" +
" s:Client\n" +
"
[
https://issues.apache.org/jira/browse/WSCOMMONS-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi resolved WSCOMMONS-500.
Resolution: Fixed
applied the patch
> EPR retu
[
https://issues.apache.org/jira/browse/WSCOMMONS-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi resolved WSCOMMONS-495.
Resolution: Fixed
applied the patch
> Enable
[
https://issues.apache.org/jira/browse/WSCOMMONS-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi resolved WSCOMMONS-494.
Resolution: Fixed
Applied the patch
> Unit Test
[
https://issues.apache.org/jira/browse/WSCOMMONS-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744562#action_12744562
]
Amila Chinthaka Suriarachchi commented on WSCOMMONS
[
https://issues.apache.org/jira/browse/WSCOMMONS-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi updated WSCOMMONS-494:
---
Attachment: org.apache.axis2
[
https://issues.apache.org/jira/browse/WSCOMMONS-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741901#action_12741901
]
Amila Chinthaka Suriarachchi commented on WSCOMMONS-494:
I
[
https://issues.apache.org/jira/browse/WSCOMMONS-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733485#action_12733485
]
Amila Chinthaka Suriarachchi commented on WSCOMMONS
[
https://issues.apache.org/jira/browse/WSCOMMONS-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi updated WSCOMMONS-472:
---
Attachment: patch.txt
patch which let support embeded jta
[
https://issues.apache.org/jira/browse/WSCOMMONS-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi updated WSCOMMONS-472:
---
Attachment: patch.txt
this patch gives this feature to
: Amila Chinthaka Suriarachchi
Currently jms transport always looks an JNDI context to get the user
transactions and jmsfactories.
But this code is used only in JMSConnectionFactory. So an alternative
implementation can be written by giving a class which extends the
JMSConnctionFactory.
This
[
https://issues.apache.org/jira/browse/WSCOMMONS-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi resolved WSCOMMONS-456.
Resolution: Fixed
applied the patch with the
[
https://issues.apache.org/jira/browse/WSCOMMONS-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694371#action_12694371
]
Amila Chinthaka Suriarachchi commented on WSCOMMONS-456:
As
[
https://issues.apache.org/jira/browse/WSCOMMONS-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694063#action_12694063
]
Amila Chinthaka Suriarachchi commented on WSCOMMONS-456:
---
[
https://issues.apache.org/jira/browse/WSCOMMONS-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi updated WSCOMMONS-456:
---
Attachment: patch.txt
patch with the changes to SMTP
Supporting SMTP transport for RM
Key: WSCOMMONS-456
URL: https://issues.apache.org/jira/browse/WSCOMMONS-456
Project: WS-Commons
Issue Type: Improvement
Reporter: Amila Chinthaka Suriarachchi
I
[
https://issues.apache.org/jira/browse/WSCOMMONS-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi resolved WSCOMMONS-455.
Resolution: Fixed
fixed the issue with revision 759639
SMTP transport does not work with Security
--
Key: WSCOMMONS-455
URL: https://issues.apache.org/jira/browse/WSCOMMONS-455
Project: WS-Commons
Issue Type: Bug
Reporter: Amila Chinthaka
[
https://issues.apache.org/jira/browse/WSCOMMONS-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689878#action_12689878
]
Amila Chinthaka Suriarachchi commented on WSCOMMONS-454:
ye
[
https://issues.apache.org/jira/browse/WSCOMMONS-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689860#action_12689860
]
Amila Chinthaka Suriarachchi commented on WSCOMMONS-454:
As
Author: chinthaka
Date: Tue Mar 24 04:45:44 2009
New Revision: 757662
URL: http://svn.apache.org/viewvc?rev=757662&view=rev
Log:
UPdating my info
Modified:
webservices/commons/site/axiom/team-list.html
Modified: webservices/commons/site/axiom/team-list.html
URL:
http://svn.apache
Reporter: Amila Chinthaka Suriarachchi
Priority: Blocker
hi all,
recently I started some RM tests with the commons mail transport.
Mail transport listener runs in a timer task.
TimerTask timerTask = new TimerTask() {
@Override
public void run
+1 (binding)
Thanks,
Chinthaka
Hi Benson,
On Sun, Nov 30, 2008 at 9:04 PM, Benson Margulies wrote:
> Eran,
>
> I get the feeling that you have some particular individuals in mind
> who haven't been heard from since the vote was called off, since there
> have been some discussion contributions from others.
I'm not sure which
ience of axis2 developer. And I
don't think that will hinder anyone using anything within WS-Commons
components.
What do you all think? Let's have a friendly discussion.
Thanks,
Chinthaka
On Fri, Nov 28, 2008 at 1:32 PM, Eran Chinthaka <[EMAIL PROTECTED]>wrote:
> Hi David,
&g
+1
On Sun, Nov 30, 2008 at 7:55 PM, Deepal jayasinghe <[EMAIL PROTECTED]>wrote:
> +1 (binding)
>
> Deepal
> > +1
> >
> > Thanks,
> > Ruchith
> >
> > On Sun, Nov 30, 2008 at 1:44 PM, Senaka Fernando <[EMAIL PROTECTED]>
> wrote:
> >
> >> +1,
> >>
> >> Thanks,
> >> Senaka
> >>
> >> On Thu, Nov 27, 2
leave in WS and promote to a proper sub project. Used
> widely, not Axis2 specific, and deserves a little more visibility.
I'm 0- on this.
>
>
> Sandesha2, Rampart, Kandula2, Savan... move to an Axis2 TLP. These are
> (reasonably) tightly coupled to Axis2, drive Axis2 in interesting ways
> and are in demand by a large number of Axis2 users. Moving them to an
> Axis2 TLP would (IMO) allow that PMC to ship a compelling bundle and
> build a coherent community.
+1
Thanks,
Chinthaka
2. All the projects within WS-Commons sub-project
3. Kandula2 (might have to refactor existing code base to extract only
Kandula2)
4. Rampart
5. Sandesha
6. Savan
With Mettha,
Eran Chinthaka
Health is the greatest gift; contentm
What if I like only ome of them and do not agree with the other?
For example, I'm "ok" with Axis2 moving out, but I'd like to see Axiom,
Neethi, etc, as sub projects in Axis2.
Thanks,
Eran
On Thu, Nov 20, 2008 at 11:02 AM, Jarek Gawor <[EMAIL PROTECTED]> wrote:
> +1
>
> Jarek
>
> On Thu, Nov 20
m in the proposal (re-evaluating the remaining
> projects).
>
> --Glen
>
> Eran Chinthaka wrote:
>
>> What if I like only ome of them and do not agree with the other?
>>
>> For example, I'm "ok" with Axis2 moving out, but I'd like to see Axiom,
ts within WS project, and taking with
Axis2 is about Axis2 dependencies, then why should we move Poloka (when it
is graduated) in to Axis2. Its just another project, which has a *plugin*
(as I think) to work with Axis2.
if this is the case, then I will argue that Synapse also should come under
Axis2. Abdera should come in to Axiom.
I am seriously missing something somewhere.
Thanks,
Chinthaka
On Sun, Nov 9, 2008 at 7:23 PM, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> Eran,
>
> You are falling behind :) Yes, please see latest TLP proposal on wiki.
> Yes, Axiom is not moving.
thanks Dims :).
My point is Axiom *should* move, if we are moving.
Thanks,
Chinthaka
+1 from me too.
Thanks,
Eran
On Thu, Apr 10, 2008 at 9:42 AM, Glen Daniels <[EMAIL PROTECTED]> wrote:
> Hi dims:
>
> Davanum Srinivas wrote:
>
> > In the interest of time, i propose we make a joint vote for all 3
> > commons projects (XmlSchema/Axiom/Neethi). Then woden
> > can pick up xmlschema
+1 from me.
On Thu, Apr 10, 2008 at 9:42 AM, Glen Daniels <[EMAIL PROTECTED]> wrote:
> Hi dims:
>
> Davanum Srinivas wrote:
>
> > In the interest of time, i propose we make a joint vote for all 3
> > commons projects (XmlSchema/Axiom/Neethi). Then woden
> > can pick up xmlschema/axiom and make th
Just forget this mail.
I'm switching email addresses and sent to commons-dev instead of
commons-dev-unsubscribe.
On Thu, Mar 6, 2008 at 3:45 PM, Eran Chinthaka <[EMAIL PROTECTED]>
wrote:
>
> -
> To unsubsc
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Author: chinthaka
Date: Sat Nov 17 20:38:09 2007
New Revision: 596052
URL: http://svn.apache.org/viewvc?rev=596052&view=rev
Log:
Adding the problem mentioned in Axis2-3155 as a test case
Modified:
webservices/commons/trunk/modules/axiom/modules/axiom-tests/src/test/java/org/apache/axio
[
https://issues.apache.org/jira/browse/WSCOMMONS-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12522383
]
Amila Chinthaka Suriarachchi commented on WSCOMMONS-222:
what is the fix you made
in
google for them if u need more info.
But I am not sure whether XMLStreamWriter does attribute value
normalization. There is one way you can know it for sure ;) Writer some
code either using pure StAX api or using Axiom to serialize some
normalizable attribute values.
HTH.
Chinthaka
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+1
Thanks,
Chinthaka
Sanka Samaranayke wrote:
> Hello Everyone,
>
> I propose the following artifacts as the release artifacts of Axiom
> 1.2.5 version.
>
> The staging area is at:
> http://people.apache.org/~sanka/sta
[
https://issues.apache.org/jira/browse/WSCOMMONS-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eran Chinthaka resolved WSCOMMONS-175.
--
Resolution: Cannot Reproduce
I just tested this within Axiom using woodstox 3.0 and
Author: chinthaka
Date: Mon Jul 9 19:53:59 2007
New Revision: 554808
URL: http://svn.apache.org/viewvc?view=rev&rev=554808
Log:
- adding the test found in WSCOMMONS-175
- fixing a minor issue in README file
Modified:
webservices/commons/trunk/modules/axiom/README.txt
webservices/com
[
https://issues.apache.org/jira/browse/WSCOMMONS-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eran Chinthaka updated WSCOMMONS-175:
-
Assignee: Eran Chinthaka
Priority: Blocker (was: Major)
> Serializat
the release than fixing it.
> Who's most apt for looking into this issue? There is a patch attached to
> the issue... can somebody review it?
>
I will review the patch and get back to you tonight. Sorry for the delay.
Thanks,
Chinthaka
-BEGIN PGP SIGNATURE-
Version: GnuPG v
not see a point in
putting RCs. Axis2 is not yet released, so why can not you do a new RC.
Thanks,
Chinthaka
Sanka Samaranayake wrote:
> Since these are minor flaws can we just go ahead with the release ?
>
> Thanks,
> Sanka
>
> On 7/7/07, Eran Chinthaka <[EMAIL PROTECTED]&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+1
Davanum Srinivas wrote:
> Folks,
>
> Believe it or not! we have 230 people who have karma to our svn:
> https://svn.apache.org/repos/asf/webservices/
>
> Out of these only about 74 people have made commits in the last 1
> year. You can get this i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- - Please remove junit jar from bin distro
- - the readme talks about a docs distro. Please remove that sentence.
Sanka Samaranayake wrote:
> Hello Everyone,
>
> I propose the following artifacts[1] as the release artifacts of Axiom
> 1.2.5version.
. Asankha
is some one who really will be affected with this change from Synapse
pov. If the users don't need it, why bother?
Just my 2 cents.
Thanks,
Chinthaka
Asankha C. Perera wrote:
> Sanka
>
> I agree with Chinthaka, and changing the group ID's will create
> confusions and
think it is
better to have it like what we have now as it reflects our Axiom project
site and the parent project.
Unlike Axis2, Axiom is *within* commons project. So don't you think the
id should reflect it?
I don't think the id matter a lot but do we really need to change
another thing??
Ch
ed in to this. So v1.2.5 is more suitable than 1.3
Chinthaka
>
> Thanks
> Deepal
>> Hello everyone,
>>
>> I suggest that we do a relase say axiom-1.2.5 prior to next
>> axis-1.3release.
>>
>> Please raise any issues that we must get fixed since I di
Reporter: Amila Chinthaka Suriarachchi
Priority: Minor
Currently there is no direct API method to give an QName as an attribute value.
for an example lets say I have to create and OMElment for this xml string
(programatically)
http://www.w3.org/2001/XMLSchema-instance";
xmln
[
https://issues.apache.org/jira/browse/WSCOMMONS-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509315
]
Eran Chinthaka commented on WSCOMMONS-211:
--
I am now trying to fix this issue. Actually the problem is
have a DOM
element, how can you validate it against a given schema.
I know how to do it creating a SAXParser and switching on validation.
But this requires me to read the whole XML again using a parser.
So do u know a way to validate an existing DOM document against a schema?
Chinthaka
-BEGIN
[
https://issues.apache.org/jira/browse/WSCOMMONS-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497344
]
Amila Chinthaka Suriarachchi commented on WSCOMMONS-205:
same problem exists with the
[
https://issues.apache.org/jira/browse/WSCOMMONS-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495690
]
Eran Chinthaka 2 commented on WSCOMMONS-206:
If you can add a small test case for this, perhaps I
[
https://issues.apache.org/jira/browse/WSCOMMONS-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495359
]
Amila Chinthaka Suriarachchi commented on WSCOMMONS-204:
thank dennis for your
Project: WS-Commons
Issue Type: Bug
Components: XmlSchema
Reporter: Amila Chinthaka Suriarachchi
Lets take this schema
http://www.w3.org/2001/XMLSchema";
xmlns="http://www.w3.org/2001/XMLSchema";
xmlns:tns="org.apa
Attribute QName problem
---
Key: WSCOMMONS-204
URL: https://issues.apache.org/jira/browse/WSCOMMONS-204
Project: WS-Commons
Issue Type: Bug
Components: XmlSchema
Reporter: Amila Chinthaka
test case that I have added so that
1. makes me understand the problem and might be able to look in to Axiom
if the problem is with it.
2. no one can break your code later, which is the case sometimes in Axis2 ;)
Thanks,
Chinthaka
Sanjaya Karunasena wrote:
> I took a look at the test code.
integrated in to Axis2, I did the same thing and the problem seems to be
still there.
I opened an issue in JIRA [1] for this.
This is somewhat related to Axiom also, so cc'ed to commons-dev list as
well.
Thanks,
Chinthaka
https://issues.apache.org/jira/browse/AXIS2-2653
-BEGIN PGP SIGN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ok, Glen. You lose. I didn't find anything similar to that within Axiom
code :)
But that made me to fix some more minor issues.
Chinthaka
Eran Chinthaka wrote:
> Glen Daniels wrote:
>> Hi Chinthaka!
>
>> Eran Chinthaka 2
Author: chinthaka
Date: Tue May 8 16:31:31 2007
New Revision: 536378
URL: http://svn.apache.org/viewvc?view=rev&rev=536378
Log:
- SOAP 1.1 and 1.2 versions of fault details elements were extending their own
serialization logic. But the only difference was the local name. Fixed it by
moving
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Glen Daniels wrote:
> Hi Chinthaka!
>
> Eran Chinthaka 2 (JIRA) wrote:
>> I am amazed to see this bug inside SOAPFaultDetail class. No one had
>> noticed this.
>
> +1, but I bet you a beer that there are more where tha
[
https://issues.apache.org/jira/browse/WSCOMMONS-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eran Chinthaka 2 resolved WSCOMMONS-202.
Resolution: Fixed
Assignee: Eran Chinthaka
Fixed in r536362. Thanks
Author: chinthaka
Date: Tue May 8 15:37:45 2007
New Revision: 536362
URL: http://svn.apache.org/viewvc?view=rev&rev=536362
Log:
Fixing WSCommons-202. Text under SOAPFaultDetail element is serialized twice.
Modified:
webservices/commons/trunk/modules/axiom/modules/axiom-impl/src/main/
[
https://issues.apache.org/jira/browse/WSCOMMONS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eran Chinthaka 2 resolved WSCOMMONS-201.
Resolution: Fixed
Assignee: Eran Chinthaka
Well the problem was due to a
Author: chinthaka
Date: Sun May 6 20:52:48 2007
New Revision: 535730
URL: http://svn.apache.org/viewvc?view=rev&rev=535730
Log:
Fixing WSCOMMONS-201. Synchronizing getUUID method.
Modified:
webservices/commons/trunk/modules/axiom/modules/axiom-api/src/main/java/org/apache/axiom/om/
it as message id. I think we are using it
without a problem in all the above cases very well.
At the same time this UUID generator was a perf bottleneck some time
back and we hacked it a bit.
So what is missing here? Please explain and help us to improve it.
Thanks,
Eran Chinthaka
Rodrigo Ruiz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Great !! I'd love to see it integrated in to Axiom if it is better than
Jaxen.
Since you are the creator/father/founder/ of SXC, any idea to integrate
it with Axiom?
Thanks a lot Dan, in advance :)
- -- Chinthaka
Dan Diephouse wrote:
> I
nst a given object model.
So if you find a better way of implementing XPath over Axiom, please do
let us know or even help us by implementing it.
Thanks,
Chinthaka
Angel Todorov wrote:
> Hi all,
>
> I can see AXIOM has support for XPath. But beneath it is a StAX
> parser, and such p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+1
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGFs2ZjON2uBzUhh8RAtBGAJ9QYxeiSYSbuPtsRnokSZMFHr5vywCgqHGX
PzWAGSQSjiqcD1mCszmajv8=
=4XBm
-END PGP SIGNATURE---
mproved SOAP version handling, and
> altered the behavior of OMText to deal with QNames in a less arcane manner.
Glen, if possible, can I know some more info about what you are changing
in Axiom? Just curious :)
Thanks,
Chinthaka
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
Co
the above method without worrying about which
version of SOAP I am dealing with.
But if you want to clean this method and create another method, I'm ok
with that too. But please please make sure we have
OMElement.getChildrenWithLocalName(String). I am a poor user which needs
that.
Thank
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+1
Davanum Srinivas wrote:
> +1
>
> On 3/21/07, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:
>> +1 for the release...
>>
>> >
>> > After Axiom 1.2.2 there were few changes which are more important for
>> > Axis2 and Axis2 wont be able to release w.o
both the approaches. Unless if we want
to really really want to change it back, for dead solid reason, I think
its better to leave it as it is :)
I hope no one will propose to have a switch to select which one to use,
dynamically ;)
- -- Chinthaka
Glen Daniels wrote:
> Hi all:
>
> Curre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Did we discuss about $subject before?
The application deadlines is on 14th March and we better maintain a wiki
with project ideas for students to see what we wanna get from them.
- -- Chinthaka
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3
ing and I hope he will be
able to help you.
- -- Chinthaka
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFF7jT8jON2uBzUhh8RAqHVAKCT5WtWakQJ4sKlaVKLqE6SOGzchQCbBR4m
FdVYg7pntDW+Qd1teBGV
's much more helpful to actually put the problem value
> into the exception In this case it only takes an extra moment to code
>
>"but received " + reason.getClass() + "."
1000 appologies for this code written by me some time back. Won't happen
again :(.
-
hints on the problem at hand, I might be able to help as I know a
little bit of both Axiom and addressing :).
Thanks,
Chinthaka
David Illsley wrote:
> Hi all,
> I've been looking at the work that occurs for OMElement.getText()
> which is currently used by the Axis2 addressing handl
ind out is whether it is a valid use case to
> support the creation of an OM tree based on the content of the URL...
>
> thanks,
> Thilina
>>
>> - From the information I got from this mail and the JIRA, I don't think I
>> agree with this proposal.
>>
>>
ssing something here.
Thanks,
Chinthaka
Thilina Gunarathne wrote:
> Hi all,
> As requested in the AXIS2-2213 I would like to change the method
> signature of the init method in the OMBuilder as follows.
>
> public void init(InputStream inputStream, String charSetEncoding,
> String
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+1 from me.
Please make sure you implement these methods in both llom and doom
implementations. Else Ruchith might yell at you later ;)
- -- Chinthaka
sumedha rubasinghe wrote:
> Hi all; I am doing a SAAJ 1.3 implementation. In order for me
Author: chinthaka
Date: Thu Dec 14 04:15:14 2006
New Revision: 487185
URL: http://svn.apache.org/viewvc?view=rev&rev=487185
Log:
Fixing a problem with handling text as QNames.
Modified:
webservices/commons/trunk/modules/axiom/modules/axiom-impl/src/main/java/org/apache/axiom/om/impl/
[ http://issues.apache.org/jira/browse/WSCOMMONS-138?page=all ]
Eran Chinthaka resolved WSCOMMONS-138.
--
Resolution: Fixed
Assignee: Eran Chinthaka
Fixed in r485676. Thanks for pointing this out
Author: chinthaka
Date: Mon Dec 11 06:28:19 2006
New Revision: 485676
URL: http://svn.apache.org/viewvc?view=rev&rev=485676
Log:
Fixing a typo mistake pointed out in
http://issues.apache.org/jira/browse/WSCOMMONS-138.
Added:
webservices/commons/trunk/modules/axiom/modules/axiom-dom
[ http://issues.apache.org/jira/browse/WSCOMMONS-136?page=all ]
Eran Chinthaka resolved WSCOMMONS-136.
--
Resolution: Fixed
Resolving as per last user comment
> OMElement.setFirstChild() can break the AXIOM t
[ http://issues.apache.org/jira/browse/WSCOMMONS-134?page=all ]
Eran Chinthaka reassigned WSCOMMONS-134:
Assignee: Eran Chinthaka
> The interface org.apache.axiom.om.OMFactory seems to be incompl
[
http://issues.apache.org/jira/browse/WSCOMMONS-123?page=comments#action_12457358
]
Eran Chinthaka commented on WSCOMMONS-123:
--
Hi Bernhard,
You have attached the two files and not the patch. Patch provides us a
difference between
[ http://issues.apache.org/jira/browse/WSCOMMONS-101?page=all ]
Eran Chinthaka reassigned WSCOMMONS-101:
Assignee: Thilina Gunarathne
Thilina, IIRC you handled base64 encoding some time back. Please check this.
> axiom base64 encoding
[
http://issues.apache.org/jira/browse/WSCOMMONS-134?page=comments#action_12455348
]
Eran Chinthaka commented on WSCOMMONS-134:
--
Do you wanna help us by providing a patch for this?
> The interface org.apache.axiom.om.OMFactory se
Author: chinthaka
Date: Fri Dec 1 09:57:58 2006
New Revision: 481323
URL: http://svn.apache.org/viewvc?view=rev&rev=481323
Log:
Some more code improvements
Modified:
webservices/commons/trunk/modules/axiom/modules/axiom-impl/src/main/java/org/apache/axiom/om/impl/llom/OMAttributeImpl.
Author: chinthaka
Date: Fri Dec 1 08:18:49 2006
New Revision: 481274
URL: http://svn.apache.org/viewvc?view=rev&rev=481274
Log:
Removing un-necessary repeated method calls in api module
Removed:
webservices/commons/trunk/modules/axiom/modules/axiom-api/src/main/java/org/apache/axio
Author: chinthaka
Date: Fri Nov 24 03:21:19 2006
New Revision: 478835
URL: http://svn.apache.org/viewvc?view=rev&rev=478835
Log:
- Improving identify SOAP version logic a bit
- removing a System out in a test.
Modified:
webservices/commons/trunk/modules/axiom/modules/axiom-api/src/
http://ws.apache.org/commons/axiom
we are proud to announce the release of Version 1.2 of Apache AXIOM!
(Download : http://ws.apache.org/commons/axiom/download.cgi )
Apache AXIOM is a StAX-based, XML Infoset compliant object model which
supports on-demand building of the object tree. It supports
Modified: webservices/commons/site/axiom/source-repository.html
URL:
http://svn.apache.org/viewvc/webservices/commons/site/axiom/source-repository.html?view=diff&rev=474712&r1=474711&r2=474712
==
--- webservices/commons/si
Author: chinthaka
Date: Sun Nov 12 12:23:34 2006
New Revision: 474028
URL: http://svn.apache.org/viewvc?view=rev&rev=474028
Log:
Moving to Axiom 1.2 release.
Modified:
webservices/commons/trunk/modules/neethi/project.properties
Modified: webservices/commons/trunk/modules/ne
Author: chinthaka
Date: Sun Nov 12 12:21:31 2006
New Revision: 474027
URL: http://svn.apache.org/viewvc?view=rev&rev=474027
Log:
Tagging for 1.2 release.
Added:
webservices/commons/tags/axiom/1_2/
- copied from r474026, webservices/commons/trunk/modules/a
1 - 100 of 495 matches
Mail list logo
