Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

I have upgraded to Spring DM 1.2 but my custom extender/web extender configuration doesn work anymore. What has changed?

April 26, 2017anymore configuration Custom DM Extender spring upgraded web

0

Posted

I have upgraded to Spring DM 1.2 but my custom extender/web extender configuration doesn work anymore. What has changed?

1 Answer

0

Posted

Since Spring 2.5.6, the symbolic names of the artifacts have changed slightly. Spring DM aligned its symbolic names as well with the new patter since 1.2.0 M2. Thus the prefix org.springframework.bundle.osgi has been changed to org.springframework.osgi; for example Spring DM extender symbolic name was changed from org.springframework.bundle.osgi.extender to org.springframework.osgi.extender (notice the missing bundle word). To fix this problem, change the reference to the old symbolic name (usually inside the fragments manifests or LDAP filters) to the new one.