Hello

czw., 3 lis 2022 o 12:37 Vamshi Krishna (External) <
vamkris...@blackberry.com> napisaƂ(a):

> Hi Grzegorz Grzybek,
>
>
>
> Please review give below issue.
>
>
>
> *Server Core :: Login Module (85)*
>
> *--------------------------------*
>
> *Status: GracePeriod*
>
> *Blueprint*
>
> *11/3/22, 3:58 PM*
>
> *Missing dependencies:*
>
> *(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://karaf.apache.org/xmlns/jaas/v1.0.0
> <http://karaf.apache.org/xmlns/jaas/v1.0.0>))*
>
> *Declarative Services*
>
>
>

"http://karaf.apache.org/xmlns/jaas/v1.0.0"; namespace is handled by
org.apache.karaf.jaas.blueprint.config.impl.NamespaceHandler which is part
of org.apache.karaf.jaas.blueprint.config bundle which is available in
"jaas-deployer" feature in Karaf 4.4.1 - please install this feature and
the problem should be gone.

regards
Grzegorz Grzybek


> Thanks,
>
> VamsiKrishna.
>
>
>
> *From:* Vamshi Krishna (External)
> *Sent:* Thursday, November 3, 2022 4:01 PM
> *To:* 'dev@karaf.apache.org' <dev@karaf.apache.org>; '
> iss...@karaf.apache.org' <iss...@karaf.apache.org>; 'u...@karaf.apache.org'
> <u...@karaf.apache.org>
> *Subject:* RE: Issue with
> org.eclipse.jetty.security.jaspi/9.4.46.v20220331 in KARAF 4.4.1
>
>
>
> Hi Grzegorz Grzybek,
>
>
>
> Thank you for looking into this.
>
>
>
> I have updated as per KARAF release notes (4.4.0 & 4.4.1 version)
> https://github.com/apache/karaf/blob/main/RELEASE-NOTES.md
>
>
>
> In feature.xml of my product, I specifically activated "org.eclipse.jetty"
> version.
>
>
>
> Simply comment out JASPI in feature.xml and try "org.eclipse.jetty" with
> 9.4.48.v20220622 version. The GracePeriod status was one of the Login
> Modules.
>
>
>
> Server Core :: Login Module (85)
>
> --------------------------------
>
> Status: GracePeriod
>
> Blueprint
>
> 11/3/22, 3:58 PM
>
> Missing dependencies:
>
>
> (&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=
> http://karaf.apache.org/xmlns/jaas/v1.0.0))
>
> Declarative Services
>
>
>
> Thanks,
>
> VamsiKrishna.
>
>
>
> *From:* Vamshi Krishna (External)
> *Sent:* Thursday, November 3, 2022 3:49 PM
> *To:* 'dev@karaf.apache.org' <dev@karaf.apache.org>; '
> iss...@karaf.apache.org' <iss...@karaf.apache.org>; u...@karaf.apache.org
> *Subject:* RE: Issue with
> org.eclipse.jetty.security.jaspi/9.4.46.v20220331 in KARAF 4.4.1
>
>
>
> Hi Grzegorz Grzybek,
>
>
>
> Thank you for looking into this.
>
>
>
> I have updated as per KARAF release notes (4.4.0 & 4.4.1 version)
> https://github.com/apache/karaf/blob/main/RELEASE-NOTES.md
>
>
>
> In feature.xml of my product, I specifically activated "org.eclipse.jetty"
> version.
>
>
>
> Simply comment out JASPI in feature.xml and try "org.eclipse.jetty" with
> 9.4.48.v20220622. The GracePeriod status was one of the Login Modules.
>
>
>
>
>
> Thanks,
>
> Vamsi Krishna.
>
> *From:* Vamshi Krishna (External)
> *Sent:* Wednesday, November 2, 2022 11:09 PM
> *To:* dev@karaf.apache.org; 'iss...@karaf.apache.org' <
> iss...@karaf.apache.org>
> *Subject:* Issue with org.eclipse.jetty.security.jaspi/9.4.46.v20220331
> in KARAF 4.4.1
>
>
>
> Hi Team,
>
>
>
> I have migrating KARAF from 4.2.15 to 4.4.1 along with Eclipse jetty
> server also from 9.4.42 to 9.4.46.v2022033. When I start KARAF having
> wiring issue.
>
>
>
> Error: missing requirement
> org.eclipse.jetty.security.jaspi/9.4.46.v20220331] osgi.extender;
> osgi.extender=osgi.serviceloader.registrar).
>
>
>
> Please can you any take a look at once.
>
>
>
> Thanks
> ------------------------------
> This transmission (including any attachments) may contain confidential
> information, privileged material (including material protected by the
> solicitor-client or other applicable privileges), or constitute non-public
> information. Any use of this information by anyone other than the intended
> recipient is prohibited. If you have received this transmission in error,
> please immediately reply to the sender and delete this information from
> your system. Use, dissemination, distribution, or reproduction of this
> transmission by unintended recipients is not authorized and may be unlawful.
>

Reply via email to