Re: FOP Serializer configuration

[Joerg Heinicke]

Shortly after writing this, I had to realize that the servlet context can be 
jndi:/localhost/..., which is not what I want and that has changed between 
Tomcat 4.0 and 4.1 (both in combination with JBoss 3.x).

Changing the <user-config> to cocoon:/ protocol does not work as you already 
have experienced. This I didn't expect, because why should context:// work 
and cocoon:// not. Can you file a bug in bugzilla?

For me simply using a relative path works now, but this won't help you as 
you seem to create the fop-config dynamically. May I ask for the use case?

Joerg

Joerg Heinicke wrote:
What Cocoon version do you use?

I have 2.0.4 and use 
<user-config>context://doc/fop/config.xml</user-config> without any 
problems.

Joerg

Carmona Perez, David wrote:

Hi all,

Alter reading this page:

http://cocoon.apache.org/2.0/userdocs/serializers/pdf-serializer.html

I've tried to configure the FOPSerializer with a file generated 
through a Cocoon pipeline in this way:

            <map:serializer logger="sitemap.serializer.fo2pdf" 
mime-type="application/pdf" name="pdf"
                src="org.apache.cocoon.serialization.FOPSerializer">
                <user-config>cocoon:/config-fop.xsp</user-config>
            </map:serializer>

I can access cocoon:/config-fop.xsp well, but the FOPSerializer class 
tries to open:

file://myContextPath/cocoon:/config-fop.xsp

Does anyone know the cause?

--------
David
--

System Development
VIRBUS AG
Fon  +49(0)341-979-7419
Fax  +49(0)341-979-7409
[EMAIL PROTECTED]
www.virbus.de
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]