Thorsten,
You might not be able to make this fully server-independent, but you
could certainly use a property in your properties-local.xml. In there:
* create your own property, e.g.:
<property as="xs:string" name="my.property.name"
value="
http://my.cms.com"/>* in your submissions, use:
<xforms:submission
resource="{xxforms:property('my.property.name')}/rest/of/path"
This assumes you are writing your own XForms.
-Erik
On Wed, Sep 14, 2011 at 6:00 AM, Stumpf, Jens Thorsten
<Thorsten.Stumpf@studiosus.com> wrote:
> Hi!
>
>
>
> I have several questions about Orbeon and its configuration.
>
>
>
> So I think I split them up in several posts.
>
> This post is about my attempt to retrieve information from an other
> webservice/webserver running in the same domain.
>
>
>
>
>
> *The Technical Infrastructure*
>
>
>
> We have a CMS with all our relevant customer information and webpages but it
> is also providing several specific XML documents to the XForms app instance.
>
> The CMS is a typical PHP system.
>
>
>
> Then additionally there is a webcontainer (Tomcat) which is delivering web
> services.
>
> The first web service delivers XML documents containing descriptions of our
> products and analogous stuff.
>
> The second web app within the web container is our Orbeon instance.
>
>
>
> So the Orbeon XForms rely on XML data from our CMS as well as on XML data
> provided by our backend.
>
>
>
> Our infrastructure is set up internally for staging and test processes and
> in an remote location in an seperated network for production.
>
> So the internal systems can not connect with the production systems and vice
> versa.
>
>
>
> The XForms webapp is transparently proxied through to the webserver and is
> thus reachable on the same domain and port as the web view of the CMS is.
>
>
>
>
>
> *The XForms Setup*
>
>
>
> For different customer requests we link from our Website (CMS) the user
> transparently to the XForms app.
>
>
>
> The XForms app requests on „startup“ documents from the backend and
> additionally from the CMS. These provide contextual information for the
> specific request.
>
> The requested data sources share exactly the same domain as the XForms
> request.
>
>
>
> The web services are connected within XPL pipelines.
>
>
>
>
>
> *The Issue*
>
>
>
> Due to the shared webcontainer and domain it isn‘t a big issue to address
> the other web service (/../service – which isn’t that cool but ok).
>
> But we haven‘t been able to figure out how to connect to the CMS without an
> full absolute URL (
http://www.cms.test/xml/product).
>
>
>
> So currently I always have to change the setup of our Orbeon XForms app when
> we deploy a new version.
>
> The deployed version differs on the setup server names. That’s all.
>
> This manual change is error prone, cumbersome and can easily be forgotten,
> especially because the number of requested sources from CMS is increasing.
>
>
>
>
>
> What I would like to achieve is to make the connection to the CMS as well
> with a relative path or at least to change it automatically.
>
> Is there an option to retrieve the connecting host or connecting server
> within the XPLs?
>
>
>
> Can you think of any solution except the trivial ant stuf fand other batch
> thinks?
>
>
>
> Again, I don't need a specific solution - though that's of course welcome -
> but would be glad to be pointed to the location where I can find the needed
> information.
>
>
>
> Thanks a lot in advance
>
>
>
> Thorsten
>
>
>
> --
> 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
> OW2 mailing lists service home page:
http://www.ow2.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
OW2 mailing lists service home page:
http://www.ow2.org/wws