Hi,
Uthaiyashankar [EMAIL PROTECTED] writes:
.NET 2.0 client expects urn:uuid prefix in the message id. (i.e
wsa:MessageIDurn:uuid:6b85e6c2-4645-1dd1-2636-000c292fec05/wsa:MessageID
). To be able to interoperate with .NET 2.0 it is better to add
urn:uuid prefix to message id. WDYT?
+1 ,
Dinesh Premalal wrote:
Hi,
Uthaiyashankar [EMAIL PROTECTED] writes:
.NET 2.0 client expects urn:uuid prefix in the message id. (i.e
wsa:MessageIDurn:uuid:6b85e6c2-4645-1dd1-2636-000c292fec05/wsa:MessageID
). To be able to interoperate with .NET 2.0 it is better to add
urn:uuid prefix to
Hi All,
I have re-packed and uploaded Apache Axis2/C 1.5.0 RC2 here [1]. Please test
and send your feedback.
[1] http://people.apache.org/~supun/axis2/release_1_5/rc2/
Thanks,
Supun..
[
https://issues.apache.org/jira/browse/AXIS2C-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varuna Parinda Jayasiri updated AXIS2C-595:
---
Attachment: xpath.zip
XPath support in AXIOM
--
HTTPLocationBased Dispatcher should not pick an endpoint when the endpoint is
not specified in the URL
--
Key: AXIS2-3897
URL:
By looking at the number of JIRAs being resolved/cleaned, I assume there
was/is a hackathon some where in this small world ;)
The command line wsdl2java.sh help states incomplete parameter syntax.
--
Key: AXIS2-3898
URL: https://issues.apache.org/jira/browse/AXIS2-3898
Project: Axis 2.0 (Axis2)
[
https://issues.apache.org/jira/browse/AXIS2-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
saminda wijeratne updated AXIS2-3898:
-
Attachment: AXIS2-3898_missing_syntax.txt
i've updated the systax to my knowledge.
The
[
https://issues.apache.org/jira/browse/AXIS2-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe reassigned AXIS2-3892:
Assignee: Amila Chinthaka Suriarachchi
WebServiceStub crashes with
[
https://issues.apache.org/jira/browse/AXIS2-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe reassigned AXIS2-3891:
Assignee: Amila Chinthaka Suriarachchi
Unwrapping failure at XmlSchemaChoice
[
https://issues.apache.org/jira/browse/AXIS2-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12610948#action_12610948
]
Deepal Jayasinghe commented on AXIS2-3894:
--
Could you please test with Axis2 1.4 ,
[
https://issues.apache.org/jira/browse/AXIS2-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe reassigned AXIS2-3896:
Assignee: Amila Chinthaka Suriarachchi
Bug with naming of the schema files.
[
https://issues.apache.org/jira/browse/AXIS2-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe reassigned AXIS2-3114:
Assignee: Deepal Jayasinghe
Control what wsdl bindings returned via services.xml
I would like to volunteer to be the release manager for Axis2 1.4.1.
I think we can fix the critical issues in the 1.4 branch (or a 1.4.1 branch
) and do the 1.4.1 release. I don't think doing 1.4.1 from the trunk is the
appropriate way as trunk is now java 1.5 and has lot of major changes after
[
https://issues.apache.org/jira/browse/AXIS2-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-3898.
--
Resolution: Fixed
Applied. Thanks for the the patch
The command line wsdl2java.sh
[
https://issues.apache.org/jira/browse/AXIS2-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12611042#action_12611042
]
Deepal Jayasinghe commented on AXIS2-3108:
--
Could you please grant the patch
[
https://issues.apache.org/jira/browse/AXIS2-3337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-3337.
--
Resolution: Fixed
As I can see , some part of this patch is already in the trunk, and
[
https://issues.apache.org/jira/browse/AXIS2-3321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-3321.
--
Resolution: Cannot Reproduce
AXIOM based Web_service, getting an unexpected exception
[
https://issues.apache.org/jira/browse/AXIS2-3320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe reassigned AXIS2-3320:
Assignee: Amila Chinthaka Suriarachchi
Getting AxisFault for Server
[
https://issues.apache.org/jira/browse/AXIS2-3319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-3319.
--
Resolution: Fixed
engageModule for ContextMessage has wrong parameters
[
https://issues.apache.org/jira/browse/AXIS2-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12611065#action_12611065
]
Deepal Jayasinghe commented on AXIS2-3316:
--
If you can work on this , then that
[
https://issues.apache.org/jira/browse/AXIS2-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-3306.
--
Resolution: Fixed
Documentation/samples are not up-to-date with Callback API changes
[
https://issues.apache.org/jira/browse/AXIS2-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-3297.
--
Resolution: Cannot Reproduce
Service classloading issues when undeploying and
[
https://issues.apache.org/jira/browse/AXIS2-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-3293.
--
Resolution: Fixed
I tested with current SVN and it seems to me that TCP works fine, so
[
https://issues.apache.org/jira/browse/AXIS2-3207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-3207.
--
Resolution: Fixed
I know , this is an issue which depend on the parser you use. Or
[
https://issues.apache.org/jira/browse/AXIS2-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-3471.
--
Resolution: Fixed
Now this issue is fixed
When deploying a POJO service my
[
https://issues.apache.org/jira/browse/AXIS2-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-3467.
--
Resolution: Fixed
I just checked with the trunk and it generated the following WSDL ,
[
https://issues.apache.org/jira/browse/AXIS2-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe reassigned AXIS2-3393:
Assignee: Deepal Jayasinghe
NullPointerException in BeanUtil.getPullParser()
[
https://issues.apache.org/jira/browse/AXIS2-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-3387.
--
Resolution: Fixed
Unfortunately thats how I have implemented the session support for
[
https://issues.apache.org/jira/browse/AXIS2-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12611127#action_12611127
]
Thomas Leonard commented on AXIS2-3108:
---
I can't see how to do that in JIRA. You're
Eclipse PlugIn Codegen URISyntaxException with whitespaces in Projectname
-
Key: AXIS2-3899
URL: https://issues.apache.org/jira/browse/AXIS2-3899
Project: Axis 2.0 (Axis2)
Nandana,
+1 from me for you to be the Release Manager for 1.4.1
IMHO, we should use 1.4 branch. The *ONLY* change should be the
security change. Nothing more.
thanks,
dims
On Mon, Jul 7, 2008 at 6:50 AM, Nandana Mihindukulasooriya
[EMAIL PROTECTED] wrote:
I would like to volunteer to be the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
AFAIK, no :) It's just Deepal @ Work!
- -- dims
Eran Chinthaka wrote:
| By looking at the number of JIRAs being resolved/cleaned, I assume there
| was/is a hackathon some where in this small world ;)
|
-BEGIN PGP SIGNATURE-
Version: GnuPG
[
https://issues.apache.org/jira/browse/AXIS2-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels reopened AXIS2-618:
This certainly hasn't been fixed, and if it's a cool feature we want at some
point, why are we
[
https://issues.apache.org/jira/browse/AXIS2-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels updated AXIS2-618:
---
Priority: Minor (was: Critical)
Assignee: (was: Sanka Samaranayake)
Reduce priority, leave
[
https://issues.apache.org/jira/browse/AXIS2-897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels reopened AXIS2-897:
Why wouldn't we fix this? How else are we to access WSDLs that are
password-protected?
WSDL2Java
On Mon, Jul 7, 2008 at 6:03 PM, Davanum Srinivas [EMAIL PROTECTED] wrote:
Nandana,
+1 from me for you to be the Release Manager for 1.4.1
+ 1 from me.
IMHO, we should use 1.4 branch. The *ONLY* change should be the
security change. Nothing more.
I think we need to fix any possible
[
https://issues.apache.org/jira/browse/AXIS2-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12611149#action_12611149
]
Detelin Yordanov commented on AXIS2-2688:
-
Hi,
We also need some means to control
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Exactly what i was afraid of :( Sigh! this is a *very* slippery slope.
- -- dims
Amila Suriarachchi wrote:
| On Mon, Jul 7, 2008 at 6:03 PM, Davanum Srinivas [EMAIL PROTECTED] wrote:
|
| Nandana,
|
| +1 from me for you to be the Release Manager for
[
https://issues.apache.org/jira/browse/AXIS2-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12611157#action_12611157
]
Thomas Poetter commented on AXIS2-3892:
---
As an attempt of a workaround for the
Deepal, what are you so worried about, exactly? That it will take
forever to get the release out?
IMHO, a point release is for fixing critical issues, and should not
necessarily be limited to one particular issue. I think we should run
this basically just like a regular release but with a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
s/Deepal/Dims/ ? :)
Glen Daniels wrote:
|
| Deepal, what are you so worried about, exactly? That it will take
| forever to get the release out?
|
| IMHO, a point release is for fixing critical issues, and should not
| necessarily be limited to one
Davanum Srinivas wrote:
s/Deepal/Dims/ ? :)
Oh for crying out... sorry Dims!!! I was just reading a bunch of the
JIRA edits from Deepal (and haven't had coffee yet today). *blush*
--G
-
To unsubscribe, e-mail: [EMAIL
Two more things.
1) Obviously +1 to Nandana as RM, which I forgot to say explicitly. :)
2) To be crystal clear, my suggestion is to time-bound the release and
ONLY fix what can be finished in the allotted time, which should prevent
the slippery slope problem. If people want we can also
[
https://issues.apache.org/jira/browse/AXIS2-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels reopened AXIS2-1755:
-
This isn't fixed
Provide a unload or remove link on the Axis2 admin page
Hi Glen,
- Let's aim to get 1.4.1 out the door at the end of next week, i.e. July
18th (is that enough time, Nandana?).
I think we have to check Sanka's input on this. He will be fixing the major
issue in policy.
- As always it's good to go through at least one RC so people can kick the
[
https://issues.apache.org/jira/browse/AXIS2-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12611187#action_12611187
]
Glen Daniels commented on AXIS2-1014:
-
No point of keeping these issues open forever?
[
https://issues.apache.org/jira/browse/AXIS2-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels reopened AXIS2-2096:
-
Good question - so we shouldn't mark it fixed until it gets answered! :)
The
[
https://issues.apache.org/jira/browse/AXIS2-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels reopened AXIS2-1810:
-
This isn't fixed.
Cannot deploy multiple versions of the same service
[
https://issues.apache.org/jira/browse/AXIS2-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels resolved AXIS2-2358.
-
Resolution: Invalid
Marked as invalid for now since the patch doesn't match the source anymore.
[
https://issues.apache.org/jira/browse/AXIS2-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels reopened AXIS2-2358:
-
If the patch is outdated, it's not fixed.
Code level Comments
---
In fairness to those (like myself) who set these messages, there is an
expectation that email is 'near-realtime' these days, and if someone sends a
message and is expecting a response, then it is polite (in the US at least) to
set those expectations much lower when you are on vacation.
We can
[
https://issues.apache.org/jira/browse/AXIS2-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12611229#action_12611229
]
Adam Killick commented on AXIS2-3894:
-
I tested Axis2 1.4, and we still receive the
Out of Office for a day or 2 I can understand
but when the emperor goes on vacation for 1 to 2 weekshe really does'nt have to
flood every inbox on the planet with I'm on vacation while everyone else is
working
Ok..Break's over..back to workMartin Gainty
[
https://issues.apache.org/jira/browse/AXIS2-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels reopened AXIS2-3387:
-
a) this clearly isn't fixed. b) it would actually be nice to have destroy()
work the same way in
55 matches
Mail list logo
