On Thu, Jan 14, 2010 at 6:41 PM, zoe slattery <[email protected]>wrote:
> Hi Forrest - Good progress :-) but I have looked and still have a small > issue. The assembly pom.xml refers to an artifact 'aries-jmx-blueprint', > this isn't found and the Aries build produces an artifact called > 'org.apache.aries.jmx.blueprint'. > Yep, aries-jmx-blueprint has been renamed to org.apache.aries.jmx.blueprint. > > I tried changing the pom.xml and the config.properties file in the assembly > module so that they refer to 'org.apache.aries.jmx.blueprint'. This gets me > to something that installs successfully. However, the run (executing run.sh) > hangs with the message: 'Awaiting MBeanServer service registration' > The message is printed out by the blueprint jmx bundle for debug purpose only, it might be improved to write into log file, not the console. However, it won't stop the sample demo. On the console, just hit enter key, you will get framework console prompt. In the prompt, user can start those bundle manually, then the sample info will be printed out on the console. By default, I set it not starting the sample when boot. To change this behavior, user can modify config.properties like this: felix.auto.start.10=\ "file:bundles/org.apache.aries.samples.blueprint.idverifier.server-1.0.0-incubating-SNAPSHOT.jar" \ "file:bundles/org.apache.aries.samples.blueprint.idverifier.client-1.0.0-incubating-SNAPSHOT.jar" \ "file:bundles/org.apache.aries.samples.blueprint.idverifier.api-1.0.0-incubating-SNAPSHOT.jar" > At this point I think I need to hand it back to you and ask you to look at > the JMX part - I'm not familiar enough with it to know what needs to be > done. > > Zoe > > Hi Zoe, >> >> I've updated the sample based on your comments, could you please help have >> a >> look and commit if no problem? >> >> Thanks! >> >> Forrest >> >> >> > >
