| Virgo tooling: issues with hot deploy to server in Servers view [message #940100] |
Thu, 11 October 2012 06:06  |
Eclipse User |
|
|
|
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] by Moderator |
|
|
|
|
|
|
| Re: Virgo tooling: issues with hot deploy to server in Servers view [message #968682 is a reply to message #948253] |
Fri, 02 November 2012 13:05  |
| Eclipse User |
|
|
|
Leo Dos Santos wrote on Wed, 17 October 2012 18:30Barbara Rosi-Schwartz wrote on Thu, 11 October 2012 06:06
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.
Hi Barbara
There is a bug in the tools where they don't generate proper manifests from Maven properties, described in this thread http://www.eclipse.org/forums/index.php/t/376751/ and at https://bugs.eclipse.org/bugs/show_bug.cgi?id=391725 as well. I've committed a fix that's available as of last night's snapshot build. I don't know if this is the cause of your problem but you might want to give that build a try to see if it helps.
I am now the running the snapshot build and the Maven properties bug is indeed fixed. Any chance that the "Enable incremental Generation of MANIFEST.MF" bug gets fixed soon?
|
|
|
| Re: Virgo tooling: issues with hot deploy to server in Servers view [message #984850 is a reply to message #968682] |
Wed, 14 November 2012 20:37 |
| Eclipse User |
|
|
|
Quote:I am now the running the snapshot build and the Maven properties bug is indeed fixed. Any chance that the "Enable incremental Generation of MANIFEST.MF" bug gets fixed soon?
Hi Simon
Can you describe what kind of behaviour you're seeing with incremental manifest generation? We had made some fixes in this area in 1.0.0 but we need to understand better the cases in which it's not working well.
|
|
|
Powered by
FUDForum. Page generated in 0.09983 seconds
Home