| Virgo tooling: issues with hot deploy to server in Servers view [message #940100] |
Thu, 11 October 2012 06:06  |
 Barbara Rosi-Schwartz
Messages: 448
Registered: July 2009 |
Senior Member |
|
|
Hello all.
I am trying to use the Virgo IDE to fast track my development by hot deploying bundles to the dev Virgo server I have configured and added to my IDE's Servers view.
However I run into the following issues:
1) if I rely on the regular Eclipse build process, any changes I make in a bundle cause immediate reloading and activating of that bundle, but the version of the bundle is invariably 0.0.0, which is incorrect and, of course, causes problems. I am wondering if this might be related to the fact that the <packaging> element in my bundle poms is "bundle" instead of "jar", because I am using the maven bundle plugin to manage manifest generation.
2) if I switch off automatic Eclipse build and I manually kick off a Maven build of any bundle I change, this causes the OSGi container to reload and restart the bundle, but my app falls over with the following exception:
2012-10-11 10:51:33.992] TCP Connection(7)-127.0.0.1 <DE0008I> Refreshed bundle 'com.iggroup.wb.workbench.accounts.accountopening' version '1.10.0.SNAPSHOT'.
Exception in thread "AWT-EventQueue-0" org.springframework.osgi.service.ServiceUnavailableException: service with id=[261] unavailable
at org.springframework.osgi.service.importer.support.internal.aop.ServiceStaticInterceptor.getTarget(ServiceStaticInterceptor.java:69)
at org.springframework.osgi.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:62)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
Any ideas on how to fix this issue?
I am currently using Virgo kernel 3.0.0.RELEASE and the latest release of the Virgo tooling.
TIA,
B.
[Updated on: Thu, 11 October 2012 06:07] Report message to a moderator |
|
|
] 
Search
Help
Register
Login
Home
