hi daniel, refreshing cms.cache bundle with felix shell command seems to make it work. please investigate whether it has to do with starting cms.cache before renderletmanager
hasan On Wed, Mar 23, 2011 at 11:56 AM, Hasan Hasan <[email protected]> wrote: > no, no relation to the typerendering problem. just noticed that. > it seems the problem relates to cms.cache... needs to investigate more > > hasan > > > On Wed, Mar 23, 2011 at 11:45 AM, Reto Bachmann-Gmuer < > [email protected]> wrote: > >> yes, devtools reuires the clerezza shell for the dsl extension it provides >> - possibly this dependency could be declared optional. >> >> note that the clerezza shell bundle need not to be active but just >> installed, sou you can still use the shell you prefer. >> >> Btw, don't see how this relates to the typerendering problem. >> >> Cheers >> Reto >> >> On Wed, Mar 23, 2011 at 11:37 AM, Hasan Hasan <[email protected]> wrote: >> >>> i tried to reproduce the problem >>> and saw this error message which means devtool requires zz shell which is >>> not there in trialox cms >>> >>> hasan >>> >>> ERROR: Error starting >>> mvn:org.apache.clerezza/bundledevtool/0.1-incubating-SNAPSHOT >>> (org.osgi.framework.BundleException: Unresolved constraint in bundle >>> org.apache.clerezza.bundledevtool [37]: Unable to resolve 37.0: missing >>> requirement [37.0] package; (package=org.apache.clerezza.shell)) >>> org.osgi.framework.BundleException: Unresolved constraint in bundle >>> org.apache.clerezza.bundledevtool [37]: Unable to resolve 37.0: missing >>> requirement [37.0] package; (package=org.apache.clerezza.shell) >>> at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3416) >>> at org.apache.felix.framework.Felix.startBundle(Felix.java:1714) >>> at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1143) >>> at >>> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264) >>> at java.lang.Thread.run(Thread.java:619) >>> [SCR Component Actor] INFO org.eclipse.jetty.util.log - Started >>> [email protected]:8080 >>> >>> >>> On Wed, Mar 23, 2011 at 11:26 AM, Reto Bachmann-Gmuer < >>> [email protected]> wrote: >>> >>>> Hi Daniel >>>> >>>> Clearly it shouldn't break compatibility as long as you're using >>>> renderletmanager. Most of clerezza (all but accountcontrolpanel) is >>>> still >>>> using this meschanism. >>>> >>>> After registering a template you should see an additional service, e.g. >>>> with >>>> the felix webconsole. >>>> >>>> Cheers, >>>> Reto >>>> >>>> On Wed, Mar 23, 2011 at 10:44 AM, Daniel Spicar >>>> <[email protected]>wrote: >>>> >>>> > Hi all, >>>> > >>>> > I ran into a problem with Trialox CMS today. I recompiled my workspace >>>> with >>>> > the latest clerezza buiild and now none of our web pages work. I get >>>> the >>>> > following exception: >>>> > >>>> > java.lang.RuntimeException: no renderer could be created for >>>> > org.apache.clerezza.rdf.core.BNode@20fcda5d (in <some graph> , >>>> > org.apache.clerezza.rdf.core.BNode@73087d19 < >>>> > http://clerezza.org/2009/11/global-menu#path> "/admin/update"^^< >>>> > http://www.w3.org/2001/XMLSchema#string>.]), menu-cache -ignoreRes >>>> > -perUser,[application/xhtml+xml] >>>> > >>>> > I am not sure where the problem lies. All our pages use the old >>>> > renderletmanager as far as I can tell. It is deprecated but does that >>>> mean >>>> > that it doesn't work at all anymore? I was under the impression the >>>> old >>>> > mechanism should still work. Am I wrong? >>>> > >>>> > Can anyone help me? >>>> > >>>> > Best, >>>> > Daniel >>>> > >>>> >>> >>> >> >
