Hi, We have just created an account with source forge for the workflow extension project and will be transferring the source code etc. to that account in the next couple of days. So we are just in early stages of code transfer. But regarding your question. As you said,most of the workflow information can be made available for reading atleast.And I had came across similar problem and mr.Matthias bauer had replied that it was just overlooked.As this extension was developed/modified as and when the requirements arose, it does not have all required extension points and public API. So that is the first task I am going to undertake.To see what parts of workflow can be made public and where all extension points are possible so that users can customise behaviour of the workflow. And I am planning a next release very soon ,But have no definite schedule.But I am really looking forward to getting more such ideas /requests so that the next version can be designed keeping into view all of this. And your requirement has just given me the idea for next immediate release.First thing I can do is to atleast make all Workflow state available in readOnly mode so that existing users can access use this functionality without breaking any of the workflow logic. Any ideas/suggestions are welcome. I am forwarding this mail to struts user list so that others can also contribute to this discussion. regards, Shirish. -----Original Message----- From: Ignacio Cruzado Nu�o [mailto:[EMAIL PROTECTED] Sent: Thursday, February 05, 2004 8:51 AM To: Sakhare, Shirishchandra Subject: Technical question about Struts Workflow Extension
Dear Struts Workflow Extension team: I'm Ignacio Cruzado, from Spain, computer programmer who works on Tecsidel SA (a programming company) as a computer consultant. Matthias Bauer gave me your email address in order to redirect this technical question... I hope to be writing to the right person (I'm sorry if you are not this one!). We are using "struts workflow extension" (SWE) in our development, and we would like to access the mapping information that SWE clases manage (the dependencies modelled in the struts-config.xml file). In your "Workflow scope" web page you only provide information about the Primary Workflow and it's state. I would find very valuable to have methods to access also to the dependencies of the actual state: nextState, prevState, isEndWorkflow and so on... I have been studying the source code of SWE and I have found out that this information is managed by the SWE, but not published (most methods and data structure that manage the mapping are on the private/protecthed/package scope, instead of the public scope (where I would love to found them!). Why SWE API design doesn't publish that information? Is there a technical reason for that? I'm talking about just readding (get) not establishing or manipulating (set) that information. I know that we can change the source code, in order to "open" that information, but before doing this I would like to ask you to put much more getter methods in order to ask the SWE about the workflow mapping that the developer has established, and get more information about the actual state of the workflow. Are you working on that? Is a new release of the SWE scheduled? Is it going to have new functionallity in the way I'm asking for? Best regards, Ignacio ------------------------------------------------------------------------ Ignacio Cruzado Nu�o Tecsidel S.A. Parque Tecnol�gico de Boecillo, Parcela 114 47151 Boecillo (Valladolid) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
