[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[jwt-dev] AW: default values in conf-file
|
Hi Sachin,
no, simply applying the patch which only changes the
PropertyAspectFactory-class should solve the bug in my opinion. Do you still
have the same experience with the default values or is there no something
completely different?
Could you please describe your experienced behavior on the bug itself, so we
can discuss further changes there?
Best regards,
Florian
-----Ursprüngliche Nachricht-----
Von: Sachin N. Chavan [mailto:Sachin.Chavan@xxxxxxxxxx]
Gesendet: Donnerstag, 7. Januar 2010 11:37
An: Florian Lautenbacher
Betreff: RE: default values in conf-file
Hi Florian,
Sorry for very late reply. But I was busy in my project work.
I have tested the patch which you have sent to me but it doesn't work for
me.
I have changed PropertyAspectFactory.java file in
org.eclipse.jwt.we.conf.property.model_0.6.0.v20090617-0420-R.jar with the
new code.
Is there anything else which I have to change other than above file?
Thanks and Regards
Sachin
-----Original Message-----
From: Florian Lautenbacher
[mailto:florian.lautenbacher@xxxxxxxxxxxxxxxxxxxxxxxxxx]
Sent: Thursday, December 03, 2009 5:22 PM
To: Sachin N. Chavan
Cc: 'Java Workflow Toolbox'
Subject: AW: default values in conf-file
Hi Sachin,
could you please have a look at bug #296319
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=296319) where you can find a
patch that should solve the issue described in your email below. Please let
me know whether this solves your problems or whether I missed anything.
Thanks and best regards,
Florian
-----Ursprüngliche Nachricht-----
Von: Sachin N. Chavan [mailto:Sachin.Chavan@xxxxxxxxxx]
Gesendet: Freitag, 6. November 2009 15:45
An: Florian Lautenbacher; 'Java Workflow Toolbox'
Betreff: RE: jwt-dev Digest, Vol 33, Issue 8
Thanks Florian / Marc for your prompt reply.
We are able to create drop-down boxes now for the aspects.
However we are facing some problem with the conf file.
We have created static aspects and have assigned some default values for the
properties.
But if the user doesn't modify the default values, then those default values
do not get stored in the conf file.
Is there any way that we can get the default values of the aspects in the
conf file?
Is there any configuration setting which we are missing here?
Thanks and Regards
Sachin
-----Original Message-----
From: Florian Lautenbacher
[mailto:florian.lautenbacher@xxxxxxxxxxxxxxxxxxxxxxxxxx]
Sent: Monday, November 02, 2009 6:57 PM
To: Sachin N. Chavan; 'Java Workflow Toolbox'
Subject: AW: jwt-dev Digest, Vol 33, Issue 8
Hi Sachin, hi Marc,
last week Marc and I developed a sample that should fit the problem you
described here:
>>For static aspects, we are facing following problems,
>>Is there a way to add a dropdown box for any static aspect property
values?
>>For e.g. I have to display/edit an "Employee Status" static aspect
property which can have following values >>"Active", "Retired",
"Terminated", "Inactive" etc.
For our presentation we developed an aspect that includes a predefined
enumeration (for logging) such as "WARN", "SEVERE", "INFO". Marc has this
code on his computer and only needs to upload it as a new sample on the CVS.
As part of this sample, we have also shown how a new property tab can be
created which only contains the dynamic properties one is interested in. So,
you could easily take your 10x5 properties and divide them into several
"classes" and for each of these "classes" you create your own property tab.
Marc should be able to answer you some more questions about the sample.
Best regards,
Florian
-----Ursprüngliche Nachricht-----
Von: Sachin N. Chavan [mailto:Sachin.Chavan@xxxxxxxxxx]
Gesendet: Montag, 2. November 2009 14:14
An: 'Java Workflow Toolbox'
Cc: Florian Lautenbacher
Betreff: FW: jwt-dev Digest, Vol 33, Issue 8
Hi Marc/Florian,
Thanks for your reply.
The dropdown change listener problem is not directly related to aspects.
The org.eclipse.jwt.we.changeListener works for the "Name" or text property
of the Action Node. But when we were trying a change listener on "Executed
by Application" property of Action which is "Standard" property(dropdown
box) it did not work.
We have already tried the static and dynamic aspects for extending the
"Action" properties as per your email and examples on the wiki(JWT Metamodel
extension).
For the dynamic aspects, we are facing following problems,
=> Default Values (which are not changed by the user) are not getting
populated in the conf file.
=> Is there any way to "hide" the dynamic aspects on the right click of
Action ("New Child" menu)? This is because if there are a lot of dynamic
aspects, then the display becomes a bit ugly.
We were trying to create dynamic aspects as we have some 10 "standard" nodes
which have a set of 5 properties each. The value of these properties can be
changed by the user. However since these are "standard" set of nodes, we
want to keep the property set as flexible as possible by avoiding code
(static aspects).
For static aspects, we are facing following problems,
Is there a way to add a dropdown box for any static aspect property values?
For e.g. I have to display/edit an "Employee Status" static aspect property
which can have following values "Active", "Retired", "Terminated",
"Inactive" etc.
Thanks
Sachin
Hi Sachin, all
Have a look at http://wiki.eclipse.org/JWT_Metamodel_Extension and all
aspect themed plugins in the source (under we/jwt-we-plugins : epcview,
staticaspect...).
Err... as said on this wiki page, "multiple" means "more than one can be
created" on a given node and not that it will not share the value, which
it never does ! That said, your use case is exactly about aspects.
Is your dropdown change listener problem related to aspects or not ?
About auto hide of properties... I'm wondering whether it is rather a
UI, EMF or Custom Property question.
Indeed, JWT Aspects allow to add features without hacking the decorated
model, but in order to customize the behaviour (events and listeners) or
the display (in the property sheet using the emf.edit framework) you
actually have to customize the code generated by EMF from your
ecore+genmodel. Which implies you have to be in the 3rd case "For
developers : developing complex additional model extensions using
EMF-generated code" described at
http://wiki.eclipse.org/JWT_Metamodel_Extension , exemplified by the
staticaspect sample, rather than Custom Properties (which are the 1rst
case on the page). Then you can do anything.
How do custom properties work ? Well, thanks to EMF ! More precisely :
Custom Properties are shown in their own property tab by a modified
version of the standard EMF property sheet that you can find in
jwt-we-conf-model.we , that uses jwt-conf-property-model.edit's
PropertyPropertyDescriptor to display each property.
So by setting in JWT your own property tab, you could display in it your
own custom property sheet. This one could either be a copy of
jwt-we-conf-model.we's that would differ only in that it would use your
own MyPropertyPropertyDescriptor, whose getLabel() would return "" and
createPropertyEditor() would return null when you don't want them. Or
you could completely rewrite your custom property sheet with code that
is specific to your (aspected) model, so it would look more like Forms UI.
It is of great importance to understand that Custom Properties are a
nice way to get introduced to Aspects and get custom features on one's
model, but once you want custom behaviour or display, you have to define
your own Aspects model and code your needs the "classic" EMF way...
Though you can take ideas from the Custom Property plugin to make your
own aspect of course !
Another thing to try could be not at the UI level, but at the EMF.edit
level, and write your own PropertyItemProvider that would sometimes NOT
add the ItemPropertyDescriptor to the list, hoping it would therefore
not display the custom property. Maybe easier to try, but very limited
in possible further behaviours.
Finally, if there is a real need of being able to code when to display
properties and when not, maybe we could add an extension point that
would do the trick. However, that would not solve your other (?) custom
EMF needs, and right now I don't know when I'd have the time for that.
Regards,
Marc
MASTEK LTD.
Mastek is in NASSCOM's 'India Top 20' Software Service Exporters List.
In the US, we're called MAJESCOMASTEK
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Opinions expressed in this e-mail are those of the individual and not that
of Mastek Limited, unless specifically indicated to that effect. Mastek
Limited does not accept any responsibility or liability for it. This e-mail
and attachments (if any) transmitted with it are confidential and/or
privileged and solely for the use of the intended person or entity to which
it is addressed. Any review, re-transmission, dissemination or other use of
or taking of any action in reliance upon this information by persons or
entities other than the intended recipient is prohibited. This e-mail and
its attachments have been scanned for the presence of computer viruses. It
is the responsibility of the recipient to run the virus check on e-mails and
attachments before opening them. If you have received this e-mail in error,
kindly delete this e-mail from desktop and server.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
MASTEK LTD.
Mastek is in NASSCOM's 'India Top 20' Software Service Exporters List.
In the US, we're called MAJESCOMASTEK
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Opinions expressed in this e-mail are those of the individual and not that
of Mastek Limited, unless specifically indicated to that effect. Mastek
Limited does not accept any responsibility or liability for it. This e-mail
and attachments (if any) transmitted with it are confidential and/or
privileged and solely for the use of the intended person or entity to which
it is addressed. Any review, re-transmission, dissemination or other use of
or taking of any action in reliance upon this information by persons or
entities other than the intended recipient is prohibited. This e-mail and
its attachments have been scanned for the presence of computer viruses. It
is the responsibility of the recipient to run the virus check on e-mails and
attachments before opening them. If you have received this e-mail in error,
kindly delete this e-mail from desktop and server.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
MASTEK LTD.
Mastek is in NASSCOM's 'India Top 20' Software Service Exporters List.
In the US, we're called MAJESCOMASTEK
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Opinions expressed in this e-mail are those of the individual and not that
of Mastek Limited, unless specifically indicated to that effect. Mastek
Limited does not accept any responsibility or liability for it. This e-mail
and attachments (if any) transmitted with it are confidential and/or
privileged and solely for the use of the intended person or entity to which
it is addressed. Any review, re-transmission, dissemination or other use of
or taking of any action in reliance upon this information by persons or
entities other than the intended recipient is prohibited. This e-mail and
its attachments have been scanned for the presence of computer viruses. It
is the responsibility of the recipient to run the virus check on e-mails and
attachments before opening them. If you have received this e-mail in error,
kindly delete this e-mail from desktop and server.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
