difference between @value and @ref on xforms:output

<p>&lt;b&gt;Alaska&lt;/b&gt; Deals<br>Find &lt;b&gt;Alaska&lt;/b&gt; Deals information on AlaskaCruises.com.<br><b><a href="http://www.alaskacruises.com/alaska_deals.asp">http://www.alaskacruises.com/alaska_deals.asp</a></b><br></p>

here is the relevant portion from the view:

Hi Richard

I'm not sure exactly what you're trying to achieve here -- from the
email thread so far I'm assuming that you've been able to view the raw
SOAP response, and have successfully managed to figure out the XPATH for
the elements you wish to display (in a formatted page)?

If this is correct then from your XSL, I gather that the problem is that
you are getting tags (element names) from the SOAP message in the data,
rather than just showing the contents of the elements?

Your XSL reads:
<xsl:for-each select="/return/resultElements/item">
   <p>
      <xsl:copy-of select="title"/>
      <br/>
      <xsl:copy-of select="snippet"/>
      <br/>
      <xsl:variable name="URL" select="URL"></xsl:variable>
      <b>
         <a href="{$URL}"><xsl:copy-of select="URL"></xsl:copy-of></a>
      </b>
      <br/>                       
   </p>
</xsl:for-each>

If it's simply a case of placing the text of the element (using xpath
notation) /return/ResultElement/item/title within some html <p></p>
tags, then the solution is simple:

Use <xsl:value-of select="title"> instead of xsl:copy-of.

xsl:copy of will take a copy of the whole element, ie the xml tag and
any text contents will be output.  xsl:value-of will take the text
contents of the element.

Or maybe I'm missing something in what you're trying to achieve?

I see you also said that the google results encode some bold and break
tags that are not being rendered correctly -- maybe you could post an
example message that you're getting back, and we can come up with some
XSL to handle this?  (this may well involve using some kind of
escaping/serializing solution as per Henrik's suggestion).

Regards
Steve




-----Original Message-----
From: Richard Braman [[hidden email]] 
Sent: 05 September 2006 05:56
To: [hidden email]
Subject: Re: [ops-users] OPS SOAP RETURN VALUES

Hi Henrick,
I am not sure how the escare-uri would help, these are html encodings. 
I looked at
saxon:serialize, but I am not sure what to put in the parameters.  I
tried

<xsl:copy-of select="saxon:serialize(snippet,'')"/>

but that printed out all sorts of additional xml. like this:

<?xml version="1.0" encoding="UTF-8"?><snippet
xmlns:ns3="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:f="http://orbeon.org/oxf/xml/formatting"
xmlns:xhtml="http://www.w3.org/1999/xhtml"
xmlns:oxf="http://www.orbeon.com/oxf/processors"
xmlns:delegation="http://orbeon.org/oxf/xml/delegation"
xmlns:p="http://www.orbeon.com/oxf/pipeline"
xmlns:v="http://orbeon.org/oxf/xml/validation"
xmlns:xsi_1="http://www.w3.org/1999/XMLSchema-instance"
xsi_1:type="xsd:string">There are six types of &lt;b&gt;Alaska&lt;/b&gt;
Cruise Vacations. Learn which &lt;b&gt;Alaska&lt;/b&gt; Cruise
Vacation&lt;br&gt; is best for you on AlaskaCruises.com.</snippet>

the docs on saxon:serialize didn;t manifest the answer, i saw a
reference to 'xml' on the second parameter from Micheal Kay, but no
details.

Richard

Henrik Pettersen wrote:
  

Richard,

have a look at these:

fn:escape-uri(stringURI,esc-res):
http://www.w3schools.com/xpath/xpath_functions.asp

http://mail-archive.objectweb.org/ops-users/2006-08/msg00629.html

Hope that helps.

Henrik

On 9/4/06, Richard Braman [hidden email] wrote:
    

Henrik , Stephen
Thanks for the input.
here is the code in view.xsl to print the results in google like
      

format,
  

but there are a couple of problems I am not sure how to handle in
      

xslt.
  

First the <title>, <snippet> , and <URL> xml elements complete with
      

type
  

information are actually printing out in the html instead of being
filtered out.  this is causing the problem of the title not being
displayed as title is a html tag. Secondly, the google results have
      

some
  

bold and break tags that are being encoded incorrectly and not
      

rendering
  

right.

<xsl:for-each select="/return/resultElements/item">
                    <p>
                        <xsl:copy-of select="title"/>
                        <br/>
                        <xsl:copy-of select="snippet"/>
                        <br/>
                        <xsl:variable name="URL"
select="URL"></xsl:variable>
                            <b>
                                <a href="{$URL}"><xsl:copy-of
select="URL"></xsl:copy-of></a>
                            </b>
                            <br/>
                    </p>
                </xsl:for-each>

here is html this returns:
  <p>
   <title xsi_1:type="xsd:string">&lt;b&gt;SEO&lt;/b&gt;
Home</title><br><snippet xsi_1:type="xsd:string">Mentor an
&lt;b&gt;SEO&lt;/b&gt; Scholar! 07 Aug 06. Click here to learn more.
&lt;b&gt;...&lt;/b&gt; 55 Exchange Place&lt;br&gt;  New York, NY
10005 (212)
    979-2040 [hidden email]
      

<b>...</b>
  

   </snippet><br><b><a href="http://www.seo-ny.org/">
     <URL
xsi_1:type="xsd:string">http://www.seo-ny.org/</URL></a></b><br></p>
  <p>


      

Richard,

if you output your data in your xpl as instance data:
   <p:param name="instance" type="output" />

you need to reference this data in the view like this:
   <xforms:instance id="user-instance">
       <xsl:copy-of select="document('input:instance')"/>
   </xforms:instance>

if you output your data in your xpl as data:
   <p:param name="data" type="output" />

you need to reference this data in the view like this:
   <xforms:instance id="user-instance">
       <xsl:copy-of select="/"/>
   </xforms:instance>

Also, you can add the attribute 'debug="somename"' to any pipeline
component's <input> or <output> elements to print the content to
        

the
  

log.

Hope that helps.

Henrik

On 9/2/06, Richard Braman [hidden email] wrote:
        

I am a little confused about the return values from the model.xpl
          

in the
      

Google SOAP sample I posted.

In the view.xsl, there is a stmt that prints out the response from
          

the
      

SOAP call like this:

<xsl:if test="doc('input:instance')/query != ''">

<pre><xsl:value-of select="/return"/></pre>

</xsl:if>


Without being able to see I return, i cant figure out the XPath
          

needed
      

to get to the elements of the response that I am interestd in for
formatting, namely
the snippet, URL, etc from the google response.

What would you use as an XPath?

Also does anyone think a WSDL to XPL generator would be a good
          

idea
  

for OPS?

Rich






--
You receive this message as a subscriber of the
[hidden email] mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page:
          

http://www.objectweb.org/wws
      

------------------------------------------------------------------------
  

--
You receive this message as a subscriber of the
        

[hidden email] mailing list.
      

To unsubscribe: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page:
        

http://www.objectweb.org/wws
      

-- 
You receive this message as a subscriber of the
[hidden email] mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page:
      

http://www.objectweb.org/wws
  

------------------------------------------------------------------------
  

--
You receive this message as a subscriber of the
    

[hidden email] mailing list.
  

To unsubscribe: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page:
    

http://www.objectweb.org/wws
  

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws