Hi Samisa, This was a misunderstanding. There are couple of e-mails on the same, :). I read the issue list first and resolved them, since the issue itself did not have any explanation. But I understood what you were expecting going through the e-mails. I already mentioned this on the other thread, "Why not promote verify the checklist in LC?" and the two issues are already reopened and I have added descriptions. However, some issues reported are actually duplicates, and I have referred to those and resolved.
There is a sample on using forEvent for validation ( http://docs.wso2.org/wiki/display/Governance450/Issue+Tracker+Sample), but this is not linked to the configuration model document - that's a miss - I agree. And, we need samples on using forEvent for checkitems, and even more samples on various aspects. Will work on reporting the missing bits. Thanks, Senaka. On Mon, Oct 8, 2012 at 11:11 AM, Samisa Abeysinghe <[email protected]> wrote: > It seems that you have rushed too much into resolving some issues, rather > than getting to the bottom of the problem. > > It is not at all good to day that we have docs on the stuff, if the user > cannot locate them. > > For e.g. I raised the docs issues on RXT and LC after looking into the > docs that Janaka sent, and there were no link or mention whatsoever on the > info on what I was looking for as a user. If I look at > http://docs.wso2.org/wiki/display/Governance450/Lifecycle+Configuration+Model, > there is no single sample on how to use forEvent, on item element, never > mentions it is about "state translation" rather than "transitions". So > technically, you cannot resolve this issue yet. It needs loads of fixing. > > I also raised a bunch along these lines in the release cycle, and I > noticed that you have resolved those with "won't fix". The issues need to > be treated holistically, rather than in isolation. > More examples on being holistic is in the original question, if I have > schema, and I was told yes, for me to figure, as a user, that required is > not behaving the Boolean way, it would have been nice, if it was checked > right, before I was pushed into the depth as a user to figure out myself > where it is broken. > > I think it is quite useless to have the feature with all the functionality > in place, if the users cannot figure how to use them. So it is good to take > time and see if the issues are fixed right. > > The same on the UI, I raised no issues, whatsoever on new UIs. Plus, no > matter who has done the policy decisions on what to do or not, if the > current UI set does not work for users, the bottom line is, you got to fix > them - meet the user needs, rather than keeping to policies. > > What I did was an end to end scenario, involving RXT plus LC. I could not > go much distance, without asking many questions or raising a bunch of > issues. That is bad, so take it slow! > > > On Mon, Oct 8, 2012 at 10:39 AM, Senaka Fernando <[email protected]> wrote: > >> Hi Samisa, >> >> Thanks. I reviewed the list of issues you created. There are few >> different types. >> >> 1. Clear misses in functionality - I mean we don't have those, or never >> tested those and missed totally. >> >> 2. Already reported issues (like support for date field). I resolved >> these as duplicate with reference to the old. >> >> 3. Issues due to not having the proper thing. Like the RXT UI, which is >> still not done. There is a separate issue on creating an RXT UI like the LC >> UI, to which I pointed your issues to. >> >> 4. Issues in documentation. The docs are complete in terms of content, >> but searching and finding the content is a real PITA. We need to focus on >> getting that right. Isuru and I fixed a lot during the last release, but we >> have gaps. RXT docs and LC docs - I mean the config language - are good >> examples, but there are few others - I actually didn't realize the >> intention of some of the issues that were reported, since it said missing >> docs but nothing about the navigation - hence I resolved. I will read and >> reopen/create new ones as needed. >> >> 5. Things that we are not planning to do. We are not accepting major new >> features for the Management Console as per discussion with Sanjiva, Paul, >> Isabelle et al if they better fit in one of the role-based UIs that we are >> developing. The G-Reg Management Console will become a stable piece and >> we'll be focusing on user oriented UIs in the upcoming releases. >> >> Thanks, >> Senaka. >> >> On Mon, Oct 8, 2012 at 8:55 AM, Samisa Abeysinghe <[email protected]>wrote: >> >>> I have raised a bunch of Jira based on the stuff I encountered with my >>> Weekend project. >>> >>> I will send a separate note on the scenarios and what I was looking for >>> >>> >>> On Mon, Oct 8, 2012 at 7:23 AM, Senaka Fernando <[email protected]> wrote: >>> >>>> Hi Samisa, >>>> >>>> Harshana was talking about EMF, which I understood as a graphical way >>>> to do this in Eclipse, provided that we have a proper schema. >>>> >>>> From the schema-side of the story, I already created an issue, [1]. We >>>> have not been doing very detailed use-case-vise testing during chunk1. But, >>>> ever since we have gathered and fixed many such issues. I believe that we >>>> can fixes all or most of these issues in the 4.5.x series. >>>> >>>> [1] https://wso2.org/jira/browse/REGISTRY-1362 >>>> >>>> Thanks, >>>> Senaka. >>>> >>>> >>>> On Mon, Oct 8, 2012 at 6:22 AM, Samisa Abeysinghe <[email protected]>wrote: >>>> >>>>> >>>>> >>>>> On Fri, Oct 5, 2012 at 11:58 PM, Sanjiva Weerawarana <[email protected] >>>>> > wrote: >>>>> >>>>>> Samisa if there's a schema then we can use the Eclipse editor to get >>>>>> content assist etc. to help edit the RXT files. >>>>> >>>>> >>>>> Yes, but still I have to edit XML - which I did, and which is not that >>>>> nice, when you are alien to the syntax and semantics. >>>>> Also, I happened to few trivial errors like using '&' in descriptions, >>>>> that it took time for me to figure. When I said a tool, I hope those would >>>>> be covered. >>>>> >>>>> Plus, I found gaps in the schema definition, which makes it almost >>>>> impossible to live with the schema given. It seems as if the schema is had >>>>> written, and not in sync with the Java code that is evaluating the RXT >>>>> that >>>>> I am providing. I had to do quite a bit of trial and error to figure what >>>>> the right syntax is. So we need to do a proper language test on this >>>>> feature. And that has nothing to do with tooling. >>>>> >>>>> >>>>>> >>>>>> >>>>>> On Fri, Oct 5, 2012 at 10:13 AM, Samisa Abeysinghe >>>>>> <[email protected]>wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> On Fri, Oct 5, 2012 at 10:10 AM, Senaka Fernando <[email protected]>wrote: >>>>>>> >>>>>>>> Hi Samisa, >>>>>>>> >>>>>>>> Harshana and the team is already working on getting the tool side >>>>>>>> of it sorted out. Also, we have a road-map item to have a add-RXT page >>>>>>>> like >>>>>>>> the add-LC page. >>>>>>>> >>>>>>> >>>>>>> Unfortunately, the story is half baked without provision of these >>>>>>> tooling and supporting aspects. >>>>>>> >>>>>>> I wonder what the priorities are on the road-map aspects - in the >>>>>>> global optima, not in the local optima. >>>>>>> >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Senaka. >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Oct 5, 2012 at 9:56 AM, Samisa Abeysinghe >>>>>>>> <[email protected]>wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Fri, Oct 5, 2012 at 9:43 AM, Senaka Fernando >>>>>>>>> <[email protected]>wrote: >>>>>>>>> >>>>>>>>>> Hi all, >>>>>>>>>> >>>>>>>>>> I think we should improve the docs to have this as a side note or >>>>>>>>>> even a sample (as to how to use the XSD to generate LC or RXT). I >>>>>>>>>> will work >>>>>>>>>> on getting this done. >>>>>>>>>> >>>>>>>>> >>>>>>>>> Well, actually, it is neither the doc nor the schema that we >>>>>>>>> should have, as that is tech detail. As a user, I would not care as >>>>>>>>> long as >>>>>>>>> I have a tool to easily define RXTs. That would solve lot of >>>>>>>>> problems. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> Senaka. >>>>>>>>>> >>>>>>>>>> On Fri, Oct 5, 2012 at 9:26 AM, Eranda Sooriyabandara < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> Hi Samisa >>>>>>>>>>> >>>>>>>>>>> On Fri, Oct 5, 2012 at 9:19 AM, Samisa Abeysinghe < >>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>> >>>>>>>>>>>> Do we have schema defined for $subject? >>>>>>>>>>>> >>>>>>>>>>>> I am trying to see how I could do the least work and generate >>>>>>>>>>>> the RXT that I want, plus the LC for that. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Yes, they are defined. You can find them in >>>>>>>>>>> CARBON_HOME/repository/resource/rxt.xsd >>>>>>>>>>> and CARBON_HOME/repository/resource/lifecycle-config.xsd. >>>>>>>>>>> >>>>>>>>>>> thanks >>>>>>>>>>> Eranda >>>>>>>>>>> * >>>>>>>>>>> * >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Dev mailing list >>>>>>>>>>> [email protected] >>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> *Senaka Fernando* >>>>>>>>>> Member - Integration Technologies Management Committee; >>>>>>>>>> Technical Lead; WSO2 Inc.; http://wso2.com* >>>>>>>>>> Member; Apache Software Foundation; http://apache.org >>>>>>>>>> >>>>>>>>>> E-mail: senaka AT wso2.com >>>>>>>>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >>>>>>>>>> Linked-In: http://linkedin.com/in/senakafernando >>>>>>>>>> >>>>>>>>>> *Lean . Enterprise . Middleware >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>> Samisa... >>>>>>>>> >>>>>>>>> Samisa Abeysinghe >>>>>>>>> VP Engineering >>>>>>>>> WSO2 Inc. >>>>>>>>> http://wso2.com >>>>>>>>> http://wso2.org >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> *Senaka Fernando* >>>>>>>> Member - Integration Technologies Management Committee; >>>>>>>> Technical Lead; WSO2 Inc.; http://wso2.com* >>>>>>>> Member; Apache Software Foundation; http://apache.org >>>>>>>> >>>>>>>> E-mail: senaka AT wso2.com >>>>>>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >>>>>>>> Linked-In: http://linkedin.com/in/senakafernando >>>>>>>> >>>>>>>> *Lean . Enterprise . Middleware >>>>>>>> >>>>>>>> Thanks, >>>>>>> Samisa... >>>>>>> >>>>>>> Samisa Abeysinghe >>>>>>> VP Engineering >>>>>>> WSO2 Inc. >>>>>>> http://wso2.com >>>>>>> http://wso2.org >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Dev mailing list >>>>>>> [email protected] >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Sanjiva Weerawarana, Ph.D. >>>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ >>>>>> email: [email protected]; phone: +94 11 763 9614; cell: +94 77 787 >>>>>> 6880 | +1 650 265 8311 >>>>>> blog: http://sanjiva.weerawarana.org/ >>>>>> >>>>>> >>>>>> Lean . Enterprise . Middleware >>>>>> >>>>> Thanks, >>>>> Samisa... >>>>> >>>>> Samisa Abeysinghe >>>>> VP Engineering >>>>> WSO2 Inc. >>>>> http://wso2.com >>>>> http://wso2.org >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Senaka Fernando* >>>> Member - Integration Technologies Management Committee; >>>> Technical Lead; WSO2 Inc.; http://wso2.com* >>>> Member; Apache Software Foundation; http://apache.org >>>> >>>> E-mail: senaka AT wso2.com >>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >>>> Linked-In: http://linkedin.com/in/senakafernando >>>> >>>> *Lean . Enterprise . Middleware >>>> >>>> Thanks, >>> Samisa... >>> >>> Samisa Abeysinghe >>> VP Engineering >>> WSO2 Inc. >>> http://wso2.com >>> http://wso2.org >>> >>> >>> >> >> >> -- >> *Senaka Fernando* >> Member - Integration Technologies Management Committee; >> Technical Lead; WSO2 Inc.; http://wso2.com* >> Member; Apache Software Foundation; http://apache.org >> >> E-mail: senaka AT wso2.com >> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >> Linked-In: http://linkedin.com/in/senakafernando >> >> *Lean . Enterprise . Middleware >> >> Thanks, > Samisa... > > Samisa Abeysinghe > VP Engineering > WSO2 Inc. > http://wso2.com > http://wso2.org > > > -- *Senaka Fernando* Member - Integration Technologies Management Committee; Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
