Minimal HTML transformations

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Minimal HTML transformations

shaworth
I am seeking examples that are more relevent to my situation than the code I have reviewed.  My enviroment is unusual, so I'll start with a quick overview.

We are using edge side includes, (ESI http://www.esi.org/) to assemble pages for our applications.  The ESI server handles authentication and constructs pages using fragments that are delivered from the origin servers.  The Origin servers are running a mix of apache and tomcat.  We are using postgres as our RDBMS.  We have embedded all of our business logic within our database.

Our goal is to deploy orbeon as an origin server.

We will need to strip out the web-page assembly (themes, headers, sidebars, footers...) that is present in all the examples I've examined.  My question is how do I best accomplish this?  Hopefully I've overlooked an example, I'm new to the Pipelines and I havn't figured this out on my own.

Any pointers / examples would be much appreicated.

Cheers,

Shannon Haworth



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Minimal HTML transformations

Erik Bruchez
Administrator
[hidden email] wrote:

 > I am seeking examples that are more relevent to my situation than
 > the code I have reviewed.  My enviroment is unusual, so I'll start
 > with a quick overview.
 >
 > We are using edge side includes, (ESI http://www.esi.org/) to
 > assemble pages for our applications.  The ESI server handles
 > authentication and constructs pages using fragments that are
 > delivered from the origin servers.  The Origin servers are running a
 > mix of apache and tomcat.  We are using postgres as our RDBMS.  We
 > have embedded all of our business logic within our database.
 >
 > Our goal is to deploy orbeon as an origin server.
 >
 > We will need to strip out the web-page assembly (themes, headers,
 > sidebars, footers...) that is present in all the examples I've
 > examined.  My question is how do I best accomplish this?  Hopefully
 > I've overlooked an example, I'm new to the Pipelines and I havn't
 > figured this out on my own.
 >
 > Any pointers / examples would be much appreicated.

Hi Shannon,

The good news is that there is absolutely no problem to achieve
something like this. There are two sides to the answer to your
question:

1. The OPS examples run in what we call the "OPS examples portal",
    which is what you see here:

      http://www.orbeon.com/ops/

    This basic portal presents all the OPS examples with the side bar
    and top-level menus, etc. The actual examples run independently in
    portlets. See BTW the now famous JSR-168 FAQ entry here:

      http://www.orbeon.com/ops/doc/home-faq#jsr-168

    Now your own examples and applications do not have to run in that
    examples portal. Several examples in fact also have an option to
    run standalone, for example the BizDoc NG example:

      http://www.orbeon.com/ops/bizdoc2

    So this is part of the answer: don't run your examples in the
    portal, just run them standalone, i.e. add your application pages
    to the top-level page flow (page-flow.xml).

2. I also recommend you have a careful look at this part of the
    documentation:

      http://www.orbeon.com/ops/doc/reference-epilogue

    Changing theme.xsl will give you control over how your page views
    are themed. In your case, you may want to modify
    config/theme/theme.xsl to output an XHTML fragment.

-Erik



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

XPL debugging

shaworth
In reply to this post by shaworth
Hello,

I have met with mixed success writing XPL.  I am able to query my
back-end database (postgres), and have had no trouble constructing lists
or xforms with the results.  However I am having a lot of trouble
creating pipelines that save forms back into the database.  (Not a
permissions problem, I checked there first).  BTW, I've tried using the
employees example as a template.

My question is:  What are best practices for troubleshooting pipelines?

Any pointers are appreciated.

Shannon Haworth





--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: XPL debugging

Alexander Žaťko
You can turn debugging on by following these steps:

1) configure your log4j.xml file located in resources/config/ directory
by adding the following info:
        a) uncomment the file appender element <appender name="FileAppender">
and
        specify path to the directory where you want to have log file written
in the <param name="File element"> element
        b) make sure the <appender-ref ref="FileAppender"/> is uncommented in
the <root> element

2) in your xpl you can attach a debug attribute to any (?) processor
output or input like this:

     <p:processor name="oxf:xslt">
         <p:input name="tn-xml" href="#url-request"/>
         <p:input name="data" href="oxf:/some-model.xml"/>
         <p:input name="config">....</p:input>
         <p:output name="data" id="sql-config" debug="sql-config"/>
     </p:processor>

Then restart your server app. You will see something like this in the
log file:

http-80-Processor24 INFO  processor.DebugProcessor - sql-config:
oxf:/<path-and-/name-of-your-xml-file>, line <line number of where the
"debug" attribute is placed>, column <column number>

....... the xml output input file listed here.....


Alex

On Oct 3, 2005, at 1:55 PM, Shannon Haworth wrote:

> Hello,
>
> I have met with mixed success writing XPL.  I am able to query my
> back-end database (postgres), and have had no trouble constructing
> lists or xforms with the results.  However I am having a lot of
> trouble creating pipelines that save forms back into the database.  
> (Not a permissions problem, I checked there first).  BTW, I've tried
> using the employees example as a template.
>
> My question is:  What are best practices for troubleshooting pipelines?
>
> Any pointers are appreciated.
>
> Shannon Haworth
>
>
> --
> You receive this message as a subscriber of the
> [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> 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: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: XPL debugging

Erik Bruchez
Administrator
Excellent summary, Alex.

You should also know that you don't have to use a ConsoleAppender (which
sends debugging info to your Servlet container's console) or a
FileAppender (which sends it to a file). You can also use the
ChainsawAppender:

<appender name="ChainsawAppender"
class="org.apache.log4j.net.SocketAppender">
     <param name="RemoteHost" value="localhost"/>
     <param name="Port" value="4445"/>
     <param name="LocationInfo" value="true"/>
</appender>

This allows you to use Chainsaw, a log viewer that comes with log4j.
This is way better than logging to a console.

Finally, you can also use Studio. In fact, this is one of the best
features of Studio: it shows log entries a little bit like Chainsaw, but
also shows XML documents with syntax coloring. Check out the "Debugging
Perspective" screenshot here:

   http://www.orbeon.com/software/studio

-Erik

Alexander Zatko wrote:

> You can turn debugging on by following these steps:
>
> 1) configure your log4j.xml file located in resources/config/ directory
> by adding the following info:
>     a) uncomment the file appender element <appender
> name="FileAppender"> and
>     specify path to the directory where you want to have log file
> written in the <param name="File element"> element
>     b) make sure the <appender-ref ref="FileAppender"/> is uncommented
> in the <root> element
>
> 2) in your xpl you can attach a debug attribute to any (?) processor
> output or input like this:
>
>     <p:processor name="oxf:xslt">
>         <p:input name="tn-xml" href="#url-request"/>
>         <p:input name="data" href="oxf:/some-model.xml"/>
>         <p:input name="config">....</p:input>
>         <p:output name="data" id="sql-config" debug="sql-config"/>
>     </p:processor>
>
> Then restart your server app. You will see something like this in the
> log file:
>
> http-80-Processor24 INFO  processor.DebugProcessor - sql-config:
> oxf:/<path-and-/name-of-your-xml-file>, line <line number of where the
> "debug" attribute is placed>, column <column number>
>
> ....... the xml output input file listed here.....
>
>
> Alex
>
> On Oct 3, 2005, at 1:55 PM, Shannon Haworth wrote:
>
>> Hello,
>>
>> I have met with mixed success writing XPL.  I am able to query my
>> back-end database (postgres), and have had no trouble constructing
>> lists or xforms with the results.  However I am having a lot of
>> trouble creating pipelines that save forms back into the database.  
>> (Not a permissions problem, I checked there first).  BTW, I've tried
>> using the employees example as a template.
>>
>> My question is:  What are best practices for troubleshooting pipelines?
>>
>> Any pointers are appreciated.
>>
>> Shannon Haworth
>>
>>
>> --
>> You receive this message as a subscriber of the
>> [hidden email] mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> 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: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> 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: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws