Re: XMP - iText - Watermark Problem

2008-10-29 Thread Jeremias Maerki
Looks like a bug in the JAXP/XSLT (javax.xml.transform) implementation
you're using. The namespace declarations are not properly generated.
Please use a recent Xalan-J or SAXON. See here for instructions:
http://xml.apache.org/xalan-j/faq.html#faq-N100EF

On 29.10.2008 13:26:22 Tobias van Treeck wrote:
 Hi,
 
 i generate a pdf with fop and afterwards i add a watermark. Until i
 didn't set the following meta data
 
 this.foUserAgent.setCreator(Creator);
 this.foUserAgent.setAuthor(Author);
 this.foUserAgent.setTitle(Title);
 
  it worked but now i get the following message:
 
 The prefix x for element x:xmpmeta is not bound.
 After looking into the PDF i realized that the namespace is not set and
 that's why iText runs into problems:
 
 x:xmpmeta
 rdf:RDF
 rdf:Description rdf:about=
 pdf:PDFVersion1.4/pdf:PDFVersion
 pdf:ProducerApache FOP Version 0.95/pdf:Producer
 /rdf:Description
 rdf:Description rdf:about=
 xmp:CreatorToolCreator/xmp:CreatorTool
 xmp:CreateDate2008-10-29T10:38:07+01:00/xmp:CreateDate
 /rdf:Description
 rdf:Description rdf:about=
 dc:date
 rdf:Seq
 rdf:li2008-10-29T10:38:07+01:00/rdf:li
 /rdf:Seq
 /dc:date
 dc:creator
 rdf:Seq
 rdf:liAuthor/rdf:li
 /rdf:Seq
 /dc:creator
 dc:title
 rdf:Alt
 rdf:li xml:lang=x-defaultTitle/rdf:li
 /rdf:Alt
 /dc:title
 /rdf:Description
 /rdf:RDF
 /x:xmpmeta
 ?xpacket end=r?
 
 So can i add the namespace manually or is that just a bug of FOP?
 I know that i can set the xmp part manually with fo:declarations but i
 don't want to do that...
 
 Regards,
 ToM
 
 




Jeremias Maerki


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



XMP - iText - Watermark Problem

2008-10-29 Thread Tobias van Treeck
Hi,

i generate a pdf with fop and afterwards i add a watermark. Until i
didn't set the following meta data

this.foUserAgent.setCreator(Creator);
this.foUserAgent.setAuthor(Author);
this.foUserAgent.setTitle(Title);

 it worked but now i get the following message:

The prefix x for element x:xmpmeta is not bound.
After looking into the PDF i realized that the namespace is not set and
that's why iText runs into problems:

x:xmpmeta
rdf:RDF
rdf:Description rdf:about=
pdf:PDFVersion1.4/pdf:PDFVersion
pdf:ProducerApache FOP Version 0.95/pdf:Producer
/rdf:Description
rdf:Description rdf:about=
xmp:CreatorToolCreator/xmp:CreatorTool
xmp:CreateDate2008-10-29T10:38:07+01:00/xmp:CreateDate
/rdf:Description
rdf:Description rdf:about=
dc:date
rdf:Seq
rdf:li2008-10-29T10:38:07+01:00/rdf:li
/rdf:Seq
/dc:date
dc:creator
rdf:Seq
rdf:liAuthor/rdf:li
/rdf:Seq
/dc:creator
dc:title
rdf:Alt
rdf:li xml:lang=x-defaultTitle/rdf:li
/rdf:Alt
/dc:title
/rdf:Description
/rdf:RDF
/x:xmpmeta
?xpacket end=r?

So can i add the namespace manually or is that just a bug of FOP?
I know that i can set the xmp part manually with fo:declarations but i
don't want to do that...

Regards,
ToM


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: XMP - iText - Watermark Problem

2008-10-29 Thread Tobias van Treeck
Yeah you are right - we are using java 1.4 here and using the endorsed
mechanism it worked.
Unfortunatly in production i can't do that, so is there another way?
Can i set the processor directly in FOP?

...otherwise i gonna try fo:declarations

Thanks
ToM

 Looks like a bug in the JAXP/XSLT (javax.xml.transform) implementation
 you're using. The namespace declarations are not properly generated.
 Please use a recent Xalan-J or SAXON. See here for instructions:
 http://xml.apache.org/xalan-j/faq.html#faq-N100EF

 On 29.10.2008 13:26:22 Tobias van Treeck wrote:
  Hi,
 
  i generate a pdf with fop and afterwards i add a watermark. Until i
  didn't set the following meta data
 
  this.foUserAgent.setCreator(Creator);
  this.foUserAgent.setAuthor(Author);
  this.foUserAgent.setTitle(Title);
 
   it worked but now i get the following message:
 
  The prefix x for element x:xmpmeta is not bound.
  After looking into the PDF i realized that the namespace is not set
  and
  that's why iText runs into problems:
 
  x:xmpmeta
  rdf:RDF
  rdf:Description rdf:about=
  pdf:PDFVersion1.4/pdf:PDFVersion
  pdf:ProducerApache FOP Version 0.95/pdf:Producer
  /rdf:Description
  rdf:Description rdf:about=
  xmp:CreatorToolCreator/xmp:CreatorTool
  xmp:CreateDate2008-10-29T10:38:07+01:00/xmp:CreateDate
  /rdf:Description
  rdf:Description rdf:about=
  dc:date
  rdf:Seq
  rdf:li2008-10-29T10:38:07+01:00/rdf:li
  /rdf:Seq
  /dc:date
  dc:creator
  rdf:Seq
  rdf:liAuthor/rdf:li
  /rdf:Seq
  /dc:creator
  dc:title
  rdf:Alt
  rdf:li xml:lang=x-defaultTitle/rdf:li
  /rdf:Alt
  /dc:title
  /rdf:Description
  /rdf:RDF
  /x:xmpmeta
  ?xpacket end=r?
 
  So can i add the namespace manually or is that just a bug of FOP?
  I know that i can set the xmp part manually with fo:declarations
  but i
  don't want to do that...
 
  Regards,
  ToM
 
 




 Jeremias Maerki


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: XMP - iText - Watermark Problem

2008-10-29 Thread Jeremias Maerki
On 29.10.2008 14:59:43 Tobias van Treeck wrote:
 Yeah you are right - we are using java 1.4 here and using the endorsed
 mechanism it worked.
 Unfortunatly in production i can't do that, so is there another way?
 Can i set the processor directly in FOP?

It's not in FOP, it's in XML Graphics Commons, and no, you can't set
override the processor just for that component. The default
TransformerFactory is used. And if it's Xalan that is used by the
production JRE, putting another Xalan into the classpath won't help
since the one in the JRE takes precedence.

 ...otherwise i gonna try fo:declarations

Won't help you. The XMP in fo:declarations is parsed, optionally merged
with other information and then written out using a Transformer.

 Thanks
 ToM
 
  Looks like a bug in the JAXP/XSLT (javax.xml.transform) implementation
  you're using. The namespace declarations are not properly generated.
  Please use a recent Xalan-J or SAXON. See here for instructions:
  http://xml.apache.org/xalan-j/faq.html#faq-N100EF
 
  On 29.10.2008 13:26:22 Tobias van Treeck wrote:
   Hi,
  
   i generate a pdf with fop and afterwards i add a watermark. Until i
   didn't set the following meta data
  
   this.foUserAgent.setCreator(Creator);
   this.foUserAgent.setAuthor(Author);
   this.foUserAgent.setTitle(Title);
  
    it worked but now i get the following message:
  
   The prefix x for element x:xmpmeta is not bound.
   After looking into the PDF i realized that the namespace is not set
   and
   that's why iText runs into problems:
  
   x:xmpmeta
   rdf:RDF
   rdf:Description rdf:about=
   pdf:PDFVersion1.4/pdf:PDFVersion
   pdf:ProducerApache FOP Version 0.95/pdf:Producer
   /rdf:Description
   rdf:Description rdf:about=
   xmp:CreatorToolCreator/xmp:CreatorTool
   xmp:CreateDate2008-10-29T10:38:07+01:00/xmp:CreateDate
   /rdf:Description
   rdf:Description rdf:about=
   dc:date
   rdf:Seq
   rdf:li2008-10-29T10:38:07+01:00/rdf:li
   /rdf:Seq
   /dc:date
   dc:creator
   rdf:Seq
   rdf:liAuthor/rdf:li
   /rdf:Seq
   /dc:creator
   dc:title
   rdf:Alt
   rdf:li xml:lang=x-defaultTitle/rdf:li
   /rdf:Alt
   /dc:title
   /rdf:Description
   /rdf:RDF
   /x:xmpmeta
   ?xpacket end=r?
  
   So can i add the namespace manually or is that just a bug of FOP?
   I know that i can set the xmp part manually with fo:declarations
   but i
   don't want to do that...
  
   Regards,
   ToM
  
  
 
 
 
 
  Jeremias Maerki
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 




Jeremias Maerki


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: XMP - iText - Watermark Problem

2008-10-29 Thread Tobias van Treeck
Is there a way to disable xmp at all?
Setting the xmp metadata with fo:declarations didn't work - in the
final pdf the namespace is then missing again...

So now i am out of options...
ToM

 Unfortunatly in production i can't do that, so is there another way?
 Can i set the processor directly in FOP?

 ...otherwise i gonna try fo:declarations

 Thanks
 ToM

  Looks like a bug in the JAXP/XSLT (javax.xml.transform)
  implementation
  you're using. The namespace declarations are not properly generated.
  Please use a recent Xalan-J or SAXON. See here for instructions:
  http://xml.apache.org/xalan-j/faq.html#faq-N100EF
 
  On 29.10.2008 13:26:22 Tobias van Treeck wrote:
   Hi,
  
   i generate a pdf with fop and afterwards i add a watermark. Until
   i
   didn't set the following meta data
  
   this.foUserAgent.setCreator(Creator);
   this.foUserAgent.setAuthor(Author);
   this.foUserAgent.setTitle(Title);
  
    it worked but now i get the following message:
  
   The prefix x for element x:xmpmeta is not bound.
   After looking into the PDF i realized that the namespace is not
   set
   and
   that's why iText runs into problems:
  
   x:xmpmeta
   rdf:RDF
   rdf:Description rdf:about=
   pdf:PDFVersion1.4/pdf:PDFVersion
   pdf:ProducerApache FOP Version 0.95/pdf:Producer
   /rdf:Description
   rdf:Description rdf:about=
   xmp:CreatorToolCreator/xmp:CreatorTool
   xmp:CreateDate2008-10-29T10:38:07+01:00/xmp:CreateDate
   /rdf:Description
   rdf:Description rdf:about=
   dc:date
   rdf:Seq
   rdf:li2008-10-29T10:38:07+01:00/rdf:li
   /rdf:Seq
   /dc:date
   dc:creator
   rdf:Seq
   rdf:liAuthor/rdf:li
   /rdf:Seq
   /dc:creator
   dc:title
   rdf:Alt
   rdf:li xml:lang=x-defaultTitle/rdf:li
   /rdf:Alt
   /dc:title
   /rdf:Description
   /rdf:RDF
   /x:xmpmeta
   ?xpacket end=r?
  
   So can i add the namespace manually or is that just a bug of
   FOP?
   I know that i can set the xmp part manually with fo:declarations
   but i
   don't want to do that...
  
   Regards,
   ToM
  
  
 
 
 
 
  Jeremias Maerki
 
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail:
  [EMAIL PROTECTED]
 


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: XMP - iText - Watermark Problem

2008-10-29 Thread Jeremias Maerki
Not at the moment.

On 29.10.2008 16:16:51 Tobias van Treeck wrote:
 Is there a way to disable xmp at all?
 Setting the xmp metadata with fo:declarations didn't work - in the
 final pdf the namespace is then missing again...
 
 So now i am out of options...
 ToM
 
  Unfortunatly in production i can't do that, so is there another way?
  Can i set the processor directly in FOP?
 
  ...otherwise i gonna try fo:declarations
 
  Thanks
  ToM
 
   Looks like a bug in the JAXP/XSLT (javax.xml.transform)
   implementation
   you're using. The namespace declarations are not properly generated.
   Please use a recent Xalan-J or SAXON. See here for instructions:
   http://xml.apache.org/xalan-j/faq.html#faq-N100EF
  
   On 29.10.2008 13:26:22 Tobias van Treeck wrote:
Hi,
   
i generate a pdf with fop and afterwards i add a watermark. Until
i
didn't set the following meta data
   
this.foUserAgent.setCreator(Creator);
this.foUserAgent.setAuthor(Author);
this.foUserAgent.setTitle(Title);
   
 it worked but now i get the following message:
   
The prefix x for element x:xmpmeta is not bound.
After looking into the PDF i realized that the namespace is not
set
and
that's why iText runs into problems:
   
x:xmpmeta
rdf:RDF
rdf:Description rdf:about=
pdf:PDFVersion1.4/pdf:PDFVersion
pdf:ProducerApache FOP Version 0.95/pdf:Producer
/rdf:Description
rdf:Description rdf:about=
xmp:CreatorToolCreator/xmp:CreatorTool
xmp:CreateDate2008-10-29T10:38:07+01:00/xmp:CreateDate
/rdf:Description
rdf:Description rdf:about=
dc:date
rdf:Seq
rdf:li2008-10-29T10:38:07+01:00/rdf:li
/rdf:Seq
/dc:date
dc:creator
rdf:Seq
rdf:liAuthor/rdf:li
/rdf:Seq
/dc:creator
dc:title
rdf:Alt
rdf:li xml:lang=x-defaultTitle/rdf:li
/rdf:Alt
/dc:title
/rdf:Description
/rdf:RDF
/x:xmpmeta
?xpacket end=r?
   
So can i add the namespace manually or is that just a bug of
FOP?
I know that i can set the xmp part manually with fo:declarations
but i
don't want to do that...
   
Regards,
ToM
   
   
  
  
  
  
   Jeremias Maerki
  
  



Jeremias Maerki


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]