NetBeans Runtime Container - Revision history

JaroslavTulach at 06:28, 11 November 2011

JaroslavTulach — Fri, 11 Nov 2011 06:28:05 GMT

←Older revision		Revision as of 06:28, 11 November 2011
Line 1:		Line 1:
-	The [[module system]] engine behind [[NetBeans]] based applications. Since [[Netigso\|version 6.9]] ~~also~~ fully [[OSGi]]-[[Netigso\|compliant]] for easy reuse of 3rd party or even ~~yours~~ [[OSGi]] bundles.	+	The [[module system]] engine behind [[NetBeans]] based applications. Created as the first modular system for desktop [[Java]] applications. Evolved into general purpose [[module system]]. Since [[Netigso\|version 6.9]] fully [[OSGi]]-[[Netigso\|compliant]] for easy reuse of 3rd party or even your own [[OSGi]] bundles.

	[[Image:Jested.jpg]]		[[Image:Jested.jpg]]

94.66.17.168 at 05:02, 1 November 2011

94.66.17.168 — Tue, 01 Nov 2011 05:02:44 GMT

←Older revision		Revision as of 05:02, 1 November 2011
Line 1:		Line 1:
-	The [[module system]] engine behind [[NetBeans]] based applications. Since [[Netigso\|version 6.9]] also fully [[OSGi]] [[Netigso\|~~complient~~]] for easy reuse of 3rd party or even yours [[OSGi]] bundles.	+	The [[module system]] engine behind [[NetBeans]] based applications. Since [[Netigso\|version 6.9]] also fully [[OSGi]]-[[Netigso\|compliant]] for easy reuse of 3rd party or even yours [[OSGi]] bundles.

	[[Image:Jested.jpg]]		[[Image:Jested.jpg]]

JaroslavTulach at 09:22, 30 October 2011

JaroslavTulach — Sun, 30 Oct 2011 09:22:53 GMT

←Older revision		Revision as of 09:22, 30 October 2011
Line 1:		Line 1:
-	The [[module system]] engine behind [[NetBeans]] based applications. Since [[Netigso\|version 6.9]] also fully [[OSGi]] complient for easy reuse of 3rd party or even yours [[OSGi]] bundles.	+	The [[module system]] engine behind [[NetBeans]] based applications. Since [[Netigso\|version 6.9]] also fully [[OSGi]] [[Netigso\|complient]] for easy reuse of 3rd party or even yours [[OSGi]] bundles.

	[[Image:Jested.jpg]]		[[Image:Jested.jpg]]

JaroslavTulach at 09:22, 30 October 2011

JaroslavTulach — Sun, 30 Oct 2011 09:22:19 GMT

←Older revision		Revision as of 09:22, 30 October 2011
Line 1:		Line 1:
-	The [[module system]] engine behind [[NetBeans]] based applications.	+	The [[module system]] engine behind [[NetBeans]] based applications. Since [[Netigso\|version 6.9]] also fully [[OSGi]] complient for easy reuse of 3rd party or even yours [[OSGi]] bundles.

	[[Image:Jested.jpg]]		[[Image:Jested.jpg]]

87.126.0.254: /* The main Module Class */

87.126.0.254 — Fri, 03 Jun 2011 10:19:12 GMT

The main Module Class

←Older revision		Revision as of 10:19, 3 June 2011
Line 50:		Line 50:
	}		}
	</source>		</source>
-	Now start the application again and check the result. As in the previous case, the splash screen is shown, the application is started and also exits. However in contrast to the previous execution, among other things also the output contains Say Hello! printed by your first module. Is it not impressive?	+	Now start the application again and check the result. As in the previous case, the splash screen is shown, the application is started and also exits. However in contrast to the previous execution, among other things also the output contains Say Hello! printed by your first module. Is it not impressive?
		+
		+	(If some error message appears try to resolve any missing module using project properties.)

	=== Registering and Discovery of Services ===		=== Registering and Discovery of Services ===

JaroslavTulach: /* Registering and Discovery of Services */

JaroslavTulach — Mon, 08 Nov 2010 08:16:51 GMT

Registering and Discovery of Services

←Older revision		Revision as of 08:16, 8 November 2010
Line 58:		Line 58:
	This section is going to show how to do registration and discovery of services and establish communication channels between individual modules in the system. First of all let's change the Hello world module to be more visual and also to offer an API to for others to contribute hello messages.		This section is going to show how to do registration and discovery of services and establish communication channels between individual modules in the system. First of all let's change the Hello world module to be more visual and also to offer an API to for others to contribute hello messages.

-	First task is to create an API. By default no other module can access classes of another module. This is enforced during runtime by ~~classloader~~ machinery provided by the NetBeans Runtime Container. Think about this as additional access modifier extending the standard java choices of private, package private, protected and public. In NetBeans we moreover add a notion of public vs. private packages. As an API is supposed to be public, it needs to be put into new package and this package has to be marked as public in the projects configuration dialog. So create:	+	First task is to create an API. By default no other module can access classes of another module. This is enforced during runtime by [[ClassLoader]] machinery provided by the NetBeans Runtime Container. Think about this as additional access modifier extending the standard java choices of private, package private, protected and public. In NetBeans we moreover add a notion of public vs. private packages. As an API is supposed to be public, it needs to be put into new package and this package has to be marked as public in the projects configuration dialog. So create:
	<source lang="java">		<source lang="java">
	package org.test.sayhello.api;		package org.test.sayhello.api;
Line 103:		Line 103:
	org.test.ciao.Ciao		org.test.ciao.Ciao
	</source>		</source>
-	This instructs the NetBeans Lookup to create instance of class Ciao when someone asks for implementations of interface HelloTip using Lookup.getDefault().lookup(HelloTip.class). To see it with your own eyes, start your app and make the system say hello. The Ciao version is going to be shown. This is a bit more interesting hello world version, isn't it?	+	This instructs the NetBeans Lookup to create instance of class Ciao when someone asks for implementations of interface HelloTip using Lookup.getDefault().lookup(HelloTip.class). To see it with your own eyes, start your app and make the system say hello. The Ciao version is going to be shown. This is a bit more interesting hello world version, isn't it?

	=== Using Virtual Files For Communication ===		=== Using Virtual Files For Communication ===

JaroslavTulach: Undo revision 3955 by Demver5 (Talk)

JaroslavTulach — Thu, 19 Aug 2010 11:24:28 GMT

Undo revision 3955 by Demver5 (Talk)

←Older revision		Revision as of 11:24, 19 August 2010
Line 139:		Line 139:

	There are two things to remember after reading this article. The first is the importance of modular applications; the second is that developing with the NetBeans Runtime Container is simple. By selecting the right modules from the NetBeans Platform, you can strip it down and make it useful even for non-visual applications. Moreover, creating a new module using NetBeans IDE is a matter of a few clicks, while using the Lookup and layers is straightforward and powerful. Building with and on top of the NetBeans Platform is simply the best development choice you can make!		There are two things to remember after reading this article. The first is the importance of modular applications; the second is that developing with the NetBeans Runtime Container is simple. By selecting the right modules from the NetBeans Platform, you can strip it down and make it useful even for non-visual applications. Moreover, creating a new module using NetBeans IDE is a matter of a few clicks, while using the Lookup and layers is straightforward and powerful. Building with and on top of the NetBeans Platform is simply the best development choice you can make!
-
-
-
-	~~==Related Links==~~
-
-
-	~~[http://www.cellulite.co.uk/how-to-get-rid-of-cellulite '''get rid of cellulite''']~~

Demver5: /* Summary */

Demver5 — Thu, 19 Aug 2010 06:39:51 GMT

Summary

←Older revision		Revision as of 06:39, 19 August 2010
Line 139:		Line 139:

	There are two things to remember after reading this article. The first is the importance of modular applications; the second is that developing with the NetBeans Runtime Container is simple. By selecting the right modules from the NetBeans Platform, you can strip it down and make it useful even for non-visual applications. Moreover, creating a new module using NetBeans IDE is a matter of a few clicks, while using the Lookup and layers is straightforward and powerful. Building with and on top of the NetBeans Platform is simply the best development choice you can make!		There are two things to remember after reading this article. The first is the importance of modular applications; the second is that developing with the NetBeans Runtime Container is simple. By selecting the right modules from the NetBeans Platform, you can strip it down and make it useful even for non-visual applications. Moreover, creating a new module using NetBeans IDE is a matter of a few clicks, while using the Lookup and layers is straightforward and powerful. Building with and on top of the NetBeans Platform is simply the best development choice you can make!
		+
		+
		+
		+	==Related Links==
		+
		+
		+	[http://www.cellulite.co.uk/how-to-get-rid-of-cellulite '''get rid of cellulite''']

192.9.112.196: /* Summary */

192.9.112.196 — Tue, 22 Jun 2010 14:15:56 GMT

Summary

←Older revision		Revision as of 14:15, 22 June 2010
Line 138:		Line 138:
	== Summary ==		== Summary ==

-	There are two things to remember after reading this article. The first is the importance of modular applications; the second is that developing with the NetBeans Runtime Container is simple. By selecting the right modules from the NetBeans Platform, you can strip it down and make it useful even for non-visual applications. Moreover, creating a new module using NetBeans IDE is a matter of few clicks, while using the Lookup and layers is straightforward and powerful. Building with and on top of the NetBeans Platform is simply the best development choice you can make!	+	There are two things to remember after reading this article. The first is the importance of modular applications; the second is that developing with the NetBeans Runtime Container is simple. By selecting the right modules from the NetBeans Platform, you can strip it down and make it useful even for non-visual applications. Moreover, creating a new module using NetBeans IDE is a matter of a few clicks, while using the Lookup and layers is straightforward and powerful. Building with and on top of the NetBeans Platform is simply the best development choice you can make!

192.9.112.196: /* Summary */

192.9.112.196 — Tue, 22 Jun 2010 14:15:24 GMT

Summary

←Older revision		Revision as of 14:15, 22 June 2010
Line 138:		Line 138:
	== Summary ==		== Summary ==

-	There are two things to remember after reading this article. The first ~~one~~ is ~~that~~ modular applications ~~are~~ the ~~necessity and one shall always develop in a modular way. The~~ second ~~one~~ is that developing with NetBeans Runtime Container is simple ~~and easy~~. By selecting the right modules ~~one~~ can strip it down and make it ~~usable~~ even for non-visual applications. Moreover creating a new module using NetBeans IDE is a matter of few clicks ~~and~~ using the ~~lookup~~ and layers is straightforward and powerful. Building with and on top of NetBeans is simply the best choice ~~one~~ can make!	+	There are two things to remember after reading this article. The first is the importance of modular applications; the second is that developing with the NetBeans Runtime Container is simple. By selecting the right modules from the NetBeans Platform, you can strip it down and make it useful even for non-visual applications. Moreover, creating a new module using NetBeans IDE is a matter of few clicks, while using the Lookup and layers is straightforward and powerful. Building with and on top of the NetBeans Platform is simply the best development choice you can make!