xforms:trigger appearance==?ISO-8859-1?Q?=93xforms?=:=?ISO-8859-1?Q?link=93?=

Hello,
Reading the forum I am not sure if or when this xforms:trigger appearance=?xforms:link? issue is closed.

I am using version 3.0 beta 3 and my application work as long as I do not use the appearance attribute.
Is the issue still open or was it closed after 3.0 beta 3.

I also tried the nightly builds from 2005-12-06 and 2005-12-07 but I receive the following error:

Error Message
The following error has occurred:
Error Message
Cannot find processor factory with name "{http://www.orbeon.com/oxf/processors}xinclude"

Should those builds work or did I just make a mistake by copying the files in my Studio environment?

Thank you in advance
Peter



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

Peter,

 > Reading the forum I am not sure if or when this xforms:trigger
 > appearance="forms:link" issue is closed.
 >
 > I am using version 3.0 beta 3 and my application work as long as I
 > do not use the appearance attribute.

 > Is the issue still open or was it closed after 3.0 beta 3.

Triggers implemented as links have been working for a long time. I do
not remember exactly when they were broken, but that must have been
quite a while ago!

 > I also tried the nightly builds from 2005-12-06 and 2005-12-07 but I
 > receive the following error:
 >
 > Error Message
 > The following error has occurred:
 > Error Message
 > Cannot find processor factory with name
"{http://www.orbeon.com/oxf/processors}xinclude"
 >
 > Should those builds work or did I just make a mistake by copying the
 > files in my Studio environment?

Yes those builds should (and do!) work. The error above seem to
suggest that some JAR file was not updated on your system. Also, the
content of resources/ops must be copied over.

-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

Peter,
        I noticed you were using <xforms:trigger appearance="xforms:link">,
but it should be xxforms:link. This might be a problem, if not try sharing
some code

Ryan Puddephatt
Web Developer
TFX Group
1 Michaelson Square
Livingston
West Lothian
Scotand
EH54 7DP
 
* [hidden email]
( 01506 407 110
7  01506 407 108
 

-----Original Message-----
From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
Sent: 07 December 2005 11:38
To: [hidden email]
Subject: Re: [ops-users] xforms:trigger appearance="xforms:link"

Peter,

 > Reading the forum I am not sure if or when this xforms:trigger
 > appearance="forms:link" issue is closed.
 >
 > I am using version 3.0 beta 3 and my application work as long as I
 > do not use the appearance attribute.

 > Is the issue still open or was it closed after 3.0 beta 3.

Triggers implemented as links have been working for a long time. I do
not remember exactly when they were broken, but that must have been
quite a while ago!

 > I also tried the nightly builds from 2005-12-06 and 2005-12-07 but I
 > receive the following error:
 >
 > Error Message
 > The following error has occurred:
 > Error Message
 > Cannot find processor factory with name
"{http://www.orbeon.com/oxf/processors}xinclude"
 >
 > Should those builds work or did I just make a mistake by copying the
 > files in my Studio environment?

Yes those builds should (and do!) work. The error above seem to
suggest that some JAR file was not updated on your system. Also, the
content of resources/ops must be copied over.

-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

Hello Ryan,
Thank you for your response. However the xform NS was only a typing mistake in my e-mail, in my view I used xxform.

I managed to change to a build from 2005-12-07 (one before Beta4) and my problem has gone.

But in that version appeared an other smaller problem with a xforms:trigger appearance="xxforms:image" because in that version I had to add a dummy <xforms:label>dummy</xforms:label> to get rid of an empty error message and a java.lang.NullPointerException.

I think this is not a big issue, however pitfall at all.

Mit freundlichen Grüßen / Best regards,

Peter Heintz

--

Knorr-Bremse SfS GmbH

COC BC,R/BCE11

Moosacher Straße 80,D-80809 Munich

Phone +49 893547-1145

Fax +49 893547-2676

mailto:[hidden email]

http://www.knorr-bremse.com


-----Ursprüngliche Nachricht-----
Von: Ryan Puddephatt [mailto:[hidden email]]
Gesendet: Donnerstag, 8. Dezember 2005 16:11
An: [hidden email]
Betreff: RE: [ops-users] xforms:trigger appearance="xforms:link"

Peter,
        I noticed you were using <xforms:trigger appearance="xforms:link">,
but it should be xxforms:link. This might be a problem, if not try sharing
some code

Ryan Puddephatt
Web Developer
TFX Group
1 Michaelson Square
Livingston
West Lothian
Scotand
EH54 7DP
 
* [hidden email]
( 01506 407 110
7  01506 407 108
 

-----Original Message-----
From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
Sent: 07 December 2005 11:38
To: [hidden email]
Subject: Re: [ops-users] xforms:trigger appearance="xforms:link"

Peter,

 > Reading the forum I am not sure if or when this xforms:trigger
 > appearance="forms:link" issue is closed.
 >
 > I am using version 3.0 beta 3 and my application work as long as I
 > do not use the appearance attribute.

 > Is the issue still open or was it closed after 3.0 beta 3.

Triggers implemented as links have been working for a long time. I do
not remember exactly when they were broken, but that must have been
quite a while ago!

 > I also tried the nightly builds from 2005-12-06 and 2005-12-07 but I
 > receive the following error:
 >
 > Error Message
 > The following error has occurred:
 > Error Message
 > Cannot find processor factory with name
"{http://www.orbeon.com/oxf/processors}xinclude"
 >
 > Should those builds work or did I just make a mistake by copying the
 > files in my Studio environment?

Yes those builds should (and do!) work. The error above seem to
suggest that some JAR file was not updated on your system. Also, the
content of resources/ops must be copied over.

-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

[hidden email] wrote:

 > I managed to change to a build from 2005-12-07 (one before Beta4)
 > and my problem has gone.

Good :-)

 > But in that version appeared an other smaller problem with a
 > xforms:trigger appearance="xxforms:image" because in that version I
 > had to add a dummy <xforms:label>dummy</xforms:label> to get rid of
 > an empty error message and a java.lang.NullPointerException.

Yes, xforms:label is in fact mandatory on all XForms controls, as per
the XForms 1.0 spec. In this case you can use an empty label too:

   <xforms:label/>

I guess providing an accessibility message would be best, and I assume
this is the intent of the XForm spec. The message will be put on the
"alt" attribute of the generated image.

 > I think this is not a big issue, however pitfall at all.

I changed the code to provide a better error message in that
particular case.

OPS should at least provide the option of validating XForms through a
schema. This would be the best way of detecting such errors. I entered
a bug to track this:

http://forge.objectweb.org/tracker/index.php?func=detail&aid=304358&group_id=168&atid=350207

-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