[jira] Created: (AXIS2-4804) Ode process failing to complete on Wesphere7.0 with the error org.apache.axis2.AxisFault: Two services cannot have same name. A service with the axis_service_for_{http:

2010-08-30 Thread Radha Gopireddy (JIRA)
Ode process failing to complete on Wesphere7.0 with the error org.apache.axis2.AxisFault: Two services cannot have same name. A service with the axis_service_for_{http://teamcenter.com/globalservices/abort/webservice/2007-06}bpel-abort-service#soap-abo

[jira] Created: (AXIS2-4805) org.apache.axis2.AxisFault: Two services cannot have same name. A service with the axis_service_for_{http://teamcenter.com/globalservices/abort/webservice/2007-06}bpel-ab

2010-08-30 Thread Radha Gopireddy (JIRA)
org.apache.axis2.AxisFault: Two services cannot have same name. A service with the axis_service_for_{http://teamcenter.com/globalservices/abort/webservice/2007-06}bpel-abort-service#soap-abort-port_hqejbhcnphr5jxnnlfrjnf name already exists in the system

[jira] Commented: (AXIS2-4804) Ode process failing to complete on Wesphere7.0 with the error org.apache.axis2.AxisFault: Two services cannot have same name. A service with the axis_service_for_{htt

2010-08-30 Thread Radha Gopireddy (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904096#action_12904096 ] Radha Gopireddy commented on AXIS2-4804: I tried to solve it by replacing the org

[jira] Commented: (AXIS2-4804) Ode process failing to complete on Wesphere7.0 with the error org.apache.axis2.AxisFault: Two services cannot have same name. A service with the axis_service_for_{htt

2010-08-30 Thread Tammo van Lessen (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904121#action_12904121 ] Tammo van Lessen commented on AXIS2-4804: - Hi, this is an ODE issue, not an Axis2 i

Build failures in Rampart 1.5?

2010-08-30 Thread Glen Daniels
Hi folks, When I try to rebuild Rampart 1.5 from source, there seem to be two repeatable build failures in the integration module: Failed tests: testRequest(org.apache.rahas.RahasSAML2TokenTest) testRequest(org.apache.rahas.RahasSAML2TokenCertForHoKTest) The first fails due to an isRecognize

[jira] Created: (AXIS2-4806) generated code does not conform to typical eclipse warnings

2010-08-30 Thread Sebastian Dietrich (JIRA)
generated code does not conform to typical eclipse warnings --- Key: AXIS2-4806 URL: https://issues.apache.org/jira/browse/AXIS2-4806 Project: Axis2 Issue Type: Bug Components

Re: Build failures in Rampart 1.5?

2010-08-30 Thread Andreas Veithen
Glen, This seems to be caused by a bug in Sun's JDK 1.5 (all versions, except 1.5.0_24 distributed on MacOS X only). Please use 1.6. Andreas On Mon, Aug 30, 2010 at 18:49, Glen Daniels wrote: > Hi folks, > > When I try to rebuild Rampart 1.5 from source, there seem to be two > repeatable build

Re: Build failures in Rampart 1.5?

2010-08-30 Thread Glen Daniels
Hi Andreas, I'm using 1.6.0_05 for these builds. --Glen On 8/30/2010 2:46 PM, Andreas Veithen wrote: > Glen, > > This seems to be caused by a bug in Sun's JDK 1.5 (all versions, > except 1.5.0_24 distributed on MacOS X only). Please use 1.6. > > Andreas > > On Mon, Aug 30, 2010 at 18:49, Glen

Re: Build failures in Rampart 1.5?

2010-08-30 Thread Andreas Veithen
Maybe you should upgrade to a more recent update of 1.6? Andreas On Mon, Aug 30, 2010 at 20:49, Glen Daniels wrote: > Hi Andreas, > > I'm using 1.6.0_05 for these builds. > > --Glen > > On 8/30/2010 2:46 PM, Andreas Veithen wrote: >> Glen, >> >> This seems to be caused by a bug in Sun's JDK 1.5

Re: Build failures in Rampart 1.5?

2010-08-30 Thread Glen Daniels
I'll try that, but isn't it a huge cause for concern if we're not compatible with 1.5? AFAIK no one agreed to drop 1.5 support, and earlier versions certainly worked... --G On 8/30/2010 2:57 PM, Andreas Veithen wrote: > Maybe you should upgrade to a more recent update of 1.6? > > Andreas > > O

Re: Build failures in Rampart 1.5?

2010-08-30 Thread Andreas Veithen
If I remember Nananda's explanation of the issue correctly, then one can make this work on 1.5 by endorsing Xerces. Andreas On Mon, Aug 30, 2010 at 21:13, Glen Daniels wrote: > I'll try that, but isn't it a huge cause for concern if we're not compatible > with 1.5?  AFAIK no one agreed to drop 1

Re: Update on 1.5.2 release

2010-08-30 Thread Andreas Veithen
On Mon, Aug 30, 2010 at 08:07, Glen Daniels wrote: > On 8/29/2010 6:58 AM, Andreas Veithen wrote: >> Something went wrong with the creation of the staging profile; see >> INFRA-2939 for more details. > > Roger.  Hopefully we can get this resolved soon. > > Couple of other things, sort of a "good n

Re: Build failures in Rampart 1.5?

2010-08-30 Thread Glen Daniels
Ah, cool, I'll dig that up and try adding it to the Rampart FAQ. --Glen On 8/30/2010 3:19 PM, Andreas Veithen wrote: > If I remember Nananda's explanation of the issue correctly, then one > can make this work on 1.5 by endorsing Xerces. > > Andreas > > On Mon, Aug 30, 2010 at 21:13, Glen Daniel

Re: Build failures in Rampart 1.5?

2010-08-30 Thread Glen Daniels
Same two failures with 1.6.0_21. Will investigate further. I notice these same two failures seem to be plaguing the Hudson build. --Glen On 8/30/2010 3:13 PM, Glen Daniels wrote: > I'll try that, but isn't it a huge cause for concern if we're not compatible > with 1.5? AFAIK no one agreed to d

Re: Update on 1.5.2 release

2010-08-30 Thread Glen Daniels
On 8/30/2010 3:21 PM, Andreas Veithen wrote: > On Mon, Aug 30, 2010 at 08:07, Glen Daniels wrote: >> We have to fix this before the release, since this was the whole reason for >> 1.5.1 in the first place. My proposal for now would be to revert Jarek's >> change and re-test the branch with Rampa

Re: Update on 1.5.2 release

2010-08-30 Thread Jarek Gawor
> 2) Unfortunately, I hadn't taken enough care to note the disposition of > AXIS2-4751.  Now that Jarek's current changes are on the branch, the built > code will have regressions for several earlier issues (search for "axis2 > close_wait" - AXIS2-2883 is a good example) - just confirmed this on Wi

[jira] Created: (AXIS2-4807) org.apache.axis2.AxisFault: Transport error: 404 Error: Not Found

2010-08-30 Thread Joy Kenneth Harry (JIRA)
org.apache.axis2.AxisFault: Transport error: 404 Error: Not Found - Key: AXIS2-4807 URL: https://issues.apache.org/jira/browse/AXIS2-4807 Project: Axis2 Issue Type: Bug Affe

[jira] Updated: (AXIS2-4807) org.apache.axis2.AxisFault: Transport error: 404 Error: Not Found

2010-08-30 Thread Joy Kenneth Harry (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joy Kenneth Harry updated AXIS2-4807: - Affects Version/s: 1.3 1.4 1.5

Re: Build failures in Rampart 1.5?

2010-08-30 Thread Andreas Veithen
I also fixed (r965136) another issue on the trunk that (I believe) affected the same test cases. Maybe you are seeing that issue? Andreas On Mon, Aug 30, 2010 at 22:05, Glen Daniels wrote: > Same two failures with 1.6.0_21.  Will investigate further.  I notice these > same two failures seem to b

[jira] Closed: (AXIS2-4804) Ode process failing to complete on Wesphere7.0 with the error org.apache.axis2.AxisFault: Two services cannot have same name. A service with the axis_service_for_{http:/

2010-08-30 Thread Radha Gopireddy (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radha Gopireddy closed AXIS2-4804. -- Resolution: Invalid > Ode process failing to complete on Wesphere7.0 with the error > org.a