David Crossley | 1 Feb 01:03 2006
Picon

Re: why is forrest xml output not utf-8

Ross Gardler wrote:
> David Crossley wrote:
> >I don't know much about encodings, but why are the documents output
> >by our xml serializer as ISO-8859-1 rather than UTF-8?
> 
> I'm confused, I thought we were outputing UTF-8, certainly recent 
> messages on the user list say we are.

For "html" we are. I am talking about xml output
both internal and final.

Ah, i just found something interesting ...

If we look at an xml output via 'forrest run'
e.g. localhost:8888/index.xml then yes the
encoding is UTF-8.

However in command-line 'forrest site' mode
the xml documents are ISO-8859-1. Try it in
our site-author which produces a few example
xml output docs (index.xml and faq.xml).

This uses the "xml-document" serializer declared
in main/webapp/sitemap.xmap

Specifically set the "encoding" parameter to be
UTF-8 and all is well in both Forrest modes.

-David

(Continue reading)

Thorsten Scherler | 1 Feb 01:05 2006
Picon

Re: why is forrest xml output not utf-8

El mar, 31-01-2006 a las 20:39 +0000, Ross Gardler escribió:
> David Crossley wrote:
> > I don't know much about encodings, but why are the documents output
> > by our xml serializer as ISO-8859-1 rather than UTF-8?
> 
> I'm confused, I thought we were outputing UTF-8, certainly recent 
> messages on the user list say we are.
> 

Forrest is using UTF-8 in both skins and the dispatcher as *HTML*
serializer.

main/webapp/sitemap.xmap
...
<map:serializer name="html" mime-type="text/html"
src="org.apache.cocoon.serialization.HTMLSerializer">
 <doctype-public>-//W3C//DTD HTML 4.01 Transitional//EN</doctype-public>
 <doctype-system>http://www.w3.org/TR/html4/loose.dtd</doctype-system>
 <encoding>UTF-8</encoding>
</map:serializer>

dispatcher/internal.xmap
...
<map:serializer logger="sitemap.serializer.xhtml" mime-type="text/html" 
 name="xhtml" pool-grow="2" pool-max="64" pool-min="2" 
 src="org.apache.cocoon.serialization.XMLSerializer">
 <doctype-public> -//W3C//DTD XHTML 1.0 Strict//EN </doctype-public>
 <doctype-system> http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd 
  </doctype-system>
 <encoding>UTF-8</encoding>
(Continue reading)

David Crossley | 1 Feb 01:46 2006
Picon

Re: why is forrest xml output not utf-8

Thorsten Scherler wrote:
> Ross Gardler escribi??:
> > David Crossley wrote:
> > > I don't know much about encodings, but why are the documents output
> > > by our xml serializer as ISO-8859-1 rather than UTF-8?
> > 
> > I'm confused, I thought we were outputing UTF-8, certainly recent 
> > messages on the user list say we are.
> 
> Forrest is using UTF-8 in both skins and the dispatcher as *HTML*
> serializer.
> 
> main/webapp/sitemap.xmap
> ...
> <map:serializer name="html" mime-type="text/html"
> src="org.apache.cocoon.serialization.HTMLSerializer">
>  <doctype-public>-//W3C//DTD HTML 4.01 Transitional//EN</doctype-public>
>  <doctype-system>http://www.w3.org/TR/html4/loose.dtd</doctype-system>
>  <encoding>UTF-8</encoding>
> </map:serializer>
> 
> dispatcher/internal.xmap
> ...
> <map:serializer logger="sitemap.serializer.xhtml" mime-type="text/html" 
>  name="xhtml" pool-grow="2" pool-max="64" pool-min="2" 
>  src="org.apache.cocoon.serialization.XMLSerializer">
>  <doctype-public> -//W3C//DTD XHTML 1.0 Strict//EN </doctype-public>
>  <doctype-system> http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd 
>   </doctype-system>
>  <encoding>UTF-8</encoding>
(Continue reading)

David Crossley | 1 Feb 09:05 2006
Picon

Re: Dispatcher rc1

Thorsten Scherler wrote:
> 
> I did a big step towards the first release and want to present the first
> candidate (rc1) of the dispatcher (current trunk - r373373). Besides
> some issues where I could use a helping hand, the biggest bugs are
> fixed.
> 
> Please test the rc1.

I am having trouble. Using head of trunk.
Did 'build clean; build'
Did local-deploy of the two new plugins.
Added the new plugins to my forrest.properties
Did 'forrest run' ...

dispatcherError:
Could not set up the "hooks transformer".

DispatcherStack:
org.apache.excalibur.source.SourceException: Could not resolve locationmap location.
at <map:serialize type="xhtml"> - file:/svn/asf/forrest/build/plugins/org.apache.forrest.plugin.internal.dispatcher/internal.xmap:145:39
at <map:transform type="dispatcher"> - file:/svn/asf/forrest/build/plugins/org.apache.forrest.plugin.internal.dispatcher/internal.xmap:140:42
at <map:generate type="jx"> - file:/svn/asf/forrest/build/plugins/org.apache.forrest.plugin.internal.dispatcher/internal.xmap:135:67
at <map:mount> - file:/svn/asf/incubator-Anakia/build/tmp/internal.xmap:33:150
at <map:mount> - file:/svn/asf/forrest/main/webapp/sitemap.xmap:394:117

Ross Gardler | 1 Feb 14:04 2006
Picon

Re: Dispatcher rc1

David Crossley wrote:
> Thorsten Scherler wrote:
> 
>>I did a big step towards the first release and want to present the first
>>candidate (rc1) of the dispatcher (current trunk - r373373). Besides
>>some issues where I could use a helping hand, the biggest bugs are
>>fixed.
>>
>>Please test the rc1.
> 
> 
> I am having trouble. Using head of trunk.

...

I have similar (identical?) problems doing forrest run to examine the 
docs in  either of the two rc1 plugins.

In error.log I see:

org.apache.cocoon.ProcessingException: Error during resolving of 
'lm://resolve.structurer.index'.
...
Caused by: org.apache.excalibur.source.SourceException: Could not 
resolve locationmap location.

I'll try and find some time to look into this, but I'm on a deadline for 
a new site, so it looks like I'll do it with the old skin system for now.

Should have more time at the end of the week.
(Continue reading)

Thorsten Scherler | 1 Feb 14:47 2006
Picon

Re: Dispatcher rc1

El mié, 01-02-2006 a las 13:04 +0000, Ross Gardler escribió:
> David Crossley wrote:
> > Thorsten Scherler wrote:
> > 
> >>I did a big step towards the first release and want to present the first
> >>candidate (rc1) of the dispatcher (current trunk - r373373). Besides
> >>some issues where I could use a helping hand, the biggest bugs are
> >>fixed.
> >>
> >>Please test the rc1.
> > 
> > 
> > I am having trouble. Using head of trunk.
> 
> ...
> 
> I have similar (identical?) problems doing forrest run to examine the 
> docs in  either of the two rc1 plugins.
> 
> In error.log I see:
> 
> org.apache.cocoon.ProcessingException: Error during resolving of 
> 'lm://resolve.structurer.index'.
> ...
> Caused by: org.apache.excalibur.source.SourceException: Could not 
> resolve locationmap location.
> 

1) did you applied the patch from:
https://issues.apache.org/jira/browse/FOR-796
(Continue reading)

Ross Gardler | 1 Feb 16:37 2006
Picon

Re: Dispatcher rc1

Thorsten Scherler wrote:
> El mié, 01-02-2006 a las 13:04 +0000, Ross Gardler escribió:
> 
>>David Crossley wrote:
>>
>>>Thorsten Scherler wrote:
>>>
>>>
>>>>I did a big step towards the first release and want to present the first
>>>>candidate (rc1) of the dispatcher (current trunk - r373373). Besides
>>>>some issues where I could use a helping hand, the biggest bugs are
>>>>fixed.
>>>>
>>>>Please test the rc1.
>>>
>>>
>>>I am having trouble. Using head of trunk.
>>
>>...
>>
>>I have similar (identical?) problems doing forrest run to examine the 
>>docs in  either of the two rc1 plugins.
>>
>>In error.log I see:
>>
>>org.apache.cocoon.ProcessingException: Error during resolving of 
>>'lm://resolve.structurer.index'.
>>...
>>Caused by: org.apache.excalibur.source.SourceException: Could not 
>>resolve locationmap location.
(Continue reading)

Thorsten Scherler | 1 Feb 18:03 2006

Re: Dispatcher rc1

El mié, 01-02-2006 a las 15:37 +0000, Ross Gardler escribió:
> Thorsten Scherler wrote:
> > El mié, 01-02-2006 a las 13:04 +0000, Ross Gardler escribió:
> > 
> >>David Crossley wrote:
> >>
> >>>Thorsten Scherler wrote:
> >>>
> >>>
> >>>>I did a big step towards the first release and want to present the first
> >>>>candidate (rc1) of the dispatcher (current trunk - r373373). Besides
> >>>>some issues where I could use a helping hand, the biggest bugs are
> >>>>fixed.
> >>>>
> >>>>Please test the rc1.
> >>>
> >>>
> >>>I am having trouble. Using head of trunk.
> >>
> >>...
> >>
> >>I have similar (identical?) problems doing forrest run to examine the 
> >>docs in  either of the two rc1 plugins.
> >>
> >>In error.log I see:
> >>
> >>org.apache.cocoon.ProcessingException: Error during resolving of 
> >>'lm://resolve.structurer.index'.
> >>...
> >>Caused by: org.apache.excalibur.source.SourceException: Could not 
(Continue reading)

Thorsten Scherler | 1 Feb 20:48 2006
Picon

to branch or not to branch part II (was Re: Dispatcher rc1)

El mié, 01-02-2006 a las 15:37 +0000, Ross Gardler escribió:
> To Branch or not to Branch?
> ===========================
> 
> [ASIDE] Don't worry Thorsten I'm not going to ask you to change anything 
> . I heard your frustration at the circular discussion about "to branch 
> or not to branch", that is why I stayed quite in the end, I was silently 
> agreeing to you just getting it done

Thanks for that, I really appreciate what you have done because I could
do the job.

> 
> This lack of ability to support both V2 and V3 during this work, which 
> Thorsten had previously warned us about, was the reason I recommended a 
> branch.

Actually the fault is lying in 
http://issues.apache.org/jira/browse/FOR-799
which normally should not be the standard situation for plugins and our
new properties system looks very promising to overcome the need for such
situations.

IMO Forrest should support different versions of plugins which should be
configurable on a project base. That would make it easy to develop
different versions of plugins without the need of a branch.

> 
> For the future reference of the community (not for Thorsten or any other 
> individual), if a development will temporarily break existing 
(Continue reading)

Thorsten Scherler (JIRA | 1 Feb 20:57 2006
Picon

[jira] Commented: (FOR-796) Merge all view/dispatcher work into org.apache.forrest.plugin.internal.dispatcher and org.apache.forrest.themes.core

    [ http://issues.apache.org/jira/browse/FOR-796?page=comments#action_12364866 ] 

Thorsten Scherler commented on FOR-796:
---------------------------------------

HEADSUP: Before you can work with the dispatcher you *have to* patch the forrest.xconf with the patch
(dispatcher-enabler.patch) attached to this issue!!!

This is due to FOR-799 and the fact that people are using v2 and we should support them till we finish this issue.

If you *do not* patch the core you may see something like the following:
org.apache.cocoon.ProcessingException: Error during resolving of 
'lm://resolve.structurer.index'.
...
Caused by: org.apache.excalibur.source.SourceException: Could not 
resolve locationmap location.

You should be able to answer "yes" to all of the following questions:
1) did you applied the attached patch?
2) are you on revision r373699 or higher (best HEAD)?
3) are you sure you did build.sh clean;./build.sh the forrest core (otherwise it will not
work!)
4) did you deploy the new plugins?

> Merge all view/dispatcher work into org.apache.forrest.plugin.internal.dispatcher and org.apache.forrest.themes.core
> --------------------------------------------------------------------------------------------------------------------
>
>          Key: FOR-796
>          URL: http://issues.apache.org/jira/browse/FOR-796
>      Project: Forrest
(Continue reading)


Gmane