Webservices example not working

NOTICE

The information contained in this email is confidential. If you are not the intended recipient, you must not disclose or use the information in this email in any way. If you received it in error, please tell us immediately by return email and delete the document. We do not guarantee the integrity of any e-mails or attached files and are not responsible for any changes made to them by any other person.

--
You receive this message as a subscriber of the ops-users@... mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Naman,

On Tue, Jul 15, 2008 at 1:35 AM, Naman Joshi <Naman.Joshi@...> wrote:
> I am trying to run the webservice example on the orbeon site:
> [...]

What example were you referring to? You might want to try the
"weather" web service example in the Sandbox, which calls a web
service directly with an XForms submission, which is what we now
recommend. See:

http://www.orbeon.com/ops/xforms-sandbox/sample/web-service-weather

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.com/
Twitter - http://twitter.com/avernet


--
You receive this message as a subscriber of the ops-users@... mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Alex,

The examples on this site:
http://www.orbeon.com/ops/doc/integration-webservices
And also:
http://www.orbeon.com/ops/doc/processors-delegation#web-service

I tried it via the xforms submission method but I think I maybe be
having problems with Orbeon trusting the certificate that the webservice
serves. I use
https://admin:xxxx@.../iControl/iControlPortal.cgi as the
URL. The log file shows:

2008-07-16 08:04:09,060 http-8080-Processor19 ERROR
processor.XFormsServer null - XForms - submission - xforms-submit-error
throwable: sun.security.provider.certpath.SunCertPathBuilderException:
unable to find valid certification path to requested target
        at
sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPat
hBuilder.java:174)
        at
java.security.cert.CertPathBuilder.build(CertPathBuilder.java:238)
.
.

Is there a truststore that orbeon can use?

NJ

-----Original Message-----
From: avernet@... [mailto:avernet@...] On Behalf Of
Alessandro Vernet
Sent: Wednesday, 16 July 2008 10:07 AM
To: ops-users@...
Subject: [ops-users] Re: Webservices example not working

Naman,

On Tue, Jul 15, 2008 at 1:35 AM, Naman Joshi <Naman.Joshi@...>
wrote:
> I am trying to run the webservice example on the orbeon site:
> [...]

What example were you referring to? You might want to try the "weather"
web service example in the Sandbox, which calls a web service directly
with an XForms submission, which is what we now recommend. See:

http://www.orbeon.com/ops/xforms-sandbox/sample/web-service-weather

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise Orbeon's
Blog: http://www.orbeon.com/blog/ Personal Blog:
http://avernet.blogspot.com/ Twitter - http://twitter.com/avernet

NOTICE
The information contained in this email is confidential. If you are not the intended recipient, you must not disclose or use the information in this email in any way. If you received it in error, please tell us immediately by return email and delete the document.  We do not guarantee the integrity of any e-mails or attached files and are not responsible for any changes made to them by any other person.


--
You receive this message as a subscriber of the ops-users@... mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Naman,

On Wed, Jul 16, 2008 at 1:27 AM, Naman Joshi <Naman.Joshi@...> wrote: Like you said, most likely you are getting this because the server
certificate can't be verified. Adding it to the truststore should
solve the issue. XForms submissions use the "standard" truststore,
which you can specify when you start your application server (e.g.
Tomcat) with -Djavax.net.ssl.trustStore=/path/to/truststore
-Djavax.net.ssl.trustStorePassword=your-password.

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.com/
Twitter - http://twitter.com/avernet


--
You receive this message as a subscriber of the ops-users@... mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Naman,

On Wed, Jul 16, 2008 at 1:27 AM, Naman Joshi <Naman.Joshi@...> wrote:
> The examples on this site:
> http://www.orbeon.com/ops/doc/integration-webservices

And regarding the issue with the delegation processor, this looks like
an integration issue with Liferay. I am not sure why the Liferay class
com.liferay.util.axis.SimpleHTTPSender can't be initialized in this
case. Hopefully you'll get around this by using an xforms:submission,
which we would recommend anyway independently of this issue with
Liferay.

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.com/
Twitter - http://twitter.com/avernet


--
You receive this message as a subscriber of the ops-users@... mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Hello all,

I know there is a pdf template processor but I was keen to investigate
this path to create a pdf, so I tried a submission which would run the
xpl:

        <p:processor name="oxf:xslfo-converter">
                <p:input name="config">
                        <config/>
                </p:input>
                <p:input name="data">
                        <fo:root>
                                <fo:layout-master-set>
                                        <fo:simple-page-master
master-name="A4-portrait" page-height="29.7cm" page-width="21.0cm"
margin="2cm">
                                                <fo:region-body/>
                                        </fo:simple-page-master>
                                </fo:layout-master-set>
                                <fo:page-sequence
master-reference="A4-portrait">
                                        <fo:flow
flow-name="xsl-region-body">
                                                <fo:block>Hello,
Bob!</fo:block>
                                        </fo:flow>
                                </fo:page-sequence>
                        </fo:root>
                </p:input>
                <p:output name="data" ref="data"/>
        </p:processor>

In the page flow:

<page path-info="/demo/pdf" view="print-pdf.xpl"/>


I wasn't sure what to put for the view or model so I just added this and
I get a page with what seems to me is the binary representation. I am
not sure how to serve this back to the client though as a pdf.

Does anyone have an idea?

Thanks,
Naman

NOTICE
The information contained in this email is confidential. If you are not the intended recipient, you must not disclose or use the information in this email in any way. If you received it in error, please tell us immediately by return email and delete the document.  We do not guarantee the integrity of any e-mails or attached files and are not responsible for any changes made to them by any other person.


--
You receive this message as a subscriber of the ops-users@... mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

It's probably the mime-type - not sure, but maybe outputting via a page-flow
view is upsetting the mime-type somehow.

You could instead have your print-pdf.xpl as a model in the page flow.

Then pipe the output through a oxf:http-serializer - in the config input of
that processor you can specify the mime-type for a pdf as application/pdf.

-----Original Message-----
From: Naman Joshi [mailto:Naman.Joshi@...]
Sent: 25 July 2008 05:10
To: ops-users@...
Subject: [ops-users] XSL_FO Convertor Processor (Hello World)


Hello all,

I know there is a pdf template processor but I was keen to investigate this
path to create a pdf, so I tried a submission which would run the
xpl:

        <p:processor name="oxf:xslfo-converter">
                <p:input name="config">
                        <config/>
                </p:input>
                <p:input name="data">
                        <fo:root>
                                <fo:layout-master-set>
                                        <fo:simple-page-master
master-name="A4-portrait" page-height="29.7cm" page-width="21.0cm"
margin="2cm">
                                                <fo:region-body/>
                                        </fo:simple-page-master>
                                </fo:layout-master-set>
                                <fo:page-sequence
master-reference="A4-portrait">
                                        <fo:flow
flow-name="xsl-region-body">
                                                <fo:block>Hello,
Bob!</fo:block>
                                        </fo:flow>
                                </fo:page-sequence>
                        </fo:root>
                </p:input>
                <p:output name="data" ref="data"/>
        </p:processor>

In the page flow:

<page path-info="/demo/pdf" view="print-pdf.xpl"/>


I wasn't sure what to put for the view or model so I just added this and I
get a page with what seems to me is the binary representation. I am not sure
how to serve this back to the client though as a pdf.

Does anyone have an idea?

Thanks,
Naman

NOTICE
The information contained in this email is confidential. If you are not the
intended recipient, you must not disclose or use the information in this
email in any way. If you received it in error, please tell us immediately by
return email and delete the document.  We do not guarantee the integrity of
any e-mails or attached files and are not responsible for any changes made
to them by any other person.



--
You receive this message as a subscriber of the ops-users@... mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Naman,

On Thu, Jul 24, 2008 at 9:10 PM, Naman Joshi <Naman.Joshi@...> wrote:
> I know there is a pdf template processor but I was keen to investigate
> this path to create a pdf, so I tried a submission which would run the
> xpl: [...]

You don't need to run the xslfo-converter yourself (and if you do, you
should do it in a model which takes care of the HTTP serialization,
not in the view). Instead, just let your view produce XSL-FO. The
epilogue will detect that, run the xslfo-converter and serialize the
output as appropriate.

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.com/
Twitter - http://twitter.com/avernet


--
You receive this message as a subscriber of the ops-users@... mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Alex,

Sorry to be a pain, but I am a little confused when you say "let your
view produce xsl-fo". What I wanted to do was:
        1. Press a button 'mViewHome.xhtml' which would convert the xml
in that instance into pdf
        2. 'print-pdf.xpl' would use XSLT to produce XSL-FO code which
would create a PDF which would be served back to the client.

I have attached my understanding of the implementation. I also tried
using xsl-fo serialization but wasn't sure how to use it.

Naman

-----Original Message-----
From: avernet@... [mailto:avernet@...] On Behalf Of
Alessandro Vernet
Sent: Monday, 28 July 2008 7:50 AM
To: ops-users@...
Subject: [ops-users] Re: XSL_FO Convertor Processor (Hello World)

Naman,

On Thu, Jul 24, 2008 at 9:10 PM, Naman Joshi <Naman.Joshi@...>
wrote:
> I know there is a pdf template processor but I was keen to investigate

> this path to create a pdf, so I tried a submission which would run the
> xpl: [...]

You don't need to run the xslfo-converter yourself (and if you do, you
should do it in a model which takes care of the HTTP serialization, not
in the view). Instead, just let your view produce XSL-FO. The epilogue
will detect that, run the xslfo-converter and serialize the output as
appropriate.

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise Orbeon's
Blog: http://www.orbeon.com/blog/ Personal Blog:
http://avernet.blogspot.com/ Twitter - http://twitter.com/avernet

NOTICE
The information contained in this email is confidential. If you are not the intended recipient, you must not disclose or use the information in this email in any way. If you received it in error, please tell us immediately by return email and delete the document.  We do not guarantee the integrity of any e-mails or attached files and are not responsible for any changes made to them by any other person.

<config xmlns="http://www.orbeon.com/oxf/controller"
        xmlns:xu="http://www.xmldb.org/xupdate"
        xmlns:oxf="http://www.orbeon.com/oxf/processors">

    <!-- Home redirects to Welcome application -->
   
      <page path-info="/mView/" view="mViewHome.xhtml" />
         
        <page path-info="/mView/pdf" model="print-pdf.xpl"/>

    <epilogue url="/config/epilogue.xpl"/>

   
</config>




--
You receive this message as a subscriber of the ops-users@... mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Naman,

On Sun, Jul 27, 2008 at 8:17 PM, Naman Joshi <Naman.Joshi@...> wrote:
> Sorry to be a pain, but I am a little confused when you say "let your
> view produce xsl-fo". What I wanted to do was:
>        1. Press a button 'mViewHome.xhtml' which would convert the xml
> in that instance into pdf
>        2. 'print-pdf.xpl' would use XSLT to produce XSL-FO code which
> would create a PDF which would be served back to the client.
>
> I have attached my understanding of the implementation. I also tried
> using xsl-fo serialization but wasn't sure how to use it.

You might want to give a try to what follows:

1. Change your page-flow.xml to use view="print-pdf.xpl" instead of
model="print-pdf.xpl".
2. Change print-pdf.xpl to remove the oxf:xslfo-serializer and connect
the output of the stylesheet directly to the "data" output of the
pipeline.

The epilogue will be looking at what your view generate: if it
generates XHTML with XForms, it will do its XForms processing, but if
it generates XSL-FO, then it uses oxf:xslfo-serializer to generate a
PDF and sends that back to the browser with the HTTP serializer.

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.com/
Twitter - http://twitter.com/avernet


--
You receive this message as a subscriber of the ops-users@... mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Makes sense.

I changed the page-flow to make it a view.

I changed the view to:

        <p:processor name="oxf:xslt">
                <p:input name="data" href="#instance"/>
                <p:input name="config">
                        <xsl:stylesheet version="2.0">
                                <xsl:template match="/">
                                        <fo:root>
                                                <fo:layout-master-set>
       
<fo:simple-page-master master-name="A4-portrait" page-height="29.7cm"
page-width="21.0cm" margin="2cm">
       
<fo:region-body/>
       
</fo:simple-page-master>
                                                </fo:layout-master-set>
                                                <fo:page-sequence
master-reference="A4-portrait">
                                                        <fo:flow
flow-name="xsl-region-body">
       
<fo:block>Hello, Bob!</fo:block>
                                                        </fo:flow>
                                                </fo:page-sequence>
                                        </fo:root>
                                </xsl:template>
                        </xsl:stylesheet>
                </p:input>
                <p:output name="data" ref="data"/>
        </p:processor>

And it just returned "Hello, Bob" on a simple XHTML page with page title
"XML Document".....??

-----Original Message-----
From: avernet@... [mailto:avernet@...] On Behalf Of
Alessandro Vernet
Sent: Monday, 28 July 2008 1:27 PM
To: ops-users@...
Subject: [ops-users] Re: RE: Re: XSL_FO Convertor Processor (Hello
World)

Naman,

On Sun, Jul 27, 2008 at 8:17 PM, Naman Joshi <Naman.Joshi@...>
wrote:
> Sorry to be a pain, but I am a little confused when you say "let your
> view produce xsl-fo". What I wanted to do was:
>        1. Press a button 'mViewHome.xhtml' which would convert the xml

> in that instance into pdf
>        2. 'print-pdf.xpl' would use XSLT to produce XSL-FO code which
> would create a PDF which would be served back to the client.
>
> I have attached my understanding of the implementation. I also tried
> using xsl-fo serialization but wasn't sure how to use it.

You might want to give a try to what follows:

1. Change your page-flow.xml to use view="print-pdf.xpl" instead of
model="print-pdf.xpl".
2. Change print-pdf.xpl to remove the oxf:xslfo-serializer and connect
the output of the stylesheet directly to the "data" output of the
pipeline.

The epilogue will be looking at what your view generate: if it generates
XHTML with XForms, it will do its XForms processing, but if it generates
XSL-FO, then it uses oxf:xslfo-serializer to generate a PDF and sends
that back to the browser with the HTTP serializer.

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise Orbeon's
Blog: http://www.orbeon.com/blog/ Personal Blog:
http://avernet.blogspot.com/ Twitter - http://twitter.com/avernet

NOTICE
The information contained in this email is confidential. If you are not the intended recipient, you must not disclose or use the information in this email in any way. If you received it in error, please tell us immediately by return email and delete the document.  We do not guarantee the integrity of any e-mails or attached files and are not responsible for any changes made to them by any other person.


--
You receive this message as a subscriber of the ops-users@... mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Alessandro Vernet wrote:

  Hi

> The epilogue will be looking at what your view generate: if it
> generates XHTML with XForms, it will do its XForms processing,
> but if it generates XSL-FO, then it uses oxf:xslfo-serializer
> to generate a PDF and sends that back to the browser with the
> HTTP serializer.

  The drawback is that you are then stuck to oxf:xslfo-serializer
and you can not set any option of FOP.  If you want for example to
configure the fonts you want to use, you have to create your own
custom processor.

  Regards,

--drkm



















      _____________________________________________________________________________
Envoyez avec Yahoo! Mail. Une boite mail plus intelligente http://mail.yahoo.fr


--
You receive this message as a subscriber of the ops-users@... mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

On Mon, Jul 28, 2008 at 1:23 AM, Florent Georges <lists@...> wrote:
>  The drawback is that you are then stuck to oxf:xslfo-serializer
> and you can not set any option of FOP.  If you want for example to
> configure the fonts you want to use, you have to create your own
> custom processor.

That's right. If the default settings don't work for you, then you can
in an XPL referenced from the page flow model="..." do the XSL
transformation generating XSL-FO, run the oxf:xslfo-converter and the
oxf:http-serializer. But in this case again, the XPL needs to be
referenced from the model, not the view.

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.com/
Twitter - http://twitter.com/avernet


--
You receive this message as a subscriber of the