[jira] Commented: (AXIS2-3712) Handling of exceptions raised by handlers in one-way invocations

[ https://issues.apache.org/jira/browse/AXIS2-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587845#action_12587845 ] Jarek Gawor commented on AXIS2-3712: To clarify, the patch suppresses (only logs) the e

Re: [Axis2] Common VOTE for XmlSchema/Axiom/Neethi

Hi +1 for all On Wed, Apr 9, 2008 at 12:18 PM, Lawrence Mandel <[EMAIL PROTECTED]> wrote: > Sounds good Dims. I'll pick up the release candidates and test in Woden. > > Lawrence > > > > > > Davanum Srinivas <[EMAIL PROTECTED]> > 04/09/2008 11:18 AM > Please respond to > axis-dev@ws.apache.org > >

Re: [Axis2] arbitrary prefix for anon operations?

Have we explored storing a specific Parameter on the AxisOperation that told them an operation was not a user-defined operation? I know there is very little chance of a collision with a user-defined operation, but there is still a small chance. Is storing a parameter on the AxisOperation instead

[jira] Issue Comment Edited: (AXIS2-3730) sandesha needs to be able to recognize jaxws-originated anon operations

[ https://issues.apache.org/jira/browse/AXIS2-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587800#action_12587800 ] dustin edited comment on AXIS2-3730 at 4/10/08 3:11 PM: It

[Axis2] arbitrary prefix for anon operations?

Hi, The sandesha team has requested that a custom prefix be included in the QNames of the anonymous operations (anonOutInOp, etc) to differentiate axis2-originated anon operations from customer-defined operations. Is it simply a matter of adding a prefix to the QName definitions in kernel cod

[jira] Commented: (AXIS2-3730) sandesha needs to be able to recognize jaxws-originated anon operations

[ https://issues.apache.org/jira/browse/AXIS2-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587800#action_12587800 ] Dustin Amrhein commented on AXIS2-3730: --- It seems like it would be extremely unlikely

[jira] Updated: (AXIS2-3730) sandesha needs to be able to recognize jaxws-originated anon operations

[ https://issues.apache.org/jira/browse/AXIS2-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Rheinheimer updated AXIS2-3730: Attachment: patch_candidate01.txt > sandesha needs to be able to recognize jaxws-originated

[jira] Created: (AXIS2-3730) sandesha needs to be able to recognize jaxws-originated anon operations

sandesha needs to be able to recognize jaxws-originated anon operations --- Key: AXIS2-3730 URL: https://issues.apache.org/jira/browse/AXIS2-3730 Project: Axis 2.0 (Axis2) I

[jira] Updated: (AXIS2-3726) All outbound handlers are invoked when an inbound handler throws exception or returns false

[ https://issues.apache.org/jira/browse/AXIS2-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Rheinheimer updated AXIS2-3726: Attachment: patch.txt Fixed in 646963. Thanks Jarek for the fix! I've included HUGE chang

[jira] Assigned: (AXIS2-3726) All outbound handlers are invoked when an inbound handler throws exception or returns false

[ https://issues.apache.org/jira/browse/AXIS2-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Rheinheimer reassigned AXIS2-3726: --- Assignee: Mike Rheinheimer > All outbound handlers are invoked when an inbound handle

[jira] Resolved: (AXIS2-3726) All outbound handlers are invoked when an inbound handler throws exception or returns false

[ https://issues.apache.org/jira/browse/AXIS2-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Rheinheimer resolved AXIS2-3726. - Resolution: Fixed > All outbound handlers are invoked when an inbound handler throws exce

[jira] Updated: (AXIS-2735) xml:id is not created in the client stub objects

[ https://issues.apache.org/jira/browse/AXIS-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McCullough updated AXIS-2735: -- Fix Version/s: (was: 1.4) > xml:id is not created in the client stub objects > -

[jira] Created: (AXIS-2735) xml:id is not created in the client stub objects

xml:id is not created in the client stub objects Key: AXIS-2735 URL: https://issues.apache.org/jira/browse/AXIS-2735 Project: Axis Issue Type: Bug Components: WSDL processing Aff

RE: Axis Error while writing to the OutputStream in MTOM

We found a fix for this issue. The problem was some how on windows when use tomcat it works fine but when we use Linux box in the client side you need to set options.setProperty(HTTPConstants.CHUNKED,false); By doing this we were able to send documents of any size else after 3 kb it fails .Hope t

[jira] Commented: (AXIS2-3712) Handling of exceptions raised by handlers in one-way invocations

[ https://issues.apache.org/jira/browse/AXIS2-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587773#action_12587773 ] Dustin Amrhein commented on AXIS2-3712: --- Jarek, Does this mean registered InvocationL

[jira] Commented: (AXIS2-3712) Handling of exceptions raised by handlers in one-way invocations

[ https://issues.apache.org/jira/browse/AXIS2-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587764#action_12587764 ] Davanum Srinivas commented on AXIS2-3712: - Jarek, +1 from me. -- dims > Handling

[jira] Updated: (AXIS2-3727) CLONE -Classpath/Classloader issue with packaging

[ https://issues.apache.org/jira/browse/AXIS2-3727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mangesh updated AXIS2-3727: --- Attachment: (was: NISalesService.aar) > CLONE -Classpath/Classloader issue with packaging > -

[jira] Updated: (AXIS2-3712) Handling of exceptions raised by handlers in one-way invocations

[ https://issues.apache.org/jira/browse/AXIS2-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor updated AXIS2-3712: --- Attachment: AXIS2-3712.patch Proposed patch. > Handling of exceptions raised by handlers in one-way

[jira] Updated: (AXIS2-3727) CLONE -Classpath/Classloader issue with packaging

[ https://issues.apache.org/jira/browse/AXIS2-3727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mangesh updated AXIS2-3727: --- Description: I have classpath issue when using axis2 top-down approch (xmlbean binding) with ibatis. Apprcei

[jira] Closed: (AXIS2-3727) CLONE -Classpath/Classloader issue with packaging

[ https://issues.apache.org/jira/browse/AXIS2-3727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mangesh closed AXIS2-3727. -- Resolution: Fixed Using composite resolved this > CLONE -Classpath/Classloader issue with packaging >

[jira] Resolved: (AXIS2-3729) Log.debug statement causes NullPointerException

[ https://issues.apache.org/jira/browse/AXIS2-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3729. - Resolution: Fixed already fixed. thanks! -- dims > Log.debug statement causes NullPoint

[jira] Created: (AXIS2-3729) Log.debug statement causes NullPointerException

Log.debug statement causes NullPointerException --- Key: AXIS2-3729 URL: https://issues.apache.org/jira/browse/AXIS2-3729 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel

Re: [VOTE] XmlSchema 1.4.1 / Axiom 1.2.6 / Neethi 2.0.3 Releases for Axis2 1.4

+1 to ship all three. Thanks, Jeff IBM Software Group - WebSphere Web Services Development Phone: 512-838-4587 or Tie Line 678-4587 Internet e-mail and Sametime ID: [EMAIL PROTECTED] Davanum Srinivas <[EMAIL PROTECTED]> 04/09/2008 11:47 PM Please respond to axis-dev@ws.apache.org To Axis de

[jira] Created: (AXIS2-3728) Context class loader not restored correctly

Context class loader not restored correctly --- Key: AXIS2-3728 URL: https://issues.apache.org/jira/browse/AXIS2-3728 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Jarek Gawor

[jira] Commented: (AXIS2-3726) All outbound handlers are invoked when an inbound handler throws exception or returns false

[ https://issues.apache.org/jira/browse/AXIS2-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587733#action_12587733 ] Davanum Srinivas commented on AXIS2-3726: - good catch jarek! > All outbound handle

Re: [VOTE] XmlSchema 1.4.1 / Axiom 1.2.6 / Neethi 2.0.3 Releases for Axis2 1.4

+1 Rich Scheuerle IBM Web Services Apache Axis2 ([EMAIL PROTECTED]) 512-838-5115 (IBM TL 678-5115) "Chamikara Jayalath" <[EMAIL PROTECTED]> wrote on 04/10/2008 11:01:55 AM: > +1 > > Chamikara > > > On Thu, Apr 10, 2008 at 11:12 AM, David Illsley <[EMAIL PROTECTED] > > wrote:> > +1 > Tested wit

[jira] Commented: (AXIS2-3726) All outbound handlers are invoked when an inbound handler throws exception or returns false

[ https://issues.apache.org/jira/browse/AXIS2-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587719#action_12587719 ] Jarek Gawor commented on AXIS2-3726: Just to explain a bit. Say we have three handlers

[jira] Updated: (AXIS2-3727) CLONE -Classpath/Classloader issue with packaging

[ https://issues.apache.org/jira/browse/AXIS2-3727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mangesh updated AXIS2-3727: --- Attachment: NISalesService.aar > CLONE -Classpath/Classloader issue with packaging >

[jira] Updated: (AXIS2-3727) CLONE -Classpath/Classloader issue with packaging

[ https://issues.apache.org/jira/browse/AXIS2-3727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mangesh updated AXIS2-3727: --- Description: I have classpath issue when using axis2 top-down approch (xmlbean binding) with ibatis. Apprcei

[jira] Created: (AXIS2-3727) CLONE -Classpath/Classloader issue with packaging

CLONE -Classpath/Classloader issue with packaging - Key: AXIS2-3727 URL: https://issues.apache.org/jira/browse/AXIS2-3727 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: deploym

Re: [AXIS2 1.1.1] OutOfMemoryError: Java heap space when engaging addressing on Stub

hello, if someone is interesting you can find a memory dump after 2400 call. Dump was done with yourkit 7.1 build 3026 http://82.232.86.179/addressing_2008_04_10.snapshot.tgz (6,8 Mo) fabrice Samisa Abeysinghe wrote: Fabrice Airault wrote: hello, I have a bug with my client (stub) when i

[jira] Commented: (AXIS2-3726) All outbound handlers are invoked when an inbound handler throws exception or returns false

[ https://issues.apache.org/jira/browse/AXIS2-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587690#action_12587690 ] Mike Rheinheimer commented on AXIS2-3726: - I don't see anything wrong with your pat

Re: [Axis2] Common VOTE for XmlSchema/Axiom/Neethi

+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

Re: [VOTE] XmlSchema 1.4.1 / Axiom 1.2.6 / Neethi 2.0.3 Releases for Axis2 1.4

+1 Chamikara On Thu, Apr 10, 2008 at 11:12 AM, David Illsley <[EMAIL PROTECTED]> wrote: > +1 > Tested with the Sandesha2 1.4 branch. > David > > On Thu, Apr 10, 2008 at 2:38 PM, Davanum Srinivas <[EMAIL PROTECTED]> > wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > Thanks

[jira] Commented: (AXIS2-3726) All outbound handlers are invoked when an inbound handler throws exception or returns false

[ https://issues.apache.org/jira/browse/AXIS2-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587673#action_12587673 ] Davanum Srinivas commented on AXIS2-3726: - Looks good Jarek. thanks. -- dims > Al

Re: [VOTE] XmlSchema 1.4.1 / Axiom 1.2.6 / Neethi 2.0.3 Releases for Axis2 1.4

+1 Tested with the Sandesha2 1.4 branch. David On Thu, Apr 10, 2008 at 2:38 PM, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Thanks Dan!!! Fixed. There is a take1 folder under > http://people.apache.org/~dims/axis2-1.4-commons/ for the old bit

[jira] Updated: (AXIS2-3726) All outbound handlers are invoked when an inbound handler throws exception or returns false

[ https://issues.apache.org/jira/browse/AXIS2-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor updated AXIS2-3726: --- Attachment: AXIS2-3726.patch Proposed patch for this issue. > All outbound handlers are invoked whe

[jira] Created: (AXIS2-3726) All outbound handlers are invoked when an inbound handler throws exception or returns false

All outbound handlers are invoked when an inbound handler throws exception or returns false --- Key: AXIS2-3726 URL: https://issues.apache.org/jira/browse/AXIS2-3726

External SAML Authority and Rampart

Hello All, At first, I am completely new in the Web service area. I have few questions about the SAML in the RAMPART. So I have a working simple prototype which using directly the integrated in Rampart SAML authority (STS). But I want to use external one. Is it possible and if "yes' - how. Are th

Re: [Axis2] Common VOTE for XmlSchema/Axiom/Neethi

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 their release. Then we cut Axis2 1.4 FINAL. Sounds like a plan? +1, sounds like a plan. I'll grab th

Re: [VOTE] XmlSchema 1.4.1 / Axiom 1.2.6 / Neethi 2.0.3 Releases for Axis2 1.4

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks Dan!!! Fixed. There is a take1 folder under http://people.apache.org/~dims/axis2-1.4-commons/ for the old bits. The new binaries are now at http://people.apache.org/~dims/axis2-1.4-commons/ NOTE: the LICENSE.txt and NOTICE.txt are under the

[jira] Commented: (AXIS2-3141) Can't use SSL with scope="transportsession"

[ https://issues.apache.org/jira/browse/AXIS2-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587634#action_12587634 ] Steve Glover commented on AXIS2-3141: - I'm also seeing this issue in Axis2 v1.3 when us

Re: [AXIS2 1.1.1] OutOfMemoryError: Java heap space when engaging addressing on Stub

Hello, (server 1.1.1) - In 1.3 wsdl2java.sh never finish on my wsdl. If i kill program, i can compile generate code with 'ant' and I have exactly the same problem. - If I do a test with service "Version", i have no problem (on axis2 1.3 and axis2 1.1.1) java : while(true){System.out.pri

Re: [VOTE] XmlSchema 1.4.1 / Axiom 1.2.6 / Neethi 2.0.3 Releases for Axis2 1.4

+1 for all -Bill On Thu, 2008-04-10 at 00:47 -0400, Davanum Srinivas wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Folks, > > Here are the src/bin dist artifacts, the maven2 repo and a revisions.txt with > the svn information: > > http://people.apache.org/~dims/axis2-1.4-common

[jira] Created: (AXIS2-3725) TCP connections in CLOSE_WAIT state after axis calls resulting in an exception

TCP connections in CLOSE_WAIT state after axis calls resulting in an exception -- Key: AXIS2-3725 URL: https://issues.apache.org/jira/browse/AXIS2-3725 Project: Axis 2.0 (Axis

Re: [AXIS2 1.1.1] OutOfMemoryError: Java heap space when engaging addressing on Stub

Fabrice Airault wrote: hello, I have a bug with my client (stub) when i use stub._getServiceClient().engageModule(new QName("addressing")); After 2650 request i have "Exception in thread "main" java.lang.OutOfMemoryError: Java heap space" If i don't use engageModule(new QName("addressing"))

[jira] Commented: (AXIS2-3724) WSDL complex type elements do not comply to JAXB Java bean

[ https://issues.apache.org/jira/browse/AXIS2-3724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587575#action_12587575 ] Davanum Srinivas commented on AXIS2-3724: - See jaxws-addressbook sample specificall

[jira] Commented: (AXIS2-3724) WSDL complex type elements do not comply to JAXB Java bean

[ https://issues.apache.org/jira/browse/AXIS2-3724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587573#action_12587573 ] Glen Verran commented on AXIS2-3724: dims, How can this be achieved? FYI, I used th

[jira] Commented: (AXIS2-3724) WSDL complex type elements do not comply to JAXB Java bean

[ https://issues.apache.org/jira/browse/AXIS2-3724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587569#action_12587569 ] Davanum Srinivas commented on AXIS2-3724: - You really need to use the JAXWS 2.1 sup

[jira] Created: (AXIS2-3724) WSDL complex type elements do not comply to JAXB Java bean

WSDL complex type elements do not comply to JAXB Java bean -- Key: AXIS2-3724 URL: https://issues.apache.org/jira/browse/AXIS2-3724 Project: Axis 2.0 (Axis2) Issue Type: Bug C

[jira] Created: (AXIS2-3723) AXIS2 is not aware of "is" methods when generating soap messages from JAXB java beans

AXIS2 is not aware of "is" methods when generating soap messages from JAXB java beans - Key: AXIS2-3723 URL: https://issues.apache.org/jira/browse/AXIS2-3723 Project: