-
-
2. Re: cms admin
gruenewa Jan 17, 2006 3:51 AM (in response to noicangi)I have the same error. It seems to me that it has to do with the choosen Locale. If i choose "english" as language everything seems to work fine. If i choose german as language i get a stack trace on the console. The stack trace is:
09:38:41,033 INFO [STDOUT] javax.jcr.PathNotFoundException: /default/products.html/en 09:38:41,036 INFO [STDOUT] at org.apache.jackrabbit.core.HierarchyManagerImpl.resolvePath(HierarchyManagerImpl.java:263) 09:38:41,036 INFO [STDOUT] at org.apache.jackrabbit.core.CachingHierarchyManager.resolvePath(CachingHierarchyManager.java:127) 09:38:41,036 INFO [STDOUT] at org.apache.jackrabbit.core.HierarchyManagerImpl.resolvePath(HierarchyManagerImpl.java:202) 09:38:41,036 INFO [STDOUT] at org.apache.jackrabbit.core.CachingHierarchyManager.resolvePath(CachingHierarchyManager.java:187) 09:38:41,036 INFO [STDOUT] at org.apache.jackrabbit.core.ItemManager.getItem(ItemManager.java:290) 09:38:41,036 INFO [STDOUT] at org.apache.jackrabbit.core.SessionImpl.getItem(SessionImpl.java:728) 09:38:41,036 INFO [STDOUT] at org.jboss.portal.cms.impl.jcr.ContentGetCommand.execute(ContentGetCommand.java:70) 09:38:41,036 INFO [STDOUT] at org.jboss.portal.cms.impl.jcr.JCRCommandContext.execute(JCRCommandContext.java:48) 09:38:41,036 INFO [STDOUT] at org.jboss.portal.cms.impl.jcr.FileGetCommand.execute(FileGetCommand.java:71) 09:38:41,036 INFO [STDOUT] at org.jboss.portal.cms.impl.jcr.JCRCommandContext.execute(JCRCommandContext.java:48) 09:38:41,037 INFO [STDOUT] at org.jboss.portal.cms.impl.jcr.FolderGetListCommand.execute(FolderGetListCommand.java:67) 09:38:41,037 INFO [STDOUT] at org.jboss.portal.cms.impl.jcr.JCRCommandContext.execute(JCRCommandContext.java:48) 09:38:41,037 INFO [STDOUT] at org.jboss.portal.cms.impl.jcr.JCRCMS.execute(JCRCMS.java:575) 09:38:41,037 INFO [STDOUT] at sun.reflect.GeneratedMethodAccessor134.invoke(Unknown Source) 09:38:41,037 INFO [STDOUT] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Of course the CMS Manager could not find the resource "/default/products.html/en". It should look for the resource "/default/products.html/de" instead, since i used german as language.
-
3. Re: cms admin
noicangi Jan 17, 2006 7:48 AM (in response to noicangi)yes gruenewa! its seems to be the same problem...
i have an idea but my knowledge about jboss its limited....if we try to use the filesystem?
please help me with the configuration of repository.xml to use the filesystem, maybe the language i use its going to work and its easier to move files. :) -
4. Re: cms admin
roy.russo Jan 17, 2006 11:13 AM (in response to noicangi)This problem was fixed in 2.2 CVS.
-
5. Re: cms admin
noicangi Jan 17, 2006 2:54 PM (in response to noicangi)another thing is when i try to edit a page....the html doesn't work properly, the colors, the size of the letter doesn't work. i tried using IE and firefox1.5
-
6. Re: cms admin
noicangi Jan 18, 2006 7:42 AM (in response to noicangi)thnks julien for the information about the new portal2.2.1rc1 realise,
but i have new questions about the portal:
using mysql4.1, winCRAP XP, jboss4.03sp1 and portal 2.0.1 when i upload an image the cms admin desapears,
in portal 2.2 if i upload an image in english its fine but the html editor doesn't work correctly.
is this a java problem || a browser problem || other?
thnx in advance,
noicangi -
7. Re: cms admin
noicangi Jan 20, 2006 11:24 AM (in response to noicangi)hi i solved my problems with portal 2.2.1rc1, for newbies here is the method:
to put up the portal with winxp + MYSQL4.1 connector 3.1 + portal-msql-DS.xml,
-download the jboss4.03sp1 bundled with the portal, do not run the installer.jar!! just unzip the file to the dir you like
-setup enviroment variables in winxp
-delete "portal-hsqldb-ds.xml" in /deploy and paste the MySQL one.
-put the connector 3.1 on the lib directory of the /default
and its going to run perfectly
now the topic:
i'm having problems with the cms admin portlet, then i try to edit an older html file the cms admin disapears, and when y try to edit the last one, the editor doen's change the letter or color or size,
i thought it was a javascript error, but y changed the tiny_mce dir under the C:\JBoss\server\default\deploy\jboss-portal.sar\portal-core.war\images\cms\admin
by the one in portal 2.0.1 which works, but it does't work.
i think its a cms portlet error.
i hope you could solve this problem un the editor, -
8. Re: cms admin
mdlatham Mar 9, 2006 4:48 PM (in response to noicangi)can anyone point me to some documentation on how to use the cms/portal ? i did the same process as noicangi to get it running on solaris 10. the instructions for adding the portal 2.2 to the app server DO NOT WORK! i tried on linux, sun, and os x. the bundled version is the only one to work. it must contain some required files not mentioned in the standard portal deploy.
-
9. Re: cms admin
theute Mar 10, 2006 3:47 AM (in response to noicangi)What is not working ? Explain what fails for you.
-
10. Re: cms admin
jordigor Mar 14, 2006 2:59 PM (in response to noicangi)Hi, first of all, thanks for your help!
I'm using jboss4.03sp1 + jbossportal2.2 bundled, linux with mysql 5.0 and connector 3.1 for mysql.
My problem is related with the next error:
[STDOUT] javax.jcr.PathNotFoundException. This error appears when I create a new HTML page with spanish language and then I try access to it. I've read this topic and noicangi has propose to use portal2.2.1rc1 realise. There aren't any alternative using a final realise?
Thanks in advance! -
11. Re: cms admin
ilangocal Mar 15, 2006 12:55 PM (in response to noicangi)"noicangi" wrote:
hi i solved my problems with portal 2.2.1rc1, for newbies here is the method:
to put up the portal with winxp + MYSQL4.1 connector 3.1 + portal-msql-DS.xml,
-download the jboss4.03sp1 bundled with the portal, do not run the installer.jar!! just unzip the file to the dir you like
-setup enviroment variables in winxp
-delete "portal-hsqldb-ds.xml" in /deploy and paste the MySQL one.
-put the connector 3.1 on the lib directory of the /default
and its going to run perfectly
now the topic:
i'm having problems with the cms admin portlet, then i try to edit an older html file the cms admin disapears, and when y try to edit the last one, the editor doen's change the letter or color or size,
i thought it was a javascript error, but y changed the tiny_mce dir under the C:\JBoss\server\default\deploy\jboss-portal.sar\portal-core.war\images\cms\admin
by the one in portal 2.0.1 which works, but it does't work.
i think its a cms portlet error.
i hope you could solve this problem un the editor,
Hi Noicangi
I was wondering if you checked out JBoss Portal 2.2 RC1. I am having problem with the CMS admin. -
12. Re: cms admin
jordigor Mar 15, 2006 2:43 PM (in response to noicangi)Hi ilangocal
Before I have written my problem I had read text that wrote Noicangi but I'm inteersting on using a Final Realese due to the fact we need to use the Portal in a Real environment. Anyway I've download de portal 2.2.1RC2 following the noicangi's instructions but appears the next error in the browser (FireFox):
HTTP Status 404 -
type Status report
message
description The requested resource () is not available.
Apache Tomcat/5.5
Moreover, when the Jboss is starting appears some differents errors:
[...]
2006-03-15 20:19:36,263 INFO [org.apache.myfaces.config.FacesConfigurator] Reading config jar:file:/usr/local/jboss-portal-2.2.1RC2-bundled/server/default/tmp/deploy/tmp52872tomahawk.jar!/META-INF/faces-config.xml
2006-03-15 20:19:36,331 INFO [org.apache.myfaces.config.FacesConfigurator] Reading config /WEB-INF/faces-config.xml
2006-03-15 20:19:36,930 DEBUG [javax.faces.application.ApplicationFactory] New ApplicationFactory instance created
2006-03-15 20:19:36,936 ERROR [org.apache.myfaces.util.LocaleUtils] Locale name null or empty, ignoring
2006-03-15 20:19:37,593 INFO [org.apache.myfaces.webapp.StartupServletContextListener] ServletContext
[...]
20:20:01,268 INFO [StandardQueryCache] starting query cache at region: org.hibernate.cache.StandardQueryCache
20:20:01,268 INFO [SessionFactoryImpl] Checking 0 named queries
20:20:01,620 WARN [ObjectDeployment] Cannot create portal object Portal[default] because the parent '' that the deployment descriptor references does not exist
20:20:01,627 WARN [ObjectDeployment] Cannot create portal object Page[CMS Manager] because the parent 'default' that the deployment descriptor references does not exist
20:20:01,628 WARN [ObjectDeployment] Cannot create portal object Page[management] because the parent 'default' that the deployment descriptor references does not exist
20:20:01,632 WARN [ObjectDeployment] Cannot create portal object Page[Secure Policy Config] because the parent 'default.default' that the deployment descriptor references does not exist
20:20:02,133 WARN [ObjectDeployment] Cannot create portal object Window[CatalogPortletWindow] because the parent 'default.CMS Manager' that the deployment descriptor references does not exist
20:20:02,829 INFO [LayoutDeployment] create new layout(s), found in : /portal
20:20:02,845 INFO [LayoutDeployment] done creating new layout(s), found in : /portal
20:20:06,429 WARN [ObjectDeployment] Cannot create portal object Page[Test] because the parent 'default' that the deployment descriptor references does not exist
[...]
file:/usr/local/jboss-portal-2.2.1RC2-bundled/server/default/deploy/jmx-console.war/WEB-INF/web.xml
2006-03-15 20:20:08,260 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.ejb:service=EJBTimerService,persistencePolicy=database
State: CONFIGURED
I Depend On:
jboss.jca:service=DataSourceBinding,name=DefaultDS
ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
State: CONFIGURED
I Depend On:
jboss.mq:service=Invoker
jboss.web:service=WebServer
ObjectName: jboss:service=KeyGeneratorFactory,type=HiLo
State: CONFIGURED
I Depend On:
jboss:service=TransactionManager
jboss.jca:service=DataSourceBinding,name=DefaultDS
ObjectName: jboss.mq:service=StateManager
State: CONFIGURED
I Depend On:
jboss.jca:service=DataSourceBinding,name=DefaultDS
Depends On Me:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq:service=DestinationManager
State: CONFIGURED
I Depend On:
jboss.mq:service=MessageCache
jboss.mq:service=PersistenceManager
jboss.mq:service=StateManager
jboss:service=Naming
Depends On Me:
jboss.mq.destination:service=Topic,name=testTopic
jboss.mq.destination:service=Topic,name=securedTopic
jboss.mq.destination:service=Topic,name=testDurableTopic
jboss.mq.destination:service=Queue,name=testQueue
jboss.mq.destination:service=Queue,name=A
jboss.mq.destination:service=Queue,name=B
jboss.mq.destination:service=Queue,name=C
jboss.mq.destination:service=Queue,name=D
jboss.mq.destination:service=Queue,name=ex
jboss.mq:service=SecurityManager
jboss.mq.destination:service=Queue,name=DLQ
ObjectName: jboss.mq:service=PersistenceManager
State: CONFIGURED
I Depend On:
jboss.jca:service=DataSourceBinding,name=DefaultDS
Depends On Me:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq.destination:service=Topic,name=testTopic
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager
ObjectName: jboss.mq.destination:service=Topic,name=securedTopic
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager
ObjectName: jboss.mq.destination:service=Topic,name=testDurableTopic
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager
ObjectName: jboss.mq.destination:service=Queue,name=testQueue
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager
ObjectName: jboss.mq.destination:service=Queue,name=A
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq.destination:service=Queue,name=B
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq.destination:service=Queue,name=C
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq.destination:service=Queue,name=D
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq.destination:service=Queue,name=ex
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq:service=Invoker
State: CONFIGURED
I Depend On:
jboss.mq:service=TracingInterceptor
jboss:service=Naming
Depends On Me:
jboss.mq:service=InvocationLayer,type=HTTP
jboss.mq:service=InvocationLayer,type=JVM
jboss.mq:service=InvocationLayer,type=UIL2
ObjectName: jboss.mq:service=TracingInterceptor
State: CONFIGURED
I Depend On:
jboss.mq:service=SecurityManager
Depends On Me:
jboss.mq:service=Invoker
ObjectName: jboss.mq:service=SecurityManager
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
Depends On Me:
jboss.mq.destination:service=Topic,name=testTopic
jboss.mq.destination:service=Topic,name=securedTopic
jboss.mq.destination:service=Topic,name=testDurableTopic
jboss.mq.destination:service=Queue,name=testQueue
jboss.mq:service=TracingInterceptor
jboss.mq.destination:service=Queue,name=DLQ
ObjectName: jboss.mq.destination:service=Queue,name=DLQ
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager
ObjectName: jboss.mq:service=InvocationLayer,type=JVM
State: CONFIGURED
I Depend On:
jboss.mq:service=Invoker
ObjectName: jboss.mq:service=InvocationLayer,type=UIL2
State: CONFIGURED
I Depend On:
jboss.mq:service=Invoker
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.jca:service=DataSourceBinding,name=DefaultDS
State: NOTYETINSTALLED
Depends On Me:
jboss.ejb:service=EJBTimerService,persistencePolicy=database
jboss:service=KeyGeneratorFactory,type=HiLo
jboss.mq:service=StateManager
jboss.mq:service=PersistenceManager
[...]
Thanks in advance! -
13. Re: cms admin
ilangocal Mar 15, 2006 3:41 PM (in response to noicangi)Hi
Did you configure the datasource properly. I guess you have the portal-*-ds.xml file..
I am going to try the latest release of JBoss portal -
14. Re: cms admin
jordigor Mar 15, 2006 6:30 PM (in response to noicangi)Hi
Yes I did. In fact I use the same portal-mysql-ds.xml file that I've used with portal 2.2.0 version and this works fine.
I'll expect impatient your test with the latest release.
Thx.