Jean-Sebastien wrote: > > Jack, this is great! Can you please upload the patch and > I'll try it and will debug the exception that you're seeing. > I'm looking at the code and thinking that maybe one of the > SCDL files is missing from the generated Jars and this is > what's causing the exception (since the SCDL .componentType > file is not found one of the components does not declare any > services and this is what's causing the IndexOutOfBoundsException).
OK, I suspect you are right. Perhaps it would be best to upload what I have and hopefully someone (perhaps you :-) won't mind tying up loose ends. Thanks. I have a set of notes to go along with this patch, as follows: 1) jsr173.jar (StAX) Most everyone on tuscany-dev already knows this, but for those who are newbies like myself, you can download jsr173.jar from http://workshop.bea.com/xmlbeans/jsr173v1/jsr173.jar or if you prefer to get it directly from Sun, you can download and install JWSDP 1.6 from http://java.sun.com/webservices/downloads/webservicespack.html and once installed, use sjsxp/lib/jsr173_api.jar as it is supposed to be the same binary. Either way, manually install the jar into your m2 repository: mvn install:install-file -DgroupId=javax.xml -DartifactId=jsr173 -Dversion=1.0 -Dpackaging=jar -Dfile=jsr173.jar 2) pom hierarchy Group IDs for dependencies from the acceptances tests onto the samples and tuscany-specific libs are still based on the groupId org.soa. That of course has to change when the acceptance tests are moved over. 3) default goal The old 'acceptance' goal is not working under M2. I have temporarily set the default goal to be 'test'. 4) acceptance build.xml This needed to be changed because of assumptions about the structure of the maven local repo necessary so that various jars can be deployed to Tomcat. I also bumped up the declared version of Derby to 10.1.2.1. Finally, I needed to rename the samples war files copied into the Tomcat webapp directory, as part of the operation of this build script, such that they do not include the version string. Otherwise, the bigbank web client test (at a minimum) fails with a 404. 5) maven.repo.local system property >From what I can tell, the ${maven.repo.local} variable does not expand to the default value if you have not otherwise set it, which causes problems when invoking the Ant task to set up Tomcat. I found that I needed to explicitly set it on my maven command-line, eg. for my Windows box: -Dmaven.local.repo="%USERPROFILE%/.m2/repository" -- Jack Unrue [EMAIL PROTECTED]
