Re: [2.1m2][xmlforms][wizard-flow] nested model-beans and continuations

2003-07-20 Thread Steven Cummings
--- Antonio Gallardo [EMAIL PROTECTED] wrote:
 Steven:
 
 This flow-continuations stuff is so new that too few people have it clear
 enough to advise about the correct way to do what you requested.
 Currently, flow-continuations is still being defined. No one is trying to
 show if someone is bad or good coder. Everybody just try to give a tip
 that can help. Nothing more or less. Your idea to go to dev is good.

Of course! Thanks. I responded too quickly the first time, so I'm sure it
sounded bad.

/S

 
 Best Regards,
 
 Antonio Gallardo.
 
 Steven Cummings dijo:
  No you didn't! I just don't think I explained my intentions well enough
  at first (and the reponse seemed way too obvious at first). No biggy.
  I'll try the dev'ers now. Thanks for the reponses!
 
  /S
  --- Upayavira [EMAIL PROTECTED] wrote:
  Steven,
 
  Hope I didn't offend your programming sensibilities ;-)
 
  I'd recommend asking this on the developer list. There are more people
  doing this kind of stuff there, so you're more likely to get a decent
  answer.
 
  HTH. Upayavira
 
  On Sat, 19 Jul 2003 12:04:08 -0700 (PDT), Steven Cummings
  [EMAIL PROTECTED] said:
   I'm not *that* bad a coder, I can make recursive calls in code! But
  I'm wondering how to ensure that a new continuation is created so
  that I can run a
   sub- formwizard with it's own continuation and then use the old
  continuation
   id to return from it. While I know how continuations are continued
  from the
   flow examples, I don't know exactly how to break back into an
  xmlforms continuation with a particular id. It is built up a little
  more, at a high-level. And I don't immediately have any pipeline
  that takes a continuation
   id like from the flow examples for the form and form-wizard
  frameworks. That is
   my wondering.
  
   /S
   --- Upayavira [EMAIL PROTECTED] wrote:
Steven,
   
On Fri, 18 Jul 2003 19:33:16 -0700 (PDT), Steven Cummings
[EMAIL PROTECTED] said:
 Antonio,

 But how do you make a recursive call within the xmlform
  functionality?
  Do
 you call it within the javascript or from a page to the desired
  pipeline?
   
I'm an extreme newbie here, but:
   
You do it the same as you would with any programming language:
   
var continueRecursing = true;
   
function foo() {
  if (continueRecursing) {
sendPageAndWait(...);
foo();
  }
}
   
Or, if you're using jxforms (flow enabled xmlforms), then you'll
  use sendForm() instead of sendPageAndWait().
   
Hope that helps a bit.
   
Regards,
   
Upayavira
 --- Antonio Gallardo [EMAIL PROTECTED] wrote:
  Steven Cummings dijo:
   Hello all,
  
   I've got kind of a hair-brained question here, forgive me if
  it is
  not
   completely clear. I'm having a hard time thinking of how to
  create
  a
   flow and forms for editing a complex, highly nested, and
  even recursively defined bean.
  
   Let's say I have a bean class A with property of class B. B
  also
  has an
   optional property of type B.
  
   My best thinking is that when I come to those items in the
  xmlform,
  I
   will display a link to another flow, so that a sub-form is
  navigated
   to. Cramming everything into one form is, of course, not a
  very
  good
   option. Anyway, the theoretical solution presents me with
  two
  problems:
  
   1. Could the new form and continuation be passed the old
  continuation,
   and access objects from the old flow?
 
  I am not sure, but maybe a recursion of the same function
  would work
here.
 
  Please comments.
 
   2. Could the new flow return to continue the old
  continuation once
  it
   was done?
 
  See above.
 
  
   I might possibly go as much as two or three continuations
  deeps.
 
  If the recursion can work here, the answer is yes. :)
 
   Remember that each is pretty much an XMLForm wizard
  implementation,
  so
   I'm not writing any other low-level flow code except that to
  control
the
   form wizard much like in the xmlform samples.
  
   I haven't looked into woody that much yet, so if I'm missing
  something
   easier there, let me know. If anybody has any good pointers
  or
  general
   suggestions I would appreciate it! Surely someone else has
  had to
  deel
   with beans that weren't skin-deep and contained further
  complex
types.
  
   TIA
   /S
  
   __
   Do you Yahoo!?
   SBC Yahoo! DSL - Now only $29.95 per month!
   http://sbc.yahoo.com
  
  
  -
To
   unsubscribe, e-mail: [EMAIL PROTECTED] For
  additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 
 -
  To unsubscribe, 

Re: [2.1m2][xmlforms][wizard-flow] nested model-beans and continuations

2003-07-19 Thread Upayavira
Steven,

On Fri, 18 Jul 2003 19:33:16 -0700 (PDT), Steven Cummings
[EMAIL PROTECTED] said:
 Antonio,
 
 But how do you make a recursive call within the xmlform functionality? Do
 you call it within the javascript or from a page to the desired pipeline?

I'm an extreme newbie here, but:

You do it the same as you would with any programming language:

var continueRecursing = true;

function foo() {
  if (continueRecursing) {
sendPageAndWait(...);
foo();
  }
}

Or, if you're using jxforms (flow enabled xmlforms), then you'll use
sendForm() instead of sendPageAndWait().

Hope that helps a bit.

Regards,

Upayavira
 --- Antonio Gallardo [EMAIL PROTECTED] wrote:
  Steven Cummings dijo:
   Hello all,
  
   I've got kind of a hair-brained question here, forgive me if it is not
   completely clear. I'm having a hard time thinking of how to create a
   flow and forms for editing a complex, highly nested, and even
   recursively defined bean.
  
   Let's say I have a bean class A with property of class B. B also has an
   optional property of type B.
  
   My best thinking is that when I come to those items in the xmlform, I
   will display a link to another flow, so that a sub-form is navigated
   to. Cramming everything into one form is, of course, not a very good
   option. Anyway, the theoretical solution presents me with two problems:
  
   1. Could the new form and continuation be passed the old continuation,
   and access objects from the old flow?
  
  I am not sure, but maybe a recursion of the same function would work here.
  
  Please comments.
  
   2. Could the new flow return to continue the old continuation once it
   was done?
  
  See above.
  
  
   I might possibly go as much as two or three continuations deeps.
  
  If the recursion can work here, the answer is yes. :)
  
   Remember that each is pretty much an XMLForm wizard implementation, so
   I'm not writing any other low-level flow code except that to control the
   form wizard much like in the xmlform samples.
  
   I haven't looked into woody that much yet, so if I'm missing something
   easier there, let me know. If anybody has any good pointers or general
   suggestions I would appreciate it! Surely someone else has had to deel
   with beans that weren't skin-deep and contained further complex types.
  
   TIA
   /S
  
   __
   Do you Yahoo!?
   SBC Yahoo! DSL - Now only $29.95 per month!
   http://sbc.yahoo.com
  
   - To
   unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
  
  
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
  
 
 
 __
 Do you Yahoo!?
 SBC Yahoo! DSL - Now only $29.95 per month!
 http://sbc.yahoo.com
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [2.1m2][xmlforms][wizard-flow] nested model-beans and continuations

2003-07-19 Thread Steven Cummings
I'm not *that* bad a coder, I can make recursive calls in code! But I'm
wondering how to ensure that a new continuation is created so that I can run a
sub- formwizard with it's own continuation and then use the old continuation
id to return from it. While I know how continuations are continued from the
flow examples, I don't know exactly how to break back into an xmlforms
continuation with a particular id. It is built up a little more, at a
high-level. And I don't immediately have any pipeline that takes a continuation
id like from the flow examples for the form and form-wizard frameworks. That is
my wondering.

/S
--- Upayavira [EMAIL PROTECTED] wrote:
 Steven,
 
 On Fri, 18 Jul 2003 19:33:16 -0700 (PDT), Steven Cummings
 [EMAIL PROTECTED] said:
  Antonio,
  
  But how do you make a recursive call within the xmlform functionality? Do
  you call it within the javascript or from a page to the desired pipeline?
 
 I'm an extreme newbie here, but:
 
 You do it the same as you would with any programming language:
 
 var continueRecursing = true;
 
 function foo() {
   if (continueRecursing) {
 sendPageAndWait(...);
 foo();
   }
 }
 
 Or, if you're using jxforms (flow enabled xmlforms), then you'll use
 sendForm() instead of sendPageAndWait().
 
 Hope that helps a bit.
 
 Regards,
 
 Upayavira
  --- Antonio Gallardo [EMAIL PROTECTED] wrote:
   Steven Cummings dijo:
Hello all,
   
I've got kind of a hair-brained question here, forgive me if it is not
completely clear. I'm having a hard time thinking of how to create a
flow and forms for editing a complex, highly nested, and even
recursively defined bean.
   
Let's say I have a bean class A with property of class B. B also has an
optional property of type B.
   
My best thinking is that when I come to those items in the xmlform, I
will display a link to another flow, so that a sub-form is navigated
to. Cramming everything into one form is, of course, not a very good
option. Anyway, the theoretical solution presents me with two problems:
   
1. Could the new form and continuation be passed the old continuation,
and access objects from the old flow?
   
   I am not sure, but maybe a recursion of the same function would work
 here.
   
   Please comments.
   
2. Could the new flow return to continue the old continuation once it
was done?
   
   See above.
   
   
I might possibly go as much as two or three continuations deeps.
   
   If the recursion can work here, the answer is yes. :)
   
Remember that each is pretty much an XMLForm wizard implementation, so
I'm not writing any other low-level flow code except that to control
 the
form wizard much like in the xmlform samples.
   
I haven't looked into woody that much yet, so if I'm missing something
easier there, let me know. If anybody has any good pointers or general
suggestions I would appreciate it! Surely someone else has had to deel
with beans that weren't skin-deep and contained further complex
 types.
   
TIA
/S
   
__
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
   
-
 To
unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   
   
   
   
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
   
  
  
  __
  Do you Yahoo!?
  SBC Yahoo! DSL - Now only $29.95 per month!
  http://sbc.yahoo.com
  
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


__
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [2.1m2][xmlforms][wizard-flow] nested model-beans and continuations

2003-07-19 Thread Upayavira
Steven,

Hope I didn't offend your programming sensibilities ;-)

I'd recommend asking this on the developer list. There are more people
doing this kind of stuff there, so you're more likely to get a decent
answer.

HTH. Upayavira

On Sat, 19 Jul 2003 12:04:08 -0700 (PDT), Steven Cummings
[EMAIL PROTECTED] said:
 I'm not *that* bad a coder, I can make recursive calls in code! But I'm
 wondering how to ensure that a new continuation is created so that I can
 run a
 sub- formwizard with it's own continuation and then use the old
 continuation
 id to return from it. While I know how continuations are continued from
 the
 flow examples, I don't know exactly how to break back into an xmlforms
 continuation with a particular id. It is built up a little more, at a
 high-level. And I don't immediately have any pipeline that takes a
 continuation
 id like from the flow examples for the form and form-wizard frameworks.
 That is
 my wondering.
 
 /S
 --- Upayavira [EMAIL PROTECTED] wrote:
  Steven,
  
  On Fri, 18 Jul 2003 19:33:16 -0700 (PDT), Steven Cummings
  [EMAIL PROTECTED] said:
   Antonio,
   
   But how do you make a recursive call within the xmlform functionality? Do
   you call it within the javascript or from a page to the desired pipeline?
  
  I'm an extreme newbie here, but:
  
  You do it the same as you would with any programming language:
  
  var continueRecursing = true;
  
  function foo() {
if (continueRecursing) {
  sendPageAndWait(...);
  foo();
}
  }
  
  Or, if you're using jxforms (flow enabled xmlforms), then you'll use
  sendForm() instead of sendPageAndWait().
  
  Hope that helps a bit.
  
  Regards,
  
  Upayavira
   --- Antonio Gallardo [EMAIL PROTECTED] wrote:
Steven Cummings dijo:
 Hello all,

 I've got kind of a hair-brained question here, forgive me if it is not
 completely clear. I'm having a hard time thinking of how to create a
 flow and forms for editing a complex, highly nested, and even
 recursively defined bean.

 Let's say I have a bean class A with property of class B. B also has an
 optional property of type B.

 My best thinking is that when I come to those items in the xmlform, I
 will display a link to another flow, so that a sub-form is navigated
 to. Cramming everything into one form is, of course, not a very good
 option. Anyway, the theoretical solution presents me with two problems:

 1. Could the new form and continuation be passed the old continuation,
 and access objects from the old flow?

I am not sure, but maybe a recursion of the same function would work
  here.

Please comments.

 2. Could the new flow return to continue the old continuation once it
 was done?

See above.


 I might possibly go as much as two or three continuations deeps.

If the recursion can work here, the answer is yes. :)

 Remember that each is pretty much an XMLForm wizard implementation, so
 I'm not writing any other low-level flow code except that to control
  the
 form wizard much like in the xmlform samples.

 I haven't looked into woody that much yet, so if I'm missing something
 easier there, let me know. If anybody has any good pointers or general
 suggestions I would appreciate it! Surely someone else has had to deel
 with beans that weren't skin-deep and contained further complex
  types.

 TIA
 /S

 __
 Do you Yahoo!?
 SBC Yahoo! DSL - Now only $29.95 per month!
 http://sbc.yahoo.com

 -
  To
 unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

   
   
   __
   Do you Yahoo!?
   SBC Yahoo! DSL - Now only $29.95 per month!
   http://sbc.yahoo.com
   
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
   
   
  
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
  
 
 
 __
 Do you Yahoo!?
 SBC Yahoo! DSL - Now only $29.95 per month!
 http://sbc.yahoo.com
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [2.1m2][xmlforms][wizard-flow] nested model-beans and continuations

2003-07-19 Thread Steven Cummings
No you didn't! I just don't think I explained my intentions well enough at
first (and the reponse seemed way too obvious at first). No biggy. I'll try the
dev'ers now. Thanks for the reponses!

/S
--- Upayavira [EMAIL PROTECTED] wrote:
 Steven,
 
 Hope I didn't offend your programming sensibilities ;-)
 
 I'd recommend asking this on the developer list. There are more people
 doing this kind of stuff there, so you're more likely to get a decent
 answer.
 
 HTH. Upayavira
 
 On Sat, 19 Jul 2003 12:04:08 -0700 (PDT), Steven Cummings
 [EMAIL PROTECTED] said:
  I'm not *that* bad a coder, I can make recursive calls in code! But I'm
  wondering how to ensure that a new continuation is created so that I can
  run a
  sub- formwizard with it's own continuation and then use the old
  continuation
  id to return from it. While I know how continuations are continued from
  the
  flow examples, I don't know exactly how to break back into an xmlforms
  continuation with a particular id. It is built up a little more, at a
  high-level. And I don't immediately have any pipeline that takes a
  continuation
  id like from the flow examples for the form and form-wizard frameworks.
  That is
  my wondering.
  
  /S
  --- Upayavira [EMAIL PROTECTED] wrote:
   Steven,
   
   On Fri, 18 Jul 2003 19:33:16 -0700 (PDT), Steven Cummings
   [EMAIL PROTECTED] said:
Antonio,

But how do you make a recursive call within the xmlform functionality?
 Do
you call it within the javascript or from a page to the desired
 pipeline?
   
   I'm an extreme newbie here, but:
   
   You do it the same as you would with any programming language:
   
   var continueRecursing = true;
   
   function foo() {
 if (continueRecursing) {
   sendPageAndWait(...);
   foo();
 }
   }
   
   Or, if you're using jxforms (flow enabled xmlforms), then you'll use
   sendForm() instead of sendPageAndWait().
   
   Hope that helps a bit.
   
   Regards,
   
   Upayavira
--- Antonio Gallardo [EMAIL PROTECTED] wrote:
 Steven Cummings dijo:
  Hello all,
 
  I've got kind of a hair-brained question here, forgive me if it is
 not
  completely clear. I'm having a hard time thinking of how to create
 a
  flow and forms for editing a complex, highly nested, and even
  recursively defined bean.
 
  Let's say I have a bean class A with property of class B. B also
 has an
  optional property of type B.
 
  My best thinking is that when I come to those items in the xmlform,
 I
  will display a link to another flow, so that a sub-form is
 navigated
  to. Cramming everything into one form is, of course, not a very
 good
  option. Anyway, the theoretical solution presents me with two
 problems:
 
  1. Could the new form and continuation be passed the old
 continuation,
  and access objects from the old flow?
 
 I am not sure, but maybe a recursion of the same function would work
   here.
 
 Please comments.
 
  2. Could the new flow return to continue the old continuation once
 it
  was done?
 
 See above.
 
 
  I might possibly go as much as two or three continuations deeps.
 
 If the recursion can work here, the answer is yes. :)
 
  Remember that each is pretty much an XMLForm wizard implementation,
 so
  I'm not writing any other low-level flow code except that to
 control
   the
  form wizard much like in the xmlform samples.
 
  I haven't looked into woody that much yet, so if I'm missing
 something
  easier there, let me know. If anybody has any good pointers or
 general
  suggestions I would appreciate it! Surely someone else has had to
 deel
  with beans that weren't skin-deep and contained further complex
   types.
 
  TIA
  /S
 
  __
  Do you Yahoo!?
  SBC Yahoo! DSL - Now only $29.95 per month!
  http://sbc.yahoo.com
 
 
 -
   To
  unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


__
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


   
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
   
  
  
  __
  Do you Yahoo!?
  SBC Yahoo! DSL - Now only $29.95 per 

[2.1m2][xmlforms][wizard-flow] nested model-beans and continuations

2003-07-18 Thread Steven Cummings
Hello all,

I've got kind of a hair-brained question here, forgive me if it is not
completely clear. I'm having a hard time thinking of how to create a flow and
forms for editing a complex, highly nested, and even recursively defined bean.

Let's say I have a bean class A with property of class B. B also has an
optional property of type B.

My best thinking is that when I come to those items in the xmlform, I will
display a link to another flow, so that a sub-form is navigated to. Cramming
everything into one form is, of course, not a very good option. Anyway, the
theoretical solution presents me with two problems:

1. Could the new form and continuation be passed the old continuation, and
access objects from the old flow?
2. Could the new flow return to continue the old continuation once it was done?

I might possibly go as much as two or three continuations deeps. Remember that
each is pretty much an XMLForm wizard implementation, so I'm not writing any
other low-level flow code except that to control the form wizard much like in
the xmlform samples.

I haven't looked into woody that much yet, so if I'm missing something easier
there, let me know. If anybody has any good pointers or general suggestions I
would appreciate it! Surely someone else has had to deel with beans that
weren't skin-deep and contained further complex types.

TIA
/S

__
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [2.1m2][xmlforms][wizard-flow] nested model-beans and continuations

2003-07-18 Thread Antonio Gallardo
Steven Cummings dijo:
 Hello all,

 I've got kind of a hair-brained question here, forgive me if it is not
 completely clear. I'm having a hard time thinking of how to create a
 flow and forms for editing a complex, highly nested, and even
 recursively defined bean.

 Let's say I have a bean class A with property of class B. B also has an
 optional property of type B.

 My best thinking is that when I come to those items in the xmlform, I
 will display a link to another flow, so that a sub-form is navigated
 to. Cramming everything into one form is, of course, not a very good
 option. Anyway, the theoretical solution presents me with two problems:

 1. Could the new form and continuation be passed the old continuation,
 and access objects from the old flow?

I am not sure, but maybe a recursion of the same function would work here.

Please comments.

 2. Could the new flow return to continue the old continuation once it
 was done?

See above.


 I might possibly go as much as two or three continuations deeps.

If the recursion can work here, the answer is yes. :)

 Remember that each is pretty much an XMLForm wizard implementation, so
 I'm not writing any other low-level flow code except that to control the
 form wizard much like in the xmlform samples.

 I haven't looked into woody that much yet, so if I'm missing something
 easier there, let me know. If anybody has any good pointers or general
 suggestions I would appreciate it! Surely someone else has had to deel
 with beans that weren't skin-deep and contained further complex types.

 TIA
 /S

 __
 Do you Yahoo!?
 SBC Yahoo! DSL - Now only $29.95 per month!
 http://sbc.yahoo.com

 - To
 unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [2.1m2][xmlforms][wizard-flow] nested model-beans and continuations

2003-07-18 Thread Steven Cummings
Antonio,

But how do you make a recursive call within the xmlform functionality? Do you
call it within the javascript or from a page to the desired pipeline? Thanks.

Steven

--- Antonio Gallardo [EMAIL PROTECTED] wrote:
 Steven Cummings dijo:
  Hello all,
 
  I've got kind of a hair-brained question here, forgive me if it is not
  completely clear. I'm having a hard time thinking of how to create a
  flow and forms for editing a complex, highly nested, and even
  recursively defined bean.
 
  Let's say I have a bean class A with property of class B. B also has an
  optional property of type B.
 
  My best thinking is that when I come to those items in the xmlform, I
  will display a link to another flow, so that a sub-form is navigated
  to. Cramming everything into one form is, of course, not a very good
  option. Anyway, the theoretical solution presents me with two problems:
 
  1. Could the new form and continuation be passed the old continuation,
  and access objects from the old flow?
 
 I am not sure, but maybe a recursion of the same function would work here.
 
 Please comments.
 
  2. Could the new flow return to continue the old continuation once it
  was done?
 
 See above.
 
 
  I might possibly go as much as two or three continuations deeps.
 
 If the recursion can work here, the answer is yes. :)
 
  Remember that each is pretty much an XMLForm wizard implementation, so
  I'm not writing any other low-level flow code except that to control the
  form wizard much like in the xmlform samples.
 
  I haven't looked into woody that much yet, so if I'm missing something
  easier there, let me know. If anybody has any good pointers or general
  suggestions I would appreciate it! Surely someone else has had to deel
  with beans that weren't skin-deep and contained further complex types.
 
  TIA
  /S
 
  __
  Do you Yahoo!?
  SBC Yahoo! DSL - Now only $29.95 per month!
  http://sbc.yahoo.com
 
  - To
  unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


__
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]