On Dec 19, 2007 11:00 AM, Andrej Koelewijn <[EMAIL PROTECTED]> wrote:
> Hi Simon, > I included everything, including the manifest jar. Removing it doesn't > help. > Removing all the jars from the modules directory does: it works as > expected > when i put only the jars from the libs directory (excluding the manifest > jar) on the classpath. > Regards, > Andrej > > On Dec 19, 2007 11:54 AM, Simon Laws <[EMAIL PROTECTED]> wrote: > > > On Dec 19, 2007 9:58 AM, Andrej Koelewijn <[EMAIL PROTECTED]> wrote: > > > > > Fixed it. It was a classpath issue, although i'm yet sure what. I had > > put > > > all jar from the libs and modules directories on my classpath. After i > > > changed it to only include lib\tuscany-sca-manifest.jar it works as > > > expected. > > > Regards, > > > Andrej > > > > > Hi Andrej > > > > Thanks for coming back with the fix you found. In the case where it > didn't > > work for you were you including all jars from lib include modules > > including > > the manifest jar or just all jars from lib and module without the > manifest > > jar. If you find out anything more let us know. > > > > Regards > > > > Simon > > > Hmm, seems strange. People might want to include tuscany JARs explicitly (as you did) rather than using the manifest jar or the all jar so this should work. When you put all the jars from the lib dir on the classpath you are also picking up the tuscany-all jar which has all of the classes from the jars in /modules. I wonder if there is some difference between that and the modules jars. I'll give this a try when I build the 1.1 RC. Can you raise a JIRA to remind me. Thanks Simon
