On Sun, May 10, 2009 at 12:01 AM, Mike Zhao zhaom...@hotmail.com wrote:
what are you talking about? Sounds like a fraud and you may be reported
soon.
IIUC, what he meant was to go here [1] and learn how to unsubscribe. :)
Cheers!
Dumindu.
[1] http://ws.apache.org/axis2/c/lists_issues.html
[
https://issues.apache.org/jira/browse/AXIS2C-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela reassigned AXIS2C-1363:
-
Assignee: Dumindu Pallewela
Streaming tests for XPath
[
https://issues.apache.org/jira/browse/AXIS2C-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela reopened AXIS2C-1363:
---
patch not comitted
Streaming tests for XPath
[
https://issues.apache.org/jira/browse/AXIS2C-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela resolved AXIS2C-1363.
---
Resolution: Fixed
Fix Version/s: 1.6.0
Fixed in the trunk. Thanks
[
https://issues.apache.org/jira/browse/AXIS2C-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela resolved AXIS2C-1347.
---
Resolution: Fixed
Fix Version/s: 1.6.0
Patch applied. Thanks Parinda. Keep
[
https://issues.apache.org/jira/browse/AXIS2C-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela updated AXIS2C-1361:
--
Attachment: test_xpath.c
This seems to work fine. Please look at the attached program
[
https://issues.apache.org/jira/browse/AXIS2C-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela reopened AXIS2C-1347:
---
Assignee: Dumindu Pallewela
the patch is not committed yet.
OR expression
Hi Parinda,
Please don't resolve the issue until the patch gets committed.
Thanks,
Dumindu.
On Thu, Mar 5, 2009 at 2:29 PM, Varuna Parinda Jayasiri (JIRA)
j...@apache.org wrote:
[
Hi Shankar,
Idea is that to *use* our xpath implementation only the api's provided
by axiom_xpath.h is needed. Other headers are for implementation
internal use only.
Thanks,
Dumindu.
On Mon, Jan 26, 2009 at 12:14 PM, Uthaiyashankar shan...@wso2.com wrote:
Hi devs,
Is there any particular
+1
-Dumindu.
On Mon, Dec 1, 2008 at 8:30 PM, Dinesh Premalal [EMAIL PROTECTED] wrote:
Damitha Kumarage [EMAIL PROTECTED] writes:
Hi Devs,
I would like to nominate Danushka Menikkumbura to be an Axis2/C commiter.
+1
thanks,
Dinesh
Hi All,
While I doubt the need for removing recursion here (given the fact that
using more than a few url components will plainly be an overkill), it seems
to me that removing recursion from both the functions is quite straight
forward.
As it was mentioned earlier the function
[
https://issues.apache.org/jira/browse/AXIS2C-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela resolved AXIS2C-595.
--
Resolution: Fixed
Fix Version/s: Current (Nightly)
Committed the xpath
Hi Hatim,
Would you like to share your patch? We'd be able to integrate it to the
trunk.
Please attach it to a jira issue if you'd like to share [1].
Thanks,
Dumindu.
[1] http://issues.apache.org/jira/browse/AXIS2C
On Thu, Oct 30, 2008 at 7:24 PM, Hatim Daginawala
[EMAIL PROTECTED] wrote:
Hi Vivian,
On Thu, Oct 30, 2008 at 10:20 AM, Vivian Wang [EMAIL PROTECTED]wrote:
Hi Dumindu,
So is it hard to provide such an option (turn on/off validation)?
I don't think it is hard to implement this. I haven't looked in to it
though. When I was working with ssl transport I didn't think
Hi Vivian,
Please find my comment inline:
On Wed, Oct 29, 2008 at 11:44 PM, Vivian Wang [EMAIL PROTECTED]wrote:
So is there an option in axis2/c that I can turn off the certificate
validation?
No we don't support that at the moment.
I think this is important because from a client point of
+1
-Dumindu.
2008/10/13 lahiru gunathilake [EMAIL PROTECTED]
+1 from me..
Lahiru
On Mon, Oct 13, 2008 at 1:50 PM, Milinda Pathirage
[EMAIL PROTECTED] wrote:
+1
Milinda...
--
http://mpathirage.com
http://wso2.org Oxygen for Web Service Developers
http://wsaxc.blogspot.com Web
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dumindu Pallewela
Cinergix - Share, Reuse, Innovate
cinergix.com
[
https://issues.apache.org/jira/browse/AXIS2C-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela reassigned AXIS2C-595:
Assignee: Dumindu Pallewela (was: S.Uthaiyashankar)
XPath support in AXIOM
[
https://issues.apache.org/jira/browse/AXIS2C-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12637008#action_12637008
]
Dumindu Pallewela commented on AXIS2C-595:
--
I have created a branch
Hi All,
I have started on integrating the XPath implementation done by Varuna for
GSoC [1] with our main trunk. I assume that (xpath being specific to axiom),
we can compile it directly into libaxis2_axiom.so. Thus the source will go
to /axiom/src/xpath directory, and the includes, tests
On Mon, Oct 6, 2008 at 8:49 PM, Manjula Peiris [EMAIL PROTECTED] wrote:
[snip]
Can't we use WS-Addressing ReferenceParameters for this ?
[/snip]
I think axis2/java too uses reference parameters in one type of session
scopes it supports (SOAPSession).
-Dumindu.
]
--
Dumindu Pallewela
Cinergix - Share, Reuse, Innovate
cinergix.com
axiom caching. But make sure that
the required support is there for streaming. Basically, if you process the
nodes as axiom provides them, without going up the tree you should be fine.
--
Dumindu Pallewela
Cinergix - Share, Reuse, Innovate
cinergix.com
.
--
Dumindu Pallewela
Cinergix - Share, Reuse, Innovate
cinergix.com
Hi Varuna,
I see that you've done quite a job implementing XPath by now. Could you
please update the list on what you have done already and what remains to be
completed.
Thanks,
Dumindu.
--
Dumindu Pallewela
Cinergix - Share, Reuse, Innovate
cinergix.com
On Thu, Jul 24, 2008 at 1:12 PM, Gaurab Paul [EMAIL PROTECTED] wrote:
i am interested in knowing the design of mod_so and mod_perl modules. Could
you please point me to some relevant documents.
direct your question to [EMAIL PROTECTED]
HTH,
Dumindu.
--
Dumindu Pallewela
Cinergix - Share
:*
should this select node without namespace
(assuming //ns:*)
No.
However, if you are selecting a particular node, it should behave in a
different manner. For examples:
//node should result in only the second node and //ns:node should result
in only the first node.
HTH,
Dumindu.
--
Dumindu
+1.
Dumindu.
--
Dumindu Pallewela
Cinergix - Share, Reuse, Innovate
cinergix.com
On Tue, Jul 8, 2008 at 8:34 PM, Samisa Abeysinghe [EMAIL PROTECTED] wrote:
+1.
Samisa...
lahiru gunathilake wrote:
Here's my +1
Regards
Lahiru
On Tue, Jul 8, 2008 at 4:54 PM, Damitha Kumarage
+1
dumindu.
On Wed, Jun 18, 2008 at 2:45 PM, Sanjaya Ratnaweera [EMAIL PROTECTED]
wrote:
+1
thanks
~sanjaya
Dimuthu Gamage wrote:
+1,
Thanks
Dimuthu
On Wed, Jun 18, 2008 at 10:25 AM, Manjula Peiris [EMAIL PROTECTED] wrote:
+1.
Thanks,
-Manjula.
On Wed, 2008-06-18 at
Hi Varuna,
Could you please update us on the research you did on the streaming
implementation? Basically I would like to know about the following:
1. What sort of queries can be handled with a streaming xpath processor?
2. What needs to be changed in Axiom in order to implement this?
3. How
On Wed, May 28, 2008 at 2:10 PM, Deepal jayasinghe [EMAIL PROTECTED]
wrote:
Hi,
This is blocked by an axiom issue and this is not fixed in the axiom
version available with axis2-1.4. I'd like us to continue with this release
and then lets try to fix the axiom issue (which I don't think has
PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dumindu Pallewela
Senior Software Engineer
WSO2 - Oxygenating the webservices platform
GPG ID: 0x9E131672
]
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID: 0x9E131672
WSO2 | Oxygenating the Web Service Platform | http://wso2.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
it to @ if they prefer. But having an %AT% prefixing all the
commands would make the batch files look quite ugly :).
Thoughts?
Regards,
Dumindu.
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID: 0x9E131672
WSO2 | Oxygenating the Web Service Platform | http://wso2.com
] wrote:
Hi,
I have created a wiki page with some parts of the API. Could you please give
suggestions and guide me in the right direction.
http://wiki.apache.org/ws/axiom-xpath-api-gsoc-varuna
Thank you in advance
--
Varuna
www.xvpj.net
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID
on, without giving it much
consideration at this stage
[/snip]
yes. that'll be the way to go, i suppose.
Regards,
Dumindu.
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID: 0x9E131672
WSO2 | Oxygenating the Web Service Platform | http://wso2.com
[
https://issues.apache.org/jira/browse/RAMPARTC-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12574483#action_12574483
]
Dumindu Pallewela commented on RAMPARTC-67:
---
I believe
resource's lifetime. Please add a jira issue.
The attached patch should solve this issue when shared memory is not
used. I'm not sure if it works when shared memory is used. Hope that
someone familiar with axis2c shared memory implementation will look
further into it.
Regards,
Dumindu.
--
Dumindu
certificate that you have used in TOMCAT server for the
SERVER_CERT parameter in axis2.xml. Note that there is no need for a
key-chain file or a pass-phrase if you do not want client
authentication.
HTH,
Dumindu.
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID: 0x9E131672
WSO2
, due to say security concerns. In such a situation, it
would be easier if we already have implemented this feature using
axis2.xml. Might be too futuristic though :)
Regards,
Senaka
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID: 0x9E131672
WSO2 | Oxygenating the Web Service Platform
options and need to allow http headers to
be accessed in a later day(accidentally seeing this thread for example),
I would rather prefer to add an entry to axis2.xml. ;-)
-Kau
Regards,
Senaka
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID: 0x9E131672
WSO2 | Oxygenating
certificate that you have used in TOMCAT server for the
SERVER_CERT parameter in axis2.xml. Note that there is no need for a
key-chain file or a pass-phrase if you do not want client
authentication.
HTH,
Dumindu.
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID
Well client certificate chain may not be the best term to use. Any
suggestions?
-Dumindu.
On Feb 13, 2008 2:21 PM, Dumindu Pallewela [EMAIL PROTECTED] wrote:
Hi Senaka,
Yes, that's why I said that he can directly use the server certificate :)
However, in axis2 manual, what is referred
it using the axis2.xml. Any
comments?
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID: 0x9E131672
WSO2 | Oxygenating the Web Service Platform | http://wso2.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
://ws.apache.org/axis2/c/docs/axis2c_manual.html#ssl_client
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID: 0x9E131672
WSO2 | Oxygenating the Web Service Platform | http://wso2.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED
for Apache Axis2/C 1.3.0
release.
Here is my vote: +1.
Thanks,
Samisa...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dumindu Pallewela
http://blog.dumindu.com
GPG
PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID: 0x9E131672
WSO2 | Oxygenating the Web Service Platform | http://wso2.com
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID: 0x9E131672
WSO2 | Oxygenating the Web Service
PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID: 0x9E131672
WSO2 | Oxygenating the Web Service Platform
it is REST, e.g.
REST_HTTPMethod REST_HTTPLocation
[/snip]
Won't *RESTMethod* and *RESTLocation* be better, as HTTP is assumed anyway?
-Dumindu.
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID: 0x9E131672
WSO2 | Oxygenating the Web Service Platform | http://wso2.com
On Jan 24, 2008 10:37 PM, Samisa Abeysinghe [EMAIL PROTECTED] wrote:
Oops! That is a glitch :(
We should add this to our check list in the release process Wiki.
Devs, should we do a patch release fixing this? I think we should.
+1
-Dumindu.
--
Dumindu Pallewela
http://blog.dumindu.com
GPG
[
https://issues.apache.org/jira/browse/AXIS2C-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561622#action_12561622
]
Dumindu Pallewela commented on AXIS2C-866:
--
+1 for option 4.
I don't see a reason
to add
improvements(if there any) before I commit these things to trunk.
working on a branch would be easier... just a suggestion.
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID: 0x9E131672
WSO2 | Oxygenating the Web Service Platform | http://wso2.com
/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID: 0x9E131672
WSO2 | Oxygenating the Web Service Platform | http://wso2.com
/
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID: 0x9E131672
WSO2 | Oxygenating the Web Service Platform | http://wso2.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/AXIS2C-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela reassigned AXIS2C-896:
Assignee: Dumindu Pallewela
Implementation of Digest Authentication Scheme
as the Windows user will have a similar experience.
Regards,
Senaka
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID
[
https://issues.apache.org/jira/browse/AXIS2C-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela resolved AXIS2C-896.
--
Resolution: Fixed
Fix Version/s: 1.2.1
Patch committed at revision 612211
[
https://issues.apache.org/jira/browse/AXIS2C-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela resolved AXIS2C-733.
--
Resolution: Fixed
Fix Version/s: Current (Nightly)
Instead of giving an option
[
https://issues.apache.org/jira/browse/AXIS2C-894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela updated AXIS2C-894:
-
Summary: Validating against server certificate when root CA certificate is
not found
[
https://issues.apache.org/jira/browse/AXIS2C-894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela resolved AXIS2C-894.
--
Resolution: Fixed
Fix Version/s: 1.2.1
Assignee: Dumindu Pallewela
/IssueNavigator.jspa?reset=truereporterSelect=specificuserreporter=wtmitchell3
--
Dinesh Premalal
http://xydinesh.wordpress.com
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID: 0x9E131672
WSO2 | Oxygenating the Web Service Platform | http://wso2.com
TC Co-chair
blog: http://pzf.fremantle.org
[EMAIL PROTECTED]
Oxygenating the Web Service Platform, www.wso2.com
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID: 0x9E131672
WSO2 | Oxygenating the Web Service Platform | http://wso2.com
[
https://issues.apache.org/jira/browse/AXIS2C-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela closed AXIS2C-698.
Fixed in 1.1.0.
Hence will close this issue
ssl transport does not verify the server
[
https://issues.apache.org/jira/browse/AXIS2C-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela resolved AXIS2C-767.
--
Resolution: Fixed
Fix Version/s: 1.2.0
Patch committed in.
http Basic
[
https://issues.apache.org/jira/browse/AXIS2C-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela resolved AXIS2C-757.
--
Resolution: Fixed
Patch committed in. Thanks Senaka.
Keep up the good work.
allow
[
https://issues.apache.org/jira/browse/AXIS2C-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela resolved AXIS2C-716.
--
Resolution: Fixed
Fixed with the patch applied for AXIS2-757.
When using basic http
[
https://issues.apache.org/jira/browse/AXIS2C-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela resolved AXIS2C-819.
--
Resolution: Fixed
Assignee: Dumindu Pallewela
Fixed with the patch applied
[
https://issues.apache.org/jira/browse/AXIS2C-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela updated AXIS2C-716:
-
Fix Version/s: (was: 1.1.0)
1.2.0
will be fixing this for 1.2.0
[
https://issues.apache.org/jira/browse/AXIS2C-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela updated AXIS2C-716:
-
Fix Version/s: (was: Current (Nightly))
1.1.0
When using basic
form, it is not much of a problem for him to
view it. That's why we need encryption even when MTOM is used.
HTH,
Dumindu.
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID: 0x9E131672
WSO2 | Oxygenating the Web Service Platform | http://wso2.com
it as Kaushalye explained
in #2 or to use a different serialization function which ignores the
MTOM optimized flag, I guess.
Regards,
-Dumindu.
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID: 0x9E131672
WSO2 | Oxygenating the Web Service Platform | http://wso2.com
://wso2.org/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID: 0x9E131672
WSO2 | Oxygenating the Web Service Platform | http
and I would like to welcome him for this role.
Here is my +1.
Thanks,
Samisa...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dumindu Pallewela
http
[
https://issues.apache.org/jira/browse/AXIS2C-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela resolved AXIS2C-728.
--
Resolution: Fixed
Fix Version/s: 1.1.1
Current (Nightly
[
https://issues.apache.org/jira/browse/AXIS2C-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela reopened AXIS2C-728:
--
Assignee: Dumindu Pallewela
this bug has not yet been fixed. hence reopening
/ssl_*.*
What I'm interested in knowing is whether it is blocking or non-blocking
or whether it may vary according to the scenario.
That (i.e., the behavior of Axis2/C sockets) I'm uncertain of.
However, it seems that SSL client's function depends much on this fact!
HTH,
Dumindu.
--
Dumindu
Components: core/transport
Affects Versions: 1.1.0
Reporter: Dumindu Pallewela
Assignee: Dumindu Pallewela
Current SSL client implementation validates the server certificate at all
times. We need some means of allowing the user to disable this validation
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID: 0x9E131672
WSO2 | http://wso2.com | Oxygenating the Web Service Platform
signature.asc
Description
) defined in axis2.xml. May
be we need to be able to provide the port numbers as command line
switches too...
Regards,
Dumindu.
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID: 0x9E131672
WSO2 | http://wso2.com | Oxygenating the Web Service Platform
signature.asc
Description: OpenPGP digital
Chintana Wilamuna wrote:
On 10/8/07, Dumindu Pallewela [EMAIL PROTECTED] wrote:
What about the port numbers? I think all the port numbers should be
removed from the axis2.xml in that case... For example we have the
transport receiver port as 6060 (default) defined in axis2.xml. May
be we
at
http://people.apache.org/~kaushalye/release/KEYS
Please test and review.
If the released artifacts are fine, please vote for the Apache
Rampart/C 1.0.0 release.
Here is my +1.
Cheers,
Kaushalye
--
Dumindu Pallewela
http://blog.dumindu.com
GPG ID: 0x9E131672
WSO2 | http://wso2
Samisa Abeysinghe wrote:
Dumindu Pallewela wrote:
Hi Samisa,
I tested the release artifacts for the SSL transport on Gentoo Linux
and they all work fine except for a minor mistake.
In axis2_build.sh of the source distribution, --with-axis2= is
mistakenly written as --with-axis2==, thus
Hi Jamie,
Please try giving a blank SSL_PASSPHRASE instead of just commenting
it out. I will test it too and let you know.
Btw, are you using the latest svn head? We had some changes yesterday.
-Dumindu.
Jamie Lyon wrote:
Hi,
Can anyone suggest what I may be doing wrong when trying to
Hi Jamie,
Please find my comments inline.
I guess the problem lies on the fact that the server you are using
could not verify your client certificate as valid. Check the server
logs and see if such an error occurs. For instant, if you are using
a self signed certificate as the client
/transport
Affects Versions: Current (Nightly)
Reporter: Dumindu Pallewela
Assignee: Dumindu Pallewela
The ssl transport sender does not check if whether the server certificate is
trusted valid. Hence, it allows connections with any server, even when the CA
certificates
+1
-Dumindu.
Sanjaya Ratnaweera wrote:
+1
~sanjaya
Damitha Kumarage wrote:
Hi devs,
Since Savan/C development has continued for some time and seems ripe
enough to be packed into a release I propose we do a Savan/C 0.90
release. I would like to be the release manager.
Currently
+1 for the release.
-Dumindu.
Manjula Peiris wrote:
Hi devs,
It is sometime back we have done the Sandesha2/C 0.90 release. Since
Axis2/C 1.1 release will happen , I propose we do a Sandesha2/C 0.91
release. I would like to be the release manager.
Your suggestions are welcome.
Thanks,
Manjula Peiris wrote:
Hi Dimindu,
On Thu, 2007-08-30 at 19:12 +0530, Dumindu Pallewela wrote:
Http Authentication does work, however, with known performance issues.
I have tested Http Authentication with Apache2 in httpd -k mode and it
is working fine with out any performance issues
Jamie Lyon wrote:
Hi,
See my reply below.
-Original Message-
The C implementation of AXIOM is different form that of Java. Hence,
it is
not easy, if not impossible to implement the clone method. This is
mainly
because of hte linked list model that we have in the C implementation.
Http Authentication does work, however, with known performance issues. Thus,
I think we should not add it as a new feature yet.
-Dumindu.
Manjula Peiris wrote:
Basic Http Authentication support can be added to it.
Other than that the list is ok to me.
Thanks.
-Manjula.
On Thu, 2007-08-30 at
Jamie Lyon wrote:
Yes, I think you're correct. I made the incorrect assumption that
detaching a node detached the node entirely from the original dom tree,
effectively making it independent.
Well in our implementation it does. Once you detach the node, neither
the detached node and it's
Is this really a bug? I don't think that we need to handle this at axiom level.
May be I'm missing something here.
Jamie Lyon (JIRA) wrote:
Detach node does not handle namespaces
--
Key: AXIS2C-675
URL:
Hi Samisa,
Thanks for taking the initiative. I think it's good to automate the styling.
Used the right way, it would make the code easily readable.
I like the indent that you have proposed except for few things that I have
mentioned below.
1. Why are we using 100 as the line length? It is 80
[
https://issues.apache.org/jira/browse/AXIS2C-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela resolved AXIS2C-656.
--
Resolution: Fixed
Fix Version/s: 1.1.0
Basic framework for http authentication
[
https://issues.apache.org/jira/browse/AXIS2C-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518896
]
Dumindu Pallewela commented on AXIS2C-656:
--
Committed the code for HTTP Basic Authentication. Note
[
https://issues.apache.org/jira/browse/AXIS2C-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela resolved AXIS2C-635.
--
Resolution: Fixed
Fix Version/s: Current (Nightly)
The axiom data handler
[
https://issues.apache.org/jira/browse/AXIS2C-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela resolved AXIS2C-653.
--
Resolution: Fixed
Fix Version/s: Current (Nightly)
Fixed.
xop:Include element
[
https://issues.apache.org/jira/browse/AXIS2C-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela reassigned AXIS2C-656:
Assignee: Dumindu Pallewela
HTTP Basic Authentication
[
https://issues.apache.org/jira/browse/AXIS2C-653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517967
]
Dumindu Pallewela commented on AXIS2C-653:
--
Fixed in revision 563170.
xop:Include element should
[
https://issues.apache.org/jira/browse/AXIS2C-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dumindu Pallewela reassigned AXIS2C-635:
Assignee: Dumindu Pallewela
The axiom data handler returns incorrect length
1 - 100 of 168 matches
Mail list logo