Comments on: Let’s play with OSGi, Spring and Maven, part 1 http://blog.krecan.net/2008/05/29/lets-play-with-osgi-spring-and-maven-part-1/ Short remarks from Java world Sat, 04 Feb 2012 09:44:38 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Geir Pettersen http://blog.krecan.net/2008/05/29/lets-play-with-osgi-spring-and-maven-part-1/comment-page-1/#comment-7630 Geir Pettersen Sat, 02 Apr 2011 09:51:45 +0000 http://blog.krecan.net/?p=74#comment-7630 Trying again, escaping < and > : <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> <version>1.4.3</version> <scope>test</scope> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-log4j12</artifactId> <version>1.4.3</version> <scope>test</scope> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>jcl104-over-slf4j</artifactId> <version>1.4.3</version> <scope>test</scope> </dependency> <dependency> <groupId>org.springframework.osgi</groupId> <artifactId>aopalliance.osgi</artifactId> <version>1.0-SNAPSHOT</version> <scope>test</scope> </dependency> Trying again, escaping < and > :

<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
<version>1.4.3</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
<version>1.4.3</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>jcl104-over-slf4j</artifactId>
<version>1.4.3</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.springframework.osgi</groupId>
<artifactId>aopalliance.osgi</artifactId>
<version>1.0-SNAPSHOT</version>
<scope>test</scope>
</dependency>

]]> By: Geir Pettersen http://blog.krecan.net/2008/05/29/lets-play-with-osgi-spring-and-maven-part-1/comment-page-1/#comment-7629 Geir Pettersen Sat, 02 Apr 2011 09:50:06 +0000 http://blog.krecan.net/?p=74#comment-7629 I got it working, after adding the following dependencies to the integration test project: org.slf4j slf4j-api 1.4.3 test org.slf4j slf4j-log4j12 1.4.3 test org.slf4j jcl104-over-slf4j 1.4.3 test org.springframework.osgi aopalliance.osgi 1.0-SNAPSHOT test Was this just left out by accident or is there something else that is wrong when I need to add these dependencies....? Thanks! I got it working, after adding the following dependencies to the integration test project:

org.slf4j
slf4j-api
1.4.3
test

org.slf4j
slf4j-log4j12
1.4.3
test

org.slf4j
jcl104-over-slf4j
1.4.3
test

org.springframework.osgi
aopalliance.osgi
1.0-SNAPSHOT
test

Was this just left out by accident or is there something else that is wrong when I need to add these dependencies....?

Thanks!

]]> By: Geir Pettersen http://blog.krecan.net/2008/05/29/lets-play-with-osgi-spring-and-maven-part-1/comment-page-1/#comment-7607 Geir Pettersen Sat, 02 Apr 2011 00:44:38 +0000 http://blog.krecan.net/?p=74#comment-7607 Very nice tutorial. I am however having some problems with building it as some of the tests fails - example (output from maven): Tests in error: testOSGiStartedOk(net.krecan.spring.osgi.dao.UiOsgiTest): C:\Users\Geir\.m2\repository\org\slf4j\slf4j-api\1.4.3\slf4j-api-1.4.3.jar Similar error occurs when i try to run the test from within Eclipse. I can't see slf4j-api-1.4.3.jar anywhere in the dependency hierarchy so I added it to the -it project hence it got loaded into my local repository. However, the test then failed on another library: Tests in error: testOSGiStartedOk(net.krecan.spring.osgi.dao.UiOsgiTest): C:\Users\Geir\.m2\repository\org\springframework\osgi\aopalliance.osgi\1.0-SNAPSHOT\aopalliance.osgi -1.0-SNAPSHOT.jar (The system cannot find the path specified) I really don't understand why it's complaining about a missing library that is not found in the pom dependency hierarchy - the only logging library I find is log4j, no slf4j... I've tried using both Maven 2.2.1 and 3.0.3 as well as cleaning my local m2 repository. Any thoughts? Thank you! Very nice tutorial. I am however having some problems with building it as some of the tests fails - example (output from maven):

Tests in error:
testOSGiStartedOk(net.krecan.spring.osgi.dao.UiOsgiTest): C:\Users\Geir\.m2\repository\org\slf4j\slf4j-api\1.4.3\slf4j-api-1.4.3.jar

Similar error occurs when i try to run the test from within Eclipse.

I can't see slf4j-api-1.4.3.jar anywhere in the dependency hierarchy so I added it to the -it project hence it got loaded into my local repository. However, the test then failed on another library:

Tests in error:
testOSGiStartedOk(net.krecan.spring.osgi.dao.UiOsgiTest): C:\Users\Geir\.m2\repository\org\springframework\osgi\aopalliance.osgi\1.0-SNAPSHOT\aopalliance.osgi
-1.0-SNAPSHOT.jar (The system cannot find the path specified)

I really don't understand why it's complaining about a missing library that is not found in the pom dependency hierarchy - the only logging library I find is log4j, no slf4j...

I've tried using both Maven 2.2.1 and 3.0.3 as well as cleaning my local m2 repository.

Any thoughts?

Thank you!

]]> By: Getting started with Maven2 « Wordpressblog http://blog.krecan.net/2008/05/29/lets-play-with-osgi-spring-and-maven-part-1/comment-page-1/#comment-1083 Getting started with Maven2 « Wordpressblog Wed, 05 Aug 2009 10:23:31 +0000 http://blog.krecan.net/?p=74#comment-1083 [...] •Nice tutorial for Spring / OSGI and Maven2 •Maven Getting started guided •How can Maven benefit my development process •The pain of switching from Ant to Maven (very good post, funny too read, thoughts of developer migrating I am sure I will suffer the same) •Maven2 Eclipse Plugin •Better builds with Maven (Free E-Book) [...] [...] •Nice tutorial for Spring / OSGI and Maven2 •Maven Getting started guided •How can Maven benefit my development process •The pain of switching from Ant to Maven (very good post, funny too read, thoughts of developer migrating I am sure I will suffer the same) •Maven2 Eclipse Plugin •Better builds with Maven (Free E-Book) [...]

]]> By: Honza Novotný http://blog.krecan.net/2008/05/29/lets-play-with-osgi-spring-and-maven-part-1/comment-page-1/#comment-482 Honza Novotný Fri, 30 May 2008 06:12:20 +0000 http://blog.krecan.net/?p=74#comment-482 Thanks, that would be much interesting. Thanks, that would be much interesting.

]]> By: Lukáš Křečan http://blog.krecan.net/2008/05/29/lets-play-with-osgi-spring-and-maven-part-1/comment-page-1/#comment-481 Lukáš Křečan Fri, 30 May 2008 05:58:09 +0000 http://blog.krecan.net/?p=74#comment-481 If you do not know, ask the machine. We can do a small experiment. I will try to write about it in part 3. If you do not know, ask the machine. We can do a small experiment. I will try to write about it in part 3.

]]> By: Honza Novotný http://blog.krecan.net/2008/05/29/lets-play-with-osgi-spring-and-maven-part-1/comment-page-1/#comment-480 Honza Novotný Fri, 30 May 2008 04:26:14 +0000 http://blog.krecan.net/?p=74#comment-480 You have my copliment ;-) . It's nice short and well understandable article. I have been thinking about different thing since last CZJUG - and that is, whether OSGI could help to minimize classloader leak problems in web application. From the speech of Michal Malohlava I assume that it does not. OSGi is mostly about dynamic installing and uninstalling bundles - but when the bundle you are uninstalled haven't clear all its references and memory allocated for it could not be GCed, this principle goes in vain. And - leaking memory in web programming is SOOO easy. As I understand OSGi wouldn't help to solve this problem, more than that - by its nature OSGi will create dozens of classloaders, so it is possible much harder to find out what's going in. Finally, when you leak classloaders, you'll run out of PermGenSpace memory and you wouldn't be able to dynamicaly install/uninstall modules at all. Am I right or miles out? You have my copliment ;-) . It's nice short and well understandable article.

I have been thinking about different thing since last CZJUG - and that is, whether OSGI could help to minimize classloader leak problems in web application. From the speech of Michal Malohlava I assume that it does not.

OSGi is mostly about dynamic installing and uninstalling bundles - but when the bundle you are uninstalled haven't clear all its references and memory allocated for it could not be GCed, this principle goes in vain. And - leaking memory in web programming is SOOO easy. As I understand OSGi wouldn't help to solve this problem, more than that - by its nature OSGi will create dozens of classloaders, so it is possible much harder to find out what's going in. Finally, when you leak classloaders, you'll run out of PermGenSpace memory and you wouldn't be able to dynamicaly install/uninstall modules at all.

Am I right or miles out?

]]>