On Thu, Mar 20, 2008 at 12:56 PM, Simon Laws <[EMAIL PROTECTED]>
wrote:

>
>
> On Thu, Mar 20, 2008 at 7:46 AM, Jean-Sebastien Delfino <
> [EMAIL PROTECTED]> wrote:
>
> > Luciano Resende wrote:
> > > Do you still see issues after revision #639171 ? If so, could you
> > > please give me the names of missing jars ? I have tried to capture the
> > > differences in [1]
> > >
> > > [1]
> > http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Release+-+Java+SCA+1.2#Release-JavaSCA1.2-Modulesincludedinthedistribution
> > >
> > > On Wed, Mar 19, 2008 at 11:29 PM, Jean-Sebastien Delfino
> > > <[EMAIL PROTECTED]> wrote:
> > >> Simon Laws wrote:
> > >>  > On Wed, Mar 19, 2008 at 5:57 PM, Jean-Sebastien Delfino <
> > >>  > [EMAIL PROTECTED]> wrote:
> > >>  >
> > >>  >> Simon Laws wrote:
> > >>  >>> I'm trying to run the calculator-distribute sample with the
> > workspace
> > >>  >>> changes from an ant build.xml. I'm getting
> > >>  >>>
> > >>  >>> runDomain:
> > >>  >>>      [java] 19-Mar-2008 11:23:38
> > >>  >>> org.apache.tuscany.sca.workspace.admin.launcher
> > >>  >>> .DomainAdminLauncher main
> > >>  >>>      [java] INFO: Apache Tuscany SCA Domain Administration
> > starting...
> > >>  >>>      [java] 19-Mar-2008 11:23:39
> > >>  >>> org.apache.tuscany.sca.workspace.admin.launcher
> > >>  >>> .DomainAdminLauncherUtil collectJARFiles
> > >>  >>>      [java] INFO: Runtime classpath: 153 JARs from
> > C:\simon\tuscany\sca-
> > >>  >>> java-1.2
> > >>  >>> \distribution\target\apache-
> > >>  >>> tuscany-sca-1.2-incubating-SNAPSHOT.dir\tuscany-sca-
> > >>  >>> 1.2-incubating-SNAPSHOT\lib
> > >>  >>>      [java] 19-Mar-2008 11:23:39
> > >>  >>> org.apache.tuscany.sca.workspace.admin.launcher
> > >>  >>> .DomainAdminLauncher main
> > >>  >>>      [java] SEVERE: SCA Domain Administration could not be
> > started
> > >>  >>>      [java] java.lang.ClassNotFoundException:
> > >>  >>> org.apache.tuscany.sca.workspace.a
> > >>  >>> dmin.launcher.DomainAdminLauncherBootstrap
> > >>  >>>      [java]     at java.lang.Class.forName(Class.java:163)
> > >>  >>>      [java]     at
> > >>  >>> org.apache.tuscany.sca.workspace.admin.launcher.DomainAdminLa
> > >>  >>> uncher.main(DomainAdminLauncher.java:53)
> > >>  >>>      [java]     at node.LaunchDomain.main(LaunchDomain.java:30)
> > >>  >>>      [java] Exception in thread "main"
> > java.lang.ClassNotFoundException:
> > >>  >>> org.apa
> > >>  >>>
> > che.tuscany.sca.workspace.admin.launcher.DomainAdminLauncherBootstrap
> > >>  >>>      [java]     at java.lang.Class.forName(Class.java:163)
> > >>  >>>      [java]     at
> > >>  >>> org.apache.tuscany.sca.workspace.admin.launcher.DomainAdminLa
> > >>  >>> uncher.main(DomainAdminLauncher.java:53)
> > >>  >>>      [java]     at node.LaunchDomain.main(LaunchDomain.java:30)
> > >>  >>>      [java] Java Result: 1
> > >>  >>>
> > >>  >>> Now the classpath looks ok to me in that it includes the tuscany
> > >>  >> manifest
> > >>  >>> jar so should have all the dependencies.
> > >>  >> Does the manifest reference
> > tuscany-workspace-admin-1.2-incubating.jar?
> > >>  >>
> > >>  >> The distribution I built yesterday didn't have it, but I saw some
> > >>  >> commits from Luciano changing the distro assembly files
> > yesterday...
> > >>  >>
> > >>  >> --
> > >>  >> Jean-Sebastien
> > >>  >>
> > >>  >>
> > ---------------------------------------------------------------------
> > >>  >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> > >>  >> For additional commands, e-mail: [EMAIL PROTECTED]
> > >>  >>
> > >>  >>
> > >>  > Yeah, I should have said that I made those changes locally. The
> > manifest
> > >>  > references the jars. Should is still work with a reference to the
> > manifest
> > >>  > jar or do I need to go and set TUSCANY_HOME which is mentioned in
> > the code.
> > >>  > If it should work as is I'll investigate more. I just didn't want
> > to spend
> > >>  > the time until I knew that I was going in the right direction.
> > >>  >
> > >>  > Simon
> > >>  >
> > >>
> > >>  I started to fix this issue in revision r639167 (trunk) and r639170
> > (1.2
> > >>  branch) although I'm still having problems with tuscany-sca-manifest
> > as
> > >>  it's missing a number of JARs.
> > >>
> > >>  As a result of these changes the domain admin app can now be started
> > as:
> > >>  java -jar .../modules/tuscany-node2-launcher-1.2-incubating.jardomain
> > >>
> > >>  --
> > >>
> > >>
> > >> Jean-Sebastien
> > >>
> >
> > The maintenance of manifest/pom.xml and bundle/pom.xml is really error
> > prone :(
> >
> > I fixed the errors I could see in these poms, added some missing JARs
> > and removed obsolete references to the old feed binding JARs.
> >
> > I also fixed incorrect class names in calculator-distributed/build.xml.
> >
> > I am able to start the domain and nodes from calculator-distributed with
> > these fixes (SVN revision r639187) but then I'm seeing a weird NPE in
> > the SDO runtime:
> >
> >  [java] Caused by: java.lang.NullPointerException
> >      [java]     at
> > commonj.sdo.impl.HelperProvider.getDefaultContext(HelperProvider.java
> > :379)
> >      [java]     at
> > org.apache.tuscany.sca.databinding.sdo.SDODataBinding.introspect(
> > SDODataBinding.java:61)
> >      [java]     at
> >
> > org.apache.tuscany.sca.databinding.DefaultDataBindingExtensionPoint$LazyDataBinding.introspect
> > (DefaultDataBindingExtensionPoint.java:191)
> >      [java]     at
> >
> > org.apache.tuscany.sca.databinding.DefaultDataBindingExtensionPoint.introspectType
> > (DefaultDataBindingExtensionPoint.java:246)
> >      [java]     at
> > ...
> >
> > It is not specific to calculator-distributed, as I can see the same
> > exception in other samples.
> >
> > Any idea?
> > --
> > Jean-Sebastien
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> Luciano/Sebastien
>
> Thanks for the fixes you worked on last night. I can get the nodes to run
> now but I too get an NPE. Different to Sebastien's though.
>
> Simon
>

Ok, so the sample works for me now. I made a change to
node2-launcher/DomainNodeLauncher to change the way the that the parent
classloader is aquired (r639292). Can you take a look a see if this is ok as
it looks like this has been carefully constructed and I expect I'm
overlooking something. Object.class.getClasspath() returns null on the IBM
JDK in this case. This was actually my original question. What does all this
new node loader stuff do?

I'll go and update the README and that should be it for this one.

Simon

Reply via email to