Such errors are logged by the xml parser.
Googling, it seems an encoding problem (as the error suggests)
and I guess it comes from files checked out by svn using a bad
encoding on Max OS X. Encoding is not set on most xml files
so I guess it defaults to the default system encoding.
Not sure how
Hi.
We have developed a new component for printing.
To be more specific there are 2 component:
the first uses jasperreports to take a template (from a config property) and
based on a hash map set in the config file it dynamically associate to
template tags either static values written in the confi
Guillaume Nodet wrote:
Such errors are logged by the xml parser.
Googling, it seems an encoding problem (as the error suggests)
and I guess it comes from files checked out by svn using a bad
encoding on Max OS X. Encoding is not set on most xml files
so I guess it defaults to the default system
On 6/6/06, gioppo <[EMAIL PROTECTED]> wrote:
Hi.
We have developed a new component for printing.
To be more specific there are 2 component:
the first uses jasperreports to take a template (from a config property) and
based on a hash map set in the config file it dynamically associate to
template
Since we did not alter any servicemix stuff, but created a new component and
a new example so we could send the tree for the
org/apache/servicemix/components/print and
/servicemix-assembly/src/main/release/examples/printer-binding
also we'll send the 1.2.3 of jasperreports to place in the /libs/op
Yes, you can use the ServiceMix BPEL example as a starting point.
Assuming you use a Spring context to initialize your webapp, it becomes
mostly a question of declaring the BPEL engine as a component in the
context and wiring components with it.And don't forget to add all
jar dependencies int
On 6/6/06, Alex Boisvert <[EMAIL PROTECTED]> wrote:
Bruce Snyder wrote:
> On 6/6/06, Alex Boisvert <[EMAIL PROTECTED]> wrote:
>>
>> Yes, you can use the ServiceMix BPEL example as a starting point.
>>
>> Assuming you use a Spring context to initialize your webapp, it becomes
>> mostly a question
