On 11/29/06, Bruce Snyder <[EMAIL PROTECTED]> wrote:
On 11/29/06, Java Energizer <[EMAIL PROTECTED]> wrote:
> Greetings,
>
> I have tried several of the builds. Testing them out
> on two environments:
> 1. Solaris sparc- SUNFIRE hardware.
> 2. Solaris x86 - PC based hardware.
> I see different results in these environments using the same builds.
> There are some difficulties at the git go. The servicemix sh in bin
> has problems, im thinking its because of the differences in SHELL.
> After fixing those, I can invoke servicemix. However, in both env
> the example servicemix-web does not work. I posted the stack trace
> already to the the list. I got the "basic" sample working on the sparc
> platform and it seems to behave OK. Havnt gotten it to work on x86
> platform yet. Im getting some stack trace dumps, that Im still trying
> to resolve. Im thinking I am missing system libs that are dependencies.
> I tried to do a build from the src in both environments and they fail
> really really bad, so bad I dont care to post logs, unless someone
> is really interested. I dont think I need to build source though.
> FIrst I will be a user! :)
Yeah, I was going to suggest using one of the binaries for the time
being. As I stated in my reply to one of your other messages, I'm
going to look into this tonight on Solaris.
Below are the results of the testing I performed this evening:
When testing with the apache-servicemix-3.0-incubating source code, no
matter whether I'm using Solaris or MacOS X, I consistently experience
failures on the following artifacts when i execute 'mvn jetty:run from
within the samples/servicemix-web directory:
1) org.apache.servicemix:servicemix-core:jar:3.0-incubating
2) org.apache.servicemix:servicemix-http:jar:3.0-incubating
3) org.apache.servicemix:servicemix-components:jar:3.0-incubating
If I perform the same exact test using the latest ServiceMix trunk,
everything goes well until Jetty actually tries to launch and it
throws the following error:
org.springframework.beans.FatalBeanException: Geronimo transaction
manager was not set
Unfortunately I'm still not sure why this error is occurring.
When I try to build the apache-servicemix-3.0-incubating source from
the base directory by executing 'mvn -Dmaven.test.skip=true install'
no matter whether I'm using Solaris or MacOS X, I experience a failure
in downloading the jbi-maven-plugin:
org.apache.servicemix.tooling:jbi-maven-plugin:maven-plugin:3.0-incubating
Concerning the issues you've seen with the servicemix shell script,
the necessary changes to support the Solaris' version of the Bourne
shell have already been committed to the ServiceMix trunk.
I'm really curious to know if others see the same results I"m seeing.
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache Geronimo - http://geronimo.apache.org/
Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Castor - http://castor.org/
