10 Replies Latest reply on Apr 11, 2006 10:01 AM by andsch

    new text file in a CMS = crush

    merlith

      Hi

      I have a problem, with CMS in JBP 2.2.0. When i create new text file (for ex. the name of this file is: "textfile" and it was created in a directory with name "blabla") and when I redirect to main view (all directories - main view) and again try to enter to the blabla directory (where i created a text file) the cms portlet throw an exception like that:

      javax.jcr.PathNoFoundException /blabla/textfile/en
      ...
      ...
      ...

      What does it mean "en" in this path: /blabla/textfile/en maybe it is an error?

      What happen do u think? Have u ever the similar situation? What`s wrong? Is now any patch for this bug? (if only is a bug -maybe I do some wrong ;) )

      thnx & peace
      MB

        • 1. Re: new text file in a CMS = crush
          theute

          This has already been fixed in CVS

          • 2. Re: new text file in a CMS = crush
            merlith

            ok, thank you.

            peace
            MB

            • 3. Re: new text file in a CMS = crush
              merlith

              I have one question about that what has been fixed in CVS....
              Was it a big change? I have old version, where i did more code changes.... download fresh codes from CVS and adapt it to my version might be difficult. So, could you tell me where did you changes? in any *.java, or *.xml file? It would be easiest for me to download only changed files, then making a global update.


              thanks & regards
              MB

              • 4. Re: new text file in a CMS = crush
                theute

                Please use the diff features of CVS

                • 5. Re: new text file in a CMS = crush
                  andsch

                  Hi Thomas,
                  you wrote


                  This has already been fixed in CVS


                  Which version do you mean Portal 2.2.0 or Portal 2.4?

                  Kind Regards,
                  Andreas

                  • 6. Re: new text file in a CMS = crush
                    andsch

                    I just encountered a quite weird issue:

                    I've built jboss portal 2.4 from source and deployed it on jboss as 4.0.3SP1 as the exploded sar version.

                    I used Mozilla Firefox to access the CMSAdminPortlet and created a simple html file (aFile.html) in the default directory.
                    When I try to access this file with Firefox via http://localhost:8080/portal/content/default/aFile.html the error trace posted below shows up.

                    But when I use Internet Explorer to access the same file, a portal page shows up with the contents of aFile.html displayed in a portlet window.

                    I can modify aFile.html from both IE and Firefox but I can read it only from IE. This is pretty surprising to me as I expected the client would have nothing to do with this issue.

                    Maybe Firefox can be configured in a different manner so that the problem does not show up an someone can give me a hint?

                    Here's the error trace when accessing http://localhost:8080/portal/content/default/aFile.html with Firefox:

                    2006-04-11 13:18:51,822 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/portal].[PortalServletWithPathMapping]] Servlet.service() for servlet PortalServletWithPathMapping threw exception
                    java.lang.NullPointerException
                    at org.jboss.portal.core.cms.CMSObjectCommandFactory.doMapping(CMSObjectCommandFactory.java:93)
                    at org.jboss.portal.core.command.mapper.DelegatingCommandFactoryService.doMapping(DelegatingCommandFactoryService.java:138)
                    at sun.reflect.GeneratedMethodAccessor171.invoke(Unknown Source)
                    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                    at java.lang.reflect.Method.invoke(Method.java:585)
                    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
                    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
                    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118)
                    at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
                    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
                    at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
                    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
                    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
                    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
                    at $Proxy47.doMapping(Unknown Source)
                    at org.jboss.portal.core.model.portal.DefaultPortalCommandFactory.doMapping(DefaultPortalCommandFactory.java:65)
                    at sun.reflect.GeneratedMethodAccessor170.invoke(Unknown Source)
                    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                    at java.lang.reflect.Method.invoke(Method.java:585)
                    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
                    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
                    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118)
                    at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
                    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
                    at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
                    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
                    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
                    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
                    at $Proxy53.doMapping(Unknown Source)
                    at org.jboss.portal.core.CoreController.handle(CoreController.java:149)
                    at sun.reflect.GeneratedMethodAccessor169.invoke(Unknown Source)
                    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                    at java.lang.reflect.Method.invoke(Method.java:585)
                    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
                    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
                    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118)
                    at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
                    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
                    at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
                    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
                    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
                    at org.jboss.mx.util.JMXInvocationHandler.invoke(JMXInvocationHandler.java:273)
                    at $Proxy123.handle(Unknown Source)
                    at org.jboss.portal.server.ServerInvocation.dispatch(ServerInvocation.java:76)
                    at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:142)
                    at org.jboss.portal.server.aspects.server.NavigationInterceptor.invoke(NavigationInterceptor.java:64)
                    at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:37)
                    at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:132)
                    at org.jboss.portal.server.aspects.server.ContentTypeInterceptor.invoke(ContentTypeInterceptor.java:65)
                    at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:37)
                    at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:132)
                    at org.jboss.portal.core.aspects.server.LocaleInterceptor.invoke(LocaleInterceptor.java:73)
                    at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:37)
                    at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:132)
                    at org.jboss.portal.core.aspects.server.UserInterceptor.invoke(UserInterceptor.java:199)
                    at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:37)
                    at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:132)
                    at org.jboss.portal.server.aspects.server.SessionInvalidatorInterceptor.invoke(SessionInvalidatorInterceptor.java:84)
                    at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:37)
                    at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:132)
                    at org.jboss.portal.core.aspects.server.TransactionInterceptor.invoke(TransactionInterceptor.java:73)
                    at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:37)
                    at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:132)
                    at org.jboss.portal.server.aspects.server.ParametersInterceptor.invoke(ParametersInterceptor.java:107)
                    at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:37)
                    at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:132)
                    at org.jboss.portal.common.invocation.Invocation.invoke(Invocation.java:177)
                    at org.jboss.portal.server.servlet.PortalServlet.doGet(PortalServlet.java:231)
                    at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
                    at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
                    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
                    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
                    at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
                    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
                    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
                    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
                    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
                    at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
                    at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159)
                    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:407)
                    at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
                    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
                    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
                    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
                    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
                    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
                    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
                    at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
                    at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
                    at java.lang.Thread.run(Thread.java:595)


                    Kind regards
                    Andreas

                    • 7. Re: new text file in a CMS = crush
                      theute

                       

                      "andsch" wrote:
                      I've built jboss portal 2.4 from source and deployed it on jboss as 4.0.3SP1 as the exploded sar version.

                      I used Mozilla Firefox to access the CMSAdminPortlet and created a simple html file (aFile.html) in the default directory.
                      When I try to access this file with Firefox via http://localhost:8080/portal/content/default/aFile.html the error trace posted below shows up.

                      But when I use Internet Explorer to access the same file, a portal page shows up with the contents of aFile.html displayed in a portlet window.


                      I just tried and could not reproduce it, it works fine, the only issue you could have is about the language settings of Firefox that is different from IE.

                      • 8. Re: new text file in a CMS = crush
                        andsch

                        Thanks a lot Thomas,

                        your hint solved the problem. I changed the language settings in Firefox and now it works.
                        Is this behaviour by intention? The language settings were one of the last things I would have thought of.

                        By the way
                        I'm just building the forums portlet and the build fails because there are various libraries (e.g. apache-myfaces/myfaces-impl.jar) missing. I'm just searching and adding these, but maybe I missed a major step.

                        Here is what i did so far:
                        1. Downloaded the current portal 2.4 version (cvs co jboss-portal-2.4)
                        2. Have built jboss-portal
                        /build/build
                        3. Deployed it
                        /build/build exploded-deploy
                        This works fine as I used a preexisting datasource descriptor
                        4. Built datasources
                        /core/build datasource
                        5. TRIED to build forums
                        /forums/build
                        I'm still having problems so maybe I am missing something?

                        Thank you.
                        Kind Regards
                        Andreas

                        • 9. Re: new text file in a CMS = crush
                          theute

                          Fixed.
                          Thanks about warning me on that bug.
                          http://jira.jboss.org/jira/browse/JBPORTAL-819

                          • 10. Re: new text file in a CMS = crush
                            andsch

                            :-) Fine.

                            According to my second language (building forums portlet)
                            Could it be that the current forums module (when checking out cvs co jboss-portal-2.4 [this morning]) is not really buildable?

                            E.g. CategoryModelTestCase, ForumModelTestCase and ForumModelTestCase in org.jboss.portlet.test.forums all contained the import

                            import org.jboss.portlet.forums.security.ForumItemImpl;

                            but it seems ForumItemImpl has been deleted:

                            http://fisheye.jboss.com/viewrep/JBoss/jboss-portal/forums/src/main/org/jboss/portlet/forums/security/ForumItemImpl.java

                            After having deleted these import I get error messages about exceptions never being thrown. I'm not sure debugging this way is leading to a solution for me.

                            So which version of the forums portlet can I use?

                            Kind Regards
                            Andreas