The stuff in the blueprint.reflect, .blueprint.di, and .blueprint.container were never meant to be be "public" and should not have been used. When we went from 0.x to 1.0, we did lock them down to make sure you couldn't use them. There were some threads around the end of November 2011 that talked about some of them.
There is a org.apache.aries.blueprint.core.compatibility-1.0.0.jar that you can install as a fragment that would re-export those packages. However, I do strongly suggest you get your code updated to not rely on those packages. Dan On Oct 14, 2013, at 3:30 AM, Rajim Ulysse <[email protected]> wrote: > Hello all, > > I had some difficulties when trying to switch from ServiceMix 4.5.2 (Aries > Blueprint 0.3.1) and JBoss Fuse (Aries Blueprint 1.0.1). > > In fact, the OSGI bundles I was hot-deploying were using the package > org.apache.aries.blueprint.reflect which doesn’t seem to be included in the > new Aries version > 1.0.1http://grepcode.com/snapshot/repo1.maven.org/maven2/org.apache.aries.blueprint/org.apache.aries.blueprint.core/1.0.1/ > (you can compare with version 0.3.1 > http://grepcode.com/snapshot/repo1.maven.org/maven2/org.apache.aries.blueprint/org.apache.aries.blueprint.core/0.3.1/). > > I then used the 1.1.0 version and modified the MANIFEST.mf of > org.apache.aries.blueprint.core.jar in order to specify that the > org.apache.aries.blueprint.reflect package had to be exported. > > I would like to know why this package wasn’t exported for the OSGI bundles to > use it ? Do you think that it’s an oversight or rather that the reflect > package is intentionally put aside ? > I am wondering if I’ll have to consider modifying the code of my OSGI bundles > later, when I’ll be using the latest versions of Aries Blueprint. Also if > I’ll have to modify the MANIFEST.MF file each time I want to use another > JBoss Fuse instance using Aries Blueprint 1.0.1. > > Thanks, > > > Ce message et les pièces jointes sont confidentiels et réservés à l'usage > exclusif de ses destinataires. Il peut également être protégé par le secret > professionnel. Si vous recevez ce message par erreur, merci d'en avertir > immédiatement l'expéditeur et de le détruire. L'intégrité du message ne > pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra > être recherchée quant au contenu de ce message. Bien que les meilleurs > efforts soient faits pour maintenir cette transmission exempte de tout virus, > l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne > saurait être recherchée pour tout dommage résultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended solely > for the addressee; it may also be privileged. If you receive this e-mail in > error, please notify the sender immediately and destroy it. As its integrity > cannot be secured on the Internet, the Worldline liability cannot be > triggered for the message content. Although the sender endeavours to maintain > a computer virus-free network, the sender does not warrant that this > transmission is virus-free and will not be liable for any damages resulting > from any virus transmitted. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
