| behaviors of XML editors for manifest and component.xml [message #721590] |
Fri, 02 September 2011 04:32 |
 Jean-Claude Royer
Messages: 7
Registered: July 2009 |
Junior Member |
|
|
Hi all
I experimented few difficulties in using OSGi inside Eclipse, but may be I don't know very well equinox.
I will know if other users have similar problems regarding the behaviors of the editors
in using declarative services.
%-----
Eclipse SDK (but I tried also Helios 3.6.2 seems the same)
Version: 3.5.2
Build id: M20100211-1343
Max OSX 10.6.8
%-----
First, regarding the MANIFEST.MF editor.
I note that my projects often require (those which seems to work) "org.osgi.framework"
but adding it with the GUI does not work (in tab édependencies").
However, editing the XML is ok and the view is correctly updated.
Furthermore if I use "find unused plugins" eclipse want to remove this one
but also "org.eclipse.osgi and org....util and org...ds" and another personal package required to compile.
Is it a bug or a strange behavior ?
Regarding the component.xml editor one problem for me is the compliance between the first tab (overview) and the xml view.
At creation the box "This component is immediately started" is not editable but becomes editable when I modified the xml.
The xml description seems to consider that the option "This component is enable when started" (enabled="true") is implicit.
For instance
<scr:component xmlns:scr="http://www.osgi.org/xmlns/scr/v1.1.0" name="Clock4"> implies the box is checked
If I checked manually the box the option enable="true" is added in the xml.
Let me know, if useful I can go deeper in the details, or isolate a simple example illustrating this behavior.
regards
|
|
|
Powered by
FUDForum. Page generated in 0.03802 seconds
] 
Search
Help
Register
Login
Home
