Schema SimpleType Must be Valid but not required

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

Schema SimpleType Must be Valid but not required

npujol73
hi,

 I have created a simpletype and use it in a bind - works great. Only
thing is I don't want to make it required. Do I need to handle it in
the simpletype definition or is there something else I can do? I am
going to dig into the xforms:date type which has this behavior.....
Thanks


--
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
Reply | Threaded
Open this post in threaded view
|

Re: Schema SimpleType Must be Valid but not required

Alessandro  Vernet
Administrator
Nicolas,

On Mon, Nov 16, 2009 at 8:30 AM, Nicolas Pujol <[hidden email]> wrote:
>  I have created a simpletype and use it in a bind - works great. Only
> thing is I don't want to make it required. Do I need to handle it in
> the simpletype definition or is there something else I can do? I am
> going to dig into the xforms:date type which has this behavior.....

Yes, you'll need to handle this in your type definition and make sure
that the empty string is an acceptable value.

Alex
--
Orbeon Forms - Web forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
My Twitter: http://twitter.com/avernet


--
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
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
Reply | Threaded
Open this post in threaded view
|

URL Issue

Ganaphathy, Karunamoorthy
All,

We were able to use load the xml form separate deployment like below.

../../../../../myexist/{instance('record-instance')/packageId}/header-fdsys.xml


Same is not working for "put". So we tried using the f:url-norewrite="true" then it worked.

But the same is throwing 403 in Unix box? Any Idea for a fix?

Thanks
Karun


<!-- submissions get to put to save it-->
 <xforms:submission id="new-submission" ref="instance('header-instance')" action="/xme/myexist/{instance('record-instance')/packageId}/header-fdsys.xml" method="put" replace="none" f:url-norewrite="true">
</xforms:submission>


--
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
Reply | Threaded
Open this post in threaded view
|

RE: URL Issue

Ganaphathy, Karunamoorthy
All,

After re deploying this issue is fixed by itself...weird!!

Thanks Again
Karun


-----Original Message-----
From: Ganaphathy, Karunamoorthy [mailto:[hidden email]]
Sent: Tuesday, November 17, 2009 3:33 PM
To: [hidden email]
Subject: [ops-users] URL Issue

All,

We were able to use load the xml form separate deployment like below.

../../../../../myexist/{instance('record-instance')/packageId}/header-fdsys.xml


Same is not working for "put". So we tried using the f:url-norewrite="true" then it worked.

But the same is throwing 403 in Unix box? Any Idea for a fix?

Thanks
Karun


<!-- submissions get to put to save it-->
 <xforms:submission id="new-submission" ref="instance('header-instance')" action="/xme/myexist/{instance('record-instance')/packageId}/header-fdsys.xml" method="put" replace="none" f:url-norewrite="true">
</xforms:submission>


--
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
Reply | Threaded
Open this post in threaded view
|

Re: RE: URL Issue

npujol73
I am running into the same problem: in my local environment it works  
but not our test environment. The difference is that in our test  
environment my jboss server ( with orbeon running in a separate  
environment) runs on a different port than the url that is actually  
exposed to the world.

For example, the server runs on port 8089  on the box. A router is  
forwarding the port 80 traffic coming into the network, to port 8089  
on the box where the server is running. From a security standpoint  
this is actually pretty typical.

So....I believe the issue is that both the instance's src  or the  
submission's action/ resource end up generating an absolute url based  
on the xform's originating request's uri. In the network environment  
described above there is, to my knowledge, no reliable way of infer an  
absolute url, and opening port 80 on the server is not an option since  
using a different port on the server than on the publically exposed  
url was the point in the first place.

I would suspect there exists a way to open an http connection to a  
trully relative url .That is what orbeon should do and not try to  
recreate an absolute url.

Thoughts?

thanks

On Nov 18, 2009, at 7:33 AM, "Ganaphathy, Karunamoorthy" <[hidden email]
 > wrote:

> All,
>
> After re deploying this issue is fixed by itself...weird!!
>
> Thanks Again
> Karun
>
>
> -----Original Message-----
> From: Ganaphathy, Karunamoorthy [mailto:[hidden email]]
> Sent: Tuesday, November 17, 2009 3:33 PM
> To: [hidden email]
> Subject: [ops-users] URL Issue
>
> All,
>
> We were able to use load the xml form separate deployment like below.
>
> ../../../../../myexist/{instance('record-instance')/packageId}/
> header-fdsys.xml
>
>
> Same is not working for "put". So we tried using the f:url-
> norewrite="true" then it worked.
>
> But the same is throwing 403 in Unix box? Any Idea for a fix?
>
> Thanks
> Karun
>
>
> <!-- submissions get to put to save it-->
> <xforms:submission id="new-submission" ref="instance('header-
> instance')" action="/xme/myexist/{instance('record-instance')/
> packageId}/header-fdsys.xml" method="put" replace="none" f:url-
> norewrite="true">
> </xforms:submission>
>
> --
> 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
Reply | Threaded
Open this post in threaded view
|

Re: Re: RE: URL Issue

Erik Bruchez
Administrator
Nicolas,

For service URLs created by xforms:submission, this property might help:

<property as="xs:anyURI"  name="oxf.url-rewriting.service.base-uri"
  value="<a href="http://my-server:my-port/">http://my-server:my-port/"/>

It was designed exactly for those proxy scenarios.

-Erik

On Wed, Nov 18, 2009 at 7:14 AM, Nicolas Pujol <[hidden email]> wrote:

> I am running into the same problem: in my local environment it works but not
> our test environment. The difference is that in our test environment my
> jboss server ( with orbeon running in a separate environment) runs on a
> different port than the url that is actually exposed to the world.
>
> For example, the server runs on port 8089  on the box. A router is
> forwarding the port 80 traffic coming into the network, to port 8089 on the
> box where the server is running. From a security standpoint this is actually
> pretty typical.
>
> So....I believe the issue is that both the instance's src  or the
> submission's action/ resource end up generating an absolute url based on the
> xform's originating request's uri. In the network environment described
> above there is, to my knowledge, no reliable way of infer an absolute url,
> and opening port 80 on the server is not an option since using a different
> port on the server than on the publically exposed url was the point in the
> first place.
>
> I would suspect there exists a way to open an http connection to a trully
> relative url .That is what orbeon should do and not try to recreate an
> absolute url.
>
> Thoughts?
>
> thanks
>
> On Nov 18, 2009, at 7:33 AM, "Ganaphathy, Karunamoorthy"
> <[hidden email]> wrote:
>
>> All,
>>
>> After re deploying this issue is fixed by itself...weird!!
>>
>> Thanks Again
>> Karun
>>
>>
>> -----Original Message-----
>> From: Ganaphathy, Karunamoorthy [mailto:[hidden email]]
>> Sent: Tuesday, November 17, 2009 3:33 PM
>> To: [hidden email]
>> Subject: [ops-users] URL Issue
>>
>> All,
>>
>> We were able to use load the xml form separate deployment like below.
>>
>>
>> ../../../../../myexist/{instance('record-instance')/packageId}/header-fdsys.xml
>>
>>
>> Same is not working for "put". So we tried using the
>> f:url-norewrite="true" then it worked.
>>
>> But the same is throwing 403 in Unix box? Any Idea for a fix?
>>
>> Thanks
>> Karun
>>
>>
>> <!-- submissions get to put to save it-->
>> <xforms:submission id="new-submission" ref="instance('header-instance')"
>> action="/xme/myexist/{instance('record-instance')/packageId}/header-fdsys.xml"
>> method="put" replace="none" f:url-norewrite="true">
>> </xforms:submission>
>>
>> --
>> 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
>
>


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