4:24 p.m.
Improve Decode Param support
----------------------------
Key: JBIDE-5687
URL: https://jira.jboss.org/jira/browse/JBIDE-5687
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: smooks
Affects Versions: 3.1.0.CR1
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Fix For: LATER
The editor supports decode parameter config through a properties sheet activated by
selecting the bean property. However, at the moment, the user needs to know the names of
the decode params relevant to the decoder being used to decode the data for that specific
binding.
Would make a big difference to the user (and shouldn't be too difficult to add) if the
editor automatically provided the decode params relevant to the binding. Also... make the
decode params the appear by default, when you select the properties of a bean property.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-5687) Improve Decode Param support
[
https://jira.jboss.org/jira/browse/JBIDE-5687?page=com.atlassian.jira.plu...
]
Tom Fennelly updated JBIDE-5687:
--------------------------------
Fix Version/s: 3.1.0.CR2
(was: LATER)
Priority: Blocker (was: Major)
Moving into view on CR2... can move it back out if we decide to push it.
Improve Decode Param support
----------------------------
Key: JBIDE-5687
URL: https://jira.jboss.org/jira/browse/JBIDE-5687
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: smooks
Affects Versions: 3.1.0.CR1
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Priority: Blocker
Fix For: 3.1.0.CR2
The editor supports decode parameter config through a properties sheet activated by
selecting the bean property. However, at the moment, the user needs to know the names of
the decode params relevant to the decoder being used to decode the data for that specific
binding.
Would make a big difference to the user (and shouldn't be too difficult to add) if
the editor automatically provided the decode params relevant to the binding. Also... make
the decode params the appear by default, when you select the properties of a bean
property.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:53 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5687) Improve Decode Param support
[
https://jira.jboss.org/jira/browse/JBIDE-5687?page=com.atlassian.jira.plu...
]
Tom Fennelly commented on JBIDE-5687:
-------------------------------------
Dart, I don't have time right now to draw a screen for this.
Basically, what I think would work better would be:
1. When the user right clicks for the properties on a value binding, they see the decode
params first. There are 2 tabs there at the moment, one of which is the decode params.
The decode params are not currently the default.
2. We pre-populate the list of decoders based on the decoder being used. So if e.g. the
Date Decoder is being used, we know we need to offer "format",
"locale-langauge" and "locale-country" as decode param options for the
user to configure as free text fields (for now anyway).
3. Remove the Add/Delete buttons. If we're pre-populating the list, we don't
need the add and delete options.
On #2 above, we can use the DataDecoder.Factory class to work out what the decoder should
be, if the decoder is not already configured.
Improve Decode Param support
----------------------------
Key: JBIDE-5687
URL: https://jira.jboss.org/jira/browse/JBIDE-5687
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: smooks
Affects Versions: 3.1.0.CR1
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Priority: Blocker
Fix For: 3.1.0.CR2
The editor supports decode parameter config through a properties sheet activated by
selecting the bean property. However, at the moment, the user needs to know the names of
the decode params relevant to the decoder being used to decode the data for that specific
binding.
Would make a big difference to the user (and shouldn't be too difficult to add) if
the editor automatically provided the decode params relevant to the binding. Also... make
the decode params the appear by default, when you select the properties of a bean
property.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:11 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5687) Improve Decode Param support
[
https://jira.jboss.org/jira/browse/JBIDE-5687?page=com.atlassian.jira.plu...
]
Xue Peng commented on JBIDE-5687:
---------------------------------
on #2 , how did I know the parameters' name of each Decoder ? can i get them from the
Decoder class?
Improve Decode Param support
----------------------------
Key: JBIDE-5687
URL: https://jira.jboss.org/jira/browse/JBIDE-5687
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: smooks
Affects Versions: 3.1.0.CR1
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Priority: Blocker
Fix For: 3.1.0.CR2
The editor supports decode parameter config through a properties sheet activated by
selecting the bean property. However, at the moment, the user needs to know the names of
the decode params relevant to the decoder being used to decode the data for that specific
binding.
Would make a big difference to the user (and shouldn't be too difficult to add) if
the editor automatically provided the decode params relevant to the binding. Also... make
the decode params the appear by default, when you select the properties of a bean
property.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:57 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5687) Improve Decode Param support
[
https://jira.jboss.org/jira/browse/JBIDE-5687?page=com.atlassian.jira.plu...
]
Xue Peng commented on JBIDE-5687:
---------------------------------
on #3 , if we remove the add/remove button , when user add a "Enum" decoder ,
how do user add/remove there parameters :
<jb:decodeParam name="LOW">NOT_IMPORTANT</jb:decodeParam>
<jb:decodeParam name="MEDIUM">IMPORTANT</jb:decodeParam>
<jb:decodeParam name="HIGH">VERY_IMPORTANT</jb:decodeParam>
These paramters depend the "enumType" , right?
Improve Decode Param support
----------------------------
Key: JBIDE-5687
URL: https://jira.jboss.org/jira/browse/JBIDE-5687
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: smooks
Affects Versions: 3.1.0.CR1
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Priority: Blocker
Fix For: 3.1.0.CR2
The editor supports decode parameter config through a properties sheet activated by
selecting the bean property. However, at the moment, the user needs to know the names of
the decode params relevant to the decoder being used to decode the data for that specific
binding.
Would make a big difference to the user (and shouldn't be too difficult to add) if
the editor automatically provided the decode params relevant to the binding. Also... make
the decode params the appear by default, when you select the properties of a bean
property.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:04 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5687) Improve Decode Param support
[
https://jira.jboss.org/jira/browse/JBIDE-5687?page=com.atlassian.jira.plu...
]
Tom Fennelly commented on JBIDE-5687:
-------------------------------------
Hi Dart....
Regarding #2... for now we'll need to create a static Map of some sort inside the
editor code. In future, I hope to add this info as annotations on the DataDecoder impls.
As I was thinking about it, the Map would be keyed by the DataDecoder type, with the
values being the names of the decodeParams supported by it (including default vals).
So perhaps something like....
class DecodeParamValueConfig {
String name;
String defaultVal;
}
static Map<Class<DataDecoder>, DecodeParamValueConfig[]> decodeParamsConfig =
new HashMap<Class<DataDecoder>, DecodeParamValueConfig[]>();
static {
decodeParamsConfig.put(DateDecoder.class, new DecodeParamValueConfig[] {new
DecodeParamValueConfig(...), new DecodeParamValueConfig(...)})
decodeParamsConfig.put(CalendarDecoder.class, ....
}
Improve Decode Param support
----------------------------
Key: JBIDE-5687
URL: https://jira.jboss.org/jira/browse/JBIDE-5687
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: smooks
Affects Versions: 3.1.0.CR1
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Priority: Blocker
Fix For: 3.1.0.CR2
The editor supports decode parameter config through a properties sheet activated by
selecting the bean property. However, at the moment, the user needs to know the names of
the decode params relevant to the decoder being used to decode the data for that specific
binding.
Would make a big difference to the user (and shouldn't be too difficult to add) if
the editor automatically provided the decode params relevant to the binding. Also... make
the decode params the appear by default, when you select the properties of a bean
property.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:06 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5687) Improve Decode Param support
[
https://jira.jboss.org/jira/browse/JBIDE-5687?page=com.atlassian.jira.plu...
]
Tom Fennelly commented on JBIDE-5687:
-------------------------------------
Regarding #3 and the enums.... isn't it easy enough to get the possible enum values
from the enum type and add them as with your example, setting the values to being the same
as the name, allowing the user to modify.
Improve Decode Param support
----------------------------
Key: JBIDE-5687
URL: https://jira.jboss.org/jira/browse/JBIDE-5687
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: smooks
Affects Versions: 3.1.0.CR1
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Priority: Blocker
Fix For: 3.1.0.CR2
The editor supports decode parameter config through a properties sheet activated by
selecting the bean property. However, at the moment, the user needs to know the names of
the decode params relevant to the decoder being used to decode the data for that specific
binding.
Would make a big difference to the user (and shouldn't be too difficult to add) if
the editor automatically provided the decode params relevant to the binding. Also... make
the decode params the appear by default, when you select the properties of a bean
property.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:45 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5687) Improve Decode Param support
[
https://jira.jboss.org/jira/browse/JBIDE-5687?page=com.atlassian.jira.plu...
]
Xue Peng commented on JBIDE-5687:
---------------------------------
When user change the decoder , will we remove the old decoder parameters?
Improve Decode Param support
----------------------------
Key: JBIDE-5687
URL: https://jira.jboss.org/jira/browse/JBIDE-5687
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: smooks
Affects Versions: 3.1.0.CR1
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Priority: Blocker
Fix For: 3.1.0.CR2
The editor supports decode parameter config through a properties sheet activated by
selecting the bean property. However, at the moment, the user needs to know the names of
the decode params relevant to the decoder being used to decode the data for that specific
binding.
Would make a big difference to the user (and shouldn't be too difficult to add) if
the editor automatically provided the decode params relevant to the binding. Also... make
the decode params the appear by default, when you select the properties of a bean
property.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:21 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5687) Improve Decode Param support
[
https://jira.jboss.org/jira/browse/JBIDE-5687?page=com.atlassian.jira.plu...
]
Tom Fennelly commented on JBIDE-5687:
-------------------------------------
Right.... but in general... it doesn't really make sense for the user to change the
decoder i.e. no point in changing to an Integer decoder for a Date property on the target
bean... it will break the binding. We should warn them if they attempt to do this.
Improve Decode Param support
----------------------------
Key: JBIDE-5687
URL: https://jira.jboss.org/jira/browse/JBIDE-5687
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: smooks
Affects Versions: 3.1.0.CR1
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Priority: Blocker
Fix For: 3.1.0.CR2
The editor supports decode parameter config through a properties sheet activated by
selecting the bean property. However, at the moment, the user needs to know the names of
the decode params relevant to the decoder being used to decode the data for that specific
binding.
Would make a big difference to the user (and shouldn't be too difficult to add) if
the editor automatically provided the decode params relevant to the binding. Also... make
the decode params the appear by default, when you select the properties of a bean
property.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:13 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5687) Improve Decode Param support
[
https://jira.jboss.org/jira/browse/JBIDE-5687?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick commented on JBIDE-5687:
------------------------------------------
So this should become a wizard then to set the decoder and parameters and just happen
once, like we do for the Java Mapping and Apply Template tasks? The properties view would
then just show read-only settings for the decoder type, but allow editing of the
parameters.
Tom, is that what you're suggesting?
Improve Decode Param support
----------------------------
Key: JBIDE-5687
URL: https://jira.jboss.org/jira/browse/JBIDE-5687
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: smooks
Affects Versions: 3.1.0.CR1
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Priority: Blocker
Fix For: 3.1.0.CR2
The editor supports decode parameter config through a properties sheet activated by
selecting the bean property. However, at the moment, the user needs to know the names of
the decode params relevant to the decoder being used to decode the data for that specific
binding.
Would make a big difference to the user (and shouldn't be too difficult to add) if
the editor automatically provided the decode params relevant to the binding. Also... make
the decode params the appear by default, when you select the properties of a bean
property.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:25 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5687) Improve Decode Param support
[
https://jira.jboss.org/jira/browse/JBIDE-5687?page=com.atlassian.jira.plu...
]
Xue Peng commented on JBIDE-5687:
---------------------------------
Tom .
If we find the decoder isn't fit for the java type we can mark it as warning. I create
a new JIRA for it : JBIDE-5716
Improve Decode Param support
----------------------------
Key: JBIDE-5687
URL: https://jira.jboss.org/jira/browse/JBIDE-5687
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: smooks
Affects Versions: 3.1.0.CR1
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Priority: Blocker
Fix For: 3.1.0.CR2
The editor supports decode parameter config through a properties sheet activated by
selecting the bean property. However, at the moment, the user needs to know the names of
the decode params relevant to the decoder being used to decode the data for that specific
binding.
Would make a big difference to the user (and shouldn't be too difficult to add) if
the editor automatically provided the decode params relevant to the binding. Also... make
the decode params the appear by default, when you select the properties of a bean
property.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:27 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5687) Improve Decode Param support
[
https://jira.jboss.org/jira/browse/JBIDE-5687?page=com.atlassian.jira.plu...
]
Xue Peng commented on JBIDE-5687:
---------------------------------
It's a rough demo :
http://www.screencast.com/t/M2YyNTg3ZTAt
Improve Decode Param support
----------------------------
Key: JBIDE-5687
URL: https://jira.jboss.org/jira/browse/JBIDE-5687
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: smooks
Affects Versions: 3.1.0.CR1
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Priority: Blocker
Fix For: 3.1.0.CR2
The editor supports decode parameter config through a properties sheet activated by
selecting the bean property. However, at the moment, the user needs to know the names of
the decode params relevant to the decoder being used to decode the data for that specific
binding.
Would make a big difference to the user (and shouldn't be too difficult to add) if
the editor automatically provided the decode params relevant to the binding. Also... make
the decode params the appear by default, when you select the properties of a bean
property.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:55 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5687) Improve Decode Param support
[
https://jira.jboss.org/jira/browse/JBIDE-5687?page=com.atlassian.jira.plu...
]
Tom Fennelly commented on JBIDE-5687:
-------------------------------------
@Brian: No... I wasn't thinking of a wizard... I think param names should be read
only, but values should be modifiable any time.
@Dart: Screencast ... looks great. JBIDE-5716 ... perfect !!!
Improve Decode Param support
----------------------------
Key: JBIDE-5687
URL: https://jira.jboss.org/jira/browse/JBIDE-5687
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: smooks
Affects Versions: 3.1.0.CR1
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Priority: Blocker
Fix For: 3.1.0.CR2
The editor supports decode parameter config through a properties sheet activated by
selecting the bean property. However, at the moment, the user needs to know the names of
the decode params relevant to the decoder being used to decode the data for that specific
binding.
Would make a big difference to the user (and shouldn't be too difficult to add) if
the editor automatically provided the decode params relevant to the binding. Also... make
the decode params the appear by default, when you select the properties of a bean
property.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:40 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5687) Improve Decode Param support
[
https://jira.jboss.org/jira/browse/JBIDE-5687?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick commented on JBIDE-5687:
------------------------------------------
This needs to get fixed by the end of next week - Feb 5
Improve Decode Param support
----------------------------
Key: JBIDE-5687
URL: https://jira.jboss.org/jira/browse/JBIDE-5687
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: smooks
Affects Versions: 3.1.0.CR1
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Priority: Blocker
Fix For: 3.1.0.CR2
The editor supports decode parameter config through a properties sheet activated by
selecting the bean property. However, at the moment, the user needs to know the names of
the decode params relevant to the decoder being used to decode the data for that specific
binding.
Would make a big difference to the user (and shouldn't be too difficult to add) if
the editor automatically provided the decode params relevant to the binding. Also... make
the decode params the appear by default, when you select the properties of a bean
property.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:02 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5687) Improve Decode Param support
[
https://jira.jboss.org/jira/browse/JBIDE-5687?page=com.atlassian.jira.plu...
]
Xue Peng commented on JBIDE-5687:
---------------------------------
Tom ,
could you close this issue ? I think we split it to JBIDE-5726 and JBIDE-5716
Improve Decode Param support
----------------------------
Key: JBIDE-5687
URL: https://jira.jboss.org/jira/browse/JBIDE-5687
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: smooks
Affects Versions: 3.1.0.CR1
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Priority: Blocker
Fix For: 3.1.0.CR2
The editor supports decode parameter config through a properties sheet activated by
selecting the bean property. However, at the moment, the user needs to know the names of
the decode params relevant to the decoder being used to decode the data for that specific
binding.
Would make a big difference to the user (and shouldn't be too difficult to add) if
the editor automatically provided the decode params relevant to the binding. Also... make
the decode params the appear by default, when you select the properties of a bean
property.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:59 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-5687) Improve Decode Param support
[
https://jira.jboss.org/jira/browse/JBIDE-5687?page=com.atlassian.jira.plu...
]
Tom Fennelly closed JBIDE-5687.
-------------------------------
Resolution: Done
Sure... I was wondering about that actually. Thanks Dart.
Improve Decode Param support
----------------------------
Key: JBIDE-5687
URL: https://jira.jboss.org/jira/browse/JBIDE-5687
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: smooks
Affects Versions: 3.1.0.CR1
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Priority: Blocker
Fix For: 3.1.0.CR2
The editor supports decode parameter config through a properties sheet activated by
selecting the bean property. However, at the moment, the user needs to know the names of
the decode params relevant to the decoder being used to decode the data for that specific
binding.
Would make a big difference to the user (and shouldn't be too difficult to add) if
the editor automatically provided the decode params relevant to the binding. Also... make
the decode params the appear by default, when you select the properties of a bean
property.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:58 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5687) Improve Decode Param support
[
https://jira.jboss.org/jira/browse/JBIDE-5687?page=com.atlassian.jira.plu...
]
Tom Fennelly commented on JBIDE-5687:
-------------------------------------
I'm working on this one!!
Improve Decode Param support
----------------------------
Key: JBIDE-5687
URL: https://jira.jboss.org/jira/browse/JBIDE-5687
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: smooks
Affects Versions: 3.1.0.CR1
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Priority: Blocker
Fix For: 3.1.0.CR2
The editor supports decode parameter config through a properties sheet activated by
selecting the bean property. However, at the moment, the user needs to know the names of
the decode params relevant to the decoder being used to decode the data for that specific
binding.
Would make a big difference to the user (and shouldn't be too difficult to add) if
the editor automatically provided the decode params relevant to the binding. Also... make
the decode params the appear by default, when you select the properties of a bean
property.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:58 a.m.
New subject: [JBoss JIRA] Reopened: (JBIDE-5687) Improve Decode Param support
[
https://jira.jboss.org/jira/browse/JBIDE-5687?page=com.atlassian.jira.plu...
]
Tom Fennelly reopened JBIDE-5687:
---------------------------------
Sorry... reopening this.
We need to better handle defaulting of decoder configs e.g. when the target property is a
date and the decoder is not configured... default the decoder to the Date Decoder and
initalize the decode params with the defaults from the decoder.
Improve Decode Param support
----------------------------
Key: JBIDE-5687
URL: https://jira.jboss.org/jira/browse/JBIDE-5687
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: smooks
Affects Versions: 3.1.0.CR1
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Priority: Blocker
Fix For: 3.1.0.CR2
The editor supports decode parameter config through a properties sheet activated by
selecting the bean property. However, at the moment, the user needs to know the names of
the decode params relevant to the decoder being used to decode the data for that specific
binding.
Would make a big difference to the user (and shouldn't be too difficult to add) if
the editor automatically provided the decode params relevant to the binding. Also... make
the decode params the appear by default, when you select the properties of a bean
property.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:49 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-5687) Improve Decode Param support
[
https://jira.jboss.org/jira/browse/JBIDE-5687?page=com.atlassian.jira.plu...
]
Tom Fennelly closed JBIDE-5687.
-------------------------------
Resolution: Done
trunk: 20034
Improve Decode Param support
----------------------------
Key: JBIDE-5687
URL: https://jira.jboss.org/jira/browse/JBIDE-5687
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: smooks
Affects Versions: 3.1.0.CR1
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Priority: Blocker
Fix For: 3.1.0.CR2
The editor supports decode parameter config through a properties sheet activated by
selecting the bean property. However, at the moment, the user needs to know the names of
the decode params relevant to the decoder being used to decode the data for that specific
binding.
Would make a big difference to the user (and shouldn't be too difficult to add) if
the editor automatically provided the decode params relevant to the binding. Also... make
the decode params the appear by default, when you select the properties of a bean
property.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5919
days inactive
5935
days old
jbosstools-issues@lists.jboss.org
18 comments
3 participants
participants (3)
-
Brian Fitzpatrick (JIRA) -
Tom Fennelly (JIRA)
-
Xue Peng (JIRA)