Erik,
You rock!!! I never would have figured I needed to include the
attachment in both processors. That was it. I figured out what I was
doing wrong on the Web service thing too (it was the schema target
namespace in the .NET webservice [document] and the soap body namespace in
the java service [rpc]). I really appreciate all your guidance on this.
My thanks to Alex as well.
Greg
Date: Tue, 16 Nov 2004 21:39:37 +0100
From: Erik Bruchez <[EMAIL PROTECTED]>
Organization: Orbeon, Inc.
To: [EMAIL PROTECTED]
Subject: Re: [orbeon-user] Re: Re: Re: Re: email processor
Reply-To: [EMAIL PROTECTED]
> <p:processor name="oxf:xslt">
> <p:input name="data" href="#instance"/>
> <p:input name="config">
> <html xmlns="http://www.w3.org/1999/xhtml";
> xsl:version="2.0">
> No html tags at all when I do a view source.
You are using the XHTML namespace. This is nice if you are actually
outputting XHTML, but for the conversion to "textual HTML" that the Email
processor does, you must be in no namespace. This is the way the HTML
converter works as well.
> Additionally, I can't see how to use the XSLT to generate the <to>
> fields of the e-mail. Any suggestions? I tried generating the entire
> message in XSLT, as I originally had it, but the XSLT processor
> complained that it could not find the xforms-instance. Looking at the
> documentation I just figured it was because the XSL processor only
> understands input by the name data or config. Am I wrong about this?
The XSLT processor actually understands optional inputs as well. If your
XSLT references doc('oxf:xforms-instance'), then you need to connect
something to the xforms-instance input of the XSLT processor. Now if you
are generating a message for the Email processor with an
src="oxf:xforms-instance", you must connect something to that input of the
Email processor. In some cases, you may have to connect your instance to
both the XSLT processor, and the Email processor. Aren't you missing one?
> The original message had no issues at all with the html but as I said
> it simply would not recognize the xml attachment part. This is what I
> had
> originally:
Until recently, text/xml was as attachment wouldn't work and simply be
considered as text. It should be fixed now but you have to use a recent
build. You also have to convert the XML to text as I showed in a different
email, and as the Email example now shows as well.
O hope things are clearer now!
> On a separate issue, I am trying to consume a MS NET webservice at
> http://services.xmethods.net that has no namespace defined for the
> input SOAP body (your example uses an Apache SOAP format on the same
site).
> When I attempt to use it without a nsuri I get
>
> Fatal Error: URI=null Line=3: The value of the attribute
> "prefix="xmlns",localpart="m",rawname="xmlns:m"" is invalid. Prefixed
> namespace bindings may not be empty.
>
> I am sure this is just due to my lack of experience with webservices
> but if you could offer a pointer or two on this I would appreciate it.
One for Alex ;-)
-Erik
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
orbeon-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/orbeon-user
