5:46 a.m.
[
https://issues.jboss.org/browse/JBIDE-12179?page=com.atlassian.jira.plugi...
]
Denis Golovin updated JBIDE-12179:
----------------------------------
Fix Version/s: 3.4.0.M1
3.4.0.M2
Assignee: Denis Golovin
Forum Reference: https://community.jboss.org/message/741828#741828,
https://community.jboss.org/message/741828 (was:
https://community.jboss.org/message/741828#741828,
https://community.jboss.org/message/741828)
Invalid Error marker when using Hibernate @Type annotation
----------------------------------------------------------
Key: JBIDE-12179
URL: https://issues.jboss.org/browse/JBIDE-12179
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 3.3.0.CR1
Reporter: Corey Puffalt
Assignee: Denis Golovin
Fix For: 3.4.0.M1, 3.4.0.M2
We're seeing invalid error markers when using the Hibernate @Type annotation where
the type value we're specifying isn't actually a Class name. This looks like a
bug in JBoss Tools (I have the new Candidate Release installed).
Sample class:
{code}
import javax.persistence.Entity;
import javax.persistence.Id;
import org.hibernate.annotations.Type;
@Entity
public class TestEntity
{
@Id
private Long id;
@Type(type = "yes_no")
private Boolean flag;
}
{code}
The error marker states 'Type class "yes_no" could not be found.' but
this is actually valid.
I did find some similar cases (JBIDE-11364, JBIDE-11368) in the bug tracker but not one
that described this issue exactly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:49 a.m.
[
https://issues.jboss.org/browse/JBIDE-12179?page=com.atlassian.jira.plugi...
]
Denis Golovin commented on JBIDE-12179:
---------------------------------------
Seems to be fixed in trunk for 3.4.0.M1. Verified for all supported Hibernate versions
3.5, 3.6 and 4.0.
Invalid Error marker when using Hibernate @Type annotation
----------------------------------------------------------
Key: JBIDE-12179
URL: https://issues.jboss.org/browse/JBIDE-12179
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 3.3.0.CR1
Reporter: Corey Puffalt
Assignee: Denis Golovin
Fix For: 3.4.0.M1, 3.4.0.M2
We're seeing invalid error markers when using the Hibernate @Type annotation where
the type value we're specifying isn't actually a Class name. This looks like a
bug in JBoss Tools (I have the new Candidate Release installed).
Sample class:
{code}
import javax.persistence.Entity;
import javax.persistence.Id;
import org.hibernate.annotations.Type;
@Entity
public class TestEntity
{
@Id
private Long id;
@Type(type = "yes_no")
private Boolean flag;
}
{code}
The error marker states 'Type class "yes_no" could not be found.' but
this is actually valid.
I did find some similar cases (JBIDE-11364, JBIDE-11368) in the bug tracker but not one
that described this issue exactly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:51 a.m.
[
https://issues.jboss.org/browse/JBIDE-12179?page=com.atlassian.jira.plugi...
]
Denis Golovin updated JBIDE-12179:
----------------------------------
Fix Version/s: (was: 3.4.0.M2)
Forum Reference: https://community.jboss.org/message/741828#741828,
https://community.jboss.org/message/741828 (was:
https://community.jboss.org/message/741828#741828,
https://community.jboss.org/message/741828)
Invalid Error marker when using Hibernate @Type annotation
----------------------------------------------------------
Key: JBIDE-12179
URL: https://issues.jboss.org/browse/JBIDE-12179
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 3.3.0.CR1
Reporter: Corey Puffalt
Assignee: Denis Golovin
Fix For: 3.4.0.M1
We're seeing invalid error markers when using the Hibernate @Type annotation where
the type value we're specifying isn't actually a Class name. This looks like a
bug in JBoss Tools (I have the new Candidate Release installed).
Sample class:
{code}
import javax.persistence.Entity;
import javax.persistence.Id;
import org.hibernate.annotations.Type;
@Entity
public class TestEntity
{
@Id
private Long id;
@Type(type = "yes_no")
private Boolean flag;
}
{code}
The error marker states 'Type class "yes_no" could not be found.' but
this is actually valid.
I did find some similar cases (JBIDE-11364, JBIDE-11368) in the bug tracker but not one
that described this issue exactly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:53 a.m.
[
https://issues.jboss.org/browse/JBIDE-12179?page=com.atlassian.jira.plugi...
]
Denis Golovin edited comment on JBIDE-12179 at 8/13/12 5:51 PM:
----------------------------------------------------------------
Seems to be fixed in trunk for 3.4.0.M1. Verified for all supported Hibernate versions
3.5, 3.6 and 4.0.
Changes were submitted with fix for Eclipse Juno.
was (Author: dgolovin):
Seems to be fixed in trunk for 3.4.0.M1. Verified for all supported Hibernate versions
3.5, 3.6 and 4.0.
Invalid Error marker when using Hibernate @Type annotation
----------------------------------------------------------
Key: JBIDE-12179
URL: https://issues.jboss.org/browse/JBIDE-12179
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 3.3.0.CR1
Reporter: Corey Puffalt
Assignee: Denis Golovin
Fix For: 3.4.0.M1
We're seeing invalid error markers when using the Hibernate @Type annotation where
the type value we're specifying isn't actually a Class name. This looks like a
bug in JBoss Tools (I have the new Candidate Release installed).
Sample class:
{code}
import javax.persistence.Entity;
import javax.persistence.Id;
import org.hibernate.annotations.Type;
@Entity
public class TestEntity
{
@Id
private Long id;
@Type(type = "yes_no")
private Boolean flag;
}
{code}
The error marker states 'Type class "yes_no" could not be found.' but
this is actually valid.
I did find some similar cases (JBIDE-11364, JBIDE-11368) in the bug tracker but not one
that described this issue exactly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:53 a.m.
[
https://issues.jboss.org/browse/JBIDE-12179?page=com.atlassian.jira.plugi...
]
Denis Golovin resolved JBIDE-12179.
-----------------------------------
Resolution: Done
Invalid Error marker when using Hibernate @Type annotation
----------------------------------------------------------
Key: JBIDE-12179
URL: https://issues.jboss.org/browse/JBIDE-12179
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 3.3.0.CR1
Reporter: Corey Puffalt
Assignee: Denis Golovin
Fix For: 3.4.0.M1
We're seeing invalid error markers when using the Hibernate @Type annotation where
the type value we're specifying isn't actually a Class name. This looks like a
bug in JBoss Tools (I have the new Candidate Release installed).
Sample class:
{code}
import javax.persistence.Entity;
import javax.persistence.Id;
import org.hibernate.annotations.Type;
@Entity
public class TestEntity
{
@Id
private Long id;
@Type(type = "yes_no")
private Boolean flag;
}
{code}
The error marker states 'Type class "yes_no" could not be found.' but
this is actually valid.
I did find some similar cases (JBIDE-11364, JBIDE-11368) in the bug tracker but not one
that described this issue exactly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:06 p.m.
[
https://issues.jboss.org/browse/JBIDE-12179?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-12179:
----------------------------------------
Fix Version/s: 3.3.2
Forum Reference: https://community.jboss.org/message/741828#741828,
https://community.jboss.org/message/741828 (was:
https://community.jboss.org/message/741828#741828,
https://community.jboss.org/message/741828)
Invalid Error marker when using Hibernate @Type annotation
----------------------------------------------------------
Key: JBIDE-12179
URL: https://issues.jboss.org/browse/JBIDE-12179
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 3.3.0.CR1
Reporter: Corey Puffalt
Assignee: Denis Golovin
Fix For: 3.3.2, 3.4.0.M1
We're seeing invalid error markers when using the Hibernate @Type annotation where
the type value we're specifying isn't actually a Class name. This looks like a
bug in JBoss Tools (I have the new Candidate Release installed).
Sample class:
{code}
import javax.persistence.Entity;
import javax.persistence.Id;
import org.hibernate.annotations.Type;
@Entity
public class TestEntity
{
@Id
private Long id;
@Type(type = "yes_no")
private Boolean flag;
}
{code}
The error marker states 'Type class "yes_no" could not be found.' but
this is actually valid.
I did find some similar cases (JBIDE-11364, JBIDE-11368) in the bug tracker but not one
that described this issue exactly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:49 a.m.
[
https://issues.jboss.org/browse/JBIDE-12179?page=com.atlassian.jira.plugi...
]
Denis Golovin commented on JBIDE-12179:
---------------------------------------
Should be possible, here is the patch
{code}
Index: src/org/jboss/tools/hibernate/jpt/core/internal/context/java/TypeImpl.java
===================================================================
--- src/org/jboss/tools/hibernate/jpt/core/internal/context/java/TypeImpl.java (revision
43033)
+++ src/org/jboss/tools/hibernate/jpt/core/internal/context/java/TypeImpl.java (working
copy)
@@ -25,6 +25,7 @@
import org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaJpaContextNode;
import org.eclipse.wst.validation.internal.provisional.core.IMessage;
import org.eclipse.wst.validation.internal.provisional.core.IReporter;
+import org.hibernate.type.TypeFactory;
import org.jboss.tools.hibernate.jpt.core.internal.context.HibernatePersistenceUnit;
import org.jboss.tools.hibernate.jpt.core.internal.context.Messages;
import org.jboss.tools.hibernate.jpt.core.internal.resource.java.TypeAnnotation;
@@ -140,7 +141,7 @@
messages.add(HibernateJpaValidationMessage.buildMessage(
IMessage.HIGH_SEVERITY,
TYPE_CANT_BE_EMPTY, this, range));
- } else if (!getPersistenceUnit().hasTypeDef(type)) {
+ } else if (TypeFactory.basic(type) == null &&
!getPersistenceUnit().hasTypeDef(type)) {
IType lwType = null;
try {
lwType = getJpaProject().getJavaProject().findType(type);
{code}
Invalid Error marker when using Hibernate @Type annotation
----------------------------------------------------------
Key: JBIDE-12179
URL: https://issues.jboss.org/browse/JBIDE-12179
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 3.3.0.CR1
Reporter: Corey Puffalt
Assignee: Denis Golovin
Fix For: 3.3.2, 3.4.0.M1
We're seeing invalid error markers when using the Hibernate @Type annotation where
the type value we're specifying isn't actually a Class name. This looks like a
bug in JBoss Tools (I have the new Candidate Release installed).
Sample class:
{code}
import javax.persistence.Entity;
import javax.persistence.Id;
import org.hibernate.annotations.Type;
@Entity
public class TestEntity
{
@Id
private Long id;
@Type(type = "yes_no")
private Boolean flag;
}
{code}
The error marker states 'Type class "yes_no" could not be found.' but
this is actually valid.
I did find some similar cases (JBIDE-11364, JBIDE-11368) in the bug tracker but not one
that described this issue exactly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:06 a.m.
[
https://issues.jboss.org/browse/JBIDE-12179?page=com.atlassian.jira.plugi...
]
Denis Golovin resolved JBIDE-12179.
-----------------------------------
Resolution: Done
resolved in 3.3.x branch
Invalid Error marker when using Hibernate @Type annotation
----------------------------------------------------------
Key: JBIDE-12179
URL: https://issues.jboss.org/browse/JBIDE-12179
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 3.3.0.CR1
Reporter: Corey Puffalt
Assignee: Denis Golovin
Fix For: 3.3.2, 4.0.0.M1
We're seeing invalid error markers when using the Hibernate @Type annotation where
the type value we're specifying isn't actually a Class name. This looks like a
bug in JBoss Tools (I have the new Candidate Release installed).
Sample class:
{code}
import javax.persistence.Entity;
import javax.persistence.Id;
import org.hibernate.annotations.Type;
@Entity
public class TestEntity
{
@Id
private Long id;
@Type(type = "yes_no")
private Boolean flag;
}
{code}
The error marker states 'Type class "yes_no" could not be found.' but
this is actually valid.
I did find some similar cases (JBIDE-11364, JBIDE-11368) in the bug tracker but not one
that described this issue exactly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:47 p.m.
[
https://issues.jboss.org/browse/JBIDE-12179?page=com.atlassian.jira.plugi...
]
Stephan Vollmer commented on JBIDE-12179:
-----------------------------------------
How can I disable this check and the error message in Eclipse until JBT is updated?
I looked in _Project Propertes / JPA / Errors/Warnings,_ but could not find the
corresponding check.
Invalid Error marker when using Hibernate @Type annotation
----------------------------------------------------------
Key: JBIDE-12179
URL: https://issues.jboss.org/browse/JBIDE-12179
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 3.3.0.CR1
Reporter: Corey Puffalt
Assignee: Denis Golovin
Fix For: 3.3.2, 4.0.0.Alpha1
We're seeing invalid error markers when using the Hibernate @Type annotation where
the type value we're specifying isn't actually a Class name. This looks like a
bug in JBoss Tools (I have the new Candidate Release installed).
Sample class:
{code}
import javax.persistence.Entity;
import javax.persistence.Id;
import org.hibernate.annotations.Type;
@Entity
public class TestEntity
{
@Id
private Long id;
@Type(type = "yes_no")
private Boolean flag;
}
{code}
The error marker states 'Type class "yes_no" could not be found.' but
this is actually valid.
I did find some similar cases (JBIDE-11364, JBIDE-11368) in the bug tracker but not one
that described this issue exactly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:38 a.m.
[
https://issues.jboss.org/browse/JBIDE-12179?page=com.atlassian.jira.plugi...
]
Jiri Peterka commented on JBIDE-12179:
--------------------------------------
Verified in JBT 4.0.0.Alfa1a, L64
Invalid Error marker when using Hibernate @Type annotation
----------------------------------------------------------
Key: JBIDE-12179
URL: https://issues.jboss.org/browse/JBIDE-12179
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 3.3.0.CR1
Reporter: Corey Puffalt
Assignee: Denis Golovin
Fix For: 3.3.2, 4.0.0.Alpha1
We're seeing invalid error markers when using the Hibernate @Type annotation where
the type value we're specifying isn't actually a Class name. This looks like a
bug in JBoss Tools (I have the new Candidate Release installed).
Sample class:
{code}
import javax.persistence.Entity;
import javax.persistence.Id;
import org.hibernate.annotations.Type;
@Entity
public class TestEntity
{
@Id
private Long id;
@Type(type = "yes_no")
private Boolean flag;
}
{code}
The error marker states 'Type class "yes_no" could not be found.' but
this is actually valid.
I did find some similar cases (JBIDE-11364, JBIDE-11368) in the bug tracker but not one
that described this issue exactly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:26 a.m.
[
https://issues.jboss.org/browse/JBIDE-12179?page=com.atlassian.jira.plugi...
]
Denis Golovin commented on JBIDE-12179:
---------------------------------------
There is no way to disable this particular check.
Invalid Error marker when using Hibernate @Type annotation
----------------------------------------------------------
Key: JBIDE-12179
URL: https://issues.jboss.org/browse/JBIDE-12179
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 3.3.0.CR1
Reporter: Corey Puffalt
Assignee: Denis Golovin
Fix For: 3.3.2, 4.0.0.Alpha1
We're seeing invalid error markers when using the Hibernate @Type annotation where
the type value we're specifying isn't actually a Class name. This looks like a
bug in JBoss Tools (I have the new Candidate Release installed).
Sample class:
{code}
import javax.persistence.Entity;
import javax.persistence.Id;
import org.hibernate.annotations.Type;
@Entity
public class TestEntity
{
@Id
private Long id;
@Type(type = "yes_no")
private Boolean flag;
}
{code}
The error marker states 'Type class "yes_no" could not be found.' but
this is actually valid.
I did find some similar cases (JBIDE-11364, JBIDE-11368) in the bug tracker but not one
that described this issue exactly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:50 a.m.
[
https://issues.jboss.org/browse/JBIDE-12179?page=com.atlassian.jira.plugi...
]
Jiri Peterka updated JBIDE-12179:
---------------------------------
Fix Version/s: (was: 4.0.0.Alpha1)
Invalid Error marker when using Hibernate @Type annotation
----------------------------------------------------------
Key: JBIDE-12179
URL: https://issues.jboss.org/browse/JBIDE-12179
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 3.3.0.CR1
Reporter: Corey Puffalt
Assignee: Denis Golovin
Fix For: 3.3.2
We're seeing invalid error markers when using the Hibernate @Type annotation where
the type value we're specifying isn't actually a Class name. This looks like a
bug in JBoss Tools (I have the new Candidate Release installed).
Sample class:
{code}
import javax.persistence.Entity;
import javax.persistence.Id;
import org.hibernate.annotations.Type;
@Entity
public class TestEntity
{
@Id
private Long id;
@Type(type = "yes_no")
private Boolean flag;
}
{code}
The error marker states 'Type class "yes_no" could not be found.' but
this is actually valid.
I did find some similar cases (JBIDE-11364, JBIDE-11368) in the bug tracker but not one
that described this issue exactly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4178
days inactive
4346
days old
jbosstools-issues@lists.jboss.org
16 comments
6 participants
participants (6)
-
Corey Puffalt (JIRA) -
Denis Golovin (JIRA)
-
Jiri Peterka (JIRA)
-
Max Rydahl Andersen (JIRA)
-
SBS JIRA Integration (JIRA)
-
Stephan Vollmer (JIRA)