I think I have narrowed down the issue here. As we already known from previous issues with Ubuntu, traversing files in this OS comes in a different order compared to other OS, and this is causing the failures, as our BPEL model is still unresolved when being processed. I'm working on a fix, and will follow the same pattern used for WSDL/XSD where some of the resolve code was moved down to the ModelResolver, in this case, BPELDocumentModelResolver.
On Sun, Jul 26, 2009 at 1:22 AM, ant elder<[email protected]> wrote: > On Sun, Jul 26, 2009 at 2:21 AM, Luciano Resende<[email protected]> wrote: >> On Sat, Jul 25, 2009 at 2:37 PM, Giorgio Zoppi<[email protected]> >> wrote: >>> Hi guys, >>> BPEL give us still problems in the trunk. Could you give it a double check? >>> >>> helloworld.HelloWorldTestCase Time elapsed: 0 sec <<< ERROR! >>> java.lang.IllegalStateException: >>> org.apache.tuscany.sca.contribution.processor.ContributionResolveException: >>> org.apache.tuscany.sca.contribution.processor.ContributionResolveException: >>> Processing composite {http://bpel}helloworld: null >>> >> >> Looks like this is a Ubuntu problem, and it's failing in the Hudson >> build as well. I'll take a look at this over the weekend. >> >> > > While you're looking at that I've taken it out of the build for now > (as well as the dosgi-dynamic-calculator-operations sample) as both > are failing in the hudson build, to try to get the hudson build > running successfully. > > ...ant > -- Luciano Resende Apache Tuscany, Apache PhotArk http://people.apache.org/~lresende http://lresende.blogspot.com/
