I tried to move the 2 dependencies below to the tradedatasource module level and made sure there is not any dependency for the streamer.jar module. But I am still getting the same error saying that starting rmi-naming failed and port 1099 already in use...
Any ideas? Lin -----Original Message----- From: Lin Sun [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 30, 2006 10:34 PM To: [email protected] Subject: RE: daytrader streamer client Thanks. The followings are the dependencies for the daytrader application at the application level: <dep:dependencies> <dep:dependency> <dep:groupId>geronimo</dep:groupId> <dep:artifactId>j2ee-server</dep:artifactId> <dep:type>car</dep:type> </dep:dependency> <dep:dependency> <dep:groupId>geronimo</dep:groupId> <dep:artifactId>system-database</dep:artifactId> <dep:type>car</dep:type> </dep:dependency> </dep:dependencies> And I don't see any dependencies for the streamer.jar module. Either of the above 2 modules will probably require the rmi-naming module. I plan to move the above dependencies to the module level and see if the exception would go away. Will post the result back tomorrow. Lin -----Original Message----- From: David Jencks [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 30, 2006 8:17 PM To: [email protected] Subject: Re: daytrader streamer client Something bad happened to the dependencies. No server-side car should be a dependency of an app client. If you can figure out what the entire set of dependencies for the app client is it will be much easier to figure out where the bad dependency is coming from. thanks david jencks
