OPS Portlets

Hello All,

I'm new to OPS. Great work.

I'm looking at deploying OPS portlets within Liferay and am encountering
problems. Has anyone here attempted to use the OPS portlets in an
alternate container?


--
Raymond Augé
Senior System Analyst/Data Architect




--
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

Ray,

Good timing: over the next two weeks, we will spend a couple of days
investigating exactly this issue with Liferay. Be sure to ping the list
back within that timeframe.

-Erik

Raymond Auge wrote:
> Hello All,
>
> I'm new to OPS. Great work.
>
> I'm looking at deploying OPS portlets within Liferay and am encountering
> problems. Has anyone here attempted to use the OPS portlets in an
> alternate container?

--
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/



--
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

Hello Erik,

I got them to at least register and load into the portal, thought I only
get a message:

"Orbeon PresentationServer - Page Not Found
We are sorry, but the resource you have requested is not available on
this server."

This is a step in the right direction.

Note: Using Liferay 4.0.0 (HEAD from SVN), Tomcat 5.5.16

What I did to get this far:

1 - remove the old version of the portlet-api.jar bundled with Orbeon
war. The existing (up-to-date) one bundled with Liferay in the
common/lib tomcat classpath is used instead.

2 - added a liferay-portlet.xml in WEB-INF

<?xml version="1.0"?>
<!DOCTYPE liferay-portlet-app PUBLIC
                  "-//Liferay//DTD Portlet Application 4.0.0//EN"
                  "http://www.liferay.com/dtd/liferay-portlet-app_4_0_0.dtd">

<liferay-portlet-app>
        <portlet>
                <portlet-name>OXFSimplePortlet</portlet-name>
                <struts-path>OXFSimplePortlet</struts-path>
        </portlet>
        <portlet>
                <portlet-name>OXFRSSPortlet</portlet-name>
                <struts-path>OXFRSSPortlet</struts-path>
        </portlet>
        <portlet>
                <portlet-name>OXFExamples</portlet-name>
                <struts-path>OXFExamples</struts-path>
        </portlet>
</liferay-portlet-app>


3 - added liferay-display.xml in WEB-INF

<?xml version="1.0"?>
<!DOCTYPE display PUBLIC
                  "-//Liferay//DTD Display 4.0.0//EN"
                  "http://www.liferay.com/dtd/liferay-display_4_0_0.dtd">

<display>
        <category name="category.test">
                <portlet id="OXFSimplePortlet" />
                <portlet id="OXFRSSPortlet" />
                <portlet id="OXFExamples" />
        </category>
</display>


4 - added the following entries in web.xml

<context-param>
        <param-name>company_id</param-name>
        <param-value>liferay.com</param-value>
</context-param>
       
<listener>
<listener-class>com.liferay.portal.shared.servlet.PortletContextListener</listener-class>
</listener>


I'm working on tracking the correct resource configuration.

Ray

On Thu, 2006-04-27 at 17:43 -0700, Erik Bruchez wrote: Raymond Augé
Senior System Analyst/Data Architect




--
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

I got further than that but I still didn't get it to work fully. We are currently paying Orbeon to sort this issue for us this week (see Erik's previous reply).

What I did was change the portlet.xml file so that the initial path was relative to the resources directory, the samples that come with ops start from a different root. And then I deployed using the Liferay deployment ant script. This adds the servlet wrapper around OPSPortlet for you (there is no real nead to change the liferay-portlet.xml & liferay-display.xml files - as far as I know).

You then get a Liferay exception saying that the content type returned by the portlet is not supported (application/xml) so I changed epilogue-portlet.xml to force the content type returned to be text/xml.

After this I can get pages displayed as long as they do not include xforms. As soon as I add xforms the page does not display, but looking at the source of the web page shows that the page was returned correctly and embedded into the liferay page (well it looks correct, but obviously something is wrong with it).

I have a document that explains all of this which I have passed to Orbeon with the support request.


Richard Shaw

¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø¤º°`°º¤ø,¸¸,ø¤

Richard Shaw  
Technical Design Authority  
Intelligent Transport Systems

Atkins Highways and Transportation
Woodcote Grove, Ashley Road, Epsom, Surrey, KT18 5BW

Tel: +44 (0) 1372 756407
Fax: +44 (0) 1372 740055
Mob: 07740 817586
E-mail: [hidden email]

www.atkinsglobal.com/its

-----Original Message-----
From: Raymond Auge [mailto:[hidden email]]
Sent: 28 April 2006 14:44
To: [hidden email]
Subject: Re: [ops-users] OPS Portlets

Hello Erik,

I got them to at least register and load into the portal, thought I only get a message:

"Orbeon PresentationServer - Page Not Found We are sorry, but the resource you have requested is not available on this server."

This is a step in the right direction.

Note: Using Liferay 4.0.0 (HEAD from SVN), Tomcat 5.5.16

What I did to get this far:

1 - remove the old version of the portlet-api.jar bundled with Orbeon war. The existing (up-to-date) one bundled with Liferay in the common/lib tomcat classpath is used instead.

2 - added a liferay-portlet.xml in WEB-INF

<?xml version="1.0"?>
<!DOCTYPE liferay-portlet-app PUBLIC
                  "-//Liferay//DTD Portlet Application 4.0.0//EN"
                  "http://www.liferay.com/dtd/liferay-portlet-app_4_0_0.dtd">

<liferay-portlet-app>
        <portlet>
                <portlet-name>OXFSimplePortlet</portlet-name>
                <struts-path>OXFSimplePortlet</struts-path>
        </portlet>
        <portlet>
                <portlet-name>OXFRSSPortlet</portlet-name>
                <struts-path>OXFRSSPortlet</struts-path>
        </portlet>
        <portlet>
                <portlet-name>OXFExamples</portlet-name>
                <struts-path>OXFExamples</struts-path>
        </portlet>
</liferay-portlet-app>


3 - added liferay-display.xml in WEB-INF

<?xml version="1.0"?>
<!DOCTYPE display PUBLIC
                  "-//Liferay//DTD Display 4.0.0//EN"
                  "http://www.liferay.com/dtd/liferay-display_4_0_0.dtd">

<display>
        <category name="category.test">
                <portlet id="OXFSimplePortlet" />
                <portlet id="OXFRSSPortlet" />
                <portlet id="OXFExamples" />
        </category>
</display>


4 - added the following entries in web.xml

<context-param>
        <param-name>company_id</param-name>
        <param-value>liferay.com</param-value>
</context-param>
       
<listener>
<listener-class>com.liferay.portal.shared.servlet.PortletContextListener</listener-class>
</listener>


I'm working on tracking the correct resource configuration.

Ray

On Thu, 2006-04-27 at 17:43 -0700, Erik Bruchez wrote: Raymond Augé
Senior System Analyst/Data Architect




This message has been scanned for viruses by MailControl - (see http://bluepages.wsatkins.co.uk/?4318150)


This email and any attached files are confidential and copyright protected. If you are not the addressee, any dissemination of this communication is strictly prohibited. Unless otherwise expressly agreed in writing, nothing stated in this communication shall be legally binding.



--
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

Hello Richard,

I have proper Orbeon error messages now at least.

How did you change the initial path? Currently, it's resolving
oxf:/examples/dispatch.xpl properly.

This is a fragment of what I have currently in portlet.xml:

<portlet>
<portlet-name>OXFExamples</portlet-name>
<display-name>OXFExamples</display-name>
<portlet-class>org.orbeon.oxf.portlet.OPSPortlet</portlet-class>
<init-param>
        <name>oxf.main-processor.name</name>
        <value>{http://www.orbeon.com/oxf/processors}pipeline</value>
</init-param>
<init-param>
        <name>oxf.main-processor.input.config</name>
        <value>oxf:/examples/dispatch.xpl</value>
</init-param>
<init-param>
        <name>oxf.error-processor.name</name>
        <value>{http://www.orbeon.com/oxf/processors}pipeline</value>
</init-param>
<init-param>
        <name>oxf.error-processor.input.config</name>
        <value>oxf:/config/error.xpl</value>
</init-param>
<init-param>
        <name>oxf.portlet-initialized-processor.name</name>
        <value>{http://www.orbeon.com/oxf/processors}pipeline</value>
</init-param>
<init-param>
        <name>oxf.portlet-initialized-processor.input.config</name>
        <value>oxf:/context/portlet-initialized.xpl</value>
</init-param>
<init-param>
        <name>oxf.portlet-destroyed-processor.name</name>
        <value>{http://www.orbeon.com/oxf/processors}pipeline</value>
</init-param>
<init-param>
        <name>oxf.portlet-destroyed-processor.input.config</name>
        <value>oxf:/context/portlet-destroyed.xpl</value>
</init-param>
<!--init-param>
        <name>oxf.main-processor.name</name>
        <value>{http://www.orbeon.com/oxf/processors}page-flow</value>
</init-param>
<init-param>
        <name>oxf.main-processor.input.controller</name>
        <value>oxf:/config/page-flow.xml</value>
</init-param>
<init-param>
        <name>oxf.error-processor.name</name>
        <value>{http://www.orbeon.com/oxf/processors}pipeline</value>
</init-param>
<init-param>
        <name>oxf.error-processor.input.config</name>
        <value>oxf:/config/error.xpl</value>
</init-param!-->
<supports>
        <mime-type>text/html</mime-type>
</supports>
<portlet-info>
        <title>PresentationServer Example Application</title>
</portlet-info>
</portlet>


Just trying to saty close to the curve as they proceed with this.

Ray

On Fri, 2006-04-28 at 15:25 +0100, Shaw, Richard A wrote: Raymond Augé
Senior System Analyst/Data Architect




--
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

Any progress on this?

Ray

On Thu, 2006-04-27 at 17:43 -0700, Erik Bruchez wrote: Raymond Augé
Senior System Analyst/Data Architect




--
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

Ray,

Yes, we have successfully deployed OPS into Liferay. It is a little
early to say what issues are left if any, but the examples we have tried
now work quite fine within a portlet. See the attached example screenshots.

We have also fixed CSS issues and a conflict between Liferay's
Javascript calendar and OPS's.

If you want to give this a try, you can get a nightly build, and in your
epilogue.xpl refer to epilogue-portlet-liferay.xpl instead of the
original epilogue-portlet.xpl.

-Erik

Raymond Auge wrote: --
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/

Hello Erik,

This is great. I'm going to test it out. I may have more questions for
you on this if it's ok. Nothing to complicated.

Thanks again,

Ray

On Mon, 2006-05-08 at 11:12 -0700, Erik Bruchez wrote: Raymond Augé
Senior System Analyst/Data Architect




--
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

Hello Erik,

Some of the resources referred to in the portlet.xml definition don't
exist in the nightly build war or in CVS.

oxf:/config/page-flow.xml
oxf:/config/error.xpl
oxf:/portlet/rss/config/page-flow.xml
oxf:/portlet/simple/config/page-flow.xml

Actually there is no portlet folder directly under resources.

Are these perhaps not checked into the repository or included in the
build process?

Thanks,

Ray

On Mon, 2006-05-08 at 14:51 -0400, Raymond Auge wrote: Raymond Augé
Senior System Analyst/Data Architect




--
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

Raymond,

That's right, it looks like portlet.xml is out of date. In fact as of
yet we do not have a portlet.xml ready for you. But you can modify this
one by:

o keeping only one portlet to make things simple
o creating a directory, say "my-portlet" under "resources"
o setting the correct links to
   oxf:/my-portlet/page-flow.xml and
   oxf:/my-portlet/error.xml

In your page-flow.xml, just create a simple entry like this:

<page id="home" path-info="/" view="my-form.xhtml"/>

Then create a simple XForms+XHTML page as my-portlet/my-forms.xhtml. You
can use for example the XForms "TODO Lists" view, or other simple examples.

-Erik

Raymond Auge wrote:
--
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/



--
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

Erik, Thank you. The porltet show errors message: Error Message The following error has occurred: Error Message Pipeline input "xformed-data" is not connected OPS Call Stack The OPS Call Stack helps you determine what sequence of OPS operations have caused the error. Resource URL Line Column Description XML Element oxf:/config/epilogue-portlet-liferay.xpl 29 48 oxf:/config/epilogue-portlet-liferay.xpl 137 45 executing processor (name='{http://www.orbeon.com/oxf/processors}http-serializer') ... oxf:/my-portlet/page-flow.xml 19 63 executing processor (name='{http://www.orbeon.com/oxf/processors}pipeline') These are codes: My portlet.xml OXFSimplePortlet org.orbeon.oxf.portlet.OPSPortlet oxf.main-processor.name {http://www.orbeon.com/oxf/processors}page-flow oxf.main-processor.input.controller oxf:/my-portlet/page-flow.xml oxf.error-processor.name {http://www.orbeon.com/oxf/processors}pipeline oxf.er ror-processor.input.config oxf:/config/error.xpl text/html 2. page-flow.xml Raymond, That's right, it looks like portlet.xml is out of date. In fact as of yet we do not have a portlet.xml ready for you. But you can modify this one by: o keeping only one portlet to make things simple o creating a directory, say "my-portlet" under "resources" o setting the correct links to oxf:/my-portlet/page-flow.xml and oxf:/my-portlet/error.xml In your page-flow.xml, just create a simple entry like this: Then create a simple XForms+XHTML page as my-portlet/my-forms.xhtml. You can use for example the XForms "TODO Lists" view, or other simple examples. -Erik Raymond Auge wrote: > Hello Erik, > > Some of the resources referred to in the portlet.xml definition don't > exist in the nightly build war or in CVS. > > oxf:/config/page-flow.xml > oxf:/config/error.xpl > oxf:/portlet/rss/config/page-flow.xml > oxf:/portlet/simple/config/page-flow.xml > > Actually there is no portlet folder directly under resources. > > Are these perhaps not checked into the repository or included in the > build process? > > Thanks, > > Ray > > On Mon, 2006-05-08 at 14:51 -0400, Raymond Auge wrote: >> Hello Erik, >> >> This is great. I'm going to test it out. I may have more questions for >> you on this if it's ok. Nothing to complicated. >> >> Thanks again, >> >> Ray >> >> On Mon, 2006-05-08 at 11:12 -0700, Erik Bruchez wrote: >>> Ray, >>> >>> Yes, we have successfully deployed OPS into Liferay. It is a little >>> early to say what issues are left if any, but the examples we have tried >>> now work quite fine within a portlet. See the attached example screenshots. >>> >>> We have also fixed CSS issues and a conflict between Liferay's >>> Javascript calendar and OPS's. >>> >>> If you want to give this a try, you can get a nightly build, and in your >>> epilogue.xpl refer to epilogue-portlet-liferay.xpl instead of the >>> original epilogue-portlet.xpl. >>> >>> -Erik >>> >>> Raymond Auge wrote: >>>> Any progress on this? >>>> >>>> Ray >>>> >>>> On Thu, 2006-04-27 at 17:43 -0700, Erik Bruchez wrote: >>>>> Ray, >>>>> >>>>> Good timing: over the next two weeks, we will spend a couple of days >>>>> investigating exactly this issue with Liferay. Be sure to ping the list >>>>> back within that timeframe. >>>>> >>>>> -Erik >>>>> >>>>> Raymond Auge wrote: >>>>>> Hello All, >>>>>> >>>>>> I'm new to OPS. Great work. >>>>>> >>>>>> I'm looking at deploying OPS portlets within Liferay and am encountering >>>>>> problems. Has anyone here attempted to use the OPS portlets in an >>>>>> alternate container? >>>>> plain text document attachment (message-footer.txt) >>> plain text document attachment (message-footer.txt) >>> -- >>> You receive this message as a subscriber of the ops-users@objectweb.org mailing list. >>> To unsubscribe: mailto:ops-users-unsubscribe@objectweb.org >>> For general help: mailto:sympa@objectweb.org?subject=help >>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws >> plain text document attachment (message-footer.txt) >> -- >> You receive this message as a subscriber of the ops-users@objectweb.org mailing list. >> To unsubscribe: mailto:ops-users-unsubscribe@objectweb.org >> For general help: mailto:sympa@objectweb.org?subject=help >> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws >> >> ------------------------------------------------------------------------ >> >> >> -- >> You receive this message as a subscriber of the ops-users@objectweb.org mailing list. >> To unsubscribe: mailto:ops-users-unsubscribe@objectweb.org >> For general help: mailto:sympa@objectweb.org?subject=help >> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws -- Orbeon - XForms Everywhere: http://www.orbeon.com/blog/ -- You receive this message as a subscriber of the ops-users@objectweb.org mailing list. To unsubscribe: mailto:ops-users-unsubscribe@objectweb.org For general help: mailto:sympa@objectweb.org?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

 Erik,
 
 Thank you. The porltet show errors message:

 Error Message
 
 The following error has occurred:
 Error Message
 Pipeline input "xformed-data" is not connected
 
 
     OPS Call Stack
 
 The OPS Call Stack helps you determine what sequence of OPS
operations
 have caused the error.
 Resource URL Line Column Description XML Element
 oxf:/config/epilogue-portlet-liferay.xpl 29 48
 oxf:/config/epilogue-portlet-liferay.xpl 137 45 executing
processor
 (name='{http://www.orbeon.com/oxf/processors}http-serializer')
   <p:processor name="oxf:http-serializer">...</p:processor>
 oxf:/my-portlet/page-flow.xml 19 63 executing processor
 (name='{http://www.orbeon.com/oxf/processors}pipeline')
 
 
 These are codes:
 
 My portlet.xml
 
 <portlet-app>
  <portlet>
   <portlet-name>OXFSimplePortlet</portlet-name>
   <portlet-class>org.orbeon.oxf.portlet.OPSPortlet</portlet-class>
   <init-param>
    <name>oxf.main-processor.name</name>
    <value>{http://www.orbeon.com/oxf/processors}page-flow</value>
   </init-param>
   <init-param>
    <name>oxf.main-processor.input.controller</name>
    <value>oxf:/my-portlet/page-flow.xml</value>
   </init-param>
   <init-param>
    <name>oxf.error-processor.name</name>
    <value>{http://www.orbeon.com/oxf/processors}pipeline</value>
   </init-param>
   <init-param>
    <name>oxf.er ror-processor.input.config</name>
    <value>oxf:/config/error.xpl</value>
   </init-param>
   <supports>
    <mime-type>text/html</mime-type>
   </supports>
   <portlet-info>
    <title>PresentationServer Simple Portlet</title>
   </portlet-info>
  </portlet
 
 </portlet-app>
 
 2. page-flow.xml
 
 <config xmlns="http://www.orbeon.com/oxf/controller"
         xmlns:xu="http://www.xmldb.org/xupdate">
     <page id="home" path-info="/" view="view.xhtml"/>
     <epilogue url="oxf:/config/epilogue-portlet-liferay.xpl"/>
 
 </config
 
 
 3. view.xhtml from "todo" example.
 
 
 If I take epilogue off page-flow.xml, I get only text show without
form.
 Do I miss something?

Sam

<quote author='Erik Bruchez'>
Raymond,

That's right, it looks like portlet.xml is out of date. In fact as of
yet we do not have a portlet.xml ready for you. But you can modify this
one by:

o keeping only one portlet to make things simple
o creating a directory, say "my-portlet" under "resources"
o setting the correct links to
   oxf:/my-portlet/page-flow.xml and
   oxf:/my-portlet/error.xml

In your page-flow.xml, just create a simple entry like this:

<page id="home" path-info="/" view="my-form.xhtml"/>

Then create a simple XForms+XHTML page as my-portlet/my-forms.xhtml. You
can use for example the XForms "TODO Lists" view, or other simple examples.

-Erik

Raymond Auge wrote:
> Hello Erik,
>
> Some of the resources referred to in the portlet.xml definition don't
> exist in the nightly build war or in CVS.
>
> oxf:/config/page-flow.xml
> oxf:/config/error.xpl
> oxf:/portlet/rss/config/page-flow.xml
> oxf:/portlet/simple/config/page-flow.xml
>
> Actually there is no portlet folder directly under resources.
>
> Are these perhaps not checked into the repository or included in the
> build process?
>
> Thanks,
>
> Ray
>
> On Mon, 2006-05-08 at 14:51 -0400, Raymond Auge wrote:
>> Hello Erik,
>>
>> This is great. I'm going to test it out. I may have more questions for
>> you on this if it's ok. Nothing to complicated.
>>
>> Thanks again,
>>
>> Ray
>>
>> On Mon, 2006-05-08 at 11:12 -0700, Erik Bruchez wrote:
>>> Ray,
>>>
>>> Yes, we have successfully deployed OPS into Liferay. It is a little
>>> early to say what issues are left if any, but the examples we have tried
>>> now work quite fine within a portlet. See the attached example screenshots.
>>>
>>> We have also fixed CSS issues and a conflict between Liferay's
>>> Javascript calendar and OPS's.
>>>
>>> If you want to give this a try, you can get a nightly build, and in your
>>> epilogue.xpl refer to epilogue-portlet-liferay.xpl instead of the
>>> original epilogue-portlet.xpl.
>>>
>>> -Erik
>>>
>>> Raymond Auge wrote:
>>>> Any progress on this?
>>>>
>>>> Ray
>>>>
>>>> On Thu, 2006-04-27 at 17:43 -0700, Erik Bruchez wrote:
>>>>> Ray,
>>>>>
>>>>> Good timing: over the next two weeks, we will spend a couple of days
>>>>> investigating exactly this issue with Liferay. Be sure to ping the list
>>>>> back within that timeframe.
>>>>>
>>>>> -Erik
>>>>>
>>>>> Raymond Auge wrote:
>>>>>> Hello All,
>>>>>>
>>>>>> I'm new to OPS. Great work.
>>>>>>
>>>>>> I'm looking at deploying OPS portlets within Liferay and am encountering
>>>>>> problems. Has anyone here attempted to use the OPS portlets in an
>>>>>> alternate container?
>>>>> plain text document attachment (message-footer.txt)
>>> plain text document attachment (message-footer.txt)
>>> --
>>> You receive this message as a subscriber of the ops-users@objectweb.org mailing list.
>>> To unsubscribe: mailto:ops-users-unsubscribe@objectweb.org
>>> For general help: mailto:sympa@objectweb.org?subject=help
>>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>> plain text document attachment (message-footer.txt)
>> --
>> You receive this message as a subscriber of the ops-users@objectweb.org mailing list.
>> To unsubscribe: mailto:ops-users-unsubscribe@objectweb.org
>> For general help: mailto:sympa@objectweb.org?subject=help
>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>>
>> ------------------------------------------------------------------------
>>
>>
>> --
>> You receive this message as a subscriber of the ops-users@objectweb.org mailing list.
>> To unsubscribe: mailto:ops-users-unsubscribe@objectweb.org
>> For general help: mailto:sympa@objectweb.org?subject=help
>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws


--
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/



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