Just one small point...
In all my (admittedly brief compared to some) travels through workflow
land, I've never had a workflow that was specifically tree. They all
end up forming a graph at some point.
One could argue that you can just have jump points from one branch to
another, but in my ex
In the ActionServlet...
javax.servlet.include.path_info
Anyone know what this is or where it comes
from?
// For prefix matching, we want to match on
the path info (if any) path =(String)
request.getAttribute("javax.servlet.include.path_info");
Since my needs are for web container persistence, let me make a suggestion
in that area.
An object called WorkflowPath could be created with configurable values
sucked up from a file. The values could be some kind of tree, like a
decision/process tree. The WorkflowPath object would be stored in
Thats fine. You would like the state of the workflow saved in spite of a
server failure. The truth is we should figure out both situations anyway
for both types of requirements:
1) storing state in a database
2) storing state in the web container
- Original Message -
From: "Geir Magnusso
Jonathan Asbell wrote:
>
> Persistent storage is an option too. I was hoping, however to limit calls
> through the enterprise parts and database.
Why?
> You could argue that it belongs
> there because the database is the central location holding all data and
> information and therefore should
Hello -
I have been using the struts tablibs for a few weeks now and
integrated them with my application by adding taglib declarations in
my web.xml file to point to the struts tld files. However, I was
reading the installation notes again and noticed that another way to
install struts is to sim
Persistent storage is an option too. I was hoping, however to limit calls
through the enterprise parts and database. You could argue that it belongs
there because the database is the central location holding all data and
information and therefore should hold workflow info, especially in the face
Can I ask why you don't go with persistant storage, like a rdbms? I
have been thinking about workflow recently as well, although not
specifically w/in struts, and I believe that for the general solution,
where someone can come back a long time later and resume, or be it an
automated process, pers
Hello all. We were talking about workflow a
few weeks ago and the conversation dissipated. I am trying to open it up
again because I have found a need for more scopes, and a need to implement these
new scopes in the next few months. I am interested specifically in
how it can be implemente
comments below...
- Original Message -
> From: "Jonathan" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, June 20, 2001 12:55 PM
> Subject: Re: server-side, java-based validation rules for struts..
>
> Hello Levi.
> I read your comment yesterday and went and read about co
Another tag works well for me :-) - we have our own customised versions of
struts tags to do this.
I submitted a Bugzilla to make tags more "granular" so that individual bits
of behaviour (like generating the name )could be overriden. Unfortunately
:-( it didn't make it into Struts 1.0 and I thi
Hi All,
Thanks for the replies, I now feel less lost in the ether :)
You each brought up excellent points which I believe are address-able.
Ultimately, I guess a working example sounds best for exploring these
ideas.. I'll try to post something back over the weekend on this.
Until then, I'll t
I hear what you are saying Niall, but again, I'd sooner introduce a new tag
like 'html2' before I'd change existing tags/property names - especially now
that struts 1.0 is out and feels "more formally defined" if you know what I
mean. Too bad there was no way to label something 'depcrecated' in a
Incident Information:-
Originator:"Johan Compagner" <[EMAIL PROTECTED]>
Recipients:<[EMAIL PROTECTED]>
Subject: Re: cvs commit: jakarta-struts/src/share/org/apache/struts/util
RequestUtils.java
Message from "Johan Compagner" <[EMAIL PROTECTED]> was NOT delivered,
because it contained ba
Jeff,
You might be right, but the question is "is it the right thing to do?" - if
it is, then it would be a shame to have to code "indexed='true'" from now to
eternity - perhaps there could be a way of specifying the default behaviour
in the struts-config.
Niall
> -Original Message-
> F
+1
David Winterfeldt wrote:
> I don't think there would be anything wrong with your
> idea, but I think it is a little more flexible keeping
> the validation separate from the ActionForm. I
> started working on a validation framework, but I put
> the info in an xml file. I would rather change
I don't think there would be anything wrong with your
idea, but I think it is a little more flexible keeping
the validation separate from the ActionForm. I
started working on a validation framework, but I put
the info in an xml file. I would rather change a
value in an xml file than having to re
Hello Levi.
I read you rcomment yesterday and went and read about constrained properties
and bound properties in section 7.4 of the java beans spec link you sent. I
think people didnt answer because you didnt speak enough about what you are
suggesting in the context of what has already been devel
I'm guessing my aforementioned ideas on validation fall into one of the
following categories:
1. its was a really bad idea, not worth commenting or elaborating on
2. i didn't provide a clearly articulated idea to review
3. they're fine and everyone's really busy, and i'm impatient
I'll a
> -Original Message-
> From: sravan mandala [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, June 08, 2001 10:04 AM
> To: [EMAIL PROTECTED]
> Subject: [EMAIL PROTECTED]
>
>
> Please unsubscribe from the list
>
> Thanks
>
> _
Niall,
Your approach is simpler. However, I believe a lot of legacy code would
break if that kind of change were to be made. I think a separate property
name is warranted here.
- jeff
- Original Message -
From: "Niall Pemberton" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesd
Title: Unsubscribe me...
Please unsubscribe me from this list.
Sachin Mapara.
Trigyn Technologies Ltd.
Tel :- 518 86 86 (O) Ext.- 537
95251 - 44 10 39 (R)
Hello Cedric,
Thank you, the solution there is.
Wednesday, June 20, 2001, 1:26:13 PM, you wrote:
CD> What you would like to do is to be able to use template "parameters"
CD> in logic tags.
CD> I have another solution to this problem : add a tag importing template
CD> "parameter/attribute"
What you would like to do is to be able to use template "parameters"
in logic tags.
I have another solution to this problem : add a tag importing template
"parameter/attribute" in jsp scope (page, request, ...), as a bean.
Like this, you can use logic tag with the imported bean (which in
rea
If any 'assumptions' were made during conversion then you could (via a
settable option) return the user to the orignal page with a message asking
them to check the converted values. An obvious example is with dates:
User enters: 1/6/75
System converts to : 01/06/1975
User is shown this, and ve
25 matches
Mail list logo
