You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by "Cristiano Gavião (JIRA)" <ji...@apache.org> on 2012/11/30 12:35:58 UTC

[jira] [Commented] (SHIRO-390) OSGi Import for JSP (javax.servlet.jsp) should be declared optional

    [ https://issues.apache.org/jira/browse/SHIRO-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507277#comment-13507277 ] 

Cristiano Gavião commented on SHIRO-390:
----------------------------------------

I'm facing the same problem. in my view optional is the best approach.
                
> 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
>         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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira