Problem with log in orbeon with multiple webapp

> Like you said, in Orbeon Forms the xforms-submit event will be  
> triggered _after_ the submission completes due to the Ajax request  
> (tested that) instead of _before_ the submission completes, as in  
> Mozilla XForms.

I did not quite say that ;-) xforms-submit is dispatch at the proper  
time. It is just that actions that impact the UI will only produce  
visible effects after the submission has completed.
Thanks for the video, I see exactly what you are trying to do.

For now, the workaround I can see is that pressing on the button would  
trigger first:

* the toggle
* a piece of xxforms:script dispatching an event to your model

Upon reception of that event, you would then perform the submission,  
and toggle back the UI when done.

-Erik

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/



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

Erik Bruchez wrote:

  Hi

> I think that the spec could be clearer on the subject, but it
> is the Forms Working Group's intent that this is allowed, but
> dependent on the host language / implementation.

  Thank you for the clarification, Erik.

--drkm





















__________________________________________________
Do You Yahoo!?
En finir avec le spam? Yahoo! Mail vous offre la meilleure protection possible contre les messages non sollicités
http://mail.yahoo.fr Yahoo! Mail



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

Thanks a lot, I will remove the ul from my alerts in the meanwhile.

Antoine

-----Original Message-----
From: Erik Bruchez [mailto:[hidden email]]
Sent: Tuesday, May 20, 2008 8:04 PM
To: [hidden email]
Subject: [ops-users] Re: Re: Using an list (ul/ol) in an xforms:alert

>  I am not that familiar with the XForms REC, but its schema doesn't
> allow HTML content.  The REC's prose seems to say that HTML content  
> for
> xf:alert is either forbidden or implementation defined (and I didn't
> find any note about it in the Orbeon doc.)
>
>  Could someone comment on that?  I would be interested to know where
> the response stands in the REC.

I think that the spec could be clearer on the subject, but it is the  
Forms Working Group's intent that this is allowed, but dependent on  
the host language / implementation.

The non-normative schema for XForms says that an alert can contain  
UI.Inline, which is defined as:

     <xsd:group name="UI.Inline">
         <xsd:sequence>
             <xsd:choice minOccurs="0">
                 <xsd:element ref="xforms:output"/>
                 <!-- containing document language to add additional  
allowed content here -->
             </xsd:choice>
         </xsd:sequence>
     </xsd:group>

Notice the "containing document language to add additional allowed  
content here".

Orbeon Forms supports (X)HTML within labels, help, hint and alert.

In my other reply in this thread, I said it was wrong for Orbeon Forms  
to output an HTML <label> to represent an alert with a label as this  
prevents inline content. I now realize that this may go against the  
notion of UI.Inline in the XForms schema. I am not clear on that, so I  
just sent an email to the working group to see what's the opinion  
there. Certainly it seems to me that help and alert in particular  
should not be restricted to inline HTML content.

-Erik

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/



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

Antoine.DE-TROOSTEMBERGH wrote:

> Thanks a lot, I will remove the ul from my alerts in the
> meanwhile.

  BTW, I didn't think about that yesterday, but a possible workaround
could be to use the following:

    <xf:alert>
       &#x25CF; The timing is required <h:br/>
       &#x25CF; The timing should be &gt; 0
    </xf:alert>

  In case the entity ref has been resolved somewhere in the email
system, it is "& # x 2 5 C F ;".  Not really satisfactory regarding the
use of a list, but that should work.

  Regards,

--drkm























__________________________________________________
Do You Yahoo!?
En finir avec le spam? Yahoo! Mail vous offre la meilleure protection possible contre les messages non sollicités
http://mail.yahoo.fr Yahoo! Mail



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

> For now, the workaround I can see is that pressing on the button would
> trigger first:
>
> * the toggle
> * a piece of xxforms:script dispatching an event to your model
>
> Upon reception of that event, you would then perform the submission, and
> toggle back the UI when done.

I managed to get the test web applications to work, thanks to your
workaround. Here is the code I used if otherones are interested:


-Markku

<head>...
   <xforms:model xxforms:external-events="orbeon-forms-xforms-submit">
     <!-- Instances -->
     <xforms:instance id="my-instance">
       <dummy xmlns="" />
     </xforms:instance>
     <!-- Submissions -->
     <xforms:submission id="my-submission" replace="instance"
instance="my-instance" method="post" action="../xformssubmiteventservlet"
encoding="UTF-8" mediatype="application/xml">
       <xforms:action ev:event="orbeon-forms-xforms-submit">
         <xforms:send submission="my-submission" />
       </xforms:action>
       ...
     </xforms:submission>
   ...</head>
   <body>...
     <xforms:trigger>
       <xforms:label>Test submission</xforms:label>
       <xforms:action ev:event="DOMActivate">
         <!-- Switch UI before dispatching the event -->
         <xforms:toggle case="on-process-working-switcher" />
         <!-- Dispatch the event using xxforms:script -->
         <xxforms:script ev:event="DOMActivate">
           ORBEON.xforms.Document.dispatchEvent( "my-submission",
"orbeon-forms-xforms-submit" );
         </xxforms:script>
       </xforms:action>
     </xforms:trigger>
   ...</body>


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

Markku,

Thanks for sharing this.

-Erik

On May 26, 2008, at 3:17 PM, .::: Markku :::. wrote:
--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/



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

Hey Alessandro,

I've found that that almost fixes the problem (we have the same issue, we're running one war with OPS and about 30 other wars *not* using OPS, and we have one common log4j config file in one location), but not quite.   I did find a fix, though.

The original defect can't be re-opened, it seems, so I've created a new one:  http://forge.objectweb.org/tracker/?group_id=168&atid=350207&func=detail&aid=310675

Thanks!

rodney

Alessandro Vernet wrote

Michael,

On Wed, Apr 30, 2008 at 6:04 PM, Michael Roberts <mroberts@reallysi.com> wrote:
>  No, we chose not to modify the Orbeon source because I would rather have a
> clean upgrade path and so I stay away from modifying in that way as much as
> is feasible.

I understand. We just commented this line, and we'll see how that
works. You'll let us know if this solves the problem for you. You can
get this change in the next nightly build. For reference the bug is:

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

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


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


-----
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
http://www.orbeon.com/

Rodney,

On Fri, Jul 25, 2008 at 4:52 PM, Rodney Gitzel <[hidden email]> wrote:
> I've found that that almost fixes the problem (we have the same issue, we're
> running one war with OPS and about 30 other wars *not* using OPS, and we
> have one common log4j config file in one location), but not quite.   I did
> find a fix, though.
>
> The original defect can't be re-opened, it seems, so I've created a new one:
> http://forge.objectweb.org/tracker/?group_id=168&atid=350207&func=detail&aid=310675

I am not sure why we would need to call
LogManager.resetConfiguration(). Ideally, the log4j classes we use are
loaded by a class loader which is specific to this web application. If
that happens, there shouldn't be anything to reset. And if we are
using a shared log4j, then reseting the configuration doesn't sound
like a good idea. So I commented that code and put there a link back
to this thread.

Regarding the static block: it has been commented for a few months
now, so this should not be a problem anymore.

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.com/
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