Mailing-List: contact clerezza-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: clerezza-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
Sender: reto@trialox.org
In-Reply-To: <AANLkTiktJHVQKJ35cxfOvvj8Lfko-FXKhBF+3j2+LwrF@mail.gmail.com>
References: <AANLkTi=Oi54WGYeJHagZnBDpK48AuNiaYzOCi+R2ozEa@mail.gmail.com>
	<AANLkTi=_DxCi8WXLs_=6yPpHmPzwi6uu6cMRGpvH2XHU@mail.gmail.com>
	<AANLkTiktJHVQKJ35cxfOvvj8Lfko-FXKhBF+3j2+LwrF@mail.gmail.com>
Date: Wed, 23 Mar 2011 11:45:01 +0100
Message-ID: <AANLkTi=ZSO-2nvSH8N_6oAu1+FQ2nUVFk9Xpg7xdGoS-@mail.gmail.com>
Subject: Re: Problem with new typerendering mechanism
From: Reto Bachmann-Gmuer <reto.bachmann@trialox.org>
To: Hasan Hasan <hasan@trialox.org>
Cc: clerezza-dev@incubator.apache.org,
	Daniel Spicar <daniel.spicar@trialox.org>
Content-Type: multipart/alternative; boundary=00151748e94081983c049f240d36

--00151748e94081983c049f240d36
Content-Type: text/plain; charset=UTF-8

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 <hasan@trialox.org> 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
> SelectChannelConnector@0.0.0.0:8080
>
>
> On Wed, Mar 23, 2011 at 11:26 AM, Reto Bachmann-Gmuer <
> reto.bachmann@trialox.org> 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
>> <daniel.spicar@trialox.org>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
>> >
>>
>
>

--00151748e94081983c049f240d36--