I've also came accross this new api-bundle and I am wondering why we cannot enhance the official JAR. I mean it is just about an entry in the manifest. Why are we not able to contribute this to the official javax.servlet-api artifact? Cant the OSGi alliance pull some strings?
regards Marc Von: Raymond Auge <[email protected]> An: felix users <[email protected]>, Datum: 28.03.2017 15:56 Betreff: Re: servlet API and Felix HTTP On Tue, Mar 28, 2017 at 3:48 PM, Raymond Auge <[email protected]> wrote: > It's because the regular bundle doesn't provide a Portal Java Contract > gah.... Portable Java Contract https://www.osgi.org/portable-java-contract-definitions/ - Ray > , the felix bundle does. > > - Ray > > On Tue, Nov 15, 2016 at 1:52 PM, Benson Margulies <[email protected]> > wrote: > >> rg.osgi.framework.BundleException: Unable to resolve >> org.apache.felix.http.jetty [65](R 65.0): missing requirement >> [org.apache.felix.http.jetty [65](R 65.0)] osgi.contract; >> (&(osgi.contract=JavaServlet)(version=3.1)) Unresolved requirements: >> [[org.apache.felix.http.jetty [65](R 65.0)] osgi.contract; >> (&(osgi.contract=JavaServlet)(version=3.1))] >> >> But I have this bundle: >> >> javax.servlet/javax.servlet-api/3.1.0 >> >> Do I also need the felix http servlet API bundle? >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > -- > *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> > (@rotty3000) > Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> > (@Liferay) > Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> > (@OSGiAlliance) > -- *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000) Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> (@Liferay) Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)
