Vadim Berestetsky/Toronto/IBM is out of the office at ITSO conference.

I will be out of the office starting  02/27/2006 and will not return until
03/03/2006.

I will be checking my mail periodically. For all JSF-related Webfacing
matters please contact either Satish Gungabeesoon or Abe Batthish.
Otherwise, contact my manager George Voutsinas.

using third party jars in equinox

What is the best approach to use third party jars in more then one plugins?

Current aapproach:
Create a plug-in with the third party jars and make other plug-ins 
dependent on this plug-in. But I could not find a way to export the 
'jars' from the plug-in. Currently it works by exporting all the 
packages in Manifest and specifying the jar as exportable in Java Build 
Properties.
Is there a better way to export 'Jars'?

Re: using third party jars in equinox

<div>
<br>http://eclipsercp.org/book/
<table width="100%"><tr><td width="100%">Chapter 20 - Integrating Code Libraries 327
</td></tr></table>
<br><a href="http://www.eclipsecon.org/"></a>
<br><br><br><table width="100%"><tr valign="top">
<td width="40%">Abhishek Verma &lt;abhishekv@...&gt;

<br>Sent by: equinox-dev-bounces@...
<p>03/01/2006 09:28 AM
</p>
<table border><tr valign="top"><td bgcolor="white">
<div align="center">Please respond to<br>
Equinox development mailing list &lt;equinox-dev@...&gt;</div>
</td></tr></table>
<br>
</td>
<td width="59%">
<table width="100%">
<tr valign="top">
<td>
<div align="right">To</div>
</td>
<td>Equinox development mailing list &lt;equinox-dev@...&gt;
</td>
</tr>
<tr valign="top">
<td>
<div align="right">cc</div>
</td>
<td>
</td>
</tr>
<tr valign="top">
<td>
<div align="right">Subject</div>
</td>
<td>[equinox-dev] using third party jars
in equinox</td>
</tr>
</table>
<br><table><tr valign="top">
<td>
</td>
<td></td>
</tr></table>
<br>
</td>
</tr></table>
<br><br><br>What is the best approach to use third party jars
in more then one plugins?<br><br>
Current aapproach:<br>
Create a plug-in with the third party jars and make other plug-ins <br>
dependent on this plug-in. But I could not find a way to export the <br>
'jars' from the plug-in. Currently it works by exporting all the <br>
packages in Manifest and specifying the jar as exportable in Java Build
<br>
Properties.<br>
Is there a better way to export 'Jars'?<br><br>
_______________________________________________<br>
equinox-dev mailing list<br>
equinox-dev@...<br>
https://dev.eclipse.org/mailman/listinfo/equinox-dev<br>
<br>
</div>

Declarative Services vs Spring

<div>
<p>How does declarative services fare when compared with Spring framework in terms of its injection capabilities ?  My apologies if this is already discussed on this forum.<br><br>
Is there a reason why declarative services does not support constructor injection, for example ? It seems constructor injection is the only way to initialize a component that holds a immutable (final) service reference injected via its constructor. <br><br>
Appreciate your thoughts.<br><br>
Regards,<br>
Subbarao<br></p>
</div>

Re: using third party jars in equinox

I simply create a plugin which contains one or more jars and export all 
packages off all jars included.

The plugin which needs the package has to import it.

In my eyes this is a very clean solution.
-

Note that eclipse supports this by using "New Project => Plug-in 
Development => Plug-in project from existing jar"

Abhishek Verma wrote:
> What is the best approach to use third party jars in more then one 
> plugins?
>
> Current aapproach:
> Create a plug-in with the third party jars and make other plug-ins 
> dependent on this plug-in. But I could not find a way to export the 
> 'jars' from the plug-in. Currently it works by exporting all the 
> packages in Manifest and specifying the jar as exportable in Java 
> Build Properties.
> Is there a better way to export 'Jars'?
>
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@...
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
>

Re: Declarative Services vs Spring

I think that's intentional. With OSGi you always have to be aware that
the services you depend on might go away, and possibly come back again
later. That's the essence of OSGi - it's dynamic. In this context an
"immutable final service reference" is an oxymoron.

Spring lives in a comfortable static world where dependencies, once
supplied, will live for at least as long as the things that depend on
them. In OSGi, that kind of assumption is only really valid for
intra-bundle dependencies. DS on the other can handle dynamic
inter-bundle dependencies, which IMHO makes it much more powerful.

On the other hand Spring has much more to it than dependency
injection. It also has a number of very powerful libraries, eg for
developing DAOs using JDBC or O/R mappers, an AOP library, remoting
libraries, etc. Because Spring is wonderfully modular, you can use as
much or as little of it as you like (just like Eclipse!).

- Neil

On 3/1/06, Subbarao Meduri <mkv <at> us.ibm.com> wrote:
>
>
> How does declarative services fare when compared with Spring framework in
> terms of its injection capabilities ? My apologies if this is already
> discussed on this forum.
>
>  Is there a reason why declarative services does not support constructor
> injection, for example ? It seems constructor injection is the only way to
> initialize a component that holds a immutable (final) service reference
> injected via its constructor.
>
>  Appreciate your thoughts.
>
>  Regards,
>  Subbarao
>
> _______________________________________________
> equinox-dev mailing list
> equinox-dev <at> eclipse.org
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
>
>
>

I think that's intentional. With OSGi you always have to be aware that
the services you depend on might go away, and possibly come back again
later. That's the essence of OSGi - it's dynamic. In this context an
"immutable final service reference" is an oxymoron.

Spring lives in a comfortable static world where dependencies, once
supplied, will live for at least as long as the things that depend on
them. In OSGi, that kind of assumption is only really valid for
intra-bundle dependencies. DS on the other can handle dynamic
inter-bundle dependencies, which IMHO makes it much more powerful.

On the other hand Spring has much more to it than dependency
injection. It also has a number of very powerful libraries, eg for
developing DAOs using JDBC or O/R mappers, an AOP library, remoting
libraries, etc. Because Spring is wonderfully modular, you can use as
much or as little of it as you like (just like Eclipse!).

- Neil

On 3/1/06, Subbarao Meduri <mkv <at> us.ibm.com> wrote:
>
>
> How does declarative services fare when compared with Spring framework in
> terms of its injection capabilities ? My apologies if this is already
> discussed on this forum.
>
>  Is there a reason why declarative services does not support constructor
> injection, for example ? It seems constructor injection is the only way to
> initialize a component that holds a immutable (final) service reference
> injected via its constructor.
>
>  Appreciate your thoughts.
>
>  Regards,
>  Subbarao
>
> _______________________________________________
> equinox-dev mailing list
> equinox-dev <at> eclipse.org
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
>
>
>

Re: Declarative Services vs Spring

<div>
<p>Agreed that OSGi is a more dynamic platform, and thus could say constructor injection is not the best thing that components should implement. However, if you take the view that OSGi is also a integration platform for components (where you don't necessarily have control over how a component is designed), it would make sense to me that declarative services support constructor injection. Obviously, it would not be a best practice, but it at least it will not inhibit a component that is not designed to leverage OSGi dynamic features from being integrated into the framework.<br><br>
Thoughts ?<br>
Subbarao<br><br>"Neil Bartlett" &lt;neil <at> integility.com&gt;<br><br><br></p>
<table width="100%" border="0" cellspacing="0" cellpadding="0"><tr valign="top">
<td width="40%">
<ul><ul><ul><ul>"Neil Bartlett" &lt;neil <at> integility.com&gt; <br>Sent by: equinox-dev-bounces@...
<p>03/01/2006 10:21 AM
</p>
<table border="1"><tr valign="top"><td width="168" bgcolor="#FFFFFF"><div align="center">Please respond to<br>
Equinox development mailing list &lt;equinox-dev@...&gt;</div></td></tr></table>
</ul></ul></ul></ul>
</td>
<td width="60%">
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td width="1%">
<br><div align="right">To</div>
</td>
<td width="100%">
<br>"Equinox development mailing list" &lt;equinox-dev@...&gt;</td>
</tr>
<tr valign="top">
<td width="1%">
<br><div align="right">cc</div>
</td>
<td width="100%"><br></td>
</tr>
<tr valign="top">
<td width="1%">
<br><div align="right">Subject</div>
</td>
<td width="100%">
<br>Re: [equinox-dev] Declarative Services vs Spring</td>
</tr>
</table>
<table border="0" cellspacing="0" cellpadding="0"><tr valign="top">
<td width="58"></td>
<td width="336"></td>
</tr></table>
</td>
</tr></table>
<br>I think that's intentional. With OSGi you always have to be aware that<br>
the services you depend on might go away, and possibly come back again<br>
later. That's the essence of OSGi - it's dynamic. In this context an<br>
"immutable final service reference" is an oxymoron.<br><br>
Spring lives in a comfortable static world where dependencies, once<br>
supplied, will live for at least as long as the things that depend on<br>
them. In OSGi, that kind of assumption is only really valid for<br>
intra-bundle dependencies. DS on the other can handle dynamic<br>
inter-bundle dependencies, which IMHO makes it much more powerful.<br><br>
On the other hand Spring has much more to it than dependency<br>
injection. It also has a number of very powerful libraries, eg for<br>
developing DAOs using JDBC or O/R mappers, an AOP library, remoting<br>
libraries, etc. Because Spring is wonderfully modular, you can use as<br>
much or as little of it as you like (just like Eclipse!).<br><br>
- Neil<br><br><br>
On 3/1/06, Subbarao Meduri &lt;mkv@...&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; How does declarative services fare when compared with Spring framework in<br>
&gt; terms of its injection capabilities ? My apologies if this is already<br>
&gt; discussed on this forum.<br>
&gt;<br>
&gt; &nbsp;Is there a reason why declarative services does not support constructor<br>
&gt; injection, for example ? It seems constructor injection is the only way to<br>
&gt; initialize a component that holds a immutable (final) service reference<br>
&gt; injected via its constructor.<br>
&gt;<br>
&gt; &nbsp;Appreciate your thoughts.<br>
&gt;<br>
&gt; &nbsp;Regards,<br>
&gt; &nbsp;Subbarao<br><br><br>
</div>

Re: using third party jars in equinox

Abhishek Verma wrote:
> What is the best approach to use third party jars in more then one plugins?
> 
> Current aapproach:
> Create a plug-in with the third party jars and make other plug-ins
> dependent on this plug-in. 

You should actually import the packages, not declare a dependency on the
plugin. That way, your plugins are independent of the actual packaging
of those other jars (if one day the other packages are supplied as
bundles, you can just drop those bundles into the framework and your
plugins continue to work).

> But I could not find a way to export the
> 'jars' from the plug-in. Currently it works by exporting all the
> packages in Manifest and specifying the jar as exportable in Java Build
> Properties.
> Is there a better way to export 'Jars'?

Exporting all the packages is exactly the right way, because it enables
you to re-package the bundles.

Harald

Declarative Services Logging ?

<div>
<p>Is there a easy way to turn on logging/tracing with Declarative Services ?<br><br>
My environment has the following bundles:<br>
	org.eclipse.equinox.ds_1.0.0<br>
	org.eclipse.osgi_3.2<br>
	org.eclipse.osgi.services_3.1<br><br>
Regards,<br>
Subbarao</p>
</div>

Re: Declarative Services Logging ?

<div>
<br>Declarative Services logs errors and
some warnings to the logservice if it is available. Install bundle org.eclipse.equinox.log.
<br><br>There is some tracing but you have to
switch it on in the code.
<br><br>Regards,<br>
Roy<br><br>
-----------------------------------------<br>
Roy Paterson<br>
IBM Pervasive Computing<br>
Austin, TX<br>
Phone: (512) 838-8898<br>
<br><br><br><table width="100%"><tr valign="top">
<td width="40%">Subbarao Meduri/Durham/IBM <at> IBMUS

<br>Sent by: equinox-dev-bounces@...
<p>03/01/2006 04:15 PM
</p>
<table border><tr valign="top"><td bgcolor="white">
<div align="center">Please respond to<br>
Equinox development mailing list &lt;equinox-dev@...&gt;</div>
</td></tr></table>
<br>
</td>
<td width="59%">
<table width="100%">
<tr valign="top">
<td>
<div align="right">To</div>
</td>
<td>Equinox development mailing list &lt;equinox-dev@...&gt;
</td>
</tr>
<tr valign="top">
<td>
<div align="right">cc</div>
</td>
<td>
</td>
</tr>
<tr valign="top">
<td>
<div align="right">Subject</div>
</td>
<td>[equinox-dev] Declarative Services Logging
?</td>
</tr>
</table>
<br><table><tr valign="top">
<td>
</td>
<td></td>
</tr></table>
<br>
</td>
</tr></table>
<br><br><br>Is there a easy way to turn on logging/tracing with Declarative
Services ?<br><br>
My environment has the following bundles:<br>
org.eclipse.equinox.ds_1.0.0<br>
org.eclipse.osgi_3.2<br>
org.eclipse.osgi.services_3.1<br><br>
Regards,<br>
Subbarao_______________________________________________<br>
equinox-dev mailing list<br>
equinox-dev@...<br>
https://dev.eclipse.org/mailman/listinfo/equinox-dev<br>
<br>
</div>