« Return to Thread: [galaxy-dev] Best way to index OSGi packages

Re: [galaxy-dev] Best way to index OSGi packages

by Ross Mason-3 :: Rate this Message:

Reply (Restricted by the Administrator) | Reply to Author | View in Thread

Good stuff Andrew!  Will it be possible to actually load the classes in Groovy? I'd like to have indexes and policies for annotations on the class...

Cheers,

Ross Mason
CTO, Co-Founder
MuleSource Inc.






On 6 Mar 2008, at 19:45, Andrew Perepelytsya wrote:

Guys,

Would love to hear on the following subject. Attached is the formatted atom entry for the indexed OSGi bundle (it's the Mule Core OSGi version from the 2.1 branch). There are 2 ways indexed properties are presented currently:
  1. Simple string property with a delimiter, see e.g. jar.manifest.Export-Package
  2. A custom-parsed value, when a list/array is saved, e.g. jar.manifest.entries
Naturally, the latter fits better for the programmatic web and JCR happily saves lists without any issues. Allows to run XPath on atom responses too. However, the 1st is the way it is presented in an OSGi manifest (standard way). Do we want to process it and make it more machine-friendly? The UI displays both merely identically, the only difference is OSGi headers have no extra space after the delimiter.

BTW, a search like

select artifact where jar.manifest.entires in ('org.mule.container.MuleContainerContext')

already works great :)

Andrew
<response.xml>---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://admin.muleforge.org/manage_email


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "MuleForge Dev" group.
To post to this group, send email to muleforgedev@...
To unsubscribe from this group, send email to muleforgedev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/muleforgedev?hl=en
-~----------~----~----~----~------~----~------~--~---

 « Return to Thread: [galaxy-dev] Best way to index OSGi packages