shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Demers (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SHIRO-390) OSGi Import for JSP (javax.servlet.jsp) should be declared optional
Date Fri, 15 Jul 2016 14:55:20 GMT

     [ https://issues.apache.org/jira/browse/SHIRO-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brian Demers updated SHIRO-390:
-------------------------------
    Fix Version/s:     (was: 1.3.0)

> OSGi Import for JSP (javax.servlet.jsp) should be declared optional
> -------------------------------------------------------------------
>
>                 Key: SHIRO-390
>                 URL: https://issues.apache.org/jira/browse/SHIRO-390
>             Project: Shiro
>          Issue Type: Bug
>    Affects Versions: 1.2.1
>         Environment: Eclipse Equinox
>            Reporter: Jan Stamer
>            Priority: Minor
>             Fix For: 1.2.2
>
>         Attachments: MANIFEST.MF
>
>
> I am using Shiro with OSGi (Equinox) in a web application. Yet I do not use JSP pages.
Therefore I use the shiro web bundle without requiring the package *.tags.
> So actually I do not need the jsp bundles as I don't use the tags. To avoid having to
include the jsp bundles the import should be declared optional. I hacked up the manifest to
suit my needs and it works just fine.
> Another option would be to create a separate package like "shiro.web.jsp" which contains
the code for using shiro with JSPs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message