[JBoss JIRA] Created: (JBESB-476) Make action, listener etc configuration setting by setter method the default
10:55 a.m.
Make action, listener etc configuration setting by setter method the default
----------------------------------------------------------------------------
Key: JBESB-476
URL: http://jira.jboss.com/jira/browse/JBESB-476
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.0
Reporter: Tom Fennelly
Assigned To: Mark Little
Fix For: 4.2
We currently configure everything by constructor. This is not great for a number of
reasons:
1. It can't be compile time validated.
2. Not as "obvious" to someone developing against the API. If in an interface,
their IDE (or at least compiler - if using a stone ax) will complain immediately that
they're not implementing the interface correctly.
3. Makes our code a little bit more complicated re the reflection code that needs to be
implemented.
So I suggest making the interface (that all these things implement) contain a setter
method that takes the config. The mandate on the implementation is that they contain a
public default constructor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:21 p.m.
New subject: [JBoss JIRA] Assigned: (JBESB-476) Make action, listener etc configuration setting by setter method the default
[ http://jira.jboss.com/jira/browse/JBESB-476?page=all ]
Mark Little reassigned JBESB-476:
---------------------------------
Assignee: Kevin Conner (was: Mark Little)
Make action, listener etc configuration setting by setter method the
default
----------------------------------------------------------------------------
Key: JBESB-476
URL: http://jira.jboss.com/jira/browse/JBESB-476
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 4.0
Reporter: Tom Fennelly
Assigned To: Kevin Conner
Fix For: 4.2
We currently configure everything by constructor. This is not great for a number of
reasons:
1. It can't be compile time validated.
2. Not as "obvious" to someone developing against the API. If in an interface,
their IDE (or at least compiler - if using a stone ax) will complain immediately that
they're not implementing the interface correctly.
3. Makes our code a little bit more complicated re the reflection code that needs to be
implemented.
So I suggest making the interface (that all these things implement) contain a setter
method that takes the config. The mandate on the implementation is that they contain a
public default constructor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:43 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-476) Make action, listener etc configuration setting by setter method the default
[ http://jira.jboss.com/jira/browse/JBESB-476?page=all ]
Mark Little updated JBESB-476:
------------------------------
Component/s: Configuration
Make action, listener etc configuration setting by setter method the
default
----------------------------------------------------------------------------
Key: JBESB-476
URL: http://jira.jboss.com/jira/browse/JBESB-476
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.0
Reporter: Tom Fennelly
Assigned To: Kevin Conner
Fix For: 4.2
We currently configure everything by constructor. This is not great for a number of
reasons:
1. It can't be compile time validated.
2. Not as "obvious" to someone developing against the API. If in an interface,
their IDE (or at least compiler - if using a stone ax) will complain immediately that
they're not implementing the interface correctly.
3. Makes our code a little bit more complicated re the reflection code that needs to be
implemented.
So I suggest making the interface (that all these things implement) contain a setter
method that takes the config. The mandate on the implementation is that they contain a
public default constructor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:33 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-476) Make action, listener etc configuration setting by setter method the default
[ http://jira.jboss.com/jira/browse/JBESB-476?page=all ]
Mark Little reassigned JBESB-476:
---------------------------------
Assignee: Daniel Bevenius (was: Kevin Conner)
Make action, listener etc configuration setting by setter method the
default
----------------------------------------------------------------------------
Key: JBESB-476
URL: http://jira.jboss.com/jira/browse/JBESB-476
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.0
Reporter: Tom Fennelly
Assigned To: Daniel Bevenius
Fix For: 4.2
We currently configure everything by constructor. This is not great for a number of
reasons:
1. It can't be compile time validated.
2. Not as "obvious" to someone developing against the API. If in an interface,
their IDE (or at least compiler - if using a stone ax) will complain immediately that
they're not implementing the interface correctly.
3. Makes our code a little bit more complicated re the reflection code that needs to be
implemented.
So I suggest making the interface (that all these things implement) contain a setter
method that takes the config. The mandate on the implementation is that they contain a
public default constructor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:15 p.m.
New subject: [JBoss JIRA] Assigned: (JBESB-476) Make action, listener etc configuration setting by setter method the default
[ http://jira.jboss.com/jira/browse/JBESB-476?page=all ]
Mark Little reassigned JBESB-476:
---------------------------------
Assignee: Kevin Conner (was: Daniel Bevenius)
Make action, listener etc configuration setting by setter method the
default
----------------------------------------------------------------------------
Key: JBESB-476
URL: http://jira.jboss.com/jira/browse/JBESB-476
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.0
Reporter: Tom Fennelly
Assigned To: Kevin Conner
Fix For: 4.2
We currently configure everything by constructor. This is not great for a number of
reasons:
1. It can't be compile time validated.
2. Not as "obvious" to someone developing against the API. If in an interface,
their IDE (or at least compiler - if using a stone ax) will complain immediately that
they're not implementing the interface correctly.
3. Makes our code a little bit more complicated re the reflection code that needs to be
implemented.
So I suggest making the interface (that all these things implement) contain a setter
method that takes the config. The mandate on the implementation is that they contain a
public default constructor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:33 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-476) Make action, listener etc configuration setting by setter method the default
[ http://jira.jboss.com/jira/browse/JBESB-476?page=all ]
Kevin Conner updated JBESB-476:
-------------------------------
Fix Version/s: 4.2.1
(was: 4.2)
This will not make the code freeze, moving to 4.2.1
Make action, listener etc configuration setting by setter method the
default
----------------------------------------------------------------------------
Key: JBESB-476
URL: http://jira.jboss.com/jira/browse/JBESB-476
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.0
Reporter: Tom Fennelly
Assigned To: Kevin Conner
Fix For: 4.2.1
We currently configure everything by constructor. This is not great for a number of
reasons:
1. It can't be compile time validated.
2. Not as "obvious" to someone developing against the API. If in an interface,
their IDE (or at least compiler - if using a stone ax) will complain immediately that
they're not implementing the interface correctly.
3. Makes our code a little bit more complicated re the reflection code that needs to be
implemented.
So I suggest making the interface (that all these things implement) contain a setter
method that takes the config. The mandate on the implementation is that they contain a
public default constructor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:08 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-476) Make action, listener etc configuration setting by setter method the default
[ http://jira.jboss.com/jira/browse/JBESB-476?page=comments#action_12381242 ]
Burr Sutter commented on JBESB-476:
-----------------------------------
Does this mean that customactions,demonstrated by the quickstarts, should use the
BeanConfiguredAction as the default?
Make action, listener etc configuration setting by setter method the
default
----------------------------------------------------------------------------
Key: JBESB-476
URL: http://jira.jboss.com/jira/browse/JBESB-476
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.0
Reporter: Tom Fennelly
Assigned To: Kevin Conner
Fix For: 4.2.1
We currently configure everything by constructor. This is not great for a number of
reasons:
1. It can't be compile time validated.
2. Not as "obvious" to someone developing against the API. If in an interface,
their IDE (or at least compiler - if using a stone ax) will complain immediately that
they're not implementing the interface correctly.
3. Makes our code a little bit more complicated re the reflection code that needs to be
implemented.
So I suggest making the interface (that all these things implement) contain a setter
method that takes the config. The mandate on the implementation is that they contain a
public default constructor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:38 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-476) Make action, listener etc configuration setting by setter method the default
[ http://jira.jboss.com/jira/browse/JBESB-476?page=comments#action_12381276 ]
Mark Little commented on JBESB-476:
-----------------------------------
I don't think we're going to get this issue done in 4.2.1 (last time I spoke with
Kev about it).
Make action, listener etc configuration setting by setter method the
default
----------------------------------------------------------------------------
Key: JBESB-476
URL: http://jira.jboss.com/jira/browse/JBESB-476
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.0
Reporter: Tom Fennelly
Assigned To: Kevin Conner
Fix For: 4.2.1
We currently configure everything by constructor. This is not great for a number of
reasons:
1. It can't be compile time validated.
2. Not as "obvious" to someone developing against the API. If in an interface,
their IDE (or at least compiler - if using a stone ax) will complain immediately that
they're not implementing the interface correctly.
3. Makes our code a little bit more complicated re the reflection code that needs to be
implemented.
So I suggest making the interface (that all these things implement) contain a setter
method that takes the config. The mandate on the implementation is that they contain a
public default constructor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:39 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-476) Make action, listener etc configuration setting by setter method the default
[ http://jira.jboss.com/jira/browse/JBESB-476?page=comments#action_12381295 ]
Tom Fennelly commented on JBESB-476:
------------------------------------
No, that BeanConfiguredAction thing is a hack and there's a better way of configuring
these components. I've moved configuration (and component lifecycle) on Smooks based
components to be totally annotation driven (auto validation, type conversion, enum support
etc). We could lift the basic code and do the same for the ESB (whenever).
Make action, listener etc configuration setting by setter method the
default
----------------------------------------------------------------------------
Key: JBESB-476
URL: http://jira.jboss.com/jira/browse/JBESB-476
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.0
Reporter: Tom Fennelly
Assigned To: Kevin Conner
Fix For: 4.2.1
We currently configure everything by constructor. This is not great for a number of
reasons:
1. It can't be compile time validated.
2. Not as "obvious" to someone developing against the API. If in an interface,
their IDE (or at least compiler - if using a stone ax) will complain immediately that
they're not implementing the interface correctly.
3. Makes our code a little bit more complicated re the reflection code that needs to be
implemented.
So I suggest making the interface (that all these things implement) contain a setter
method that takes the config. The mandate on the implementation is that they contain a
public default constructor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:03 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-476) Make action, listener etc configuration setting by setter method the default
[ http://jira.jboss.com/jira/browse/JBESB-476?page=all ]
Kevin Conner updated JBESB-476:
-------------------------------
Fix Version/s: 4.3
(was: 4.2.1)
Make action, listener etc configuration setting by setter method the
default
----------------------------------------------------------------------------
Key: JBESB-476
URL: http://jira.jboss.com/jira/browse/JBESB-476
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.0
Reporter: Tom Fennelly
Assigned To: Kevin Conner
Fix For: 4.3
We currently configure everything by constructor. This is not great for a number of
reasons:
1. It can't be compile time validated.
2. Not as "obvious" to someone developing against the API. If in an interface,
their IDE (or at least compiler - if using a stone ax) will complain immediately that
they're not implementing the interface correctly.
3. Makes our code a little bit more complicated re the reflection code that needs to be
implemented.
So I suggest making the interface (that all these things implement) contain a setter
method that takes the config. The mandate on the implementation is that they contain a
public default constructor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:40 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-476) Make action, listener etc configuration setting by setter method the default
[ http://jira.jboss.com/jira/browse/JBESB-476?page=all ]
Kevin Conner updated JBESB-476:
-------------------------------
Fix Version/s: 4.4
(was: 4.3)
Make action, listener etc configuration setting by setter method the
default
----------------------------------------------------------------------------
Key: JBESB-476
URL: http://jira.jboss.com/jira/browse/JBESB-476
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.0
Reporter: Tom Fennelly
Assigned To: Kevin Conner
Fix For: 4.4
We currently configure everything by constructor. This is not great for a number of
reasons:
1. It can't be compile time validated.
2. Not as "obvious" to someone developing against the API. If in an interface,
their IDE (or at least compiler - if using a stone ax) will complain immediately that
they're not implementing the interface correctly.
3. Makes our code a little bit more complicated re the reflection code that needs to be
implemented.
So I suggest making the interface (that all these things implement) contain a setter
method that takes the config. The mandate on the implementation is that they contain a
public default constructor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:30 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-476) Make action, listener etc configuration setting by setter method the default
[ http://jira.jboss.com/jira/browse/JBESB-476?page=all ]
Kevin Conner updated JBESB-476:
-------------------------------
Fix Version/s: 4.x
(was: 4.4)
Make action, listener etc configuration setting by setter method the
default
----------------------------------------------------------------------------
Key: JBESB-476
URL: http://jira.jboss.com/jira/browse/JBESB-476
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.0
Reporter: Tom Fennelly
Assigned To: Kevin Conner
Fix For: 4.x
We currently configure everything by constructor. This is not great for a number of
reasons:
1. It can't be compile time validated.
2. Not as "obvious" to someone developing against the API. If in an interface,
their IDE (or at least compiler - if using a stone ax) will complain immediately that
they're not implementing the interface correctly.
3. Makes our code a little bit more complicated re the reflection code that needs to be
implemented.
So I suggest making the interface (that all these things implement) contain a setter
method that takes the config. The mandate on the implementation is that they contain a
public default constructor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:24 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-476) Make action, listener etc configuration setting by setter method the default
[
https://jira.jboss.org/browse/JBESB-476?page=com.atlassian.jira.plugin.sy...
]
Kevin Conner closed JBESB-476.
------------------------------
Fix Version/s: (was: 4.x)
Resolution: Out of Date
Tom is looking at creating actions using annotations, which is as far as we intend to go
with ESB 4.x codebase.
Make action, listener etc configuration setting by setter method the
default
----------------------------------------------------------------------------
Key: JBESB-476
URL: https://jira.jboss.org/browse/JBESB-476
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.0
Reporter: Tom Fennelly
Assignee: Kevin Conner
We currently configure everything by constructor. This is not great for a number of
reasons:
1. It can't be compile time validated.
2. Not as "obvious" to someone developing against the API. If in an interface,
their IDE (or at least compiler - if using a stone ax) will complain immediately that
they're not implementing the interface correctly.
3. Makes our code a little bit more complicated re the reflection code that needs to be
implemented.
So I suggest making the interface (that all these things implement) contain a setter
method that takes the config. The mandate on the implementation is that they contain a
public default constructor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5335
days inactive
6494
days old
12 comments
4 participants
participants (4)
-
Burr Sutter (JIRA) -
Kevin Conner (JIRA)
-
Mark Little (JIRA)
-
Tom Fennelly (JIRA)