[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2008) Query should use parameterized type for results
12:54 a.m.
Query should use parameterized type for results
-----------------------------------------------
Key: JBSEAM-2008
URL: http://jira.jboss.com/jira/browse/JBSEAM-2008
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.CR1
Reporter: Dan Allen
Priority: Minor
Fix For: 2.0.0.GA
I don't see any reason why Query cannot be defined as Query<T, E> rather than
Query<T>. The general design of Query is that it operates on a static base query
(only the conditions are dynamic). Therefore, the item type in the result list should be
anticipated. In any case, if it is not, you can always define it using the generic type
Object.
To cite an example, we start with:
public class EntityQuery<E> extends Query<EntityManager, E> {}
We can use it as:
public class CategoryQuery extends EntityQuery<Category> {
}
CategoryQuery q = new CategoryQuery();
for ( Category c : q.getResultList() ) {
// didn't need to cast!
}
On the other hand, if the query component is defined without the type, it will still work.
The type will be treated as java.lang.Object.
public class CategoryQuery extends EntityQuery {
}
--
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
12:56 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2008) Query should use parameterized type for results
[ http://jira.jboss.com/jira/browse/JBSEAM-2008?page=all ]
Dan Allen updated JBSEAM-2008:
------------------------------
Attachment: JBSEAM-2008-v1.txt
Uploading patch.
Query should use parameterized type for results
-----------------------------------------------
Key: JBSEAM-2008
URL: http://jira.jboss.com/jira/browse/JBSEAM-2008
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.CR1
Reporter: Dan Allen
Priority: Minor
Fix For: 2.0.0.GA
Attachments: JBSEAM-2008-v1.txt
Original Estimate: 1 hour
Remaining Estimate: 1 hour
I don't see any reason why Query cannot be defined as Query<T, E> rather than
Query<T>. The general design of Query is that it operates on a static base query
(only the conditions are dynamic). Therefore, the item type in the result list should be
anticipated. In any case, if it is not, you can always define it using the generic type
Object.
To cite an example, we start with:
public class EntityQuery<E> extends Query<EntityManager, E> {}
We can use it as:
public class CategoryQuery extends EntityQuery<Category> {
}
CategoryQuery q = new CategoryQuery();
for ( Category c : q.getResultList() ) {
// didn't need to cast!
}
On the other hand, if the query component is defined without the type, it will still
work. The type will be treated as java.lang.Object.
public class CategoryQuery extends EntityQuery {
}
--
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
12:56 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2008) Query should use parameterized type for results
[ http://jira.jboss.com/jira/browse/JBSEAM-2008?page=comments#action_12379461 ]
Dan Allen commented on JBSEAM-2008:
-----------------------------------
This small fix further justifies why the Seam Application Framework is so useful. It is
the generic wrapper around the non-generic Java Persistence API, the one extreme weak spot
in the EJB 3 improvements.
Query should use parameterized type for results
-----------------------------------------------
Key: JBSEAM-2008
URL: http://jira.jboss.com/jira/browse/JBSEAM-2008
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.CR1
Reporter: Dan Allen
Priority: Minor
Fix For: 2.0.0.GA
Attachments: JBSEAM-2008-v1.txt
Original Estimate: 1 hour
Remaining Estimate: 1 hour
I don't see any reason why Query cannot be defined as Query<T, E> rather than
Query<T>. The general design of Query is that it operates on a static base query
(only the conditions are dynamic). Therefore, the item type in the result list should be
anticipated. In any case, if it is not, you can always define it using the generic type
Object.
To cite an example, we start with:
public class EntityQuery<E> extends Query<EntityManager, E> {}
We can use it as:
public class CategoryQuery extends EntityQuery<Category> {
}
CategoryQuery q = new CategoryQuery();
for ( Category c : q.getResultList() ) {
// didn't need to cast!
}
On the other hand, if the query component is defined without the type, it will still
work. The type will be treated as java.lang.Object.
public class CategoryQuery extends EntityQuery {
}
--
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:47 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2008) Query should use parameterized type for results
[ http://jira.jboss.com/jira/browse/JBSEAM-2008?page=all ]
Norman Richards updated JBSEAM-2008:
------------------------------------
Fix Version/s: 2.0.x
(was: 2.0.0.GA)
Query should use parameterized type for results
-----------------------------------------------
Key: JBSEAM-2008
URL: http://jira.jboss.com/jira/browse/JBSEAM-2008
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.CR1
Reporter: Dan Allen
Priority: Minor
Fix For: 2.0.x
Attachments: JBSEAM-2008-v1.txt
Original Estimate: 1 hour
Remaining Estimate: 1 hour
I don't see any reason why Query cannot be defined as Query<T, E> rather than
Query<T>. The general design of Query is that it operates on a static base query
(only the conditions are dynamic). Therefore, the item type in the result list should be
anticipated. In any case, if it is not, you can always define it using the generic type
Object.
To cite an example, we start with:
public class EntityQuery<E> extends Query<EntityManager, E> {}
We can use it as:
public class CategoryQuery extends EntityQuery<Category> {
}
CategoryQuery q = new CategoryQuery();
for ( Category c : q.getResultList() ) {
// didn't need to cast!
}
On the other hand, if the query component is defined without the type, it will still
work. The type will be treated as java.lang.Object.
public class CategoryQuery extends EntityQuery {
}
--
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:43 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2008) Query should use parameterized type for results
[ http://jira.jboss.com/jira/browse/JBSEAM-2008?page=all ]
Dan Allen updated JBSEAM-2008:
------------------------------
Fix Version/s: 2.0.1.GA
(was: 2.0.x)
This is a pretty basic fix. I am inclined to say Seam 2.0.0 or 2.0.1.
Query should use parameterized type for results
-----------------------------------------------
Key: JBSEAM-2008
URL: http://jira.jboss.com/jira/browse/JBSEAM-2008
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.CR1
Reporter: Dan Allen
Priority: Minor
Fix For: 2.0.1.GA
Attachments: JBSEAM-2008-v1.txt
Original Estimate: 1 hour
Remaining Estimate: 1 hour
I don't see any reason why Query cannot be defined as Query<T, E> rather than
Query<T>. The general design of Query is that it operates on a static base query
(only the conditions are dynamic). Therefore, the item type in the result list should be
anticipated. In any case, if it is not, you can always define it using the generic type
Object.
To cite an example, we start with:
public class EntityQuery<E> extends Query<EntityManager, E> {}
We can use it as:
public class CategoryQuery extends EntityQuery<Category> {
}
CategoryQuery q = new CategoryQuery();
for ( Category c : q.getResultList() ) {
// didn't need to cast!
}
On the other hand, if the query component is defined without the type, it will still
work. The type will be treated as java.lang.Object.
public class CategoryQuery extends EntityQuery {
}
--
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:47 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2008) Query should use parameterized type for results
[ http://jira.jboss.com/jira/browse/JBSEAM-2008?page=all ]
Dan Allen updated JBSEAM-2008:
------------------------------
Fix Version/s: 2.0.0.CR2
(was: 2.0.1.GA)
Let's throw this on the CR2 pile as well.
Query should use parameterized type for results
-----------------------------------------------
Key: JBSEAM-2008
URL: http://jira.jboss.com/jira/browse/JBSEAM-2008
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.CR1
Reporter: Dan Allen
Priority: Minor
Fix For: 2.0.0.CR2
Attachments: JBSEAM-2008-v1.txt
Original Estimate: 1 hour
Remaining Estimate: 1 hour
I don't see any reason why Query cannot be defined as Query<T, E> rather than
Query<T>. The general design of Query is that it operates on a static base query
(only the conditions are dynamic). Therefore, the item type in the result list should be
anticipated. In any case, if it is not, you can always define it using the generic type
Object.
To cite an example, we start with:
public class EntityQuery<E> extends Query<EntityManager, E> {}
We can use it as:
public class CategoryQuery extends EntityQuery<Category> {
}
CategoryQuery q = new CategoryQuery();
for ( Category c : q.getResultList() ) {
// didn't need to cast!
}
On the other hand, if the query component is defined without the type, it will still
work. The type will be treated as java.lang.Object.
public class CategoryQuery extends EntityQuery {
}
--
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:56 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2008) Query should use parameterized type for results
[ http://jira.jboss.com/jira/browse/JBSEAM-2008?page=comments#action_12380191 ]
Norman Richards commented on JBSEAM-2008:
-----------------------------------------
Let's try not to make API changes at this point.
Query should use parameterized type for results
-----------------------------------------------
Key: JBSEAM-2008
URL: http://jira.jboss.com/jira/browse/JBSEAM-2008
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.CR1
Reporter: Dan Allen
Priority: Minor
Fix For: 2.0.0.CR2
Attachments: JBSEAM-2008-v1.txt
Original Estimate: 1 hour
Remaining Estimate: 1 hour
I don't see any reason why Query cannot be defined as Query<T, E> rather than
Query<T>. The general design of Query is that it operates on a static base query
(only the conditions are dynamic). Therefore, the item type in the result list should be
anticipated. In any case, if it is not, you can always define it using the generic type
Object.
To cite an example, we start with:
public class EntityQuery<E> extends Query<EntityManager, E> {}
We can use it as:
public class CategoryQuery extends EntityQuery<Category> {
}
CategoryQuery q = new CategoryQuery();
for ( Category c : q.getResultList() ) {
// didn't need to cast!
}
On the other hand, if the query component is defined without the type, it will still
work. The type will be treated as java.lang.Object.
public class CategoryQuery extends EntityQuery {
}
--
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:58 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2008) Query should use parameterized type for results
[ http://jira.jboss.com/jira/browse/JBSEAM-2008?page=all ]
Norman Richards updated JBSEAM-2008:
------------------------------------
Fix Version/s: 2.0.1.GA
(was: 2.0.0.CR2)
Query should use parameterized type for results
-----------------------------------------------
Key: JBSEAM-2008
URL: http://jira.jboss.com/jira/browse/JBSEAM-2008
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.CR1
Reporter: Dan Allen
Priority: Minor
Fix For: 2.0.1.GA
Attachments: JBSEAM-2008-v1.txt
Original Estimate: 1 hour
Remaining Estimate: 1 hour
I don't see any reason why Query cannot be defined as Query<T, E> rather than
Query<T>. The general design of Query is that it operates on a static base query
(only the conditions are dynamic). Therefore, the item type in the result list should be
anticipated. In any case, if it is not, you can always define it using the generic type
Object.
To cite an example, we start with:
public class EntityQuery<E> extends Query<EntityManager, E> {}
We can use it as:
public class CategoryQuery extends EntityQuery<Category> {
}
CategoryQuery q = new CategoryQuery();
for ( Category c : q.getResultList() ) {
// didn't need to cast!
}
On the other hand, if the query component is defined without the type, it will still
work. The type will be treated as java.lang.Object.
public class CategoryQuery extends EntityQuery {
}
--
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:28 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2008) Query should use parameterized type for results
[ http://jira.jboss.com/jira/browse/JBSEAM-2008?page=comments#action_12380204 ]
Dan Allen commented on JBSEAM-2008:
-----------------------------------
I'm cool with fixing it in 2.0.1, but I don't necessarily agree it is an API
change. The code will work exactly as is today. This just adds a compile time enhancement.
But I can be patient on it.
Query should use parameterized type for results
-----------------------------------------------
Key: JBSEAM-2008
URL: http://jira.jboss.com/jira/browse/JBSEAM-2008
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.CR1
Reporter: Dan Allen
Priority: Minor
Fix For: 2.0.1.GA
Attachments: JBSEAM-2008-v1.txt
Original Estimate: 1 hour
Remaining Estimate: 1 hour
I don't see any reason why Query cannot be defined as Query<T, E> rather than
Query<T>. The general design of Query is that it operates on a static base query
(only the conditions are dynamic). Therefore, the item type in the result list should be
anticipated. In any case, if it is not, you can always define it using the generic type
Object.
To cite an example, we start with:
public class EntityQuery<E> extends Query<EntityManager, E> {}
We can use it as:
public class CategoryQuery extends EntityQuery<Category> {
}
CategoryQuery q = new CategoryQuery();
for ( Category c : q.getResultList() ) {
// didn't need to cast!
}
On the other hand, if the query component is defined without the type, it will still
work. The type will be treated as java.lang.Object.
public class CategoryQuery extends EntityQuery {
}
--
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:29 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-2008) Query should use parameterized type for results
[ http://jira.jboss.com/jira/browse/JBSEAM-2008?page=all ]
Dan Allen reassigned JBSEAM-2008:
---------------------------------
Assignee: Dan Allen
Query should use parameterized type for results
-----------------------------------------------
Key: JBSEAM-2008
URL: http://jira.jboss.com/jira/browse/JBSEAM-2008
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.CR1
Reporter: Dan Allen
Assigned To: Dan Allen
Priority: Minor
Fix For: 2.0.1.GA
Attachments: JBSEAM-2008-v1.txt
Original Estimate: 1 hour
Remaining Estimate: 1 hour
I don't see any reason why Query cannot be defined as Query<T, E> rather than
Query<T>. The general design of Query is that it operates on a static base query
(only the conditions are dynamic). Therefore, the item type in the result list should be
anticipated. In any case, if it is not, you can always define it using the generic type
Object.
To cite an example, we start with:
public class EntityQuery<E> extends Query<EntityManager, E> {}
We can use it as:
public class CategoryQuery extends EntityQuery<Category> {
}
CategoryQuery q = new CategoryQuery();
for ( Category c : q.getResultList() ) {
// didn't need to cast!
}
On the other hand, if the query component is defined without the type, it will still
work. The type will be treated as java.lang.Object.
public class CategoryQuery extends EntityQuery {
}
--
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:32 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2008) Query should use parameterized type for results
[ http://jira.jboss.com/jira/browse/JBSEAM-2008?page=all ]
Dan Allen updated JBSEAM-2008:
------------------------------
Component/s: Core
(was: Tools)
Query should use parameterized type for results
-----------------------------------------------
Key: JBSEAM-2008
URL: http://jira.jboss.com/jira/browse/JBSEAM-2008
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.0.0.CR1
Reporter: Dan Allen
Assigned To: Dan Allen
Priority: Minor
Fix For: 2.0.1.GA
Attachments: JBSEAM-2008-v1.txt
Original Estimate: 1 hour
Remaining Estimate: 1 hour
I don't see any reason why Query cannot be defined as Query<T, E> rather than
Query<T>. The general design of Query is that it operates on a static base query
(only the conditions are dynamic). Therefore, the item type in the result list should be
anticipated. In any case, if it is not, you can always define it using the generic type
Object.
To cite an example, we start with:
public class EntityQuery<E> extends Query<EntityManager, E> {}
We can use it as:
public class CategoryQuery extends EntityQuery<Category> {
}
CategoryQuery q = new CategoryQuery();
for ( Category c : q.getResultList() ) {
// didn't need to cast!
}
On the other hand, if the query component is defined without the type, it will still
work. The type will be treated as java.lang.Object.
public class CategoryQuery extends EntityQuery {
}
--
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:02 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Resolved: (JBSEAM-2008) Query should use parameterized type for results
[ http://jira.jboss.com/jira/browse/JBSEAM-2008?page=all ]
Dan Allen resolved JBSEAM-2008.
-------------------------------
Resolution: Done
patch applied.
Query should use parameterized type for results
-----------------------------------------------
Key: JBSEAM-2008
URL: http://jira.jboss.com/jira/browse/JBSEAM-2008
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.0.0.CR1
Reporter: Dan Allen
Assigned To: Dan Allen
Priority: Minor
Fix For: 2.0.1.GA
Attachments: JBSEAM-2008-v1.txt
Original Estimate: 1 hour
Remaining Estimate: 1 hour
I don't see any reason why Query cannot be defined as Query<T, E> rather than
Query<T>. The general design of Query is that it operates on a static base query
(only the conditions are dynamic). Therefore, the item type in the result list should be
anticipated. In any case, if it is not, you can always define it using the generic type
Object.
To cite an example, we start with:
public class EntityQuery<E> extends Query<EntityManager, E> {}
We can use it as:
public class CategoryQuery extends EntityQuery<Category> {
}
CategoryQuery q = new CategoryQuery();
for ( Category c : q.getResultList() ) {
// didn't need to cast!
}
On the other hand, if the query component is defined without the type, it will still
work. The type will be treated as java.lang.Object.
public class CategoryQuery extends EntityQuery {
}
--
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:02 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-2008) Query should use parameterized type for results
[ http://jira.jboss.com/jira/browse/JBSEAM-2008?page=all ]
Dan Allen closed JBSEAM-2008.
-----------------------------
Query should use parameterized type for results
-----------------------------------------------
Key: JBSEAM-2008
URL: http://jira.jboss.com/jira/browse/JBSEAM-2008
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.0.0.CR1
Reporter: Dan Allen
Assigned To: Dan Allen
Priority: Minor
Fix For: 2.0.1.GA
Attachments: JBSEAM-2008-v1.txt
Original Estimate: 1 hour
Remaining Estimate: 1 hour
I don't see any reason why Query cannot be defined as Query<T, E> rather than
Query<T>. The general design of Query is that it operates on a static base query
(only the conditions are dynamic). Therefore, the item type in the result list should be
anticipated. In any case, if it is not, you can always define it using the generic type
Object.
To cite an example, we start with:
public class EntityQuery<E> extends Query<EntityManager, E> {}
We can use it as:
public class CategoryQuery extends EntityQuery<Category> {
}
CategoryQuery q = new CategoryQuery();
for ( Category c : q.getResultList() ) {
// didn't need to cast!
}
On the other hand, if the query component is defined without the type, it will still
work. The type will be treated as java.lang.Object.
public class CategoryQuery extends EntityQuery {
}
--
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
6713
days inactive
6772
days old
12 comments
2 participants
participants (2)
-
Dan Allen (JIRA) -
Norman Richards (JIRA)