[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1600) Lowercase first letter of context variable for @Name
8:48 a.m.
Lowercase first letter of context variable for @Name
----------------------------------------------------
Key: JBSEAM-1600
URL: http://jira.jboss.com/jira/browse/JBSEAM-1600
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.0.0.BETA1
Reporter: Dan Allen
Priority: Minor
99.99999999% of the time, when you want to create a Seam component, the convention is to
use the simple name of the class with the first letter in lowercase. Open any Seam
component in the examples directory and you will observe this conversion. Would it be
reasonable to use the clazz.getSimpleName() and lowercase the first letter by default when
creating the context variable? I would even settle for a configuration setting in
core:manager that would enable this even if it were not used as the default. The change
shouldn't cause compatibility issues since an explicit value is required as is.
We are going around saying, "Look! Configuration by exception, see!"
@Name("hotel")
public class Hotel {
...
}
Um, hello. No. That is not configuration by exception. Let's make it that way!
--
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:50 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1600) Make @Name value optional, use the simple name of class as default
[ http://jira.jboss.com/jira/browse/JBSEAM-1600?page=all ]
Dan Allen updated JBSEAM-1600:
------------------------------
Summary: Make @Name value optional, use the simple name of class as default (was:
Lowercase first letter of context variable for @Name)
Make @Name value optional, use the simple name of class as default
------------------------------------------------------------------
Key: JBSEAM-1600
URL: http://jira.jboss.com/jira/browse/JBSEAM-1600
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.0.0.BETA1
Reporter: Dan Allen
Priority: Minor
Original Estimate: 4 hours
Remaining Estimate: 4 hours
99.99999999% of the time, when you want to create a Seam component, the convention is to
use the simple name of the class with the first letter in lowercase. Open any Seam
component in the examples directory and you will observe this conversion. Would it be
reasonable to use the clazz.getSimpleName() and lowercase the first letter by default when
creating the context variable? I would even settle for a configuration setting in
core:manager that would enable this even if it were not used as the default. The change
shouldn't cause compatibility issues since an explicit value is required as is.
We are going around saying, "Look! Configuration by exception, see!"
@Name("hotel")
public class Hotel {
...
}
Um, hello. No. That is not configuration by exception. Let's make it that way!
--
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
1:46 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-1600) Make @Name value optional, use the simple name of class as default
[ http://jira.jboss.com/jira/browse/JBSEAM-1600?page=all ]
Gavin King closed JBSEAM-1600.
------------------------------
Resolution: Duplicate Issue
This is a dupe, and I'm not going to redesign this in Seam. We have a new design in
the Web Beans spec, which we will implement in Seam when the time comes.
Make @Name value optional, use the simple name of class as default
------------------------------------------------------------------
Key: JBSEAM-1600
URL: http://jira.jboss.com/jira/browse/JBSEAM-1600
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.0.0.BETA1
Reporter: Dan Allen
Priority: Minor
Original Estimate: 4 hours
Remaining Estimate: 4 hours
99.99999999% of the time, when you want to create a Seam component, the convention is to
use the simple name of the class with the first letter in lowercase. Open any Seam
component in the examples directory and you will observe this conversion. Would it be
reasonable to use the clazz.getSimpleName() and lowercase the first letter by default when
creating the context variable? I would even settle for a configuration setting in
core:manager that would enable this even if it were not used as the default. The change
shouldn't cause compatibility issues since an explicit value is required as is.
We are going around saying, "Look! Configuration by exception, see!"
@Name("hotel")
public class Hotel {
...
}
Um, hello. No. That is not configuration by exception. Let's make it that way!
--
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:05 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1600) Make @Name value optional, use the simple name of class as default
[ http://jira.jboss.com/jira/browse/JBSEAM-1600?page=comments#action_12367698 ]
Dan Allen commented on JBSEAM-1600:
-----------------------------------
Rats. Oh well, worth a try I guess. I will be excited to see this implemented in
WebBeans. To earn bragging rights when demonstrating Seam, I look for places where typing
can be eliminated. I guess I won't get to draw a line through this one. Hell, I
would even settle for the verbatim getSimpleName() since that is the way that @Entity
works. But if you insist...life goes on.
Make @Name value optional, use the simple name of class as default
------------------------------------------------------------------
Key: JBSEAM-1600
URL: http://jira.jboss.com/jira/browse/JBSEAM-1600
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.0.0.BETA1
Reporter: Dan Allen
Priority: Minor
Original Estimate: 4 hours
Remaining Estimate: 4 hours
99.99999999% of the time, when you want to create a Seam component, the convention is to
use the simple name of the class with the first letter in lowercase. Open any Seam
component in the examples directory and you will observe this conversion. Would it be
reasonable to use the clazz.getSimpleName() and lowercase the first letter by default when
creating the context variable? I would even settle for a configuration setting in
core:manager that would enable this even if it were not used as the default. The change
shouldn't cause compatibility issues since an explicit value is required as is.
We are going around saying, "Look! Configuration by exception, see!"
@Name("hotel")
public class Hotel {
...
}
Um, hello. No. That is not configuration by exception. Let's make it that way!
--
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:48 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Reopened: (JBSEAM-1600) Make @Name value optional, use the simple name of class as default
[ http://jira.jboss.com/jira/browse/JBSEAM-1600?page=all ]
Dan Allen reopened JBSEAM-1600:
-------------------------------
I am going to stick out my neck on this one and pray that it pays off, but I really think
you should reconsider. I bring a patch as a peace offering. The patch is SO simple and it
adds such elegance to Seam. It is also 100% backward compatible, so we aren't taking
any risk here.
Make @Name value optional, use the simple name of class as default
------------------------------------------------------------------
Key: JBSEAM-1600
URL: http://jira.jboss.com/jira/browse/JBSEAM-1600
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.0.0.BETA1
Reporter: Dan Allen
Priority: Minor
Attachments: JBSEAM-1600-v1.txt
Original Estimate: 4 hours
Remaining Estimate: 4 hours
99.99999999% of the time, when you want to create a Seam component, the convention is to
use the simple name of the class with the first letter in lowercase. Open any Seam
component in the examples directory and you will observe this conversion. Would it be
reasonable to use the clazz.getSimpleName() and lowercase the first letter by default when
creating the context variable? I would even settle for a configuration setting in
core:manager that would enable this even if it were not used as the default. The change
shouldn't cause compatibility issues since an explicit value is required as is.
We are going around saying, "Look! Configuration by exception, see!"
@Name("hotel")
public class Hotel {
...
}
Um, hello. No. That is not configuration by exception. Let's make it that way!
--
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:48 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1600) Make @Name value optional, use the simple name of class as default
[ http://jira.jboss.com/jira/browse/JBSEAM-1600?page=all ]
Dan Allen updated JBSEAM-1600:
------------------------------
Attachment: JBSEAM-1600-v1.txt
Make @Name value optional, use the simple name of class as default
------------------------------------------------------------------
Key: JBSEAM-1600
URL: http://jira.jboss.com/jira/browse/JBSEAM-1600
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.0.0.BETA1
Reporter: Dan Allen
Priority: Minor
Attachments: JBSEAM-1600-v1.txt
Original Estimate: 4 hours
Remaining Estimate: 4 hours
99.99999999% of the time, when you want to create a Seam component, the convention is to
use the simple name of the class with the first letter in lowercase. Open any Seam
component in the examples directory and you will observe this conversion. Would it be
reasonable to use the clazz.getSimpleName() and lowercase the first letter by default when
creating the context variable? I would even settle for a configuration setting in
core:manager that would enable this even if it were not used as the default. The change
shouldn't cause compatibility issues since an explicit value is required as is.
We are going around saying, "Look! Configuration by exception, see!"
@Name("hotel")
public class Hotel {
...
}
Um, hello. No. That is not configuration by exception. Let's make it that way!
--
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:52 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1600) Make @Name value optional, use the simple name of class as default
[ http://jira.jboss.com/jira/browse/JBSEAM-1600?page=comments#action_12369041 ]
Dan Allen commented on JBSEAM-1600:
-----------------------------------
I linked in the other issue, but I am proposing and even simpler default of the
getSimpleName() verbatim.
Make @Name value optional, use the simple name of class as default
------------------------------------------------------------------
Key: JBSEAM-1600
URL: http://jira.jboss.com/jira/browse/JBSEAM-1600
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.0.0.BETA1
Reporter: Dan Allen
Priority: Minor
Attachments: JBSEAM-1600-v1.txt
Original Estimate: 4 hours
Remaining Estimate: 4 hours
99.99999999% of the time, when you want to create a Seam component, the convention is to
use the simple name of the class with the first letter in lowercase. Open any Seam
component in the examples directory and you will observe this conversion. Would it be
reasonable to use the clazz.getSimpleName() and lowercase the first letter by default when
creating the context variable? I would even settle for a configuration setting in
core:manager that would enable this even if it were not used as the default. The change
shouldn't cause compatibility issues since an explicit value is required as is.
We are going around saying, "Look! Configuration by exception, see!"
@Name("hotel")
public class Hotel {
...
}
Um, hello. No. That is not configuration by exception. Let's make it that way!
--
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
1:52 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-1600) Make @Name value optional, use the simple name of class as default
[ http://jira.jboss.com/jira/browse/JBSEAM-1600?page=all ]
Gavin King closed JBSEAM-1600.
------------------------------
Resolution: Rejected
Nope, sorry. @Name without a name inside it is sooo ugly....
Make @Name value optional, use the simple name of class as default
------------------------------------------------------------------
Key: JBSEAM-1600
URL: http://jira.jboss.com/jira/browse/JBSEAM-1600
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.0.0.BETA1
Reporter: Dan Allen
Priority: Minor
Attachments: JBSEAM-1600-v1.txt
Original Estimate: 4 hours
Remaining Estimate: 4 hours
99.99999999% of the time, when you want to create a Seam component, the convention is to
use the simple name of the class with the first letter in lowercase. Open any Seam
component in the examples directory and you will observe this conversion. Would it be
reasonable to use the clazz.getSimpleName() and lowercase the first letter by default when
creating the context variable? I would even settle for a configuration setting in
core:manager that would enable this even if it were not used as the default. The change
shouldn't cause compatibility issues since an explicit value is required as is.
We are going around saying, "Look! Configuration by exception, see!"
@Name("hotel")
public class Hotel {
...
}
Um, hello. No. That is not configuration by exception. Let's make it that way!
--
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:48 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1600) Make @Name value optional, use the simple name of class as default
[ http://jira.jboss.com/jira/browse/JBSEAM-1600?page=comments#action_12369089 ]
Dan Allen commented on JBSEAM-1600:
-----------------------------------
The man has spoken ;)
I now see your point. I mean, after all, it is a @Name annotation. That implies you are
going to supply a name. Time to fry bigger fish.
Make @Name value optional, use the simple name of class as default
------------------------------------------------------------------
Key: JBSEAM-1600
URL: http://jira.jboss.com/jira/browse/JBSEAM-1600
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.0.0.BETA1
Reporter: Dan Allen
Priority: Minor
Attachments: JBSEAM-1600-v1.txt
Original Estimate: 4 hours
Remaining Estimate: 4 hours
99.99999999% of the time, when you want to create a Seam component, the convention is to
use the simple name of the class with the first letter in lowercase. Open any Seam
component in the examples directory and you will observe this conversion. Would it be
reasonable to use the clazz.getSimpleName() and lowercase the first letter by default when
creating the context variable? I would even settle for a configuration setting in
core:manager that would enable this even if it were not used as the default. The change
shouldn't cause compatibility issues since an explicit value is required as is.
We are going around saying, "Look! Configuration by exception, see!"
@Name("hotel")
public class Hotel {
...
}
Um, hello. No. That is not configuration by exception. Let's make it that way!
--
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
6391
days inactive
6404
days old
8 comments
2 participants
participants (2)
-
Dan Allen (JIRA) -
Gavin King (JIRA)