Re: Error on build checkout

Thanks to look at it, patch very welcome. Ask questions if needed.

About the kupu, I invest a little bit and found this :

$ find . -name kupublank.html -print | grep -v build
$ ./src/modules/kupu/resources/kupu/common/kupublank.html

here is the kupublank.html (error is left for kupublank.xml cause of 
Lenya processing)


$ rgrep kupublank . | grep -v .svn | grep -v build

$ ./src/modules/kupu/resources/kupu/default/drawers.kupu: 
id="kupu-linkdrawer-preview" src="kupublank.html">

$ ./src/modules/kupu/resources/kupu/apache-lenya/kupu/kupumacros.html: 
       <iframe frameborder="1" scrolling="auto" width="440" height="198" 
id="kupu-linkdrawer-preview" src="kupublank.html">

$ ./src/modules/kupu/resources/kupu/common/kupudrawers/drawer.xsl: 
           src="kupublank.html" scrolling="off" frameborder="0" 
width="0px" height="0px" display="None">

IMO, change
- src="kupublank.html"
to
- src="modules/kupu/resources/kupu/common/kupublank.html"
in file
- /src/modules/kupu/resources/kupu/apache-lenya/kupu/kupumacros.html
may solve this.

Let's editor killers says if it's the best way to proceed.

Can you try it and send some feedback ?

Thanks.
Have a good day

On 09/16/2010 01:14 PM, [email protected] wrote:
>
> Yes, that's exactly what I see.
>
> A direct publish doesn't seem to cause any problems, even with
> "notification" checkbox checked.
>
> However, Submit a modified document, and as a second step Publish a
> document with notification checked, gives the error you described.
>
> I'm looking into it today. Maybe I'll be able to find something to help
> fix it.
>
> -doug
>
> florent andré <[email protected]> wrote on 09/16/2010
> 06:04:57 AM:
>
>  > Hi Douglas,
>  >
>  > Thanks for this report.
>  >
>  > I just have a try to a "fresh" 2.0.3 on ubuntu with open-jdk-6
>  >
>  > When I directly publish, it's work
>  > When I commit then publish : commit work well, but publish says on form
>  > "Exception during commit or rollback: null (see logfiles for details)"
>  > ... but in fact, page is publish.
>  > Have to invest more on this.
>  >
>  >
>  > No more much time right now, will try kupu this afternoon.
>  >
>  > Cheers
>  >
>  >
>  > On 09/15/2010 05:21 PM, [email protected] wrote:
>  > >
>  > > Hi all,
>  > >
>  > > Maybe someone can shed some light on what might be common errors thrown
>  > > by a fresh build of a fresh checkout of Lenya 2.0.3.
>  > >
>  > > System:
>  > > OS X 10.5
>  > > JDK 1.5
>  > > JbossAS 5.1.0
>  > >
>  > > In general, the build works, I can log in and import the default
> content
>  > > to the default publication. However, when publishing and selecting the
>  > > options for notification, I get the following error:
>  > >
>  > > Caused by: org.mozilla.javascript.WrappedException: Wrapped
>  > > java.lang.IllegalStateException: No transition found for event
>  > > [checkPreconditions] in state [execChecked]!
>  > > (file:///Volumes/Sun/Installed/jboss_deploy/lenya.war/lenya/modules/
>  > > <
> <file:////Volumes/Sun/Installed/jboss_deploy/lenya.war/lenya/modules/>file:////Volumes/Sun/Installed/jboss_deploy/lenya.war/lenya/modules/>
>  > > usecase/usecases.js#254)
>  > >
>  > > and also:
>  > >
>  > > 2010-09-15 10:33:55,469 [ajp-192.168.1.2-8009-2] ERROR
> usecases.workflow
>  > > - Could not commit/rollback usecase [workflow.submit]:
>  > > java.lang.NullPointerException
>  > >
>  > >
>  > > I'm also getting a persistent Kupu error:
>  > >
>  > > 2010-09-15 10:33:43,527 [ajp-192.168.1.2-8009-3] ERROR
>  > > sitemap.handled-errors - Unable to get transformer handler for
>  > > cocoon://lenya-page/default/authoring/kupublank.xml
>  > >
>  > > Kupublank doesn't seem to exist.
>  > >
>  > > I've checked permissions and Jboss is able to write to write and read
>  > > the entire install base.
>  > >
>  > > Without using notification I can edit/publish as expected.
>  > >
>  > > Thanks for any light you can shed on why this would happen to a clean
>  > > checkout and build.
>  > >
>  > > -doug
>  >
>  > ---------------------------------------------------------------------
>  > To unsubscribe, e-mail: [email protected]
>  > For additional commands, e-mail: [email protected]
>  >