Ok - if I understand you right this would mean to change Felix OBR's code to strip the unrecognized operators before it calls BundleContextImpl.createFilter()? Or do you mean to change the Equinox implementation?
Thanx again, Michael -----Ursprüngliche Nachricht----- Von: Peter Kriens [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 30. September 2008 09:50 An: [email protected] Betreff: Re: AW: Problem with bindex/generation of repository.xml The problem is that the OSGi filter syntax is too restricted for the kind of things you need to do for OBR. Therefore, OBR implementations must add these operators as described in RFC 112. I am not sure what software you are running, but the software should adapt ... The OBR filter syntax is a superset of the OSGi filter syntax. Kind regards, Peter Kriens On 30 sep 2008, at 08:03, Hampel, Michael wrote: > > Hello Mr. Kriens, > > Thank you for your answer and clarifications - but I still have to > avoid the InvalidSyntaxException. > Would it be better to change bindex code to not add the mandatory > header or > To alter the Spring-core manifest file? > > Thanks again for any help, > > Michael > > > > > > -----Ursprüngliche Nachricht----- > Von: Peter Kriens [mailto:[EMAIL PROTECTED] > Gesendet: Montag, 29. September 2008 21:35 > An: [email protected] > Betreff: Re: Problem with bindex/generation of repository.xml > > The <* is an operator that I added to the filter. It mean that the > attribute can have multiple values and is therefor a set. This set > must then be a subset of the right hand site. RFC 112 elaborates this > further. I tried to get these operators (subset/superset) part of the > spec but it was rejected. However, OBR needed them to model mandatory > directive. There you have a set of attribute names that all needed to > be present. > > In this case, mandatory: is the set of attribute names in the > expression, and we verify that they are all there with <* operator. > Again, these operators did not make for the next OSGi release. > > Hope this helps, RFC 1112 can be found here: > http://www.osgi.org/Download/File?url=/download/rfc-0112_BundleRepository.pdf > > Kind regards, > > Peter Kriens > > > > On 29 sep 2008, at 13:00, Hampel, Michael wrote: > >> Hello, >> >> today I ran into a problem when generating my repository.xml with >> bindex: >> Spring-core has a manifest entry: >> org.eclipse.core.runtime;resolution:=optional;common=split >> >> Bindex will generate the following <require> entry: >> >> <require extend='false' >> filter='(&(package=org.eclipse.core.runtime)(version>=0.0.0) >> (comm >> on=split)(mandatory:<*common))' >> multiple='false' name='package' optional='true'> >> Import package org.eclipse.core.runtime >> </require> >> >> The problem is the >> >> mandatory:<*common >> >> entry - this will cause an org.osgi.framework.InvalidSyntaxException >> in >> the org.eclipse.osgi.framework.internal.core.FilterImpl class for the >> mandatory: input. >> >> Why does bindex add this attribute and what does it stand for? >> >> Thanx in advance for any help, >> >> Michael >> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
