Comments on: Passing Data between Plug-ins http://www.techjava.de/topics/2009/07/passing-data-between-plug-ins/ Journal on Java Technology Tue, 23 Aug 2011 08:02:05 +0000 hourly 1 http://wordpress.org/?v=3.1.2 By: Chris http://www.techjava.de/topics/2009/07/passing-data-between-plug-ins/comment-page-1/#comment-17583 Chris Mon, 25 Jan 2010 13:17:59 +0000 http://www.techjava.de/?p=436#comment-17583 Many Thanks Simon, and again: great tutorial. I went with another tutorial first and it was seriously messed up. Yours is easy to understand! Many Thanks Simon, and again: great tutorial. I went with another tutorial first and it was seriously messed up. Yours is easy to understand!

]]> By: Simon Zambrovski http://www.techjava.de/topics/2009/07/passing-data-between-plug-ins/comment-page-1/#comment-17579 Simon Zambrovski Mon, 25 Jan 2010 11:04:47 +0000 http://www.techjava.de/?p=436#comment-17579 There are several possibilities to fix this. For example the product configuration has the Launching configuration, where you could add the plug-ins to (and set up the activation during the start-up of OSGi). Another thing is: make sure to activate the checkbox "Launch plugin on access to the class". The third thing is, make sure you design is correct.. It is important that your product / application is independent from the UI. Especially, it seems that you want to launch the Core* functionality and gather extensions implemented by the UI plugin. So, the right way to do so would be to trigger the core plugins from your Application.java... Again, I think you should seriously reason about the way your plug-ins are activated. Don't rely on some order of OSGi activation, but make it explicit... The Application / Advisors allow you to participate in the lifecycle (check out the correspnding methods like preWindowsOpen() etc...). Make sure to insert your activation code there... There are several possibilities to fix this. For example the product configuration has the Launching configuration, where you could add the plug-ins to (and set up the activation during the start-up of OSGi). Another thing is: make sure to activate the checkbox “Launch plugin on access to the class”. The third thing is, make sure you design is correct.. It is important that your product / application is independent from the UI. Especially, it seems that you want to launch the Core* functionality and gather extensions implemented by the UI plugin. So, the right way to do so would be to trigger the core plugins from your Application.java… Again, I think you should seriously reason about the way your plug-ins are activated. Don’t rely on some order of OSGi activation, but make it explicit… The Application / Advisors allow you to participate in the lifecycle (check out the correspnding methods like preWindowsOpen() etc…). Make sure to insert your activation code there…

]]> By: Chris http://www.techjava.de/topics/2009/07/passing-data-between-plug-ins/comment-page-1/#comment-17575 Chris Mon, 25 Jan 2010 05:23:09 +0000 http://www.techjava.de/?p=436#comment-17575 A great tutorial Simon. I got it to work fine and without any issues. I just stumble over an issue right now. Lets say the UI is my main plugin (extends more than one extension point, lets say core1 and core2 - of different plugin's each). In your case the product launch configuration is in the core package - which works. However, if I try to create a product of the UI (with the core* plugins as dependencies and started) then it never seems to start the core* plugins... . Any hint? A great tutorial Simon.

I got it to work fine and without any issues. I just stumble over an issue right now. Lets say the UI is my main plugin (extends more than one extension point, lets say core1 and core2 – of different plugin’s each).

In your case the product launch configuration is in the core package – which works. However, if I try to create a product of the UI (with the core* plugins as dependencies and started) then it never seems to start the core* plugins… . Any hint?

]]> By: Simon Zambrovski http://www.techjava.de/topics/2009/07/passing-data-between-plug-ins/comment-page-1/#comment-16783 Simon Zambrovski Mon, 07 Dec 2009 18:46:40 +0000 http://www.techjava.de/?p=436#comment-16783 Read it like add a "reference to the listener" to the sequence. After execution of the previous step, your "extension" element should have a "sequence" element. If the "listener" element is already created, and you right-click on the "sequence" element, you will see the "new" popup-menu, containing "choice", "sequence" and "listener" items. Clicking on the listener item, you will not create a new element called "listener" but a reference to existing one. If you look up the source of the definition, you'll see something like: element ref="listener". Read it like add a “reference to the listener” to the sequence. After execution of the previous step, your “extension” element should have a “sequence” element. If the “listener” element is already created, and you right-click on the “sequence” element, you will see the “new” popup-menu, containing “choice”, “sequence” and “listener” items. Clicking on the listener item, you will not create a new element called “listener” but a reference to existing one. If you look up the source of the definition, you’ll see something like: element ref=”listener”.

]]> By: Martin http://www.techjava.de/topics/2009/07/passing-data-between-plug-ins/comment-page-1/#comment-16781 Martin Mon, 07 Dec 2009 18:25:29 +0000 http://www.techjava.de/?p=436#comment-16781 I don't understand the step'Add a reference to the listener to the Sequence' in the creation of the extension Point, could you check it again? I don’t understand the step’Add a reference to the listener to the Sequence’ in the creation of the extension Point, could you check it again?

]]>