You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Jean-Sebastien Delfino <js...@apache.org> on 2008/07/25 19:35:42 UTC
Error building binding-ws-axis2
I'm seeing the following error when building binding-ws-axis2. Anybody
else seeing this?
testSOAP12Endpoint(org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.QuestionMarkWSDLTestCase)
Time elapsed: 0.702 sec <<< ERROR!
org.osoa.sca.ServiceRuntimeException:
org.osoa.sca.ServiceRuntimeException: Provided Intent -
{http://tuscany.apache.org/xmlns/sca/1.0}wsAuthentication not found for
PolicySet
{http://tuscany.apache.org/xmlns/sca/1.0}wsClientAuthenticationIntegrityPolicy
at
org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:276)
at
org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:70)
at
org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.QuestionMarkWSDLTestCase.setUp(QuestionMarkWSDLTestCase.java:130)
at junit.framework.TestCase.runBare(TestCase.java:132)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at
org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.java:35)
at
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308)
at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
Caused by: org.osoa.sca.ServiceRuntimeException: Provided Intent -
{http://tuscany.apache.org/xmlns/sca/1.0}wsAuthentication not found for
PolicySet
{http://tuscany.apache.org/xmlns/sca/1.0}wsClientAuthenticationIntegrityPolicy
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.analyseProblems(DefaultSCADomain.java:309)
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.addContribution(DefaultSCADomain.java:334)
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:183)
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.<init>(DefaultSCADomain.java:120)
at
org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:242)
... 20 more
--
Jean-Sebastien
Re: Error building binding-ws-axis2
Posted by Simon Nash <na...@apache.org>.
Jean-Sebastien Delfino wrote:
> Simon Nash wrote:
>> Raymond Feng wrote:
>> One possibility is such
>> cases is a difference between the Sun and IBM JDKs. I'm on Sun JDK
>> 1.5.0_13-b03, so I tried changing to the IBM JDK and this produced the
>> build failure you and Sebastien are seeing when the system ID is set
>> to a non-null string.
>
> I'm usually building in parallel on Windows IBM JDK 1.5 SR8, Linux RHEL
> 5 IBM JDK 1.5 SR8 and Linux RHEL 5 SUN JDK 6 Update 7.
>
> All three failed with the same error before Raymond's change.
> All work with his change.
>
I'm running with the Windows Sun JDK, so this is different from the
versions you are using.
Simon
Re: Error building binding-ws-axis2
Posted by Raymond Feng <en...@gmail.com>.
I guess I found the mystery here. As illustrated by the stacktrace below,
the XmlSchema code builds a DOM from the input source.
DocumentBuilderFactory docFac =
DocumentBuilderFactory.newInstance();
docFac.setNamespaceAware(true);
DocumentBuilder builder = docFac.newDocumentBuilder();
Document doc = builder.parse(inputSource);
In my environment, I get instance of
org.apache.xerces.jaxp.DocumentBuilderImpl (from xercesImpl-2.8.1) for the
builder and the parser tries to follow the schemaLocation which in turn
throws the UnknownHostException.
So those who doesn't see the problems, you probably get a different impl of
the DocumentBuilder.
Thanks,
Raymond
Thread [main] (Suspended (exception UnknownHostException)) Inet4AddressImpl.lookupAllHostAddr(String)
line: not available [native method] InetAddress$1.lookupAllHostAddr(String)
line: 849 InetAddress.getAddressFromNameService(String,
InetAddress) line: 1200 InetAddress.getAllByName0(String,
InetAddress, boolean) line: 1153 InetAddress.getAllByName(String,
InetAddress) line: 1083 InetAddress.getAllByName(String)
line: 1019 InetAddress.getByName(String)
line: 969 InetSocketAddress.<init>(String,
int) line: 124 HttpClient(NetworkClient).doConnect(String,
int) line: 157 HttpClient.openServer(String,
int) line: 394 HttpClient.openServer()
line: 529 HttpClient.<init>(URL,
Proxy, int) line: 233 HttpClient.New(URL,
Proxy, int, boolean) line: 306 HttpClient.New(URL,
Proxy, int) line: 323 HttpURLConnection.getNewHttpClient(URL,
Proxy, int) line: 788 HttpURLConnection.plainConnect()
line: 729 HttpURLConnection.connect()
line: 654 HttpURLConnection.getInputStream()
line: 977 XMLEntityManager.setupCurrentEntity(String,
XMLInputSource, boolean, boolean) line: not available XMLVersionDetector.determineDocVersion(XMLInputSource)
line: not available XIncludeAwareParserConfiguration(XML11Configuration).parse(boolean)
line: not available XIncludeAwareParserConfiguration(XML11Configuration).parse(XMLInputSource)
line: not available DOMParser(XMLParser).parse(XMLInputSource)
line: not available DOMParser.parse(InputSource)
line: not available DocumentBuilderImpl.parse(InputSource)
line: not available XmlSchemaCollection.read(InputSource,
ValidationEventHandler, TargetNamespaceValidator) line: 303 SchemaBuilder.resolveXmlSchema(String,
String, String, TargetNamespaceValidator) line: 1884 SchemaBuilder.handleImport(XmlSchema,
Element, Element) line: 1620 SchemaBuilder.handleXmlSchemaElement(Element,
String) line: 175 SchemaBuilder.build(Document,
String, ValidationEventHandler) line: 82 XmlSchemaCollection.read(Document,
String, ValidationEventHandler, TargetNamespaceValidator) line: 359 XmlSchemaCollection.read(Document,
String, ValidationEventHandler) line: 353 Interface2WSDLGenerator.loadXSD(XmlSchemaCollection,
XSDefinition) line: 402 Interface2WSDLGenerator.addSchemaExtension(XSDefinition,
XmlSchemaCollection, WSDLDefinition, Definition) line: 384 Interface2WSDLGenerator.generate(Interface,
WSDLDefinition) line: 256 Interface2WSDLGeneratorTestCase.testGenerate()
line: 57 NativeMethodAccessorImpl.invoke0(Method,
Object, Object[]) line: not available [native method] NativeMethodAccessorImpl.invoke(Object,
Object[]) line: 39 DelegatingMethodAccessorImpl.invoke(Object,
Object[]) line: 25 Method.invoke(Object,
Object...) line: 597 TestMethodRunner.executeMethodBody()
line: 99 TestMethodRunner.runUnprotected()
line: 81 TestMethodRunner(BeforeAndAfterRunner).runProtected()
line: 34 TestMethodRunner.runMethod()
line: 75 TestMethodRunner.run()
line: 45 TestClassMethodsRunner.invokeTestMethod(Method,
RunNotifier) line: 75 TestClassMethodsRunner.run(RunNotifier)
line: 36 TestClassRunner$1.runUnprotected()
line: 42 TestClassRunner$1(BeforeAndAfterRunner).runProtected()
line: 34 TestClassRunner.run(RunNotifier)
line: 52 JUnit4TestClassReference(JUnit4TestReference).run(TestExecution)
line: 45 TestExecution.run(ITestReference[])
line: 38 RemoteTestRunner.runTests(String[],
String, TestExecution) line: 460 RemoteTestRunner.runTests(TestExecution)
line: 673 RemoteTestRunner.run()
line: 386 RemoteTestRunner.main(String[])
line: 196--------------------------------------------------
From: "Jean-Sebastien Delfino" <js...@apache.org>
Sent: Friday, July 25, 2008 4:33 PM
To: <de...@tuscany.apache.org>
Subject: Re: Error building binding-ws-axis2
> Simon Nash wrote:
>> Raymond Feng wrote:
>> One possibility is such
>> cases is a difference between the Sun and IBM JDKs. I'm on Sun JDK
>> 1.5.0_13-b03, so I tried changing to the IBM JDK and this produced the
>> build failure you and Sebastien are seeing when the system ID is set
>> to a non-null string.
>
> I'm usually building in parallel on Windows IBM JDK 1.5 SR8, Linux RHEL 5
> IBM JDK 1.5 SR8 and Linux RHEL 5 SUN JDK 6 Update 7.
>
> All three failed with the same error before Raymond's change.
> All work with his change.
>
> --
> Jean-Sebastien
Re: Error building binding-ws-axis2
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Simon Nash wrote:
> Raymond Feng wrote:
> One possibility is such
> cases is a difference between the Sun and IBM JDKs. I'm on Sun JDK
> 1.5.0_13-b03, so I tried changing to the IBM JDK and this produced the
> build failure you and Sebastien are seeing when the system ID is set
> to a non-null string.
I'm usually building in parallel on Windows IBM JDK 1.5 SR8, Linux RHEL
5 IBM JDK 1.5 SR8 and Linux RHEL 5 SUN JDK 6 Update 7.
All three failed with the same error before Raymond's change.
All work with his change.
--
Jean-Sebastien
Re: Error building binding-ws-axis2
Posted by Simon Nash <na...@apache.org>.
ant elder wrote:
>
>
> On Sat, Jul 26, 2008 at 12:08 AM, Simon Nash <nash@apache.org
> <ma...@apache.org>> wrote:
>
> Raymond Feng wrote:
>
> The system id was set to <namespace> + <a file name generated by
> JAXB, such as schema3.xsd>. In the failing test case, it was
> "http://other.ws.binding.sca.tuscany.apache.org/schema3.xsd" and
> "other.ws.binding.sca.tuscany.apache.org
> <http://other.ws.binding.sca.tuscany.apache.org>" was taken as
> the host name.
>
> The system ID has always been set to this value. The recent change
> I made for TUSCANY-2479 did not change the system ID, but made sure
> that its value is propagated to the XmlSchema object that is created
> by Interface2WSDLGenerator.loadXSD(). This allows XmlSchema imports
> to resolve correctly.
>
> I built 1.3 RC2 with an empty maven repo. The modules databinding-jaxb,
> binding-ws-wsdlgen and binding-ws-axis2 all built OK. We are doing the
> same thing, but our results are different. One possibility is such
> cases is a difference between the Sun and IBM JDKs. I'm on Sun JDK
> 1.5.0_13-b03, so I tried changing to the IBM JDK and this produced the
> build failure you and Sebastien are seeing when the system ID is set
> to a non-null string.
>
> I applied your change to set the system ID to "" and it seems this
> works OK for me. I'd like to know whether this also works for Scott in
> his environment. If it does, it seems we should go with this approach
> for 1.3 as this appears to be the only combination that works on both
> the Sun and IBM JDKs.
>
>
> Seems fine to me too if it fixes it but it does work fine for me with
> both Sun JDK and IBMs "1.5.0" Java(TM) 2 Runtime Environment, Standard
> Edition (build pwi32dev-20080315 (SR7))
>
Do you mean RC2 works fine with both of these, without the recent change
from Raymond?
The IBM JDK that I used for testing was "J2RE 1.5.0 IBM Windows 32 build
pwi32dev-20070201 (SR4)". Maybe there is an IBM JDK bug that was fixed
in the newer level.
Simon
> ...ant
Re: Error building binding-ws-axis2
Posted by ant elder <an...@gmail.com>.
On Sat, Jul 26, 2008 at 12:08 AM, Simon Nash <na...@apache.org> wrote:
> Raymond Feng wrote:
>
>> The system id was set to <namespace> + <a file name generated by JAXB,
>> such as schema3.xsd>. In the failing test case, it was "
>> http://other.ws.binding.sca.tuscany.apache.org/schema3.xsd" and "
>> other.ws.binding.sca.tuscany.apache.org" was taken as the host name.
>>
>> The system ID has always been set to this value. The recent change
> I made for TUSCANY-2479 did not change the system ID, but made sure
> that its value is propagated to the XmlSchema object that is created
> by Interface2WSDLGenerator.loadXSD(). This allows XmlSchema imports
> to resolve correctly.
>
> I built 1.3 RC2 with an empty maven repo. The modules databinding-jaxb,
> binding-ws-wsdlgen and binding-ws-axis2 all built OK. We are doing the
> same thing, but our results are different. One possibility is such
> cases is a difference between the Sun and IBM JDKs. I'm on Sun JDK
> 1.5.0_13-b03, so I tried changing to the IBM JDK and this produced the
> build failure you and Sebastien are seeing when the system ID is set
> to a non-null string.
>
> I applied your change to set the system ID to "" and it seems this
> works OK for me. I'd like to know whether this also works for Scott in
> his environment. If it does, it seems we should go with this approach
> for 1.3 as this appears to be the only combination that works on both
> the Sun and IBM JDKs.
Seems fine to me too if it fixes it but it does work fine for me with both
Sun JDK and IBMs "1.5.0" Java(TM) 2 Runtime Environment, Standard Edition
(build pwi32dev-20080315 (SR7))
...ant
Re: Error building binding-ws-axis2
Posted by Simon Nash <na...@apache.org>.
Raymond Feng wrote:
> The system id was set to <namespace> + <a file name generated by JAXB,
> such as schema3.xsd>. In the failing test case, it was
> "http://other.ws.binding.sca.tuscany.apache.org/schema3.xsd" and
> "other.ws.binding.sca.tuscany.apache.org" was taken as the host name.
>
The system ID has always been set to this value. The recent change
I made for TUSCANY-2479 did not change the system ID, but made sure
that its value is propagated to the XmlSchema object that is created
by Interface2WSDLGenerator.loadXSD(). This allows XmlSchema imports
to resolve correctly.
I built 1.3 RC2 with an empty maven repo. The modules databinding-jaxb,
binding-ws-wsdlgen and binding-ws-axis2 all built OK. We are doing the
same thing, but our results are different. One possibility is such
cases is a difference between the Sun and IBM JDKs. I'm on Sun JDK
1.5.0_13-b03, so I tried changing to the IBM JDK and this produced the
build failure you and Sebastien are seeing when the system ID is set
to a non-null string.
I applied your change to set the system ID to "" and it seems this
works OK for me. I'd like to know whether this also works for Scott in
his environment. If it does, it seems we should go with this approach
for 1.3 as this appears to be the only combination that works on both
the Sun and IBM JDKs.
> BTW, don't we have a testcase for TUSCANY-2479? My change doesn't break
> anything in the build.
>
Yes, the test case for this is in binding-ws-wsdlgen. This is the test
case that was breaking for you with the IBM JDK before you made your
change. However, it was working for me with the Sun JDK.
Simon
> Thanks,
> Raymond
> --------------------------------------------------
> From: "Simon Nash" <na...@apache.org>
> Sent: Friday, July 25, 2008 1:50 PM
> To: <de...@tuscany.apache.org>
> Subject: Re: Error building binding-ws-axis2
>
>> Raymond Feng wrote:
>>> Hi,
>>>
>>> I just checked in a fix for TUSCANY-2498 into trunk after a clean
>>> build. Please let me know if we agree to merge it into the 1.3 branch.
>>>
>> I don't agree until we understand more about what is the problem
>> with the code currently in 1.3 RC2. What value do you see in the
>> system ID without the change that you just checked in?
>>
>> Simon
>>
>>> Thanks,
>>> Raymond
>>> --------------------------------------------------
>>> From: "Simon Nash" <na...@apache.org>
>>> Sent: Friday, July 25, 2008 12:13 PM
>>> To: <de...@tuscany.apache.org>
>>> Subject: Re: Error building binding-ws-axis2
>>>
>>>> Raymond Feng wrote:
>>>>> Hi,
>>>>>
>>>>> I just ran a build against the trunk and 1.3 tag and I don't see
>>>>> the issue related to the binding-ws-axis2.
>>>>>
>>>>> I already opened a JIRA for wsdlgen test failures:
>>>>> https://issues.apache.org/jira/browse/TUSCANY-2498.
>>>>>
>>>> Does this problem only apply to the 1.3 tag? The description in
>>>> TUSCANY-2498 suggests this. Does trunk build cleanly for you?
>>>>
>>>> Simon
>>>>
>>>>> Thanks,
>>>>> Raymond
>>>>> --------------------------------------------------
>>>>> From: "Jean-Sebastien Delfino" <js...@apache.org>
>>>>> Sent: Friday, July 25, 2008 10:55 AM
>>>>> To: <de...@tuscany.apache.org>
>>>>> Subject: Re: Error building binding-ws-axis2
>>>>>
>>>>>> Jean-Sebastien Delfino wrote:
>>>>>>> I'm seeing the following error when building binding-ws-axis2.
>>>>>>> Anybody else seeing this?
>>>>>>>
>>>>>> ...
>>>>>>
>>>>>> Well that was with a revision from yesterday, with SVN r679776 I'm
>>>>>> getting another error in modules/binding-ws-wsdlgen.
>>>>>>
>>>>>> Running
>>>>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase
>>>>>>
>>>>>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
>>>>>> 0.156 sec <<< FAILURE!
>>>>>> testGenerate(org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase)
>>>>>> Time elapsed: 0.139 sec <<< ERROR!
>>>>>> java.lang.RuntimeException:
>>>>>> org.apache.ws.commons.schema.XmlSchemaException:
>>>>>> other.ws.binding.sca.tuscany.apache.org
>>>>>> at
>>>>>> org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1886)
>>>>>>
>>>>>> at
>>>>>> org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:1620)
>>>>>>
>>>>>> at
>>>>>> org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:175)
>>>>>>
>>>>>> at
>>>>>> org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:82)
>>>>>>
>>>>>> at
>>>>>> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:359)
>>>>>>
>>>>>> at
>>>>>> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:353)
>>>>>>
>>>>>> at
>>>>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.loadXSD(Interface2WSDLGenerator.java:402)
>>>>>>
>>>>>> at
>>>>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.addSchemaExtension(Interface2WSDLGenerator.java:384)
>>>>>>
>>>>>> at
>>>>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.generate(Interface2WSDLGenerator.java:256)
>>>>>>
>>>>>> at
>>>>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase.testGenerate(Interface2WSDLGeneratorTestCase.java:57)
>>>>>>
>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>> Method)
>>>>>> at
>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>>
>>>>>> at
>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>
>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>> at
>>>>>> org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
>>>>>>
>>>>>> at
>>>>>> org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
>>>>>>
>>>>>> at
>>>>>> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
>>>>>>
>>>>>> at
>>>>>> org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
>>>>>>
>>>>>> at
>>>>>> org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
>>>>>>
>>>>>> at
>>>>>> org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75)
>>>>>>
>>>>>> at
>>>>>> org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36)
>>>>>>
>>>>>> at
>>>>>> org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
>>>>>>
>>>>>> at
>>>>>> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
>>>>>>
>>>>>> at
>>>>>> org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
>>>>>>
>>>>>> at
>>>>>> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
>>>>>>
>>>>>> at
>>>>>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
>>>>>>
>>>>>> at
>>>>>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
>>>>>>
>>>>>> at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>> Method)
>>>>>> at
>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>>
>>>>>> at
>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>
>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>> at
>>>>>> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308)
>>>>>>
>>>>>> at
>>>>>> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
>>>>>>
>>>>>> Caused by: org.apache.ws.commons.schema.XmlSchemaException:
>>>>>> other.ws.binding.sca.tuscany.apache.org
>>>>>> at
>>>>>> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:308)
>>>>>>
>>>>>> at
>>>>>> org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1884)
>>>>>>
>>>>>> ... 33 more
>>>>>>
>>>>>> --
>>>>>> Jean-Sebastien
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>
Re: Error building binding-ws-axis2
Posted by Raymond Feng <en...@gmail.com>.
The system id was set to <namespace> + <a file name generated by JAXB, such
as schema3.xsd>. In the failing test case, it was
"http://other.ws.binding.sca.tuscany.apache.org/schema3.xsd" and
"other.ws.binding.sca.tuscany.apache.org" was taken as the host name.
BTW, don't we have a testcase for TUSCANY-2479? My change doesn't break
anything in the build.
Thanks,
Raymond
--------------------------------------------------
From: "Simon Nash" <na...@apache.org>
Sent: Friday, July 25, 2008 1:50 PM
To: <de...@tuscany.apache.org>
Subject: Re: Error building binding-ws-axis2
> Raymond Feng wrote:
>> Hi,
>>
>> I just checked in a fix for TUSCANY-2498 into trunk after a clean build.
>> Please let me know if we agree to merge it into the 1.3 branch.
>>
> I don't agree until we understand more about what is the problem
> with the code currently in 1.3 RC2. What value do you see in the
> system ID without the change that you just checked in?
>
> Simon
>
>> Thanks,
>> Raymond
>> --------------------------------------------------
>> From: "Simon Nash" <na...@apache.org>
>> Sent: Friday, July 25, 2008 12:13 PM
>> To: <de...@tuscany.apache.org>
>> Subject: Re: Error building binding-ws-axis2
>>
>>> Raymond Feng wrote:
>>>> Hi,
>>>>
>>>> I just ran a build against the trunk and 1.3 tag and I don't see the
>>>> issue related to the binding-ws-axis2.
>>>>
>>>> I already opened a JIRA for wsdlgen test failures:
>>>> https://issues.apache.org/jira/browse/TUSCANY-2498.
>>>>
>>> Does this problem only apply to the 1.3 tag? The description in
>>> TUSCANY-2498 suggests this. Does trunk build cleanly for you?
>>>
>>> Simon
>>>
>>>> Thanks,
>>>> Raymond
>>>> --------------------------------------------------
>>>> From: "Jean-Sebastien Delfino" <js...@apache.org>
>>>> Sent: Friday, July 25, 2008 10:55 AM
>>>> To: <de...@tuscany.apache.org>
>>>> Subject: Re: Error building binding-ws-axis2
>>>>
>>>>> Jean-Sebastien Delfino wrote:
>>>>>> I'm seeing the following error when building binding-ws-axis2.
>>>>>> Anybody else seeing this?
>>>>>>
>>>>> ...
>>>>>
>>>>> Well that was with a revision from yesterday, with SVN r679776 I'm
>>>>> getting another error in modules/binding-ws-wsdlgen.
>>>>>
>>>>> Running
>>>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase
>>>>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.156
>>>>> sec <<< FAILURE!
>>>>> testGenerate(org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase)
>>>>> Time elapsed: 0.139 sec <<< ERROR!
>>>>> java.lang.RuntimeException:
>>>>> org.apache.ws.commons.schema.XmlSchemaException:
>>>>> other.ws.binding.sca.tuscany.apache.org
>>>>> at
>>>>> org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1886)
>>>>> at
>>>>> org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:1620)
>>>>> at
>>>>> org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:175)
>>>>> at
>>>>> org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:82)
>>>>> at
>>>>> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:359)
>>>>> at
>>>>> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:353)
>>>>> at
>>>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.loadXSD(Interface2WSDLGenerator.java:402)
>>>>> at
>>>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.addSchemaExtension(Interface2WSDLGenerator.java:384)
>>>>> at
>>>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.generate(Interface2WSDLGenerator.java:256)
>>>>> at
>>>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase.testGenerate(Interface2WSDLGeneratorTestCase.java:57)
>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>> at
>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>> at
>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>> at
>>>>> org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
>>>>> at
>>>>> org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
>>>>> at
>>>>> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
>>>>> at
>>>>> org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
>>>>> at
>>>>> org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
>>>>> at
>>>>> org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75)
>>>>> at
>>>>> org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36)
>>>>> at
>>>>> org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
>>>>> at
>>>>> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
>>>>> at
>>>>> org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
>>>>> at
>>>>> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
>>>>> at
>>>>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
>>>>> at
>>>>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
>>>>> at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>> at
>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>> at
>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>> at
>>>>> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308)
>>>>> at
>>>>> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
>>>>> Caused by: org.apache.ws.commons.schema.XmlSchemaException:
>>>>> other.ws.binding.sca.tuscany.apache.org
>>>>> at
>>>>> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:308)
>>>>> at
>>>>> org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1884)
>>>>> ... 33 more
>>>>>
>>>>> --
>>>>> Jean-Sebastien
>>>>
>>>>
>>>
>>>
>>
>
Re: Error building binding-ws-axis2
Posted by Simon Nash <na...@apache.org>.
Raymond Feng wrote:
> Hi,
>
> I just checked in a fix for TUSCANY-2498 into trunk after a clean build.
> Please let me know if we agree to merge it into the 1.3 branch.
>
I don't agree until we understand more about what is the problem
with the code currently in 1.3 RC2. What value do you see in the
system ID without the change that you just checked in?
Simon
> Thanks,
> Raymond
> --------------------------------------------------
> From: "Simon Nash" <na...@apache.org>
> Sent: Friday, July 25, 2008 12:13 PM
> To: <de...@tuscany.apache.org>
> Subject: Re: Error building binding-ws-axis2
>
>> Raymond Feng wrote:
>>> Hi,
>>>
>>> I just ran a build against the trunk and 1.3 tag and I don't see the
>>> issue related to the binding-ws-axis2.
>>>
>>> I already opened a JIRA for wsdlgen test failures:
>>> https://issues.apache.org/jira/browse/TUSCANY-2498.
>>>
>> Does this problem only apply to the 1.3 tag? The description in
>> TUSCANY-2498 suggests this. Does trunk build cleanly for you?
>>
>> Simon
>>
>>> Thanks,
>>> Raymond
>>> --------------------------------------------------
>>> From: "Jean-Sebastien Delfino" <js...@apache.org>
>>> Sent: Friday, July 25, 2008 10:55 AM
>>> To: <de...@tuscany.apache.org>
>>> Subject: Re: Error building binding-ws-axis2
>>>
>>>> Jean-Sebastien Delfino wrote:
>>>>> I'm seeing the following error when building binding-ws-axis2.
>>>>> Anybody else seeing this?
>>>>>
>>>> ...
>>>>
>>>> Well that was with a revision from yesterday, with SVN r679776 I'm
>>>> getting another error in modules/binding-ws-wsdlgen.
>>>>
>>>> Running
>>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase
>>>>
>>>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
>>>> 0.156 sec <<< FAILURE!
>>>> testGenerate(org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase)
>>>> Time elapsed: 0.139 sec <<< ERROR!
>>>> java.lang.RuntimeException:
>>>> org.apache.ws.commons.schema.XmlSchemaException:
>>>> other.ws.binding.sca.tuscany.apache.org
>>>> at
>>>> org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1886)
>>>>
>>>> at
>>>> org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:1620)
>>>>
>>>> at
>>>> org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:175)
>>>>
>>>> at
>>>> org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:82)
>>>> at
>>>> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:359)
>>>>
>>>> at
>>>> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:353)
>>>>
>>>> at
>>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.loadXSD(Interface2WSDLGenerator.java:402)
>>>>
>>>> at
>>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.addSchemaExtension(Interface2WSDLGenerator.java:384)
>>>>
>>>> at
>>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.generate(Interface2WSDLGenerator.java:256)
>>>>
>>>> at
>>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase.testGenerate(Interface2WSDLGeneratorTestCase.java:57)
>>>>
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>
>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>> at
>>>> org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
>>>>
>>>> at
>>>> org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
>>>>
>>>> at
>>>> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
>>>>
>>>> at
>>>> org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
>>>>
>>>> at
>>>> org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
>>>>
>>>> at
>>>> org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75)
>>>>
>>>> at
>>>> org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36)
>>>>
>>>> at
>>>> org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
>>>>
>>>> at
>>>> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
>>>>
>>>> at
>>>> org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
>>>> at
>>>> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
>>>>
>>>> at
>>>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
>>>>
>>>> at
>>>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
>>>>
>>>> at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>
>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>> at
>>>> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308)
>>>>
>>>> at
>>>> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
>>>>
>>>> Caused by: org.apache.ws.commons.schema.XmlSchemaException:
>>>> other.ws.binding.sca.tuscany.apache.org
>>>> at
>>>> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:308)
>>>>
>>>> at
>>>> org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1884)
>>>>
>>>> ... 33 more
>>>>
>>>> --
>>>> Jean-Sebastien
>>>
>>>
>>
>>
>
Re: Error building binding-ws-axis2
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Raymond Feng wrote:
> Hi,
>
> I just checked in a fix for TUSCANY-2498 into trunk after a clean build.
> Please let me know if we agree to merge it into the 1.3 branch.
>
> Thanks,
> Raymond
SVN r679890 fixes the build break in trunk. Thanks!
--
Jean-Sebastien
Re: Error building binding-ws-axis2
Posted by Raymond Feng <en...@gmail.com>.
Hi,
I just checked in a fix for TUSCANY-2498 into trunk after a clean build.
Please let me know if we agree to merge it into the 1.3 branch.
Thanks,
Raymond
--------------------------------------------------
From: "Simon Nash" <na...@apache.org>
Sent: Friday, July 25, 2008 12:13 PM
To: <de...@tuscany.apache.org>
Subject: Re: Error building binding-ws-axis2
> Raymond Feng wrote:
>> Hi,
>>
>> I just ran a build against the trunk and 1.3 tag and I don't see the
>> issue related to the binding-ws-axis2.
>>
>> I already opened a JIRA for wsdlgen test failures:
>> https://issues.apache.org/jira/browse/TUSCANY-2498.
>>
> Does this problem only apply to the 1.3 tag? The description in
> TUSCANY-2498 suggests this. Does trunk build cleanly for you?
>
> Simon
>
>> Thanks,
>> Raymond
>> --------------------------------------------------
>> From: "Jean-Sebastien Delfino" <js...@apache.org>
>> Sent: Friday, July 25, 2008 10:55 AM
>> To: <de...@tuscany.apache.org>
>> Subject: Re: Error building binding-ws-axis2
>>
>>> Jean-Sebastien Delfino wrote:
>>>> I'm seeing the following error when building binding-ws-axis2. Anybody
>>>> else seeing this?
>>>>
>>> ...
>>>
>>> Well that was with a revision from yesterday, with SVN r679776 I'm
>>> getting another error in modules/binding-ws-wsdlgen.
>>>
>>> Running
>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase
>>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.156
>>> sec <<< FAILURE!
>>> testGenerate(org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase)
>>> Time elapsed: 0.139 sec <<< ERROR!
>>> java.lang.RuntimeException:
>>> org.apache.ws.commons.schema.XmlSchemaException:
>>> other.ws.binding.sca.tuscany.apache.org
>>> at
>>> org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1886)
>>> at
>>> org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:1620)
>>> at
>>> org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:175)
>>> at
>>> org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:82)
>>> at
>>> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:359)
>>> at
>>> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:353)
>>> at
>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.loadXSD(Interface2WSDLGenerator.java:402)
>>> at
>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.addSchemaExtension(Interface2WSDLGenerator.java:384)
>>> at
>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.generate(Interface2WSDLGenerator.java:256)
>>> at
>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase.testGenerate(Interface2WSDLGeneratorTestCase.java:57)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>> at
>>> org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
>>> at
>>> org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
>>> at
>>> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
>>> at
>>> org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
>>> at
>>> org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
>>> at
>>> org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75)
>>> at
>>> org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36)
>>> at
>>> org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
>>> at
>>> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
>>> at
>>> org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
>>> at
>>> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
>>> at
>>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
>>> at
>>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
>>> at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>> at
>>> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308)
>>> at
>>> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
>>> Caused by: org.apache.ws.commons.schema.XmlSchemaException:
>>> other.ws.binding.sca.tuscany.apache.org
>>> at
>>> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:308)
>>> at
>>> org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1884)
>>> ... 33 more
>>>
>>> --
>>> Jean-Sebastien
>>
>>
>
>
Re: Error building binding-ws-axis2
Posted by Simon Nash <na...@apache.org>.
Raymond Feng wrote:
> Hi,
>
> It's broken on both trunk and 1.3 tag. The problem is that the generated
> <xsd:import> statement has invalid schemaLocation from the system id of
> the DOMResult which contains the schema from JAXB. I'm setting system id
> to "" so that the schemaLocation will be not generated. If the build is
> successful, I can commit the fix.
>
I think this change will regress the fix for TUSCANY-2479. I'm not
sure why Ant and I don't see this problem and you and Sebastien do.
What values do you see in the system ID with the current code?
Simon
> Thanks,
> Raymond
> --------------------------------------------------
> From: "Simon Nash" <na...@apache.org>
> Sent: Friday, July 25, 2008 12:13 PM
> To: <de...@tuscany.apache.org>
> Subject: Re: Error building binding-ws-axis2
>
>> Raymond Feng wrote:
>>> Hi,
>>>
>>> I just ran a build against the trunk and 1.3 tag and I don't see the
>>> issue related to the binding-ws-axis2.
>>>
>>> I already opened a JIRA for wsdlgen test failures:
>>> https://issues.apache.org/jira/browse/TUSCANY-2498.
>>>
>> Does this problem only apply to the 1.3 tag? The description in
>> TUSCANY-2498 suggests this. Does trunk build cleanly for you?
>>
>> Simon
>>
>>> Thanks,
>>> Raymond
>>> --------------------------------------------------
>>> From: "Jean-Sebastien Delfino" <js...@apache.org>
>>> Sent: Friday, July 25, 2008 10:55 AM
>>> To: <de...@tuscany.apache.org>
>>> Subject: Re: Error building binding-ws-axis2
>>>
>>>> Jean-Sebastien Delfino wrote:
>>>>> I'm seeing the following error when building binding-ws-axis2.
>>>>> Anybody else seeing this?
>>>>>
>>>> ...
>>>>
>>>> Well that was with a revision from yesterday, with SVN r679776 I'm
>>>> getting another error in modules/binding-ws-wsdlgen.
>>>>
>>>> Running
>>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase
>>>>
>>>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
>>>> 0.156 sec <<< FAILURE!
>>>> testGenerate(org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase)
>>>> Time elapsed: 0.139 sec <<< ERROR!
>>>> java.lang.RuntimeException:
>>>> org.apache.ws.commons.schema.XmlSchemaException:
>>>> other.ws.binding.sca.tuscany.apache.org
>>>> at
>>>> org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1886)
>>>>
>>>> at
>>>> org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:1620)
>>>>
>>>> at
>>>> org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:175)
>>>>
>>>> at
>>>> org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:82)
>>>> at
>>>> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:359)
>>>>
>>>> at
>>>> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:353)
>>>>
>>>> at
>>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.loadXSD(Interface2WSDLGenerator.java:402)
>>>>
>>>> at
>>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.addSchemaExtension(Interface2WSDLGenerator.java:384)
>>>>
>>>> at
>>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.generate(Interface2WSDLGenerator.java:256)
>>>>
>>>> at
>>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase.testGenerate(Interface2WSDLGeneratorTestCase.java:57)
>>>>
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>
>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>> at
>>>> org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
>>>>
>>>> at
>>>> org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
>>>>
>>>> at
>>>> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
>>>>
>>>> at
>>>> org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
>>>>
>>>> at
>>>> org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
>>>>
>>>> at
>>>> org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75)
>>>>
>>>> at
>>>> org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36)
>>>>
>>>> at
>>>> org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
>>>>
>>>> at
>>>> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
>>>>
>>>> at
>>>> org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
>>>> at
>>>> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
>>>>
>>>> at
>>>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
>>>>
>>>> at
>>>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
>>>>
>>>> at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>
>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>> at
>>>> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308)
>>>>
>>>> at
>>>> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
>>>>
>>>> Caused by: org.apache.ws.commons.schema.XmlSchemaException:
>>>> other.ws.binding.sca.tuscany.apache.org
>>>> at
>>>> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:308)
>>>>
>>>> at
>>>> org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1884)
>>>>
>>>> ... 33 more
>>>>
>>>> --
>>>> Jean-Sebastien
>>>
>>>
>>
>>
>
Re: Error building binding-ws-axis2
Posted by Raymond Feng <en...@gmail.com>.
Hi,
It's broken on both trunk and 1.3 tag. The problem is that the generated
<xsd:import> statement has invalid schemaLocation from the system id of the
DOMResult which contains the schema from JAXB. I'm setting system id to ""
so that the schemaLocation will be not generated. If the build is
successful, I can commit the fix.
Thanks,
Raymond
--------------------------------------------------
From: "Simon Nash" <na...@apache.org>
Sent: Friday, July 25, 2008 12:13 PM
To: <de...@tuscany.apache.org>
Subject: Re: Error building binding-ws-axis2
> Raymond Feng wrote:
>> Hi,
>>
>> I just ran a build against the trunk and 1.3 tag and I don't see the
>> issue related to the binding-ws-axis2.
>>
>> I already opened a JIRA for wsdlgen test failures:
>> https://issues.apache.org/jira/browse/TUSCANY-2498.
>>
> Does this problem only apply to the 1.3 tag? The description in
> TUSCANY-2498 suggests this. Does trunk build cleanly for you?
>
> Simon
>
>> Thanks,
>> Raymond
>> --------------------------------------------------
>> From: "Jean-Sebastien Delfino" <js...@apache.org>
>> Sent: Friday, July 25, 2008 10:55 AM
>> To: <de...@tuscany.apache.org>
>> Subject: Re: Error building binding-ws-axis2
>>
>>> Jean-Sebastien Delfino wrote:
>>>> I'm seeing the following error when building binding-ws-axis2. Anybody
>>>> else seeing this?
>>>>
>>> ...
>>>
>>> Well that was with a revision from yesterday, with SVN r679776 I'm
>>> getting another error in modules/binding-ws-wsdlgen.
>>>
>>> Running
>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase
>>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.156
>>> sec <<< FAILURE!
>>> testGenerate(org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase)
>>> Time elapsed: 0.139 sec <<< ERROR!
>>> java.lang.RuntimeException:
>>> org.apache.ws.commons.schema.XmlSchemaException:
>>> other.ws.binding.sca.tuscany.apache.org
>>> at
>>> org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1886)
>>> at
>>> org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:1620)
>>> at
>>> org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:175)
>>> at
>>> org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:82)
>>> at
>>> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:359)
>>> at
>>> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:353)
>>> at
>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.loadXSD(Interface2WSDLGenerator.java:402)
>>> at
>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.addSchemaExtension(Interface2WSDLGenerator.java:384)
>>> at
>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.generate(Interface2WSDLGenerator.java:256)
>>> at
>>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase.testGenerate(Interface2WSDLGeneratorTestCase.java:57)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>> at
>>> org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
>>> at
>>> org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
>>> at
>>> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
>>> at
>>> org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
>>> at
>>> org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
>>> at
>>> org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75)
>>> at
>>> org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36)
>>> at
>>> org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
>>> at
>>> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
>>> at
>>> org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
>>> at
>>> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
>>> at
>>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
>>> at
>>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
>>> at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>> at
>>> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308)
>>> at
>>> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
>>> Caused by: org.apache.ws.commons.schema.XmlSchemaException:
>>> other.ws.binding.sca.tuscany.apache.org
>>> at
>>> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:308)
>>> at
>>> org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1884)
>>> ... 33 more
>>>
>>> --
>>> Jean-Sebastien
>>
>>
>
>
Re: Error building binding-ws-axis2
Posted by Simon Nash <na...@apache.org>.
Raymond Feng wrote:
> Hi,
>
> I just ran a build against the trunk and 1.3 tag and I don't see the
> issue related to the binding-ws-axis2.
>
> I already opened a JIRA for wsdlgen test failures:
> https://issues.apache.org/jira/browse/TUSCANY-2498.
>
Does this problem only apply to the 1.3 tag? The description in
TUSCANY-2498 suggests this. Does trunk build cleanly for you?
Simon
> Thanks,
> Raymond
> --------------------------------------------------
> From: "Jean-Sebastien Delfino" <js...@apache.org>
> Sent: Friday, July 25, 2008 10:55 AM
> To: <de...@tuscany.apache.org>
> Subject: Re: Error building binding-ws-axis2
>
>> Jean-Sebastien Delfino wrote:
>>> I'm seeing the following error when building binding-ws-axis2.
>>> Anybody else seeing this?
>>>
>> ...
>>
>> Well that was with a revision from yesterday, with SVN r679776 I'm
>> getting another error in modules/binding-ws-wsdlgen.
>>
>> Running
>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase
>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.156
>> sec <<< FAILURE!
>> testGenerate(org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase)
>> Time elapsed: 0.139 sec <<< ERROR!
>> java.lang.RuntimeException:
>> org.apache.ws.commons.schema.XmlSchemaException:
>> other.ws.binding.sca.tuscany.apache.org
>> at
>> org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1886)
>>
>> at
>> org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:1620)
>>
>> at
>> org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:175)
>>
>> at
>> org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:82)
>> at
>> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:359)
>>
>> at
>> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:353)
>>
>> at
>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.loadXSD(Interface2WSDLGenerator.java:402)
>>
>> at
>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.addSchemaExtension(Interface2WSDLGenerator.java:384)
>>
>> at
>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.generate(Interface2WSDLGenerator.java:256)
>>
>> at
>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase.testGenerate(Interface2WSDLGeneratorTestCase.java:57)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> at
>> org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
>>
>> at
>> org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
>>
>> at
>> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
>>
>> at
>> org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
>>
>> at
>> org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
>> at
>> org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75)
>>
>> at
>> org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36)
>>
>> at
>> org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
>>
>> at
>> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
>>
>> at
>> org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
>> at
>> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
>>
>> at
>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
>>
>> at
>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
>>
>> at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> at
>> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308)
>>
>> at
>> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
>>
>> Caused by: org.apache.ws.commons.schema.XmlSchemaException:
>> other.ws.binding.sca.tuscany.apache.org
>> at
>> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:308)
>>
>> at
>> org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1884)
>>
>> ... 33 more
>>
>> --
>> Jean-Sebastien
>
>
Re: Error building binding-ws-axis2
Posted by Simon Nash <na...@apache.org>.
Raymond Feng wrote:
> Hi,
>
> I just ran a build against the trunk and 1.3 tag and I don't see the
> issue related to the binding-ws-axis2.
>
> I already opened a JIRA for wsdlgen test failures:
> https://issues.apache.org/jira/browse/TUSCANY-2498.
>
I updated trunk to r679881 and did a mvn clean and rebuild of the modules
directory. I didn't see any problems with binding-ws-wsdlgen or with
binding-ws-axis2.
Simon
> Thanks,
> Raymond
> --------------------------------------------------
> From: "Jean-Sebastien Delfino" <js...@apache.org>
> Sent: Friday, July 25, 2008 10:55 AM
> To: <de...@tuscany.apache.org>
> Subject: Re: Error building binding-ws-axis2
>
>> Jean-Sebastien Delfino wrote:
>>> I'm seeing the following error when building binding-ws-axis2.
>>> Anybody else seeing this?
>>>
>> ...
>>
>> Well that was with a revision from yesterday, with SVN r679776 I'm
>> getting another error in modules/binding-ws-wsdlgen.
>>
>> Running
>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase
>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.156
>> sec <<< FAILURE!
>> testGenerate(org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase)
>> Time elapsed: 0.139 sec <<< ERROR!
>> java.lang.RuntimeException:
>> org.apache.ws.commons.schema.XmlSchemaException:
>> other.ws.binding.sca.tuscany.apache.org
>> at
>> org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1886)
>>
>> at
>> org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:1620)
>>
>> at
>> org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:175)
>>
>> at
>> org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:82)
>> at
>> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:359)
>>
>> at
>> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:353)
>>
>> at
>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.loadXSD(Interface2WSDLGenerator.java:402)
>>
>> at
>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.addSchemaExtension(Interface2WSDLGenerator.java:384)
>>
>> at
>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.generate(Interface2WSDLGenerator.java:256)
>>
>> at
>> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase.testGenerate(Interface2WSDLGeneratorTestCase.java:57)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> at
>> org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
>>
>> at
>> org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
>>
>> at
>> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
>>
>> at
>> org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
>>
>> at
>> org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
>> at
>> org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75)
>>
>> at
>> org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36)
>>
>> at
>> org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
>>
>> at
>> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
>>
>> at
>> org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
>> at
>> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
>>
>> at
>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
>>
>> at
>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
>>
>> at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> at
>> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308)
>>
>> at
>> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
>>
>> Caused by: org.apache.ws.commons.schema.XmlSchemaException:
>> other.ws.binding.sca.tuscany.apache.org
>> at
>> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:308)
>>
>> at
>> org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1884)
>>
>> ... 33 more
>>
>> --
>> Jean-Sebastien
>
>
Re: Error building binding-ws-axis2
Posted by Raymond Feng <en...@gmail.com>.
Hi,
I just ran a build against the trunk and 1.3 tag and I don't see the issue
related to the binding-ws-axis2.
I already opened a JIRA for wsdlgen test failures:
https://issues.apache.org/jira/browse/TUSCANY-2498.
Thanks,
Raymond
--------------------------------------------------
From: "Jean-Sebastien Delfino" <js...@apache.org>
Sent: Friday, July 25, 2008 10:55 AM
To: <de...@tuscany.apache.org>
Subject: Re: Error building binding-ws-axis2
> Jean-Sebastien Delfino wrote:
>> I'm seeing the following error when building binding-ws-axis2. Anybody
>> else seeing this?
>>
> ...
>
> Well that was with a revision from yesterday, with SVN r679776 I'm getting
> another error in modules/binding-ws-wsdlgen.
>
> Running
> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.156 sec
> <<< FAILURE!
> testGenerate(org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase)
> Time elapsed: 0.139 sec <<< ERROR!
> java.lang.RuntimeException:
> org.apache.ws.commons.schema.XmlSchemaException:
> other.ws.binding.sca.tuscany.apache.org
> at
> org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1886)
> at
> org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:1620)
> at
> org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:175)
> at
> org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:82)
> at
> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:359)
> at
> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:353)
> at
> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.loadXSD(Interface2WSDLGenerator.java:402)
> at
> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.addSchemaExtension(Interface2WSDLGenerator.java:384)
> at
> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.generate(Interface2WSDLGenerator.java:256)
> at
> org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase.testGenerate(Interface2WSDLGeneratorTestCase.java:57)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
> at
> org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
> at
> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
> at
> org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
> at
> org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
> at
> org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75)
> at
> org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36)
> at
> org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
> at
> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
> at
> org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
> at
> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308)
> at
> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
> Caused by: org.apache.ws.commons.schema.XmlSchemaException:
> other.ws.binding.sca.tuscany.apache.org
> at
> org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:308)
> at
> org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1884)
> ... 33 more
>
> --
> Jean-Sebastien
Re: Policy error building binding-ws-axis2, was: Error building binding-ws-axis2
Posted by Raymond Feng <en...@gmail.com>.
Let's go ahead to make 1.3 release without any actions to TUSCANY-2499. We'll continue the discussions around the policy stuff and hopefully we'll come out a better solution for future releases.
Thanks,
Raymond
From: Simon Laws
Sent: Monday, July 28, 2008 11:44 AM
To: dev@tuscany.apache.org ; antelder@apache.org
Subject: Re: Policy error building binding-ws-axis2, was: Error building binding-ws-axis2
On Mon, Jul 28, 2008 at 7:39 PM, ant elder <an...@gmail.com> wrote:
On Mon, Jul 28, 2008 at 7:33 PM, Simon Laws <si...@googlemail.com> wrote:
On Mon, Jul 28, 2008 at 7:02 PM, Ramkumar R <ra...@gmail.com> wrote:
Hi Ant,
I believe, this issue cropped up due to a fix provided through TUSCANY-2354, this issue did not exist before in 1.2 release as the code did not do proper validation to ensure that all the intents and policysets are resolved. TUSCANY-2354 came up with a fix as to resolve all the simple intents first and then simple policysets and then the referred policysets and so on, which i believe worked for most of the validation.
Currently, I am able to resolve this issue by applying this patch.... (reason: a confilict exist wsClientAuthenticationPolicy)
Index: modules/binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/definitions.xml
===================================================================
--- modules/binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/definitions.xml (revision 680260)
+++ modules/binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/definitions.xml (working copy)
@@ -37,7 +37,7 @@
</tuscany:wsConfigParam>
</sca:policySet>
- <sca:policySet name="wsClientAuthenticationPolicy"
+ <sca:policySet name="wsClientAuthenticationPolicy2"
provides="tuscany:wsAuthentication"
appliesTo="//sca:binding.ws">
<tuscany:wsConfigParam>
Index: src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/WSSecurityAuthentication.composite
===================================================================
--- modules/binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/WSSecurityAuthentication.composite (revision 680260)
+++ modules/binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/WSSecurityAuthentication.composite (working copy)
@@ -41,7 +41,7 @@
<reference name="helloWorldWS" />
</component>
- <reference name="helloWorldWS" promote="HelloWorldComponent/helloWorldWS" policySets="tuscany:wsClientAuthenticationPolicy">
+ <reference name="helloWorldWS" promote="HelloWorldComponent/helloWorldWS" policySets="tuscany:wsClientAuthenticationPolicy2">
<interface.wsdl interface="http://helloworld-om-uri#wsdl.interface(HelloWorld)" />
<binding.ws wsdlElement="http://helloworld-om-uri#wsdl.binding(HelloWorldSoapBinding)"
uri="http://localhost:8085/myExplicitURI"/>
Can anyone try this and let me know if this works.
NOTE: I also strongly believe that we need to address the issue of treating the definitions.xml as global to SCA domain, and try to resolve the policy artifacts once all the policy definitions are loaded.
On 7/28/08, ant elder <an...@gmail.com> wrote:
On Mon, Jul 28, 2008 at 6:20 PM, Jean-Sebastien Delfino <js...@apache.org> wrote:
Simon Laws wrote:
On Sat, Jul 26, 2008 at 7:27 PM, Raymond Feng <enjoyjava@gmail.com <ma...@gmail.com>> wrote:
I see the same regression too.
I further debugged the issue and found out the behavior depends the
order how artifacts are resolved.
1) The SCADefinitions model contains the Intent and PolicySet models
2) The PolicySet model may reference Intent models
Now say we have two definitions.xml file in the contribution, then
there will be two SCADefinitions objects: D1 and D2. Let's assume D1
contains I1 (Intent) and D2 contains P1 (PolicySet). P1 references
I1. The current code resolve D1 and D2 independently. If D1 is resolved before D2, then I1 is set to resolved and P1 will
be resolved as I1 is resolved. But if D2 is resolved before D1, the
P1 cannot be resolved as I1 is not resolved yet. This explains why
we see different behaviors.
It seems that we will have to resolve all the Intents first before
we can resolve PolictSets. This happens within one single
SCADefinitions but not across more than one SCADefinitions.
One hack would be to set Intent to resolved during the read phase.
Or we merge all the definitions before the resolve. Any suggestions?
Thanks,
Raymond
*From:* ant elder <ma...@gmail.com>
*Sent:* Saturday, July 26, 2008 4:20 AM
*To:* dev@tuscany.apache.org <ma...@tuscany.apache.org>
*Subject:* Re: Policy error building binding-ws-axis2, was: Error
building binding-ws-axis2
On Sat, Jul 26, 2008 at 2:38 AM, Jean-Sebastien Delfino
<jsdelfino@apache.org <ma...@apache.org>> wrote:
Raymond Feng wrote:
My guess is that the message complains:
With the following policySet:
<sca:policySet name="wsClientAuthenticationPolicy"
provides="tuscany:wsAuthentication"
appliesTo="//sca:binding.ws <http://binding.ws>">
"tuscany:wsAuthentication" is a provided intent by the
policy set and it cannot find the definition of intent
"tuscany:wsAuthentication".
Thanks,
Raymond
I've debugged, opened JIRA TUSCANY-2499 to track the problem and
committed a workaround (linked to 2499).
-- Jean-Sebastien
The work around breaks the build for me with the error below.
Backing out r679944 and everything is working ok in my environment.
Caused by: org.osoa.sca.ServiceRuntimeException: Provided Intent -
{http://tuscany.apache.org/xmlns/sca/1.0}wsAuthentica
<http://tuscany.apache.org/xmlns/sca/1.0%7DwsAuthentica>
tion not found for PolicySet
{http://tuscany.apache.org/xmlns/sca/1.0}wsClientAuthenticationPolicy
<http://tuscany.apache.org/xmlns/sca/1.0%7DwsClientAuthenticationPolicy>
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.analyseProblems(DefaultSCADomain.java:309)
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.addContribution(DefaultSCADomain.java:334)
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:183)
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.<init>(DefaultSCADomain.java:120)
at
org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:242)
... 20 more
...ant
Looking at the code it's interesting as ContributionServiceImp.processReadPhase() has special code to ensure that all the intents, policy sets etc from all definitions that are found during the read of a single contribution are added to the policyDefinitionsResolver. However when it comes to resolve time, as Raymond points out, the definitions.xml files are resolved independently, one at a time. Hence successful resolution is order dependent.
It seems to me that the solution to this depends on whether we take the spec at face value and assume that definitions.xml files that can appear in contributions in Tuscany are logically part of "a global, SCA Domain-wide file". Or if these individual definitions.xml files are subject to contribution import/export semantics?
If the former then we need some separate domain level processing (just before the build phase?) that does policy resolution. If the latter we need to make sure that the policy artifacts are resolved in the correct order across definitions files within a contribution rather than just within a single definitons.xml file.
To me the latter seems to fit the contribution model more accurately and hence it seems to be the more consistent of the two. Does seem to contradict the spec though.
Simon
Two thoughts:
- We should follow the spec and assume that definitions.xml are global in an SCA domain. Using the contribution resolve mechanism would contribute to pollute app artifacts (contributions) with Policy related declarations (as your app contributions would have to declare imports for the policies).
- This issue is just another manifestation of a bigger issue with the Contribution service which runs the resolve phase too early, per contribution, before all contributions are read. Fixing that will fix the Policy issue and will allow us to remove the workarounds in the current Policy processing code, which - although I didn't completely understand that code - seems to change the Intent's unresolved flag when it shouldn't.
--
Jean-Sebastien
Does anyone know if something changed recently to cause this problem or did it exist before in the 1.2 release? It sounds like it existed before and as it seems like a non-trivial fix I wondered if we could still release 1.3 anyway and try to fix this later in a 1.3.1 release?
...ant
--
Thanks & Regards,
Ramkumar Ramalingam
So am I right in thinking that this patch does not affect release 1.3?
Simon
That looks right to me, the change was in r675018 in trunk and thats not included the 1.3 branch.
...ant
OK, agreed. (I'm just running through the samples etc. now. It looks like Raymond has applied his patch so we just about good to go I think)
Simon
Re: Policy error building binding-ws-axis2, was: Error building binding-ws-axis2
Posted by Simon Laws <si...@googlemail.com>.
On Mon, Jul 28, 2008 at 7:39 PM, ant elder <an...@gmail.com> wrote:
>
>
> On Mon, Jul 28, 2008 at 7:33 PM, Simon Laws <si...@googlemail.com>wrote:
>
>>
>>
>> On Mon, Jul 28, 2008 at 7:02 PM, Ramkumar R <ra...@gmail.com>wrote:
>>
>>> Hi Ant,
>>> I believe, this issue cropped up due to a fix provided through
>>> TUSCANY-2354, this issue did not exist before in 1.2 release as the code did
>>> not do proper validation to ensure that all the intents and policysets are
>>> resolved. TUSCANY-2354 came up with a fix as to resolve all the simple
>>> intents first and then simple policysets and then the referred policysets
>>> and so on, which i believe worked for most of the validation.
>>>
>>> Currently, I am able to resolve this issue by applying this patch....
>>> (reason: a confilict exist wsClientAuthenticationPolicy)
>>>
>>> Index:
>>> modules/binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/definitions.xml
>>> ===================================================================
>>> ---
>>> modules/binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/definitions.xml (revision
>>> 680260)
>>> +++
>>> modules/binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/definitions.xml (working
>>> copy)
>>> @@ -37,7 +37,7 @@
>>> </tuscany:wsConfigParam>
>>> </sca:policySet>
>>>
>>> - <sca:policySet name="wsClientAuthenticationPolicy"
>>> + <sca:policySet name="wsClientAuthenticationPolicy2"
>>> provides="tuscany:wsAuthentication"
>>> appliesTo="//sca:binding.ws">
>>> <tuscany:wsConfigParam>
>>> Index:
>>> src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/WSSecurityAuthentication.composite
>>> ===================================================================
>>> ---
>>> modules/binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/WSSecurityAuthentication.composite (revision
>>> 680260)
>>> +++
>>> modules/binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/WSSecurityAuthentication.composite (working
>>> copy)
>>> @@ -41,7 +41,7 @@
>>> <reference name="helloWorldWS" />
>>> </component>
>>>
>>> - <reference name="helloWorldWS"
>>> promote="HelloWorldComponent/helloWorldWS"
>>> policySets="tuscany:wsClientAuthenticationPolicy">
>>> + <reference name="helloWorldWS"
>>> promote="HelloWorldComponent/helloWorldWS"
>>> policySets="tuscany:wsClientAuthenticationPolicy2">
>>> <interface.wsdl interface="
>>> http://helloworld-om-uri#wsdl.interface(HelloWorld<http://helloworld-om-uri/#wsdl.interface%28HelloWorld>)"
>>> />
>>> <binding.ws wsdlElement="
>>> http://helloworld-om-uri#wsdl.binding(HelloWorldSoapBinding<http://helloworld-om-uri/#wsdl.binding%28HelloWorldSoapBinding>
>>> )"
>>> uri="http://localhost:8085/myExplicitURI"/<http://localhost:8085/myExplicitURI%22/>
>>> >
>>>
>>> Can anyone try this and let me know if this works.
>>>
>>> NOTE: I also strongly believe that we need to address the issue of
>>> treating the definitions.xml as global to SCA domain, and try to resolve the
>>> policy artifacts once all the policy definitions are loaded.
>>>
>>>
>>> On 7/28/08, ant elder <an...@gmail.com> wrote:
>>>>
>>>>
>>>>
>>>> On Mon, Jul 28, 2008 at 6:20 PM, Jean-Sebastien Delfino <
>>>> jsdelfino@apache.org> wrote:
>>>>
>>>>> Simon Laws wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Sat, Jul 26, 2008 at 7:27 PM, Raymond Feng <enjoyjava@gmail.com<mailto:
>>>>>> enjoyjava@gmail.com>> wrote:
>>>>>>
>>>>>> I see the same regression too.
>>>>>> I further debugged the issue and found out the behavior depends
>>>>>> the
>>>>>> order how artifacts are resolved.
>>>>>> 1) The SCADefinitions model contains the Intent and PolicySet
>>>>>> models
>>>>>> 2) The PolicySet model may reference Intent models
>>>>>> Now say we have two definitions.xml file in the contribution,
>>>>>> then
>>>>>> there will be two SCADefinitions objects: D1 and D2. Let's assume
>>>>>> D1
>>>>>> contains I1 (Intent) and D2 contains P1 (PolicySet). P1 references
>>>>>> I1. The current code resolve D1 and D2 independently. If
>>>>>> D1 is resolved before D2, then I1 is set to resolved and P1 will
>>>>>> be resolved as I1 is resolved. But if D2 is resolved before D1, the
>>>>>> P1 cannot be resolved as I1 is not resolved yet. This explains why
>>>>>> we see different behaviors.
>>>>>> It seems that we will have to resolve all the Intents first
>>>>>> before
>>>>>> we can resolve PolictSets. This happens within one single
>>>>>> SCADefinitions but not across more than one SCADefinitions.
>>>>>> One hack would be to set Intent to resolved during the read
>>>>>> phase.
>>>>>> Or we merge all the definitions before the resolve. Any
>>>>>> suggestions?
>>>>>> Thanks,
>>>>>> Raymond
>>>>>>
>>>>>>
>>>>>> *From:* ant elder <ma...@gmail.com>
>>>>>> *Sent:* Saturday, July 26, 2008 4:20 AM
>>>>>> *To:* dev@tuscany.apache.org <ma...@tuscany.apache.org>
>>>>>> *Subject:* Re: Policy error building binding-ws-axis2, was: Error
>>>>>> building binding-ws-axis2
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sat, Jul 26, 2008 at 2:38 AM, Jean-Sebastien Delfino
>>>>>>
>>>>>> <jsdelfino@apache.org <ma...@apache.org>> wrote:
>>>>>>
>>>>>> Raymond Feng wrote:
>>>>>>
>>>>>> My guess is that the message complains:
>>>>>>
>>>>>> With the following policySet:
>>>>>>
>>>>>> <sca:policySet name="wsClientAuthenticationPolicy"
>>>>>> provides="tuscany:wsAuthentication"
>>>>>>
>>>>>> appliesTo="//sca:binding.ws <http://binding.ws>">
>>>>>>
>>>>>> "tuscany:wsAuthentication" is a provided intent by the
>>>>>> policy set and it cannot find the definition of intent
>>>>>> "tuscany:wsAuthentication".
>>>>>>
>>>>>> Thanks,
>>>>>> Raymond
>>>>>>
>>>>>>
>>>>>> I've debugged, opened JIRA TUSCANY-2499 to track the problem
>>>>>> and
>>>>>> committed a workaround (linked to 2499).
>>>>>>
>>>>>> -- Jean-Sebastien
>>>>>>
>>>>>>
>>>>>> The work around breaks the build for me with the error below.
>>>>>> Backing out r679944 and everything is working ok in my environment.
>>>>>>
>>>>>> Caused by: org.osoa.sca.ServiceRuntimeException: Provided Intent -
>>>>>> {http://tuscany.apache.org/xmlns/sca/1.0}wsAuthentica<http://tuscany.apache.org/xmlns/sca/1.0%7DwsAuthentica>
>>>>>>
>>>>>> <http://tuscany.apache.org/xmlns/sca/1.0%7DwsAuthentica>
>>>>>> tion not found for PolicySet
>>>>>> {
>>>>>> http://tuscany.apache.org/xmlns/sca/1.0}wsClientAuthenticationPolicy<http://tuscany.apache.org/xmlns/sca/1.0%7DwsClientAuthenticationPolicy>
>>>>>>
>>>>>> <
>>>>>> http://tuscany.apache.org/xmlns/sca/1.0%7DwsClientAuthenticationPolicy>
>>>>>>
>>>>>> at
>>>>>>
>>>>>> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.analyseProblems(DefaultSCADomain.java:309)
>>>>>> at
>>>>>>
>>>>>> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.addContribution(DefaultSCADomain.java:334)
>>>>>> at
>>>>>>
>>>>>> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:183)
>>>>>> at
>>>>>>
>>>>>> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.<init>(DefaultSCADomain.java:120)
>>>>>> at
>>>>>>
>>>>>> org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:242)
>>>>>> ... 20 more
>>>>>>
>>>>>> ...ant
>>>>>>
>>>>>> Looking at the code it's interesting as
>>>>>> ContributionServiceImp.processReadPhase() has special code to ensure that
>>>>>> all the intents, policy sets etc from all definitions that are found during
>>>>>> the read of a single contribution are added to the
>>>>>> policyDefinitionsResolver. However when it comes to resolve time, as Raymond
>>>>>> points out, the definitions.xml files are resolved independently, one at a
>>>>>> time. Hence successful resolution is order dependent.
>>>>>>
>>>>>> It seems to me that the solution to this depends on whether we take
>>>>>> the spec at face value and assume that definitions.xml files that can appear
>>>>>> in contributions in Tuscany are logically part of "a global, SCA Domain-wide
>>>>>> file". Or if these individual definitions.xml files are subject to
>>>>>> contribution import/export semantics?
>>>>>>
>>>>>> If the former then we need some separate domain level processing (just
>>>>>> before the build phase?) that does policy resolution. If the latter we need
>>>>>> to make sure that the policy artifacts are resolved in the correct order
>>>>>> across definitions files within a contribution rather than just within a
>>>>>> single definitons.xml file.
>>>>>>
>>>>>> To me the latter seems to fit the contribution model more accurately
>>>>>> and hence it seems to be the more consistent of the two. Does seem to
>>>>>> contradict the spec though.
>>>>>>
>>>>>> Simon
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> Two thoughts:
>>>>>
>>>>> - We should follow the spec and assume that definitions.xml are global
>>>>> in an SCA domain. Using the contribution resolve mechanism would contribute
>>>>> to pollute app artifacts (contributions) with Policy related declarations
>>>>> (as your app contributions would have to declare imports for the policies).
>>>>>
>>>>> - This issue is just another manifestation of a bigger issue with the
>>>>> Contribution service which runs the resolve phase too early, per
>>>>> contribution, before all contributions are read. Fixing that will fix the
>>>>> Policy issue and will allow us to remove the workarounds in the current
>>>>> Policy processing code, which - although I didn't completely understand that
>>>>> code - seems to change the Intent's unresolved flag when it shouldn't.
>>>>>
>>>>> --
>>>>> Jean-Sebastien
>>>>>
>>>>
>>>> Does anyone know if something changed recently to cause this problem or
>>>> did it exist before in the 1.2 release? It sounds like it existed before and
>>>> as it seems like a non-trivial fix I wondered if we could still release 1.3
>>>> anyway and try to fix this later in a 1.3.1 release?
>>>>
>>>> ...ant
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Thanks & Regards,
>>> Ramkumar Ramalingam
>>
>>
>> So am I right in thinking that this patch does not affect release 1.3?
>>
>> Simon
>>
>
> That looks right to me, the change was in r675018 in trunk and thats not
> included the 1.3 branch.
>
> ...ant
>
>
>
OK, agreed. (I'm just running through the samples etc. now. It looks like
Raymond has applied his patch so we just about good to go I think)
Simon
Re: Policy error building binding-ws-axis2, was: Error building binding-ws-axis2
Posted by ant elder <an...@gmail.com>.
On Mon, Jul 28, 2008 at 7:33 PM, Simon Laws <si...@googlemail.com>wrote:
>
>
> On Mon, Jul 28, 2008 at 7:02 PM, Ramkumar R <ra...@gmail.com> wrote:
>
>> Hi Ant,
>> I believe, this issue cropped up due to a fix provided through
>> TUSCANY-2354, this issue did not exist before in 1.2 release as the code did
>> not do proper validation to ensure that all the intents and policysets are
>> resolved. TUSCANY-2354 came up with a fix as to resolve all the simple
>> intents first and then simple policysets and then the referred policysets
>> and so on, which i believe worked for most of the validation.
>>
>> Currently, I am able to resolve this issue by applying this patch....
>> (reason: a confilict exist wsClientAuthenticationPolicy)
>>
>> Index:
>> modules/binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/definitions.xml
>> ===================================================================
>> ---
>> modules/binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/definitions.xml (revision
>> 680260)
>> +++
>> modules/binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/definitions.xml (working
>> copy)
>> @@ -37,7 +37,7 @@
>> </tuscany:wsConfigParam>
>> </sca:policySet>
>>
>> - <sca:policySet name="wsClientAuthenticationPolicy"
>> + <sca:policySet name="wsClientAuthenticationPolicy2"
>> provides="tuscany:wsAuthentication"
>> appliesTo="//sca:binding.ws">
>> <tuscany:wsConfigParam>
>> Index:
>> src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/WSSecurityAuthentication.composite
>> ===================================================================
>> ---
>> modules/binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/WSSecurityAuthentication.composite (revision
>> 680260)
>> +++
>> modules/binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/WSSecurityAuthentication.composite (working
>> copy)
>> @@ -41,7 +41,7 @@
>> <reference name="helloWorldWS" />
>> </component>
>>
>> - <reference name="helloWorldWS"
>> promote="HelloWorldComponent/helloWorldWS"
>> policySets="tuscany:wsClientAuthenticationPolicy">
>> + <reference name="helloWorldWS"
>> promote="HelloWorldComponent/helloWorldWS"
>> policySets="tuscany:wsClientAuthenticationPolicy2">
>> <interface.wsdl interface="
>> http://helloworld-om-uri#wsdl.interface(HelloWorld<http://helloworld-om-uri/#wsdl.interface%28HelloWorld>)"
>> />
>> <binding.ws wsdlElement="
>> http://helloworld-om-uri#wsdl.binding(HelloWorldSoapBinding<http://helloworld-om-uri/#wsdl.binding%28HelloWorldSoapBinding>
>> )"
>> uri="http://localhost:8085/myExplicitURI"/<http://localhost:8085/myExplicitURI%22/>
>> >
>>
>> Can anyone try this and let me know if this works.
>>
>> NOTE: I also strongly believe that we need to address the issue of
>> treating the definitions.xml as global to SCA domain, and try to resolve the
>> policy artifacts once all the policy definitions are loaded.
>>
>>
>> On 7/28/08, ant elder <an...@gmail.com> wrote:
>>>
>>>
>>>
>>> On Mon, Jul 28, 2008 at 6:20 PM, Jean-Sebastien Delfino <
>>> jsdelfino@apache.org> wrote:
>>>
>>>> Simon Laws wrote:
>>>>
>>>>>
>>>>>
>>>>> On Sat, Jul 26, 2008 at 7:27 PM, Raymond Feng <enjoyjava@gmail.com<mailto:
>>>>> enjoyjava@gmail.com>> wrote:
>>>>>
>>>>> I see the same regression too.
>>>>> I further debugged the issue and found out the behavior depends
>>>>> the
>>>>> order how artifacts are resolved.
>>>>> 1) The SCADefinitions model contains the Intent and PolicySet
>>>>> models
>>>>> 2) The PolicySet model may reference Intent models
>>>>> Now say we have two definitions.xml file in the contribution,
>>>>> then
>>>>> there will be two SCADefinitions objects: D1 and D2. Let's assume D1
>>>>> contains I1 (Intent) and D2 contains P1 (PolicySet). P1 references
>>>>> I1. The current code resolve D1 and D2 independently. If D1
>>>>> is resolved before D2, then I1 is set to resolved and P1 will
>>>>> be resolved as I1 is resolved. But if D2 is resolved before D1, the
>>>>> P1 cannot be resolved as I1 is not resolved yet. This explains why
>>>>> we see different behaviors.
>>>>> It seems that we will have to resolve all the Intents first
>>>>> before
>>>>> we can resolve PolictSets. This happens within one single
>>>>> SCADefinitions but not across more than one SCADefinitions.
>>>>> One hack would be to set Intent to resolved during the read
>>>>> phase.
>>>>> Or we merge all the definitions before the resolve. Any suggestions?
>>>>> Thanks,
>>>>> Raymond
>>>>>
>>>>>
>>>>> *From:* ant elder <ma...@gmail.com>
>>>>> *Sent:* Saturday, July 26, 2008 4:20 AM
>>>>> *To:* dev@tuscany.apache.org <ma...@tuscany.apache.org>
>>>>> *Subject:* Re: Policy error building binding-ws-axis2, was: Error
>>>>> building binding-ws-axis2
>>>>>
>>>>>
>>>>>
>>>>> On Sat, Jul 26, 2008 at 2:38 AM, Jean-Sebastien Delfino
>>>>>
>>>>> <jsdelfino@apache.org <ma...@apache.org>> wrote:
>>>>>
>>>>> Raymond Feng wrote:
>>>>>
>>>>> My guess is that the message complains:
>>>>>
>>>>> With the following policySet:
>>>>>
>>>>> <sca:policySet name="wsClientAuthenticationPolicy"
>>>>> provides="tuscany:wsAuthentication"
>>>>>
>>>>> appliesTo="//sca:binding.ws <http://binding.ws>">
>>>>>
>>>>> "tuscany:wsAuthentication" is a provided intent by the
>>>>> policy set and it cannot find the definition of intent
>>>>> "tuscany:wsAuthentication".
>>>>>
>>>>> Thanks,
>>>>> Raymond
>>>>>
>>>>>
>>>>> I've debugged, opened JIRA TUSCANY-2499 to track the problem and
>>>>> committed a workaround (linked to 2499).
>>>>>
>>>>> -- Jean-Sebastien
>>>>>
>>>>>
>>>>> The work around breaks the build for me with the error below.
>>>>> Backing out r679944 and everything is working ok in my environment.
>>>>>
>>>>> Caused by: org.osoa.sca.ServiceRuntimeException: Provided Intent -
>>>>> {http://tuscany.apache.org/xmlns/sca/1.0}wsAuthentica<http://tuscany.apache.org/xmlns/sca/1.0%7DwsAuthentica>
>>>>>
>>>>> <http://tuscany.apache.org/xmlns/sca/1.0%7DwsAuthentica>
>>>>> tion not found for PolicySet
>>>>> {
>>>>> http://tuscany.apache.org/xmlns/sca/1.0}wsClientAuthenticationPolicy<http://tuscany.apache.org/xmlns/sca/1.0%7DwsClientAuthenticationPolicy>
>>>>>
>>>>> <
>>>>> http://tuscany.apache.org/xmlns/sca/1.0%7DwsClientAuthenticationPolicy>
>>>>>
>>>>> at
>>>>>
>>>>> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.analyseProblems(DefaultSCADomain.java:309)
>>>>> at
>>>>>
>>>>> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.addContribution(DefaultSCADomain.java:334)
>>>>> at
>>>>>
>>>>> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:183)
>>>>> at
>>>>>
>>>>> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.<init>(DefaultSCADomain.java:120)
>>>>> at
>>>>>
>>>>> org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:242)
>>>>> ... 20 more
>>>>>
>>>>> ...ant
>>>>>
>>>>> Looking at the code it's interesting as
>>>>> ContributionServiceImp.processReadPhase() has special code to ensure that
>>>>> all the intents, policy sets etc from all definitions that are found during
>>>>> the read of a single contribution are added to the
>>>>> policyDefinitionsResolver. However when it comes to resolve time, as Raymond
>>>>> points out, the definitions.xml files are resolved independently, one at a
>>>>> time. Hence successful resolution is order dependent.
>>>>>
>>>>> It seems to me that the solution to this depends on whether we take the
>>>>> spec at face value and assume that definitions.xml files that can appear in
>>>>> contributions in Tuscany are logically part of "a global, SCA Domain-wide
>>>>> file". Or if these individual definitions.xml files are subject to
>>>>> contribution import/export semantics?
>>>>>
>>>>> If the former then we need some separate domain level processing (just
>>>>> before the build phase?) that does policy resolution. If the latter we need
>>>>> to make sure that the policy artifacts are resolved in the correct order
>>>>> across definitions files within a contribution rather than just within a
>>>>> single definitons.xml file.
>>>>>
>>>>> To me the latter seems to fit the contribution model more accurately
>>>>> and hence it seems to be the more consistent of the two. Does seem to
>>>>> contradict the spec though.
>>>>>
>>>>> Simon
>>>>>
>>>>>
>>>>>
>>>>
>>>> Two thoughts:
>>>>
>>>> - We should follow the spec and assume that definitions.xml are global
>>>> in an SCA domain. Using the contribution resolve mechanism would contribute
>>>> to pollute app artifacts (contributions) with Policy related declarations
>>>> (as your app contributions would have to declare imports for the policies).
>>>>
>>>> - This issue is just another manifestation of a bigger issue with the
>>>> Contribution service which runs the resolve phase too early, per
>>>> contribution, before all contributions are read. Fixing that will fix the
>>>> Policy issue and will allow us to remove the workarounds in the current
>>>> Policy processing code, which - although I didn't completely understand that
>>>> code - seems to change the Intent's unresolved flag when it shouldn't.
>>>>
>>>> --
>>>> Jean-Sebastien
>>>>
>>>
>>> Does anyone know if something changed recently to cause this problem or
>>> did it exist before in the 1.2 release? It sounds like it existed before and
>>> as it seems like a non-trivial fix I wondered if we could still release 1.3
>>> anyway and try to fix this later in a 1.3.1 release?
>>>
>>> ...ant
>>>
>>>
>>
>>
>>
>> --
>> Thanks & Regards,
>> Ramkumar Ramalingam
>
>
> So am I right in thinking that this patch does not affect release 1.3?
>
> Simon
>
That looks right to me, the change was in r675018 in trunk and thats not
included the 1.3 branch.
...ant
Re: Policy error building binding-ws-axis2, was: Error building binding-ws-axis2
Posted by Simon Laws <si...@googlemail.com>.
On Mon, Jul 28, 2008 at 7:02 PM, Ramkumar R <ra...@gmail.com> wrote:
> Hi Ant,
> I believe, this issue cropped up due to a fix provided through
> TUSCANY-2354, this issue did not exist before in 1.2 release as the code did
> not do proper validation to ensure that all the intents and policysets are
> resolved. TUSCANY-2354 came up with a fix as to resolve all the simple
> intents first and then simple policysets and then the referred policysets
> and so on, which i believe worked for most of the validation.
>
> Currently, I am able to resolve this issue by applying this patch....
> (reason: a confilict exist wsClientAuthenticationPolicy)
>
> Index:
> modules/binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/definitions.xml
> ===================================================================
> ---
> modules/binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/definitions.xml (revision
> 680260)
> +++
> modules/binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/definitions.xml (working
> copy)
> @@ -37,7 +37,7 @@
> </tuscany:wsConfigParam>
> </sca:policySet>
>
> - <sca:policySet name="wsClientAuthenticationPolicy"
> + <sca:policySet name="wsClientAuthenticationPolicy2"
> provides="tuscany:wsAuthentication"
> appliesTo="//sca:binding.ws">
> <tuscany:wsConfigParam>
> Index:
> src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/WSSecurityAuthentication.composite
> ===================================================================
> ---
> modules/binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/WSSecurityAuthentication.composite (revision
> 680260)
> +++
> modules/binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/WSSecurityAuthentication.composite (working
> copy)
> @@ -41,7 +41,7 @@
> <reference name="helloWorldWS" />
> </component>
>
> - <reference name="helloWorldWS"
> promote="HelloWorldComponent/helloWorldWS"
> policySets="tuscany:wsClientAuthenticationPolicy">
> + <reference name="helloWorldWS"
> promote="HelloWorldComponent/helloWorldWS"
> policySets="tuscany:wsClientAuthenticationPolicy2">
> <interface.wsdl interface="
> http://helloworld-om-uri#wsdl.interface(HelloWorld<http://helloworld-om-uri/#wsdl.interface%28HelloWorld>)"
> />
> <binding.ws wsdlElement="
> http://helloworld-om-uri#wsdl.binding(HelloWorldSoapBinding<http://helloworld-om-uri/#wsdl.binding%28HelloWorldSoapBinding>
> )"
> uri="http://localhost:8085/myExplicitURI"/<http://localhost:8085/myExplicitURI%22/>
> >
>
> Can anyone try this and let me know if this works.
>
> NOTE: I also strongly believe that we need to address the issue of treating
> the definitions.xml as global to SCA domain, and try to resolve the policy
> artifacts once all the policy definitions are loaded.
>
>
> On 7/28/08, ant elder <an...@gmail.com> wrote:
>>
>>
>>
>> On Mon, Jul 28, 2008 at 6:20 PM, Jean-Sebastien Delfino <
>> jsdelfino@apache.org> wrote:
>>
>>> Simon Laws wrote:
>>>
>>>>
>>>>
>>>> On Sat, Jul 26, 2008 at 7:27 PM, Raymond Feng <enjoyjava@gmail.com<mailto:
>>>> enjoyjava@gmail.com>> wrote:
>>>>
>>>> I see the same regression too.
>>>> I further debugged the issue and found out the behavior depends
>>>> the
>>>> order how artifacts are resolved.
>>>> 1) The SCADefinitions model contains the Intent and PolicySet
>>>> models
>>>> 2) The PolicySet model may reference Intent models
>>>> Now say we have two definitions.xml file in the contribution,
>>>> then
>>>> there will be two SCADefinitions objects: D1 and D2. Let's assume D1
>>>> contains I1 (Intent) and D2 contains P1 (PolicySet). P1 references
>>>> I1. The current code resolve D1 and D2 independently. If D1
>>>> is resolved before D2, then I1 is set to resolved and P1 will
>>>> be resolved as I1 is resolved. But if D2 is resolved before D1, the
>>>> P1 cannot be resolved as I1 is not resolved yet. This explains why
>>>> we see different behaviors.
>>>> It seems that we will have to resolve all the Intents first
>>>> before
>>>> we can resolve PolictSets. This happens within one single
>>>> SCADefinitions but not across more than one SCADefinitions.
>>>> One hack would be to set Intent to resolved during the read
>>>> phase.
>>>> Or we merge all the definitions before the resolve. Any suggestions?
>>>> Thanks,
>>>> Raymond
>>>>
>>>>
>>>> *From:* ant elder <ma...@gmail.com>
>>>> *Sent:* Saturday, July 26, 2008 4:20 AM
>>>> *To:* dev@tuscany.apache.org <ma...@tuscany.apache.org>
>>>> *Subject:* Re: Policy error building binding-ws-axis2, was: Error
>>>> building binding-ws-axis2
>>>>
>>>>
>>>>
>>>> On Sat, Jul 26, 2008 at 2:38 AM, Jean-Sebastien Delfino
>>>>
>>>> <jsdelfino@apache.org <ma...@apache.org>> wrote:
>>>>
>>>> Raymond Feng wrote:
>>>>
>>>> My guess is that the message complains:
>>>>
>>>> With the following policySet:
>>>>
>>>> <sca:policySet name="wsClientAuthenticationPolicy"
>>>> provides="tuscany:wsAuthentication"
>>>>
>>>> appliesTo="//sca:binding.ws <http://binding.ws>">
>>>>
>>>> "tuscany:wsAuthentication" is a provided intent by the
>>>> policy set and it cannot find the definition of intent
>>>> "tuscany:wsAuthentication".
>>>>
>>>> Thanks,
>>>> Raymond
>>>>
>>>>
>>>> I've debugged, opened JIRA TUSCANY-2499 to track the problem and
>>>> committed a workaround (linked to 2499).
>>>>
>>>> -- Jean-Sebastien
>>>>
>>>>
>>>> The work around breaks the build for me with the error below.
>>>> Backing out r679944 and everything is working ok in my environment.
>>>>
>>>> Caused by: org.osoa.sca.ServiceRuntimeException: Provided Intent -
>>>> {http://tuscany.apache.org/xmlns/sca/1.0}wsAuthentica<http://tuscany.apache.org/xmlns/sca/1.0%7DwsAuthentica>
>>>>
>>>> <http://tuscany.apache.org/xmlns/sca/1.0%7DwsAuthentica>
>>>> tion not found for PolicySet
>>>> {
>>>> http://tuscany.apache.org/xmlns/sca/1.0}wsClientAuthenticationPolicy<http://tuscany.apache.org/xmlns/sca/1.0%7DwsClientAuthenticationPolicy>
>>>>
>>>> <
>>>> http://tuscany.apache.org/xmlns/sca/1.0%7DwsClientAuthenticationPolicy>
>>>>
>>>> at
>>>>
>>>> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.analyseProblems(DefaultSCADomain.java:309)
>>>> at
>>>>
>>>> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.addContribution(DefaultSCADomain.java:334)
>>>> at
>>>>
>>>> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:183)
>>>> at
>>>>
>>>> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.<init>(DefaultSCADomain.java:120)
>>>> at
>>>>
>>>> org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:242)
>>>> ... 20 more
>>>>
>>>> ...ant
>>>>
>>>> Looking at the code it's interesting as
>>>> ContributionServiceImp.processReadPhase() has special code to ensure that
>>>> all the intents, policy sets etc from all definitions that are found during
>>>> the read of a single contribution are added to the
>>>> policyDefinitionsResolver. However when it comes to resolve time, as Raymond
>>>> points out, the definitions.xml files are resolved independently, one at a
>>>> time. Hence successful resolution is order dependent.
>>>>
>>>> It seems to me that the solution to this depends on whether we take the
>>>> spec at face value and assume that definitions.xml files that can appear in
>>>> contributions in Tuscany are logically part of "a global, SCA Domain-wide
>>>> file". Or if these individual definitions.xml files are subject to
>>>> contribution import/export semantics?
>>>>
>>>> If the former then we need some separate domain level processing (just
>>>> before the build phase?) that does policy resolution. If the latter we need
>>>> to make sure that the policy artifacts are resolved in the correct order
>>>> across definitions files within a contribution rather than just within a
>>>> single definitons.xml file.
>>>>
>>>> To me the latter seems to fit the contribution model more accurately and
>>>> hence it seems to be the more consistent of the two. Does seem to contradict
>>>> the spec though.
>>>>
>>>> Simon
>>>>
>>>>
>>>>
>>>
>>> Two thoughts:
>>>
>>> - We should follow the spec and assume that definitions.xml are global in
>>> an SCA domain. Using the contribution resolve mechanism would contribute to
>>> pollute app artifacts (contributions) with Policy related declarations (as
>>> your app contributions would have to declare imports for the policies).
>>>
>>> - This issue is just another manifestation of a bigger issue with the
>>> Contribution service which runs the resolve phase too early, per
>>> contribution, before all contributions are read. Fixing that will fix the
>>> Policy issue and will allow us to remove the workarounds in the current
>>> Policy processing code, which - although I didn't completely understand that
>>> code - seems to change the Intent's unresolved flag when it shouldn't.
>>>
>>> --
>>> Jean-Sebastien
>>>
>>
>> Does anyone know if something changed recently to cause this problem or
>> did it exist before in the 1.2 release? It sounds like it existed before and
>> as it seems like a non-trivial fix I wondered if we could still release 1.3
>> anyway and try to fix this later in a 1.3.1 release?
>>
>> ...ant
>>
>>
>
>
>
> --
> Thanks & Regards,
> Ramkumar Ramalingam
So am I right in thinking that this patch does not affect release 1.3?
Simon
Re: Policy error building binding-ws-axis2, was: Error building binding-ws-axis2
Posted by Ramkumar R <ra...@gmail.com>.
Hi Ant,
I believe, this issue cropped up due to a fix provided through TUSCANY-2354,
this issue did not exist before in 1.2 release as the code did not do proper
validation to ensure that all the intents and policysets are resolved.
TUSCANY-2354 came up with a fix as to resolve all the simple intents first
and then simple policysets and then the referred policysets and so on, which
i believe worked for most of the validation.
Currently, I am able to resolve this issue by applying this patch....
(reason: a confilict exist wsClientAuthenticationPolicy)
Index:
modules/binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/definitions.xml
===================================================================
---
modules/binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/definitions.xml
(revision
680260)
+++
modules/binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/definitions.xml
(working
copy)
@@ -37,7 +37,7 @@
</tuscany:wsConfigParam>
</sca:policySet>
- <sca:policySet name="wsClientAuthenticationPolicy"
+ <sca:policySet name="wsClientAuthenticationPolicy2"
provides="tuscany:wsAuthentication"
appliesTo="//sca:binding.ws">
<tuscany:wsConfigParam>
Index:
src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/WSSecurityAuthentication.composite
===================================================================
---
modules/binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/WSSecurityAuthentication.composite
(revision
680260)
+++
modules/binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/configparams/WSSecurityAuthentication.composite
(working
copy)
@@ -41,7 +41,7 @@
<reference name="helloWorldWS" />
</component>
- <reference name="helloWorldWS"
promote="HelloWorldComponent/helloWorldWS"
policySets="tuscany:wsClientAuthenticationPolicy">
+ <reference name="helloWorldWS"
promote="HelloWorldComponent/helloWorldWS"
policySets="tuscany:wsClientAuthenticationPolicy2">
<interface.wsdl interface="
http://helloworld-om-uri#wsdl.interface(HelloWorld<http://helloworld-om-uri/#wsdl.interface(HelloWorld>)"
/>
<binding.ws wsdlElement="
http://helloworld-om-uri#wsdl.binding(HelloWorldSoapBinding<http://helloworld-om-uri/#wsdl.binding(HelloWorldSoapBinding>
)"
uri="http://localhost:8085/myExplicitURI"/>
Can anyone try this and let me know if this works.
NOTE: I also strongly believe that we need to address the issue of treating
the definitions.xml as global to SCA domain, and try to resolve the policy
artifacts once all the policy definitions are loaded.
On 7/28/08, ant elder <an...@gmail.com> wrote:
>
>
>
> On Mon, Jul 28, 2008 at 6:20 PM, Jean-Sebastien Delfino <
> jsdelfino@apache.org> wrote:
>
>> Simon Laws wrote:
>>
>>>
>>>
>>> On Sat, Jul 26, 2008 at 7:27 PM, Raymond Feng <enjoyjava@gmail.com<mailto:
>>> enjoyjava@gmail.com>> wrote:
>>>
>>> I see the same regression too.
>>> I further debugged the issue and found out the behavior depends
>>> the
>>> order how artifacts are resolved.
>>> 1) The SCADefinitions model contains the Intent and PolicySet
>>> models
>>> 2) The PolicySet model may reference Intent models
>>> Now say we have two definitions.xml file in the contribution, then
>>> there will be two SCADefinitions objects: D1 and D2. Let's assume D1
>>> contains I1 (Intent) and D2 contains P1 (PolicySet). P1 references
>>> I1. The current code resolve D1 and D2 independently. If D1
>>> is resolved before D2, then I1 is set to resolved and P1 will
>>> be resolved as I1 is resolved. But if D2 is resolved before D1, the
>>> P1 cannot be resolved as I1 is not resolved yet. This explains why
>>> we see different behaviors.
>>> It seems that we will have to resolve all the Intents first before
>>> we can resolve PolictSets. This happens within one single
>>> SCADefinitions but not across more than one SCADefinitions.
>>> One hack would be to set Intent to resolved during the read phase.
>>> Or we merge all the definitions before the resolve. Any suggestions?
>>> Thanks,
>>> Raymond
>>>
>>>
>>> *From:* ant elder <ma...@gmail.com>
>>> *Sent:* Saturday, July 26, 2008 4:20 AM
>>> *To:* dev@tuscany.apache.org <ma...@tuscany.apache.org>
>>> *Subject:* Re: Policy error building binding-ws-axis2, was: Error
>>> building binding-ws-axis2
>>>
>>>
>>>
>>> On Sat, Jul 26, 2008 at 2:38 AM, Jean-Sebastien Delfino
>>>
>>> <jsdelfino@apache.org <ma...@apache.org>> wrote:
>>>
>>> Raymond Feng wrote:
>>>
>>> My guess is that the message complains:
>>>
>>> With the following policySet:
>>>
>>> <sca:policySet name="wsClientAuthenticationPolicy"
>>> provides="tuscany:wsAuthentication"
>>>
>>> appliesTo="//sca:binding.ws <http://binding.ws>">
>>>
>>> "tuscany:wsAuthentication" is a provided intent by the
>>> policy set and it cannot find the definition of intent
>>> "tuscany:wsAuthentication".
>>>
>>> Thanks,
>>> Raymond
>>>
>>>
>>> I've debugged, opened JIRA TUSCANY-2499 to track the problem and
>>> committed a workaround (linked to 2499).
>>>
>>> -- Jean-Sebastien
>>>
>>>
>>> The work around breaks the build for me with the error below.
>>> Backing out r679944 and everything is working ok in my environment.
>>>
>>> Caused by: org.osoa.sca.ServiceRuntimeException: Provided Intent -
>>> {http://tuscany.apache.org/xmlns/sca/1.0}wsAuthentica<http://tuscany.apache.org/xmlns/sca/1.0%7DwsAuthentica>
>>>
>>> <http://tuscany.apache.org/xmlns/sca/1.0%7DwsAuthentica>
>>> tion not found for PolicySet
>>> {http://tuscany.apache.org/xmlns/sca/1.0}wsClientAuthenticationPolicy<http://tuscany.apache.org/xmlns/sca/1.0%7DwsClientAuthenticationPolicy>
>>>
>>> <
>>> http://tuscany.apache.org/xmlns/sca/1.0%7DwsClientAuthenticationPolicy>
>>> at
>>>
>>> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.analyseProblems(DefaultSCADomain.java:309)
>>> at
>>>
>>> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.addContribution(DefaultSCADomain.java:334)
>>> at
>>>
>>> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:183)
>>> at
>>>
>>> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.<init>(DefaultSCADomain.java:120)
>>> at
>>>
>>> org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:242)
>>> ... 20 more
>>>
>>> ...ant
>>>
>>> Looking at the code it's interesting as
>>> ContributionServiceImp.processReadPhase() has special code to ensure that
>>> all the intents, policy sets etc from all definitions that are found during
>>> the read of a single contribution are added to the
>>> policyDefinitionsResolver. However when it comes to resolve time, as Raymond
>>> points out, the definitions.xml files are resolved independently, one at a
>>> time. Hence successful resolution is order dependent.
>>>
>>> It seems to me that the solution to this depends on whether we take the
>>> spec at face value and assume that definitions.xml files that can appear in
>>> contributions in Tuscany are logically part of "a global, SCA Domain-wide
>>> file". Or if these individual definitions.xml files are subject to
>>> contribution import/export semantics?
>>>
>>> If the former then we need some separate domain level processing (just
>>> before the build phase?) that does policy resolution. If the latter we need
>>> to make sure that the policy artifacts are resolved in the correct order
>>> across definitions files within a contribution rather than just within a
>>> single definitons.xml file.
>>>
>>> To me the latter seems to fit the contribution model more accurately and
>>> hence it seems to be the more consistent of the two. Does seem to contradict
>>> the spec though.
>>>
>>> Simon
>>>
>>>
>>>
>>
>> Two thoughts:
>>
>> - We should follow the spec and assume that definitions.xml are global in
>> an SCA domain. Using the contribution resolve mechanism would contribute to
>> pollute app artifacts (contributions) with Policy related declarations (as
>> your app contributions would have to declare imports for the policies).
>>
>> - This issue is just another manifestation of a bigger issue with the
>> Contribution service which runs the resolve phase too early, per
>> contribution, before all contributions are read. Fixing that will fix the
>> Policy issue and will allow us to remove the workarounds in the current
>> Policy processing code, which - although I didn't completely understand that
>> code - seems to change the Intent's unresolved flag when it shouldn't.
>>
>> --
>> Jean-Sebastien
>>
>
> Does anyone know if something changed recently to cause this problem or did
> it exist before in the 1.2 release? It sounds like it existed before and as
> it seems like a non-trivial fix I wondered if we could still release 1.3
> anyway and try to fix this later in a 1.3.1 release?
>
> ...ant
>
>
--
Thanks & Regards,
Ramkumar Ramalingam
Re: Policy error building binding-ws-axis2, was: Error building binding-ws-axis2
Posted by ant elder <an...@gmail.com>.
On Mon, Jul 28, 2008 at 6:20 PM, Jean-Sebastien Delfino <
jsdelfino@apache.org> wrote:
> Simon Laws wrote:
>
>>
>>
>> On Sat, Jul 26, 2008 at 7:27 PM, Raymond Feng <enjoyjava@gmail.com<mailto:
>> enjoyjava@gmail.com>> wrote:
>>
>> I see the same regression too.
>> I further debugged the issue and found out the behavior depends the
>> order how artifacts are resolved.
>> 1) The SCADefinitions model contains the Intent and PolicySet
>> models
>> 2) The PolicySet model may reference Intent models
>> Now say we have two definitions.xml file in the contribution, then
>> there will be two SCADefinitions objects: D1 and D2. Let's assume D1
>> contains I1 (Intent) and D2 contains P1 (PolicySet). P1 references
>> I1. The current code resolve D1 and D2 independently. If D1 is
>> resolved before D2, then I1 is set to resolved and P1 will
>> be resolved as I1 is resolved. But if D2 is resolved before D1, the
>> P1 cannot be resolved as I1 is not resolved yet. This explains why
>> we see different behaviors.
>> It seems that we will have to resolve all the Intents first before
>> we can resolve PolictSets. This happens within one single
>> SCADefinitions but not across more than one SCADefinitions.
>> One hack would be to set Intent to resolved during the read phase.
>> Or we merge all the definitions before the resolve. Any suggestions?
>> Thanks,
>> Raymond
>>
>> *From:* ant elder <ma...@gmail.com>
>> *Sent:* Saturday, July 26, 2008 4:20 AM
>> *To:* dev@tuscany.apache.org <ma...@tuscany.apache.org>
>> *Subject:* Re: Policy error building binding-ws-axis2, was: Error
>> building binding-ws-axis2
>>
>>
>>
>> On Sat, Jul 26, 2008 at 2:38 AM, Jean-Sebastien Delfino
>> <jsdelfino@apache.org <ma...@apache.org>> wrote:
>>
>> Raymond Feng wrote:
>>
>> My guess is that the message complains:
>>
>> With the following policySet:
>>
>> <sca:policySet name="wsClientAuthenticationPolicy"
>> provides="tuscany:wsAuthentication"
>> appliesTo="//sca:binding.ws <http://binding.ws>">
>>
>> "tuscany:wsAuthentication" is a provided intent by the
>> policy set and it cannot find the definition of intent
>> "tuscany:wsAuthentication".
>>
>> Thanks,
>> Raymond
>>
>>
>> I've debugged, opened JIRA TUSCANY-2499 to track the problem and
>> committed a workaround (linked to 2499).
>>
>> -- Jean-Sebastien
>>
>>
>> The work around breaks the build for me with the error below.
>> Backing out r679944 and everything is working ok in my environment.
>>
>> Caused by: org.osoa.sca.ServiceRuntimeException: Provided Intent -
>> {http://tuscany.apache.org/xmlns/sca/1.0}wsAuthentica<http://tuscany.apache.org/xmlns/sca/1.0%7DwsAuthentica>
>> <http://tuscany.apache.org/xmlns/sca/1.0%7DwsAuthentica>
>> tion not found for PolicySet
>> {http://tuscany.apache.org/xmlns/sca/1.0}wsClientAuthenticationPolicy<http://tuscany.apache.org/xmlns/sca/1.0%7DwsClientAuthenticationPolicy>
>> <
>> http://tuscany.apache.org/xmlns/sca/1.0%7DwsClientAuthenticationPolicy>
>> at
>>
>> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.analyseProblems(DefaultSCADomain.java:309)
>> at
>>
>> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.addContribution(DefaultSCADomain.java:334)
>> at
>>
>> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:183)
>> at
>>
>> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.<init>(DefaultSCADomain.java:120)
>> at
>>
>> org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:242)
>> ... 20 more
>>
>> ...ant
>>
>> Looking at the code it's interesting as
>> ContributionServiceImp.processReadPhase() has special code to ensure that
>> all the intents, policy sets etc from all definitions that are found during
>> the read of a single contribution are added to the
>> policyDefinitionsResolver. However when it comes to resolve time, as Raymond
>> points out, the definitions.xml files are resolved independently, one at a
>> time. Hence successful resolution is order dependent.
>>
>> It seems to me that the solution to this depends on whether we take the
>> spec at face value and assume that definitions.xml files that can appear in
>> contributions in Tuscany are logically part of "a global, SCA Domain-wide
>> file". Or if these individual definitions.xml files are subject to
>> contribution import/export semantics?
>>
>> If the former then we need some separate domain level processing (just
>> before the build phase?) that does policy resolution. If the latter we need
>> to make sure that the policy artifacts are resolved in the correct order
>> across definitions files within a contribution rather than just within a
>> single definitons.xml file.
>>
>> To me the latter seems to fit the contribution model more accurately and
>> hence it seems to be the more consistent of the two. Does seem to contradict
>> the spec though.
>>
>> Simon
>>
>>
> Two thoughts:
>
> - We should follow the spec and assume that definitions.xml are global in
> an SCA domain. Using the contribution resolve mechanism would contribute to
> pollute app artifacts (contributions) with Policy related declarations (as
> your app contributions would have to declare imports for the policies).
>
> - This issue is just another manifestation of a bigger issue with the
> Contribution service which runs the resolve phase too early, per
> contribution, before all contributions are read. Fixing that will fix the
> Policy issue and will allow us to remove the workarounds in the current
> Policy processing code, which - although I didn't completely understand that
> code - seems to change the Intent's unresolved flag when it shouldn't.
>
> --
> Jean-Sebastien
>
Does anyone know if something changed recently to cause this problem or did
it exist before in the 1.2 release? It sounds like it existed before and as
it seems like a non-trivial fix I wondered if we could still release 1.3
anyway and try to fix this later in a 1.3.1 release?
...ant
Re: Policy error building binding-ws-axis2, was: Error building binding-ws-axis2
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Simon Laws wrote:
>
>
> On Sat, Jul 26, 2008 at 7:27 PM, Raymond Feng <enjoyjava@gmail.com
> <ma...@gmail.com>> wrote:
>
> I see the same regression too.
>
> I further debugged the issue and found out the behavior depends the
> order how artifacts are resolved.
>
> 1) The SCADefinitions model contains the Intent and PolicySet models
> 2) The PolicySet model may reference Intent models
>
> Now say we have two definitions.xml file in the contribution, then
> there will be two SCADefinitions objects: D1 and D2. Let's assume D1
> contains I1 (Intent) and D2 contains P1 (PolicySet). P1 references
> I1. The current code resolve D1 and D2 independently.
>
> If D1 is resolved before D2, then I1 is set to resolved and P1 will
> be resolved as I1 is resolved. But if D2 is resolved before D1, the
> P1 cannot be resolved as I1 is not resolved yet. This explains why
> we see different behaviors.
>
> It seems that we will have to resolve all the Intents first before
> we can resolve PolictSets. This happens within one single
> SCADefinitions but not across more than one SCADefinitions.
>
> One hack would be to set Intent to resolved during the read phase.
> Or we merge all the definitions before the resolve. Any suggestions?
>
> Thanks,
> Raymond
>
> *From:* ant elder <ma...@gmail.com>
> *Sent:* Saturday, July 26, 2008 4:20 AM
> *To:* dev@tuscany.apache.org <ma...@tuscany.apache.org>
> *Subject:* Re: Policy error building binding-ws-axis2, was: Error
> building binding-ws-axis2
>
>
>
> On Sat, Jul 26, 2008 at 2:38 AM, Jean-Sebastien Delfino
> <jsdelfino@apache.org <ma...@apache.org>> wrote:
>
> Raymond Feng wrote:
>
> My guess is that the message complains:
>
> With the following policySet:
>
> <sca:policySet name="wsClientAuthenticationPolicy"
> provides="tuscany:wsAuthentication"
> appliesTo="//sca:binding.ws <http://binding.ws>">
>
> "tuscany:wsAuthentication" is a provided intent by the
> policy set and it cannot find the definition of intent
> "tuscany:wsAuthentication".
>
> Thanks,
> Raymond
>
>
> I've debugged, opened JIRA TUSCANY-2499 to track the problem and
> committed a workaround (linked to 2499).
>
> --
> Jean-Sebastien
>
>
> The work around breaks the build for me with the error below.
> Backing out r679944 and everything is working ok in my environment.
>
> Caused by: org.osoa.sca.ServiceRuntimeException: Provided Intent -
> {http://tuscany.apache.org/xmlns/sca/1.0}wsAuthentica
> <http://tuscany.apache.org/xmlns/sca/1.0%7DwsAuthentica>
> tion not found for PolicySet
> {http://tuscany.apache.org/xmlns/sca/1.0}wsClientAuthenticationPolicy
> <http://tuscany.apache.org/xmlns/sca/1.0%7DwsClientAuthenticationPolicy>
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.analyseProblems(DefaultSCADomain.java:309)
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.addContribution(DefaultSCADomain.java:334)
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:183)
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.<init>(DefaultSCADomain.java:120)
> at
> org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:242)
> ... 20 more
>
> ...ant
>
> Looking at the code it's interesting as
> ContributionServiceImp.processReadPhase() has special code to ensure
> that all the intents, policy sets etc from all definitions that are
> found during the read of a single contribution are added to the
> policyDefinitionsResolver. However when it comes to resolve time, as
> Raymond points out, the definitions.xml files are resolved
> independently, one at a time. Hence successful resolution is order
> dependent.
>
> It seems to me that the solution to this depends on whether we take the
> spec at face value and assume that definitions.xml files that can appear
> in contributions in Tuscany are logically part of "a global, SCA
> Domain-wide file". Or if these individual definitions.xml files are
> subject to contribution import/export semantics?
>
> If the former then we need some separate domain level processing (just
> before the build phase?) that does policy resolution. If the latter we
> need to make sure that the policy artifacts are resolved in the correct
> order across definitions files within a contribution rather than just
> within a single definitons.xml file.
>
> To me the latter seems to fit the contribution model more accurately and
> hence it seems to be the more consistent of the two. Does seem to
> contradict the spec though.
>
> Simon
>
Two thoughts:
- We should follow the spec and assume that definitions.xml are global
in an SCA domain. Using the contribution resolve mechanism would
contribute to pollute app artifacts (contributions) with Policy related
declarations (as your app contributions would have to declare imports
for the policies).
- This issue is just another manifestation of a bigger issue with the
Contribution service which runs the resolve phase too early, per
contribution, before all contributions are read. Fixing that will fix
the Policy issue and will allow us to remove the workarounds in the
current Policy processing code, which - although I didn't completely
understand that code - seems to change the Intent's unresolved flag when
it shouldn't.
--
Jean-Sebastien
Re: Policy error building binding-ws-axis2, was: Error building binding-ws-axis2
Posted by Simon Laws <si...@googlemail.com>.
On Sat, Jul 26, 2008 at 7:27 PM, Raymond Feng <en...@gmail.com> wrote:
> I see the same regression too.
>
> I further debugged the issue and found out the behavior depends the order
> how artifacts are resolved.
>
> 1) The SCADefinitions model contains the Intent and PolicySet models
> 2) The PolicySet model may reference Intent models
>
> Now say we have two definitions.xml file in the contribution, then there
> will be two SCADefinitions objects: D1 and D2. Let's assume D1 contains I1
> (Intent) and D2 contains P1 (PolicySet). P1 references I1. The current
> code resolve D1 and D2 independently.
>
> If D1 is resolved before D2, then I1 is set to resolved and P1 will be
> resolved as I1 is resolved. But if D2 is resolved before D1, the P1 cannot
> be resolved as I1 is not resolved yet. This explains why we see different
> behaviors.
>
> It seems that we will have to resolve all the Intents first before we can
> resolve PolictSets. This happens within one single SCADefinitions but not
> across more than one SCADefinitions.
>
> One hack would be to set Intent to resolved during the read phase. Or we
> merge all the definitions before the resolve. Any suggestions?
>
> Thanks,
> Raymond
>
> *From:* ant elder <an...@gmail.com>
> *Sent:* Saturday, July 26, 2008 4:20 AM
> *To:* dev@tuscany.apache.org
> *Subject:* Re: Policy error building binding-ws-axis2, was: Error building
> binding-ws-axis2
>
>
>
> On Sat, Jul 26, 2008 at 2:38 AM, Jean-Sebastien Delfino <
> jsdelfino@apache.org> wrote:
>
>> Raymond Feng wrote:
>>
>>> My guess is that the message complains:
>>>
>>> With the following policySet:
>>>
>>> <sca:policySet name="wsClientAuthenticationPolicy"
>>> provides="tuscany:wsAuthentication"
>>> appliesTo="//sca:binding.ws">
>>>
>>> "tuscany:wsAuthentication" is a provided intent by the policy set and it
>>> cannot find the definition of intent "tuscany:wsAuthentication".
>>>
>>> Thanks,
>>> Raymond
>>>
>>>
>> I've debugged, opened JIRA TUSCANY-2499 to track the problem and committed
>> a workaround (linked to 2499).
>>
>> --
>> Jean-Sebastien
>>
>
> The work around breaks the build for me with the error below. Backing out
> r679944 and everything is working ok in my environment.
>
> Caused by: org.osoa.sca.ServiceRuntimeException: Provided Intent - {
> http://tuscany.apache.org/xmlns/sca/1.0}wsAuthentica<http://tuscany.apache.org/xmlns/sca/1.0%7DwsAuthentica>
> tion not found for PolicySet {
> http://tuscany.apache.org/xmlns/sca/1.0}wsClientAuthenticationPolicy<http://tuscany.apache.org/xmlns/sca/1.0%7DwsClientAuthenticationPolicy>
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.analyseProblems(DefaultSCADomain.java:309)
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.addContribution(DefaultSCADomain.java:334)
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:183)
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.<init>(DefaultSCADomain.java:120)
> at
> org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:242)
> ... 20 more
>
> ...ant
>
> Looking at the code it's interesting as
ContributionServiceImp.processReadPhase() has special code to ensure that
all the intents, policy sets etc from all definitions that are found during
the read of a single contribution are added to the
policyDefinitionsResolver. However when it comes to resolve time, as Raymond
points out, the definitions.xml files are resolved independently, one at a
time. Hence successful resolution is order dependent.
It seems to me that the solution to this depends on whether we take the spec
at face value and assume that definitions.xml files that can appear in
contributions in Tuscany are logically part of "a global, SCA Domain-wide
file". Or if these individual definitions.xml files are subject to
contribution import/export semantics?
If the former then we need some separate domain level processing (just
before the build phase?) that does policy resolution. If the latter we need
to make sure that the policy artifacts are resolved in the correct order
across definitions files within a contribution rather than just within a
single definitons.xml file.
To me the latter seems to fit the contribution model more accurately and
hence it seems to be the more consistent of the two. Does seem to contradict
the spec though.
Simon
Re: Policy error building binding-ws-axis2, was: Error building binding-ws-axis2
Posted by Ramkumar R <ra...@gmail.com>.
Hi Raymond,
I believe I know about this issue, I saw the same issue some time back and
fixed it with TUSCANY-2354. As you can see from the patch file, to fix the
issue i removed the existing intent definitions
<sca:policySet name="wsClientAuthenticationPolicy"
provides="tuscany:wsAuthentication"
appliesTo="//sca:binding.ws">
from
binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/mixed/definitions.xml
and from
binding-ws-axis2/src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/wspolicy/definitions.xml.
Not sure, why we see this again. Let me have a look at it, and post my
findings soon. Thanks.
On Sat, Jul 26, 2008 at 11:57 PM, Raymond Feng <en...@gmail.com> wrote:
> I see the same regression too.
>
> I further debugged the issue and found out the behavior depends the order
> how artifacts are resolved.
>
> 1) The SCADefinitions model contains the Intent and PolicySet models
> 2) The PolicySet model may reference Intent models
>
> Now say we have two definitions.xml file in the contribution, then there
> will be two SCADefinitions objects: D1 and D2. Let's assume D1 contains I1
> (Intent) and D2 contains P1 (PolicySet). P1 references I1. The current
> code resolve D1 and D2 independently.
>
> If D1 is resolved before D2, then I1 is set to resolved and P1 will be
> resolved as I1 is resolved. But if D2 is resolved before D1, the P1 cannot
> be resolved as I1 is not resolved yet. This explains why we see different
> behaviors.
>
> It seems that we will have to resolve all the Intents first before we can
> resolve PolictSets. This happens within one single SCADefinitions but not
> across more than one SCADefinitions.
>
> One hack would be to set Intent to resolved during the read phase. Or we
> merge all the definitions before the resolve. Any suggestions?
>
> Thanks,
> Raymond
>
> *From:* ant elder <an...@gmail.com>
> *Sent:* Saturday, July 26, 2008 4:20 AM
> *To:* dev@tuscany.apache.org
> *Subject:* Re: Policy error building binding-ws-axis2, was: Error building
> binding-ws-axis2
>
>
>
> On Sat, Jul 26, 2008 at 2:38 AM, Jean-Sebastien Delfino <
> jsdelfino@apache.org> wrote:
>
>> Raymond Feng wrote:
>>
>>> My guess is that the message complains:
>>>
>>> With the following policySet:
>>>
>>> <sca:policySet name="wsClientAuthenticationPolicy"
>>> provides="tuscany:wsAuthentication"
>>> appliesTo="//sca:binding.ws">
>>>
>>> "tuscany:wsAuthentication" is a provided intent by the policy set and it
>>> cannot find the definition of intent "tuscany:wsAuthentication".
>>>
>>> Thanks,
>>> Raymond
>>>
>>>
>> I've debugged, opened JIRA TUSCANY-2499 to track the problem and committed
>> a workaround (linked to 2499).
>>
>> --
>> Jean-Sebastien
>>
>
> The work around breaks the build for me with the error below. Backing out
> r679944 and everything is working ok in my environment.
>
> Caused by: org.osoa.sca.ServiceRuntimeException: Provided Intent - {
> http://tuscany.apache.org/xmlns/sca/1.0}wsAuthentica<http://tuscany.apache.org/xmlns/sca/1.0%7DwsAuthentica>
> tion not found for PolicySet {
> http://tuscany.apache.org/xmlns/sca/1.0}wsClientAuthenticationPolicy<http://tuscany.apache.org/xmlns/sca/1.0%7DwsClientAuthenticationPolicy>
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.analyseProblems(DefaultSCADomain.java:309)
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.addContribution(DefaultSCADomain.java:334)
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:183)
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.<init>(DefaultSCADomain.java:120)
> at
> org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:242)
> ... 20 more
>
> ...ant
>
>
--
Thanks & Regards,
Ramkumar Ramalingam
Re: Policy error building binding-ws-axis2, was: Error building binding-ws-axis2
Posted by Raymond Feng <en...@gmail.com>.
I see the same regression too.
I further debugged the issue and found out the behavior depends the order how artifacts are resolved.
1) The SCADefinitions model contains the Intent and PolicySet models
2) The PolicySet model may reference Intent models
Now say we have two definitions.xml file in the contribution, then there will be two SCADefinitions objects: D1 and D2. Let's assume D1 contains I1 (Intent) and D2 contains P1 (PolicySet). P1 references I1. The current code resolve D1 and D2 independently.
If D1 is resolved before D2, then I1 is set to resolved and P1 will be resolved as I1 is resolved. But if D2 is resolved before D1, the P1 cannot be resolved as I1 is not resolved yet. This explains why we see different behaviors.
It seems that we will have to resolve all the Intents first before we can resolve PolictSets. This happens within one single SCADefinitions but not across more than one SCADefinitions.
One hack would be to set Intent to resolved during the read phase. Or we merge all the definitions before the resolve. Any suggestions?
Thanks,
Raymond
From: ant elder
Sent: Saturday, July 26, 2008 4:20 AM
To: dev@tuscany.apache.org
Subject: Re: Policy error building binding-ws-axis2, was: Error building binding-ws-axis2
On Sat, Jul 26, 2008 at 2:38 AM, Jean-Sebastien Delfino <js...@apache.org> wrote:
Raymond Feng wrote:
My guess is that the message complains:
With the following policySet:
<sca:policySet name="wsClientAuthenticationPolicy"
provides="tuscany:wsAuthentication"
appliesTo="//sca:binding.ws">
"tuscany:wsAuthentication" is a provided intent by the policy set and it cannot find the definition of intent "tuscany:wsAuthentication".
Thanks,
Raymond
I've debugged, opened JIRA TUSCANY-2499 to track the problem and committed a workaround (linked to 2499).
--
Jean-Sebastien
The work around breaks the build for me with the error below. Backing out r679944 and everything is working ok in my environment.
Caused by: org.osoa.sca.ServiceRuntimeException: Provided Intent - {http://tuscany.apache.org/xmlns/sca/1.0}wsAuthentica
tion not found for PolicySet {http://tuscany.apache.org/xmlns/sca/1.0}wsClientAuthenticationPolicy
at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.analyseProblems(DefaultSCADomain.java:309)
at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.addContribution(DefaultSCADomain.java:334)
at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:183)
at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.<init>(DefaultSCADomain.java:120)
at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:242)
... 20 more
...ant
Re: Policy error building binding-ws-axis2, was: Error building binding-ws-axis2
Posted by ant elder <an...@gmail.com>.
On Sat, Jul 26, 2008 at 2:38 AM, Jean-Sebastien Delfino <
jsdelfino@apache.org> wrote:
> Raymond Feng wrote:
>
>> My guess is that the message complains:
>>
>> With the following policySet:
>>
>> <sca:policySet name="wsClientAuthenticationPolicy"
>> provides="tuscany:wsAuthentication"
>> appliesTo="//sca:binding.ws">
>>
>> "tuscany:wsAuthentication" is a provided intent by the policy set and it
>> cannot find the definition of intent "tuscany:wsAuthentication".
>>
>> Thanks,
>> Raymond
>>
>>
> I've debugged, opened JIRA TUSCANY-2499 to track the problem and committed
> a workaround (linked to 2499).
>
> --
> Jean-Sebastien
>
The work around breaks the build for me with the error below. Backing out
r679944 and everything is working ok in my environment.
Caused by: org.osoa.sca.ServiceRuntimeException: Provided Intent - {
http://tuscany.apache.org/xmlns/sca/1.0}wsAuthentica
tion not found for PolicySet {
http://tuscany.apache.org/xmlns/sca/1.0}wsClientAuthenticationPolicy
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.analyseProblems(DefaultSCADomain.java:309)
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.addContribution(DefaultSCADomain.java:334)
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:183)
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.<init>(DefaultSCADomain.java:120)
at
org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:242)
... 20 more
...ant
Re: Policy error building binding-ws-axis2, was: Error building binding-ws-axis2
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Raymond Feng wrote:
> My guess is that the message complains:
>
> With the following policySet:
>
> <sca:policySet name="wsClientAuthenticationPolicy"
> provides="tuscany:wsAuthentication"
> appliesTo="//sca:binding.ws">
>
> "tuscany:wsAuthentication" is a provided intent by the policy set and it
> cannot find the definition of intent "tuscany:wsAuthentication".
>
> Thanks,
> Raymond
>
I've debugged, opened JIRA TUSCANY-2499 to track the problem and
committed a workaround (linked to 2499).
--
Jean-Sebastien
Re: Policy error building binding-ws-axis2, was: Error building binding-ws-axis2
Posted by Raymond Feng <en...@gmail.com>.
My guess is that the message complains:
With the following policySet:
<sca:policySet name="wsClientAuthenticationPolicy"
provides="tuscany:wsAuthentication"
appliesTo="//sca:binding.ws">
"tuscany:wsAuthentication" is a provided intent by the policy set and it
cannot find the definition of intent "tuscany:wsAuthentication".
Thanks,
Raymond
--------------------------------------------------
From: "Jean-Sebastien Delfino" <js...@apache.org>
Sent: Friday, July 25, 2008 4:39 PM
To: <de...@tuscany.apache.org>
Subject: Policy error building binding-ws-axis2, was: Error building
binding-ws-axis2
> Raymond Feng wrote:
>> Can you try this patch?
>
> ...
> Sorry, it didn't fix it. I'm not too surprised as the error below says the
> problem is a "provided" intent cannot be found (while your patch was
> trying to "apply" an intent).
>
> However I'm just guessing as I'm a little confused by the error message
> and the policy definitions in the failing test case.
>
>>> org.osoa.sca.ServiceRuntimeException: Provided Intent -
>>> {http://tuscany.apache.org/xmlns/sca/1.0}wsAuthentication not found for
>>> PolicySet
>>> {http://tuscany.apache.org/xmlns/sca/1.0}wsClientAuthenticationIntegrityPolicy
>
> --
> Jean-Sebastien
Policy error building binding-ws-axis2, was: Error building binding-ws-axis2
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Raymond Feng wrote:
> Can you try this patch?
...
Sorry, it didn't fix it. I'm not too surprised as the error below says
the problem is a "provided" intent cannot be found (while your patch was
trying to "apply" an intent).
However I'm just guessing as I'm a little confused by the error message
and the policy definitions in the failing test case.
>> org.osoa.sca.ServiceRuntimeException: Provided Intent -
>> {http://tuscany.apache.org/xmlns/sca/1.0}wsAuthentication not found
>> for PolicySet
>> {http://tuscany.apache.org/xmlns/sca/1.0}wsClientAuthenticationIntegrityPolicy
--
Jean-Sebastien
Re: Error building binding-ws-axis2
Posted by Raymond Feng <en...@gmail.com>.
Hi,
Can you try this patch?
Index:
src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/mixed/definitions.xml
===================================================================
---
src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/mixed/definitions.xml (revision
679873)
+++
src/test/resources/org/apache/tuscany/sca/binding/ws/axis2/itests/policy/mixed/definitions.xml (working
copy)
@@ -23,6 +23,15 @@
xmlns:tuscany="http://tuscany.apache.org/xmlns/sca/1.0">
<!-- WS Security POLICY SETS -->
+ <!-- A policyset that uses WS Policy -->
+ <sca:intent name="wsAuthentication"
+ constrains="sca:binding.ws">
+ <description>
+ Communitcation thro this binding required Authentication.
+ </description>
+ </sca:intent>+
+ <!-- WS Security POLICY SETS -->
<sca:policySet name="wsAuthenticationPolicy"
provides="sca:authentication"
appliesTo="//sca:binding.ws"
Thanks,
Raymond
--------------------------------------------------
From: "Jean-Sebastien Delfino" <js...@apache.org>
Sent: Friday, July 25, 2008 3:45 PM
To: <de...@tuscany.apache.org>
Subject: Re: Error building binding-ws-axis2
> Jean-Sebastien Delfino wrote:
>> Jean-Sebastien Delfino wrote:
>>> I'm seeing the following error when building binding-ws-axis2. Anybody
>>> else seeing this?
>>>
>> ...
>>
>> Well that was with a revision from yesterday, with SVN r679776 I'm
>> getting another error in modules/binding-ws-wsdlgen.
>>
>
> So, the binding-ws-wsdlgen error is fixed, back to the error with
> binding-ws-axis2, now on SVN r679890, as you can see below, 26 out of 30
> tests are failing:
>
> testSOAP12Endpoint(org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.QuestionMarkWSDLTestCase)
> Time elapsed: 1.229 sec <<< ERROR!
> org.osoa.sca.ServiceRuntimeException:
> org.osoa.sca.ServiceRuntimeException: Provided Intent -
> {http://tuscany.apache.org/xmlns/sca/1.0}wsAuthentication not found for
> PolicySet
> {http://tuscany.apache.org/xmlns/sca/1.0}wsClientAuthenticationIntegrityPolicy
> at
> org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:276)
> at
> org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:70)
> at
> org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.QuestionMarkWSDLTestCase.setUp(QuestionMarkWSDLTestCase.java:130)
> at junit.framework.TestCase.runBare(TestCase.java:132)
> at junit.framework.TestResult$1.protect(TestResult.java:110)
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.framework.TestResult.run(TestResult.java:113)
> at junit.framework.TestCase.run(TestCase.java:124)
> at junit.framework.TestSuite.runTest(TestSuite.java:232)
> at junit.framework.TestSuite.run(TestSuite.java:227)
> at
> org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.java:35)
> at
> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308)
> at
> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
> Caused by: org.osoa.sca.ServiceRuntimeException: Provided Intent -
> {http://tuscany.apache.org/xmlns/sca/1.0}wsAuthentication not found for
> PolicySet
> {http://tuscany.apache.org/xmlns/sca/1.0}wsClientAuthenticationIntegrityPolicy
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.analyseProblems(DefaultSCADomain.java:309)
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.addContribution(DefaultSCADomain.java:334)
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:183)
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.<init>(DefaultSCADomain.java:120)
> at
> org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:242)
> ... 20 more
>
>
> Results :
>
> Tests in error:
>
> testHelloWorld(org.apache.tuscany.sca.binding.ws.axis2.itests.HelloWorldNoWSDLTestCase)
>
> testEchoFoo(org.apache.tuscany.sca.binding.ws.axis2.itests.HelloWorldNoWSDLTestCase)
>
> testCalculator(org.apache.tuscany.sca.binding.ws.axis2.itests.HelloWorldTestCase)
>
> testUriPrecedence(org.apache.tuscany.sca.binding.ws.axis2.itests.UriPrecedenceTestCase)
>
> testCalculator(org.apache.tuscany.sca.binding.ws.axis2.itests.epr.HelloWorldTestCase)
>
> testHelloWorld(org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.HelloWorldSOAP12TestCase)
>
> testHelloWorldSOAP(org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.HelloWorldSOAP12TestCase)
>
> testHelloWorldSOAP11(org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.HelloWorldSOAP12TestCase)
>
> testHelloWorldSOAP12(org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.HelloWorldSOAP12TestCase)
>
> testWSDLImportPortEndpoint(org.apache.tuscany.sca.binding.ws.axis2.itests.QuestionMarkWSDLImportTestCase)
>
> testWSDLPortEndpoint(org.apache.tuscany.sca.binding.ws.axis2.itests.QuestionMarkWSDLTestCase)
>
> testCustomEndpoint(org.apache.tuscany.sca.binding.ws.axis2.itests.QuestionMarkWSDLTestCase)
>
> testCalculator(org.apache.tuscany.sca.binding.ws.axis2.itests.endpoints.WSDLRelativeURITestCase)
>
> testHelloWorld(org.apache.tuscany.sca.binding.ws.axis2.itests.policy.mixed.WSSecurityMixedTestCase)
>
> testCalculator(org.apache.tuscany.sca.binding.ws.axis2.itests.endpoints.WSDLExplicitURITestCase)
>
> testHelloWorld(org.apache.tuscany.sca.binding.ws.axis2.itests.HelloWorldWSDLMergedTestCase)
>
> testHelloWorld(org.apache.tuscany.sca.binding.ws.axis2.itests.HelloWorldOMTestCase)
>
> testCalculator(org.apache.tuscany.sca.binding.ws.axis2.itests.endpoints.DefaultMultiServiceTestCase)
>
> testHelloWorld(org.apache.tuscany.sca.binding.ws.axis2.itests.policy.configparams.WSSecurityIntegrityTestCase)
>
> testCalculator(org.apache.tuscany.sca.binding.ws.axis2.itests.endpoints.DefaultSingleServiceTestCase)
>
> testHelloWorld(org.apache.tuscany.sca.binding.ws.axis2.itests.policy.wspolicy.WSSecurityIntegrityTestCase)
>
> testHelloWorld(org.apache.tuscany.sca.binding.ws.axis2.itests.policy.wspolicy.WSSecurityAuthenticationTestCase)
>
> testWSDLIncludePortEndpoint(org.apache.tuscany.sca.binding.ws.axis2.itests.QuestionMarkWSDLIncludeTestCase)
>
> testSOAPDefault(org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.QuestionMarkWSDLTestCase)
>
> testSOAP11Endpoint(org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.QuestionMarkWSDLTestCase)
>
> testSOAP12Endpoint(org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.QuestionMarkWSDLTestCase)
>
> Tests run: 30, Failures: 0, Errors: 26, Skipped: 0
>
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
>
> --
> Jean-Sebastien
Re: Error building binding-ws-axis2
Posted by ant elder <an...@gmail.com>.
On Fri, Jul 25, 2008 at 11:45 PM, Jean-Sebastien Delfino <
jsdelfino@apache.org> wrote:
> Jean-Sebastien Delfino wrote:
>
>> Jean-Sebastien Delfino wrote:
>>
>>> I'm seeing the following error when building binding-ws-axis2. Anybody
>>> else seeing this?
>>>
>>> ...
>>
>> Well that was with a revision from yesterday, with SVN r679776 I'm getting
>> another error in modules/binding-ws-wsdlgen.
>>
>>
> So, the binding-ws-wsdlgen error is fixed, back to the error with
> binding-ws-axis2, now on SVN r679890, as you can see below, 26 out of 30
> tests are failing:
>
> testSOAP12Endpoint(org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.QuestionMarkWSDLTestCase)
> Time elapsed: 1.229 sec <<< ERROR!
> org.osoa.sca.ServiceRuntimeException: org.osoa.sca.ServiceRuntimeException:
> Provided Intent - {
> http://tuscany.apache.org/xmlns/sca/1.0}wsAuthentication<http://tuscany.apache.org/xmlns/sca/1.0%7DwsAuthentication>not found for PolicySet {
> http://tuscany.apache.org/xmlns/sca/1.0}wsClientAuthenticationIntegrityPolicy<http://tuscany.apache.org/xmlns/sca/1.0%7DwsClientAuthenticationIntegrityPolicy>
> at
> org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:276)
> at
> org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:70)
> at
> org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.QuestionMarkWSDLTestCase.setUp(QuestionMarkWSDLTestCase.java:130)
> at junit.framework.TestCase.runBare(TestCase.java:132)
> at junit.framework.TestResult$1.protect(TestResult.java:110)
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.framework.TestResult.run(TestResult.java:113)
> at junit.framework.TestCase.run(TestCase.java:124)
> at junit.framework.TestSuite.runTest(TestSuite.java:232)
> at junit.framework.TestSuite.run(TestSuite.java:227)
> at
> org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.java:35)
> at
> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308)
> at
> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
> Caused by: org.osoa.sca.ServiceRuntimeException: Provided Intent - {
> http://tuscany.apache.org/xmlns/sca/1.0}wsAuthentication<http://tuscany.apache.org/xmlns/sca/1.0%7DwsAuthentication>not found for PolicySet {
> http://tuscany.apache.org/xmlns/sca/1.0}wsClientAuthenticationIntegrityPolicy<http://tuscany.apache.org/xmlns/sca/1.0%7DwsClientAuthenticationIntegrityPolicy>
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.analyseProblems(DefaultSCADomain.java:309)
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.addContribution(DefaultSCADomain.java:334)
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:183)
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.<init>(DefaultSCADomain.java:120)
> at
> org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:242)
> ... 20 more
>
>
> Results :
>
> Tests in error:
>
>
> testHelloWorld(org.apache.tuscany.sca.binding.ws.axis2.itests.HelloWorldNoWSDLTestCase)
>
>
> testEchoFoo(org.apache.tuscany.sca.binding.ws.axis2.itests.HelloWorldNoWSDLTestCase)
>
>
> testCalculator(org.apache.tuscany.sca.binding.ws.axis2.itests.HelloWorldTestCase)
>
>
> testUriPrecedence(org.apache.tuscany.sca.binding.ws.axis2.itests.UriPrecedenceTestCase)
>
>
> testCalculator(org.apache.tuscany.sca.binding.ws.axis2.itests.epr.HelloWorldTestCase)
>
>
> testHelloWorld(org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.HelloWorldSOAP12TestCase)
>
>
> testHelloWorldSOAP(org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.HelloWorldSOAP12TestCase)
>
>
> testHelloWorldSOAP11(org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.HelloWorldSOAP12TestCase)
>
>
> testHelloWorldSOAP12(org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.HelloWorldSOAP12TestCase)
>
>
> testWSDLImportPortEndpoint(org.apache.tuscany.sca.binding.ws.axis2.itests.QuestionMarkWSDLImportTestCase)
>
>
> testWSDLPortEndpoint(org.apache.tuscany.sca.binding.ws.axis2.itests.QuestionMarkWSDLTestCase)
>
>
> testCustomEndpoint(org.apache.tuscany.sca.binding.ws.axis2.itests.QuestionMarkWSDLTestCase)
>
>
> testCalculator(org.apache.tuscany.sca.binding.ws.axis2.itests.endpoints.WSDLRelativeURITestCase)
>
>
> testHelloWorld(org.apache.tuscany.sca.binding.ws.axis2.itests.policy.mixed.WSSecurityMixedTestCase)
>
>
> testCalculator(org.apache.tuscany.sca.binding.ws.axis2.itests.endpoints.WSDLExplicitURITestCase)
>
>
> testHelloWorld(org.apache.tuscany.sca.binding.ws.axis2.itests.HelloWorldWSDLMergedTestCase)
>
>
> testHelloWorld(org.apache.tuscany.sca.binding.ws.axis2.itests.HelloWorldOMTestCase)
>
>
> testCalculator(org.apache.tuscany.sca.binding.ws.axis2.itests.endpoints.DefaultMultiServiceTestCase)
>
>
> testHelloWorld(org.apache.tuscany.sca.binding.ws.axis2.itests.policy.configparams.WSSecurityIntegrityTestCase)
>
>
> testCalculator(org.apache.tuscany.sca.binding.ws.axis2.itests.endpoints.DefaultSingleServiceTestCase)
>
>
> testHelloWorld(org.apache.tuscany.sca.binding.ws.axis2.itests.policy.wspolicy.WSSecurityIntegrityTestCase)
>
>
> testHelloWorld(org.apache.tuscany.sca.binding.ws.axis2.itests.policy.wspolicy.WSSecurityAuthenticationTestCase)
>
>
> testWSDLIncludePortEndpoint(org.apache.tuscany.sca.binding.ws.axis2.itests.QuestionMarkWSDLIncludeTestCase)
>
>
> testSOAPDefault(org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.QuestionMarkWSDLTestCase)
>
>
> testSOAP11Endpoint(org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.QuestionMarkWSDLTestCase)
>
>
> testSOAP12Endpoint(org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.QuestionMarkWSDLTestCase)
>
> Tests run: 30, Failures: 0, Errors: 26, Skipped: 0
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
>
> --
> Jean-Sebastien
>
It still builds cleanly for me both before and after the JAXBTypeHelper
change, both 1.3 branch and trunk.
Is there any explanation why Simon and i aren't seeing any problem from that
system id issue?
...ant
Re: Error building binding-ws-axis2
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Jean-Sebastien Delfino wrote:
> Jean-Sebastien Delfino wrote:
>> I'm seeing the following error when building binding-ws-axis2. Anybody
>> else seeing this?
>>
> ...
>
> Well that was with a revision from yesterday, with SVN r679776 I'm
> getting another error in modules/binding-ws-wsdlgen.
>
So, the binding-ws-wsdlgen error is fixed, back to the error with
binding-ws-axis2, now on SVN r679890, as you can see below, 26 out of 30
tests are failing:
testSOAP12Endpoint(org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.QuestionMarkWSDLTestCase)
Time elapsed: 1.229 sec <<< ERROR!
org.osoa.sca.ServiceRuntimeException:
org.osoa.sca.ServiceRuntimeException: Provided Intent -
{http://tuscany.apache.org/xmlns/sca/1.0}wsAuthentication not found for
PolicySet
{http://tuscany.apache.org/xmlns/sca/1.0}wsClientAuthenticationIntegrityPolicy
at
org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:276)
at
org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:70)
at
org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.QuestionMarkWSDLTestCase.setUp(QuestionMarkWSDLTestCase.java:130)
at junit.framework.TestCase.runBare(TestCase.java:132)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at
org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.java:35)
at
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308)
at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
Caused by: org.osoa.sca.ServiceRuntimeException: Provided Intent -
{http://tuscany.apache.org/xmlns/sca/1.0}wsAuthentication not found for
PolicySet
{http://tuscany.apache.org/xmlns/sca/1.0}wsClientAuthenticationIntegrityPolicy
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.analyseProblems(DefaultSCADomain.java:309)
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.addContribution(DefaultSCADomain.java:334)
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:183)
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.<init>(DefaultSCADomain.java:120)
at
org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:242)
... 20 more
Results :
Tests in error:
testHelloWorld(org.apache.tuscany.sca.binding.ws.axis2.itests.HelloWorldNoWSDLTestCase)
testEchoFoo(org.apache.tuscany.sca.binding.ws.axis2.itests.HelloWorldNoWSDLTestCase)
testCalculator(org.apache.tuscany.sca.binding.ws.axis2.itests.HelloWorldTestCase)
testUriPrecedence(org.apache.tuscany.sca.binding.ws.axis2.itests.UriPrecedenceTestCase)
testCalculator(org.apache.tuscany.sca.binding.ws.axis2.itests.epr.HelloWorldTestCase)
testHelloWorld(org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.HelloWorldSOAP12TestCase)
testHelloWorldSOAP(org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.HelloWorldSOAP12TestCase)
testHelloWorldSOAP11(org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.HelloWorldSOAP12TestCase)
testHelloWorldSOAP12(org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.HelloWorldSOAP12TestCase)
testWSDLImportPortEndpoint(org.apache.tuscany.sca.binding.ws.axis2.itests.QuestionMarkWSDLImportTestCase)
testWSDLPortEndpoint(org.apache.tuscany.sca.binding.ws.axis2.itests.QuestionMarkWSDLTestCase)
testCustomEndpoint(org.apache.tuscany.sca.binding.ws.axis2.itests.QuestionMarkWSDLTestCase)
testCalculator(org.apache.tuscany.sca.binding.ws.axis2.itests.endpoints.WSDLRelativeURITestCase)
testHelloWorld(org.apache.tuscany.sca.binding.ws.axis2.itests.policy.mixed.WSSecurityMixedTestCase)
testCalculator(org.apache.tuscany.sca.binding.ws.axis2.itests.endpoints.WSDLExplicitURITestCase)
testHelloWorld(org.apache.tuscany.sca.binding.ws.axis2.itests.HelloWorldWSDLMergedTestCase)
testHelloWorld(org.apache.tuscany.sca.binding.ws.axis2.itests.HelloWorldOMTestCase)
testCalculator(org.apache.tuscany.sca.binding.ws.axis2.itests.endpoints.DefaultMultiServiceTestCase)
testHelloWorld(org.apache.tuscany.sca.binding.ws.axis2.itests.policy.configparams.WSSecurityIntegrityTestCase)
testCalculator(org.apache.tuscany.sca.binding.ws.axis2.itests.endpoints.DefaultSingleServiceTestCase)
testHelloWorld(org.apache.tuscany.sca.binding.ws.axis2.itests.policy.wspolicy.WSSecurityIntegrityTestCase)
testHelloWorld(org.apache.tuscany.sca.binding.ws.axis2.itests.policy.wspolicy.WSSecurityAuthenticationTestCase)
testWSDLIncludePortEndpoint(org.apache.tuscany.sca.binding.ws.axis2.itests.QuestionMarkWSDLIncludeTestCase)
testSOAPDefault(org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.QuestionMarkWSDLTestCase)
testSOAP11Endpoint(org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.QuestionMarkWSDLTestCase)
testSOAP12Endpoint(org.apache.tuscany.sca.binding.ws.axis2.itests.soap12.QuestionMarkWSDLTestCase)
Tests run: 30, Failures: 0, Errors: 26, Skipped: 0
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
--
Jean-Sebastien
Re: Error building binding-ws-axis2
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Jean-Sebastien Delfino wrote:
> I'm seeing the following error when building binding-ws-axis2. Anybody
> else seeing this?
>
...
Well that was with a revision from yesterday, with SVN r679776 I'm
getting another error in modules/binding-ws-wsdlgen.
Running
org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.156
sec <<< FAILURE!
testGenerate(org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase)
Time elapsed: 0.139 sec <<< ERROR!
java.lang.RuntimeException:
org.apache.ws.commons.schema.XmlSchemaException:
other.ws.binding.sca.tuscany.apache.org
at
org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1886)
at
org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:1620)
at
org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:175)
at
org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:82)
at
org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:359)
at
org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:353)
at
org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.loadXSD(Interface2WSDLGenerator.java:402)
at
org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.addSchemaExtension(Interface2WSDLGenerator.java:384)
at
org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGenerator.generate(Interface2WSDLGenerator.java:256)
at
org.apache.tuscany.sca.binding.ws.wsdlgen.Interface2WSDLGeneratorTestCase.testGenerate(Interface2WSDLGeneratorTestCase.java:57)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
at
org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
at
org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
at
org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
at
org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
at
org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75)
at
org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36)
at
org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
at
org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
at
org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
at
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308)
at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
Caused by: org.apache.ws.commons.schema.XmlSchemaException:
other.ws.binding.sca.tuscany.apache.org
at
org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:308)
at
org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1884)
... 33 more
--
Jean-Sebastien