Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Subject: dispatcherError: Could not setup transformer in the contractBean
	(was Re: Dispatcher rc1)
From: Thorsten Scherler <thorsten@apache.org>
To: dev@forrest.apache.org
In-Reply-To: <003a01c62803$a49d4120$0400a8c0@madaboutipv6>
References: <1138576606.8283.46.camel@localhost.localdomain>
	 <20060201080537.GA3761@igg.indexgeo.com.au> <43E0B1E4.3080302@apache.org>
	 <1138801657.14636.30.camel@localhost>
	 <20060202081541.GA19204@igg.indexgeo.com.au>
	 <003a01c62803$a49d4120$0400a8c0@madaboutipv6>
Content-Type: text/plain; charset=UTF-8
Date: Thu, 02 Feb 2006 18:57:07 +0100
Message-Id: <1138903027.8351.124.camel@localhost>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit

El jue, 02-02-2006 a las 22:19 +0800, Gav.... escribió:
> Doesn't work for me.
> 
> Then I didn't know how to patch properly. I copied and pasted the changes 
> into forrest-core.xconf.
> 
> Did all the other steps.
> 
> Then did forrest run on my 'Existing' v2 pili themed site.

Remember what I was saying about v2 and v3, when you started with v3, I
said something like, bravery will be honored by not having to adopt the
new contract grammar.

You *cannot* use v2 contracts (nor v2 structurer) in the dispatcher. See
the "Subversion Commits" of http://issues.apache.org/jira/browse/FOR-787
(thx again cdupoirieux as well for keeping track) then you know how to
update your contracts.


> 
> I get :-
> 
> dispatcherError: 500 - Internal server error
> The contract "branding-logo" has thrown an exception by resolving the 
> implementation from "cocoon://resolve.contract.html.branding-logo".
> 
> dispatcherErrorStack:
> org.apache.forrest.dispatcher.DispatcherException: 500 - Internal server 
> error
> component: ContractBean
> message:
> Could not setup transformer in the contractBean.
> Please check that the contract implementation is wellformed and valid!
> 
> One reason that an implementation may not be valid is that you are using 
> variables that cannot be resolved.
> Please see the logs and the sysout for more information, you may are see 
> right away the error.
> 

Yeah, actually that pretty much said it all, didn't it? ;-)

"Please check that the contract implementation is wellformed and valid!"

v2 and v1 contracts are not valid contract implementations for the
dispatcher.

BTW IMO one of the best enhancement moving to java are this awesome
error messages. I actually added heaps of them, so it will become easier
to know what the actual error may be by seeing the error stack. ;-)

HTH
-- 
thorsten

"Together we stand, divided we fall!" 
Hey you (Pink Floyd)