You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Luke Holden <al...@prodigy.net> on 2002/01/23 13:10:36 UTC
XSL and turbine
I am curious, is any body else using XML/XSLT in turbine?
If so, I would be interested in knowing how you went about using it.
I am currently using a slightly modifed VelocityXmlLayout (the original did
not work for some reason?) Instead of screens/navigations I am using xml
files full of data. The final xml output (layout, navigation and screen xml
output) is processed by a XSL transformation belonging to the layout.
(Strange, the original VelocityXmlLayouy could not find the xsl file... This
might be due to the fact I am not using a standard release ver of turbine...)
Anyways... If anyone else has gone about this in a different fassion, I would
love to know.
Also, has any one used intake in addition to the xslt service?
Luke
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Turbine and the Google Web Services API
Posted by Diederik de Groot <dd...@talon.nl>.
Hi there Bruce,
Congrats with getting it to work. I'm working on a new application skeleton
which is a bit more elaborate the newapp and i want to incorporate as many
little sample solutions to possible problems people might have, as possible.
I would like to set up a repository of good software and handy utils. It's
goiing to reside in /crontrib under the turbine repository. Would you
contribute you peace of solution ?
Thanks in advance,
Diederik de Groot [mailto:ddegroot@talon.nl]
> -----Original Message-----
> From: Bruce Altner [mailto:baltner@hq.nasa.gov]
> Sent: vrijdag 3 mei 2002 23:29
> To: Turbine Users List
> Subject: Re: Turbine and the Google Web Services API
>
>
> For future reference for those who try to do Web service apps within
> Turbine, I finally got it to work, after much thrashing, by
> replacing the
> version of xerces parser that shipped with tdk2.1 (1.3.0) with the most
> current version (1.4.4).
>
> Bruce
>
> At 05:31 AM 4/30/2002 -0400, you wrote:
> >Greetings:
> >
> >I'm trying to use the Google Web Services API
> >(http://www.google.com/apis/index.html) from within Turbine for a
> >demonstration of web services. Outside of Turbine, i.e., on the command
> >line, it works great, but I'm getting the following error upon doing a
> >search within a Turbine action class:
> >
> >java.lang.reflect.InvocationTargetException:
> >com.google.soap.search.GoogleSearchFault: [SOAPException:
> > faultCode=SOAP-ENV:Client; msg=Unable to resolve namespace URI
> for 'ns1'.;
> > targetException=java.lang.IllegalArgumentException: Unable to resolve
> > namespace URI for 'ns1'.] at
> > com.google.soap.search.GoogleSearch.doSearch(GoogleSearch.java:164) at
> > gov.nasa.hq.apps.actions.google.Searcher.doSearch(Searcher.java:35) at
> > java.lang.reflect.Method.invoke(Native
> > Method) at
> >
> org.apache.turbine.util.velocity.VelocityActionEvent.executeEvents
> (VelocityActionEvent.java:166)
> > at
> >
> >org.apache.turbine.util.velocity.VelocityActionEvent.perform(Velo
> cityActionEvent.java:114)
> >at...etc.
> >
> >Since I'm connecting fine from command line it is not a proxy
> problem, but
> >I suspect that maybe Turbine is mangling something in the SOAP call. Has
> >anyone else tried this API withing Turbine yet?
> >
> >Thanks,
> >Bruce
> >
> >
> >--
> >To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> >For additional commands, e-mail:
> <ma...@jakarta.apache.org>
> >
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Turbine and the Google Web Services API
Posted by Bruce Altner <ba...@hq.nasa.gov>.
For future reference for those who try to do Web service apps within
Turbine, I finally got it to work, after much thrashing, by replacing the
version of xerces parser that shipped with tdk2.1 (1.3.0) with the most
current version (1.4.4).
Bruce
At 05:31 AM 4/30/2002 -0400, you wrote:
>Greetings:
>
>I'm trying to use the Google Web Services API
>(http://www.google.com/apis/index.html) from within Turbine for a
>demonstration of web services. Outside of Turbine, i.e., on the command
>line, it works great, but I'm getting the following error upon doing a
>search within a Turbine action class:
>
>java.lang.reflect.InvocationTargetException:
>com.google.soap.search.GoogleSearchFault: [SOAPException:
> faultCode=SOAP-ENV:Client; msg=Unable to resolve namespace URI for 'ns1'.;
> targetException=java.lang.IllegalArgumentException: Unable to resolve
> namespace URI for 'ns1'.] at
> com.google.soap.search.GoogleSearch.doSearch(GoogleSearch.java:164) at
> gov.nasa.hq.apps.actions.google.Searcher.doSearch(Searcher.java:35) at
> java.lang.reflect.Method.invoke(Native
> Method) at
> org.apache.turbine.util.velocity.VelocityActionEvent.executeEvents(VelocityActionEvent.java:166)
> at
>
>org.apache.turbine.util.velocity.VelocityActionEvent.perform(VelocityActionEvent.java:114)
>at...etc.
>
>Since I'm connecting fine from command line it is not a proxy problem, but
>I suspect that maybe Turbine is mangling something in the SOAP call. Has
>anyone else tried this API withing Turbine yet?
>
>Thanks,
>Bruce
>
>
>--
>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Turbine and the Google Web Services API
Posted by Bruce Altner <ba...@hq.nasa.gov>.
Greetings:
I'm trying to use the Google Web Services API
(http://www.google.com/apis/index.html) from within Turbine for a
demonstration of web services. Outside of Turbine, i.e., on the command
line, it works great, but I'm getting the following error upon doing a
search within a Turbine action class:
java.lang.reflect.InvocationTargetException:
com.google.soap.search.GoogleSearchFault: [SOAPException:
faultCode=SOAP-ENV:Client; msg=Unable to resolve namespace URI for 'ns1'.;
targetException=java.lang.IllegalArgumentException: Unable to resolve
namespace URI for 'ns1'.] at
com.google.soap.search.GoogleSearch.doSearch(GoogleSearch.java:164) at
gov.nasa.hq.apps.actions.google.Searcher.doSearch(Searcher.java:35) at
java.lang.reflect.Method.invoke(Native
Method) at
org.apache.turbine.util.velocity.VelocityActionEvent.executeEvents(VelocityActionEvent.java:166)
at
org.apache.turbine.util.velocity.VelocityActionEvent.perform(VelocityActionEvent.java:114)
at...etc.
Since I'm connecting fine from command line it is not a proxy problem, but
I suspect that maybe Turbine is mangling something in the SOAP call. Has
anyone else tried this API withing Turbine yet?
Thanks,
Bruce
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: XSL and turbine
Posted by Luke Holden <al...@prodigy.net>.
> I have been playing around with XML/DVSL :-) I will probably add a view
> system that uses DVSL instead of XSL. You can find information on DVSL
> here:
Ohh interesting. I have not really descovered DVSL until now. I am really not
sure if that is a direction I want to go in however. The thing I like about
using XML and XSL is the further seperation between logic and layout. Even
with pure Velocity/html files you end up with some non display logic sitting
in your templates... (I am using pull model by the way). The thing I like
about using XML and XSL is that you end up with xml describing the
content. Then the XSL file is used for JUST layout of the content.
The advantage I in this is that I can modify the back end however I want. My
customer can modify the front end how ever he wants. As long as the xml
remains consistant neither of us has to worry much about what the other does.
My logic in this might be flawed so please feel free to tell me wrong :)
> This is all in Turbine 3. I will attempt to make Velocity, JSP and DVSL all
> work with the classic model in t3: layouts, navigations and screens.
However, xsl is a bit limiting. (and rather verbose.) I would be interested
in learning more about DVSL. I would actually rather like to play with t3
some... However, it seems that right now, the torque stuff is commented out
of the build.xml file in the TDK for t3. (and some parts seem to be missing,
like the taskdef's.) So I could build an app, and if I wanted to, I could
manually get the DB stuff working............... I guess I will check out the
tdk in a few days and see if the torque stuff is working again :)
Thanks for the reply :)
Luke
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: XSL and turbine
Posted by Jason van Zyl <jv...@zenplex.com>.
On 1/23/02 7:10 AM, "Luke Holden" <al...@prodigy.net> wrote:
> I am curious, is any body else using XML/XSLT in turbine?
I have been playing around with XML/DVSL :-) I will probably add a view
system that uses DVSL instead of XSL. You can find information on DVSL here:
http://jakarta.apache.org/velocity/dvsl/
This is all in Turbine 3. I will attempt to make Velocity, JSP and DVSL all
work with the classic model in t3: layouts, navigations and screens.
>
> If so, I would be interested in knowing how you went about using it.
>
> I am currently using a slightly modifed VelocityXmlLayout (the original did
> not work for some reason?) Instead of screens/navigations I am using xml
> files full of data. The final xml output (layout, navigation and screen xml
> output) is processed by a XSL transformation belonging to the layout.
> (Strange, the original VelocityXmlLayouy could not find the xsl file... This
> might be due to the fact I am not using a standard release ver of turbine...)
>
> Anyways... If anyone else has gone about this in a different fassion, I would
> love to know.
>
> Also, has any one used intake in addition to the xslt service?
>
> Luke
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>