I download the full source from shiro svn and build sample web application
using maven (mvn clean install). The build process works fine (no error). It
is just after starting up the web sample (no spring and hibernate)
application, navigating to the page e.g. clicking the login hyper link the
exception is thrown. 

That's why I am confused. Not very sure what goes wrong.

The env I use is Debian kernel 2.6.30, Maven 2.0.9, Java 1.6.0_10, apache
tomcat 6.0.18.

The ShiroFilter configuration in web.xml is as below
(shiro/samples/web/src/main/webapp/WEB-INF/web.xml)

    <filter>
        <filter-name>ShiroFilter</filter-name>
       
<filter-class>org.apache.shiro.web.servlet.ShiroFilter</filter-class>
        <init-param>
            <param-name>config</param-name>
            <param-value>

                # The ShiroFilter configuration is very powerful and
flexible, while still remaining succinct.
                # Please read the comprehensive example, with full comments
and explanations, in the JavaDoc:
                #
                #
http://shiro.apache.org/api/org/apache/shiro/web/servlet/ShiroFilter.html

                [main]

                demoRealm = org.apache.shiro.realm.text.PropertiesRealm

                [filters]
                shiro.loginUrl = /login.jsp

                [urls]
                # The /login.jsp is not restricted to authenticated users
(otherwise no one could log in!), but
                # the 'authc' filter must still be specified for it so it
can process that url's
                # login submissions. It is 'smart' enough to allow those
requests through as specified by the
                # shiro.loginUrl above.
                /login.jsp = authc

                /account/** = authc
                /remoting/** = authc, roles[b2bClient],
perms[remote:invoke:"lan,wan"]

            </param-value>
        </init-param>
    </filter>

    <filter-mapping>
        <filter-name>ShiroFilter</filter-name>
        <url-pattern>/*</url-pattern>
    </filter-mapping>



mad.rug wrote:
> 
> Is ShiroFilter OK in your web.xml?If you used the sample to build your own
> test application, you might have left if behind.
> In this case, use the build script and deploy it, you should have no
> problems at all.
> 
> On Mon, Aug 24, 2009 at 1:42 PM, Neo Anderson
> <[email protected]>wrote:
> 
>>
>>
>> Thanks. That looks like can be done by simply adding new version tag lib
>> from
>>
>> http://www.apache.org/dist/jakarta/taglibs/standard/jakarta-taglibs-standard-current.zip
>> (http://forums.sun.com/thread.jspa?threadID=486791)
>>
>> But still there's other error
>>
>> java.lang.IllegalStateException: No ServletRequest found in
>> ThreadContext.
>> Make sure WebUtils.bind() is being called. (typically called by
>> ShiroFilter)
>> This could also happen when running integration tests that don't properly
>> call WebUtils.bind().
>>
>> 
>> org.apache.shiro.web.WebUtils.getRequiredServletRequest(WebUtils.java:351)
>>
>>
>> org.apache.shiro.web.session.ServletContainerSessionManager.doGetSession(ServletContainerSessionManager.java:69)
>>
>>
>> org.apache.shiro.session.mgt.AbstractSessionManager.getSession(AbstractSessionManager.java:246)
>>
>>
>> org.apache.shiro.session.mgt.AbstractSessionManager.checkValid(AbstractSessionManager.java:265)
>>
>>
>> org.apache.shiro.mgt.SessionsSecurityManager.checkValid(SessionsSecurityManager.java:294)
>>
>>
>> org.apache.shiro.mgt.DefaultSecurityManager.getSession(DefaultSecurityManager.java:196)
>>
>>
>> org.apache.shiro.mgt.DefaultSecurityManager.resolveSessionIfNecessary(DefaultSecurityManager.java:437)
>>
>>
>> org.apache.shiro.mgt.DefaultSecurityManager.getSubject(DefaultSecurityManager.java:403)
>>
>>  org.apache.shiro.subject.SubjectBuilder.build(SubjectBuilder.java:95)
>>       
>> org.apache.shiro.web.servlet.ShiroFilter.bind(ShiroFilter.java:486)
>>
>>
>> org.apache.shiro.web.servlet.ShiroFilter.doFilterInternal(ShiroFilter.java:573)
>>
>>
>> org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:190)
>>
>>
>> Need to check what goes wrong there first. Thanks again for the answer.
>>
>> Thank you.
>>
>>
>>
>>
>> mad.rug wrote:
>> >
>> > Try this:
>> > http://forums.sun.com/thread.jspa?threadID=5213387
>> >
>> > On Mon, Aug 24, 2009 at 11:20 AM, Neo Anderson
>> > <[email protected]
>> >> wrote:
>> >
>> >>
>> >> I try to deploy the sample web application (one that doesn't integrate
>> >> with
>> >> srping, hibernate) to tomcat 6.0.18. However, when starting up, it
>> throws
>> >>
>> >> org.apache.jasper.JasperException: /home.jsp(19,0) The absolute uri:
>> >> http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml
>> or
>> >> the jar files deployed with this application
>> >>
>> >>
>> >> I try to change the uri in include.jsp to
>> http://java.sun.com/jstl/core
>> >> (older version), but it still does not work.
>> >>
>> >> What version deos the jstl use? or how to fix this problem?
>> >>
>> >> Thanks.
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://n2.nabble.com/http-java-sun-com-jstl-core-cannot-be-resolved-error-tp3503668p3503668.html
>> >> Sent from the Shiro User mailing list archive at Nabble.com.
>> >>
>> >
>> >
>>
>> --
>> View this message in context:
>> http://n2.nabble.com/http-java-sun-com-jstl-core-cannot-be-resolved-error-tp3503668p3504661.html
>> Sent from the Shiro User mailing list archive at Nabble.com.
>>
> 
> 

-- 
View this message in context: 
http://n2.nabble.com/http-java-sun-com-jstl-core-cannot-be-resolved-error-tp3503668p3505300.html
Sent from the Shiro User mailing list archive at Nabble.com.

Reply via email to