[
https://issues.apache.org/jira/browse/AXIS2-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chatra Nakkawita resolved AXIS2-2827.
-
Resolution: Fixed
Yes Sumedha, your absolutely correct. It works perfectly with maven1.x
Can somebody explain the reasons behind the following change...This
change went in svn commit: r547986 done by Deepal...
Thanks,
Thilina
On 6/25/07, David Illsley <[EMAIL PROTECTED]> wrote:
I'd agree that this looks a bit odd and precludes a scenario we were
talking about only last week (settin
[
https://issues.apache.org/jira/browse/AXIS2-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chatra Nakkawita resolved AXIS2-2846.
-
Resolution: Fixed
Fix Version/s: 1.2
Fixed on Axis2 site -1.2
Thanks,
Chatra
> A
[
https://issues.apache.org/jira/browse/AXIS2-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508064
]
Lahiru Sandakith commented on AXIS2-2818:
-
Hi Shiv,
If you have a eclipse project structured like this,
Te
Dear all,
I'm doing some debugging with WebsphereMQ as the axis2 JMS provider and I've
adopted the new dispatcher layout of axis2.xml in the nightly build.
Suddenly I can't seem to get JMS to work.
Specifically the following code in axis2.xml:
results in the following:
[
https://issues.apache.org/jira/browse/AXIS2-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Sandakith updated AXIS2-2765:
Attachment: TestHandler.png
screen shot of the client invocation using the TestHandler POJO
[
https://issues.apache.org/jira/browse/AXIS2-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Sandakith updated AXIS2-2765:
Attachment: TestHandlerClient.java
attaching the client file
> Message Receiver not found
[
https://issues.apache.org/jira/browse/AXIS2-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Sandakith resolved AXIS2-2765.
-
Resolution: Cannot Reproduce
Hi Satish,
I have written a client and successfully invoked
[
https://issues.apache.org/jira/browse/AXIS2-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508056
]
Deepal Jayasinghe commented on AXIS2-1304:
--
Engaging module to AxisMessage is done , but we need to have a w
[
https://issues.apache.org/jira/browse/AXIS2-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas reassigned AXIS2-2859:
---
Assignee: sumedha rubasinghe
> SAAJ - set default fault code and faul string for the
[
https://issues.apache.org/jira/browse/AXIS2-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Sun updated AXIS2-2859:
---
Attachment: AXIS2-2859.patch
Tested in geronimo env.
> SAAJ - set default fault code and faul string for the
SAAJ - set default fault code and faul string for the addFault method
-
Key: AXIS2-2859
URL: https://issues.apache.org/jira/browse/AXIS2-2859
Project: Axis 2.0 (Axis2)
Issue
axis2 plugins missing the transport libraries
--
Key: AXIS2-2858
URL: https://issues.apache.org/jira/browse/AXIS2-2858
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: ide plugins
[
https://issues.apache.org/jira/browse/AXIS2-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Sandakith resolved AXIS2-1486.
-
Resolution: Fixed
After debugging the whole scenarios at last found the cause, because of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Glen Daniels wrote:
> (note new subject line)
>
> Hi Chinthaka:
>
> Eran Chinthaka wrote:
>> Can you remember you raised the same question during the hackathon and I
>> answered it :). Anyway here it is again.
>
> IIRC I asked about why Options were
[
https://issues.apache.org/jira/browse/AXIS2-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dustin Amrhein updated AXIS2-2851:
--
Attachment: patch.txt
> Move RESPONSE_WRITTEN flag from OperationContext to RequestResponseTran
Rich,
So far I only updated the metadata package. The definitions there were
only marked as private. Btw, what do you mean by Java 2 Security
reasons exactly?
Thanks,
Jarek
On 6/25/07, R J Scheuerle Jr <[EMAIL PROTECTED]> wrote:
In some cases the forName and getContextClassLoader() methods w
In some cases the forName and getContextClassLoader() methods were
intentionally are intentionally not private for Java 2 Security reasons.
I have not looked at your changes, but did you take this into
consideration ?
Thanks for the code inspection !
Rich Scheuerle
IBM Web Services
Apache Ax
[
https://issues.apache.org/jira/browse/AXIS2-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507993
]
Dustin Amrhein commented on AXIS2-2851:
---
Dims,
I should have a patch put together pretty soon.
> Move RESPONSE
[
https://issues.apache.org/jira/browse/AXIS2-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett resolved AXIS2-2597.
-
Resolution: Fixed
Commited patch to revision 550594. Thanks, Roy!
> Support WS-A action generat
[
https://issues.apache.org/jira/browse/AXIS2-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett resolved AXIS2-2216.
-
Resolution: Fixed
The changes for this Jira were commited under Jira
https://issues.apache.org/j
[
https://issues.apache.org/jira/browse/AXIS2-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2853:
Fix Version/s: 1.3
Priority: Blocker (was: Major)
> Pluggable Must Understand Han
[
https://issues.apache.org/jira/browse/AXIS2-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2854:
Fix Version/s: 1.3
Priority: Blocker (was: Major)
> MessageContext and Options
>
[
https://issues.apache.org/jira/browse/AXIS2-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2855:
Fix Version/s: 1.3
Priority: Blocker (was: Major)
> Callback Interface changes
>
[
https://issues.apache.org/jira/browse/AXIS2-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2856:
Fix Version/s: 1.3
Priority: Blocker (was: Major)
> Module Config Changes
> -
[
https://issues.apache.org/jira/browse/AXIS2-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2857:
Fix Version/s: 1.3
Priority: Blocker (was: Major)
> Handler interface cleanup
> -
[
https://issues.apache.org/jira/browse/AXIS2-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2845:
Assignee: Deepal Jayasinghe
> Throwing exceptions causes 400 HTTP header appearing when run
[
https://issues.apache.org/jira/browse/AXIS2-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2850:
Assignee: Deepal Jayasinghe
> "In" MessageContext.envelope is overwritten by "Fault"
> Mes
[
https://issues.apache.org/jira/browse/AXIS2-2852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2852:
Assignee: Amila Chinthaka Suriarachchi
> Invalid number of parameters in method toOM() afte
[
https://issues.apache.org/jira/browse/AXIS2-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2848:
Assignee: Deepal Jayasinghe
> Module versioning problem
> -
>
>
[
https://issues.apache.org/jira/browse/AXIS2-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2851:
Assignee: Jeff Barrett
> Move RESPONSE_WRITTEN flag from OperationContext to RequestRespons
[
https://issues.apache.org/jira/browse/AXIS2-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2846:
Assignee: Chatra Nakkawita
> Architecture Guide has wrong title "eApache Axis2 Architecture
[
https://issues.apache.org/jira/browse/AXIS2-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2856:
Assignee: Glen Daniels
> Module Config Changes
> -
>
>
[
https://issues.apache.org/jira/browse/AXIS2-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2854:
Assignee: Glen Daniels
> MessageContext and Options
> --
>
>
[
https://issues.apache.org/jira/browse/AXIS2-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2855:
Assignee: Glen Daniels
> Callback Interface changes
> --
>
>
[
https://issues.apache.org/jira/browse/AXIS2-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2853:
Assignee: Jeff Barrett
> Pluggable Must Understand Handling?
>
[
https://issues.apache.org/jira/browse/AXIS2-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2857:
Assignee: Glen Daniels
> Handler interface cleanup
> -
>
>
Handler interface cleanup
-
Key: AXIS2-2857
URL: https://issues.apache.org/jira/browse/AXIS2-2857
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Reporter: Davanum Srinivas
Discussion here - http://mar
Module Config Changes
-
Key: AXIS2-2856
URL: https://issues.apache.org/jira/browse/AXIS2-2856
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Reporter: Davanum Srinivas
Discussion here - http://marc.info/?
Callback Interface changes
--
Key: AXIS2-2855
URL: https://issues.apache.org/jira/browse/AXIS2-2855
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Reporter: Davanum Srinivas
Discussion here: http://ma
MessageContext and Options
--
Key: AXIS2-2854
URL: https://issues.apache.org/jira/browse/AXIS2-2854
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Reporter: Davanum Srinivas
Should we de-link Options
Pluggable Must Understand Handling?
---
Key: AXIS2-2853
URL: https://issues.apache.org/jira/browse/AXIS2-2853
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Reporter: Davanum Srinivas
Discussi
David, can you explain what RM and ESB scenarios require this? I don't see
Sandesha or Synapse needing it. I don't know enough about JAX-WS to have
intelligent input.
Sanjiva.
David Illsley wrote:
Jeff,
I still think some kind of pluggability would be a good thing, as this
has come up for a n
Folks,
Please review the changes i made today. FYI, here's a quick html where
you can view all the commits (a week's worth).
http://ws.zones.apache.org/~dims/axis2/
thanks,
dims
On 6/25/07, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote:
+1 for this change as long as we have the backwards comp
Jarek,
+1 Thanks for cleaning that up...
-Nick
"Jarek Gawor"
<[EMAIL PROTECTED]
>
Jeff,
I still think some kind of pluggability would be a good thing, as this
has come up for a number of scenarios (JAX-WS, building an ESB,
WS-RM). What you're describing is really a hack, and it doesn't
actually stop the mU code running in the engine. How about a form of
plugability at the level
[
https://issues.apache.org/jira/browse/AXIS2-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raghu Upadhyayula updated AXIS2-2352:
-
Attachment: TestWS.zip
Hi,
When I deploy my webservices on my localhost (de
[
https://issues.apache.org/jira/browse/AXIS2-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507932
]
Raghu Upadhyayula commented on AXIS2-2352:
--
Hi,
When I deploy my webservices on my localhost (d
[
https://issues.apache.org/jira/browse/AXIS2-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raghu Upadhyayula updated AXIS2-2352:
-
Comment: was deleted
> XMLBeans client getting org.apache.axis2.AxisFault: First Element
Folks,
There is a bunch of replicated code in jaxws module. Specifically,
functions such as forName() [11 times] and getContextClassLoader() [9
times]. Does anybody mind if I move these functions into a new
ClassLoaderUtils class (or something like that) and make rest of the
code use that?
Jare
[
https://issues.apache.org/jira/browse/AXIS-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507927
]
Wayne Johnson commented on AXIS-1708:
-
I spent all morning trying to track down the fact that port 5001 was alread
Hi Dims and Sanjiva,
I've read the previous discussion of mustUnderstand processing which Dims
sent me via a chat http://marc.info/?t=11694997345&r=1&w=2 (Thanks,
Dims)
Given that discussion, I believe the suggested approach here is to add a
handler in the distpatch phase that will mark th
A few comments:
Davanum Srinivas wrote:
How about we make allow MU handling to be pluggable? with an entry in
axis2.xml, just like the TargetResolver
I don't think we should go too far in a "pluggable MU handling"
direction. I do think we need a single API for allowing external
components (
+1 for this change as long as we have the backwards compat capability.
Sanjiva.
Nicholas L Gallardo wrote:
Chintaka,
+1
That's exactly what I was thinking as well...
-Nick
Inactive hide details for Eran Chinthaka <[EMAIL PROTECTED]>Eran
Chinthaka <[EMAIL PROTECTED]>
Team,
We absolutely need to deal with these threads this week/ASAP. Please
chime in on the respective threads if you haven't already.
* Dispatchers package name change [1]
* Pluggable Must Understand Handling? [2]
* MessageContext and Options [3]
* Callback Interface changes [4]
* ModuleConfig c
[
https://issues.apache.org/jira/browse/AXIS2-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jorge Fernández updated AXIS2-2845:
---
Attachment: exception.txt
These are the messages I see with TCPMon
> Throwing exceptions cau
So, IMO, lets move them, lets get the API/SPI right if we can (while
maintaining backwards compatibility).
+1 to this, and to the "move, extend, and deprecate" pattern that's
being discussed.
--Glen
-
To unsubscribe, e-mai
Hehe, that's what i am doing right now :)
-- dims
On 6/25/07, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I can remember a trick that we have used for UUID generator. How about
the following.
package o.a.a.engine;
/**
* This class is moved to o.a
Chintaka,
+1
That's exactly what I was thinking as well...
-Nick
Eran Chinthaka
<[EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/AXIS2-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Gallardo closed AXIS2-2539.
Resolution: Fixed
> Add support for the Endpoint.publish() API
> --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I can remember a trick that we have used for UUID generator. How about
the following.
package o.a.a.engine;
/**
* This class is moved to o.a.a.dispatchers.FooDispatcher
* @deprecated
*/
public class FooDispatcher extends o.a.a.dispatchers.FooDi
[
https://issues.apache.org/jira/browse/AXIS-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507901
]
Tom Jordahl commented on AXIS-2664:
---
I think that for SOAP-encoded XML, you can always set an element to nil.
See Se
[
https://issues.apache.org/jira/browse/AXIS-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507898
]
Tom Jordahl commented on AXIS-2668:
---
Hi Prasanna,
I am afraid you get what you pay for in Open Source Land and if y
[
https://issues.apache.org/jira/browse/AXIS-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Jordahl resolved AXIS-2442.
---
Resolution: Fixed
Fix Version/s: current (nightly)
I believe I fixed this in the current source
+1 That sounds like the best solution here. I agree with David's comment
that user's shouldn't be accessing anything inside of the .engine package
either. If it's part of an official API, move it to other package.
Dims, what about adding something that issues a deprecation warning when
the
So, if i come up with a technique for backward compat w/o touching the
old axis2.xml files, that should be ok right?
thanks,
dims
On 6/25/07, Afkham Azeez <[EMAIL PROTECTED]> wrote:
I am not in favor of this change. This is going to annoy a large number of
users who may want to migrate from Axi
Invalid number of parameters in method toOM() after generating code with jaxbri
---
Key: AXIS2-2852
URL: https://issues.apache.org/jira/browse/AXIS2-2852
Project: Axis 2.0 (Ax
(note new subject line)
Hi Chinthaka:
Eran Chinthaka wrote:
Can you remember you raised the same question during the hackathon and I
answered it :). Anyway here it is again.
IIRC I asked about why Options were getting *copied* from place to place
during MEPs, not why we're using the Options
Please log a bug and upload your wsdl/schemas.
thanks,
dims
On 6/25/07, Naecker, Thomas <[EMAIL PROTECTED]> wrote:
Hi all,
for my degree disertation i have to analyse AXIS2 and the different ways to
realize a Web Service.
After i created Service Implementations with ADB and XMLBeans, i trie
Ruwan,
Can you please make appropriate changes in axis2 as well?
thanks,
dims
On 6/25/07, Ruwan Linton <[EMAIL PROTECTED]> wrote:
On 6/25/07, Oleg Kalnichevski <[EMAIL PROTECTED]> wrote:
> On Mon, 2007-06-25 at 11:44 +0530, Ruwan Linton wrote:
> > Hi Oleg,
> >
> > I am done with the performa
[
https://issues.apache.org/jira/browse/AXIS2-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507872
]
Davanum Srinivas commented on AXIS2-2851:
-
Dustin,
Is there a patch?
thanks,
dims
> Move RESPONSE_WRITTEN
Move RESPONSE_WRITTEN flag from OperationContext to RequestResponseTransport
instance
-
Key: AXIS2-2851
URL: https://issues.apache.org/jira/browse/AXIS2-2851
Project:
[
https://issues.apache.org/jira/browse/AXIS2-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507862
]
Dustin Amrhein edited comment on AXIS2-2370 at 6/25/07 5:29 AM:
K.R.,
If this is a de
[
https://issues.apache.org/jira/browse/AXIS2-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507862
]
Dustin Amrhein commented on AXIS2-2370:
---
K.R.,
If this is a deploy time issue, I would be curious as to the cla
"In" MessageContext.envelope is overwritten by "Fault" MessageContext.envelope
on Exception
---
Key: AXIS2-2850
URL: https://issues.apache.org/jira/browse/AXIS2-2850
[
https://issues.apache.org/jira/browse/AXIS2-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shivantha Huruggamuwa updated AXIS2-2849:
-
Attachment: Axis_Idea_plugin_07_25.txt
current Axis2-Idea plugin java2wsdl and ws
Improve Axis idea plugin wizard as resizable wizard
---
Key: AXIS2-2849
URL: https://issues.apache.org/jira/browse/AXIS2-2849
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Compone
Thanks Dims for pointing that out. I will look in to this and see how far I
can proceed.
/Sanjaya
On Monday 25 June 2007, Davanum Srinivas (JIRA) wrote:
> [
> https://issues.apache.org/jira/browse/AXIS2-2689?page=com.atlassian.jira.pl
>ugin.system.issuetabpanels:comment-tabpanel#action_12507
Hi,
How to configure in code java a proxy http for only his webservice?
Thanks for your response!
Ruben BAYEMI NLOGA
[
https://issues.apache.org/jira/browse/AXIS2-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507804
]
Usha Nandhini K. R. commented on AXIS2-2370:
I am facing the below exception while trying to deploy th
Hi all,
for my degree disertation i have to analyse AXIS2 and the different ways to
realize a Web Service.
After i created Service Implementations with ADB and XMLBeans, i tried to use
JAXBRI for the Binding. The Code was created, but there is an error occured in
the Message Receiver. The me
I was teaching an Axis2 course last week and I was explaining the way
that we keep the multiple configurations separate, yet composable: in
other words the way that on the server side, the combination of
axis2.xml, module.xml(s) and services.xml group together to create the
correct configuration.
I'd agree that this looks a bit odd and precludes a scenario we were
talking about only last week (setting an anon EPR w/refparams).
Can someone explain the intention here?
Thanks,
David
On 23/06/07, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:
Hi,
> fixing the issue.
hmm... Fixing which issue
Aaaargh.
Sorry, this is all my fault. I was trying to do the *right thing* and
have them in .engine but I keep on getting distracted. I think in
.dispatchers is the right place - I've always said I don't think any
user should have to look in the .engine package.
If we do move the dispatchers, my
84 matches
Mail list logo
