[Hibernate-JIRA] Created: (HV-456) The MethodValidator could not handle Proxied objects like in EJB environment
8:26 a.m.
The MethodValidator could not handle Proxied objects like in EJB environment
----------------------------------------------------------------------------
Key: HV-456
URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-456
Project: Hibernate Validator
Issue Type: Bug
Components: engine
Affects Versions: 4.2.0.Beta2
Environment: linux, java 1.6.0_24, hibernate-validator-4.2.0.Beta2,
JBoss-5.1.0.GA
Reporter: Ingo Bruell
Using the MethodValidator with proxied objects via an interceptor in an ejb environment
throws the following exception:
javax.validation.ConstraintDeclarationException: Only the root method of an overridden
method in an inheritance hierarchy may be annotated with parameter constraints. The
following method itself has no parameter constraints but it is not defined on a sub-type
of class de.enexoma.smartmeter.server.facade.config.ResourceBundleFacadeBean:
MethodMetaData [method=public abstract java.util.Map
de.enexoma.smartmeter.server.facade.ResourceBundleFacade.get(java.lang.String) throws
de.enexoma.smartmeter.server.error.EnexomaException, parameterMetaData=[ParameterMetaData
[type=class java.lang.String], [index=0], name=arg0], constraints=[], isCascading=false]],
constraints=[], isCascading=false, hasParameterConstraints=false]
The method in the "real" class has constraints defined:
public Map<Locale,List<ResourceBundle>> get(@NotNull @Size(min=1)final String
appName)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:34 p.m.
New subject: [Hibernate-JIRA] Commented: (HV-456) The MethodValidator could not handle Proxied objects like in EJB environment
[
http://opensource.atlassian.com/projects/hibernate/browse/HV-456?page=com...
]
Kevin Pollet commented on HV-456:
---------------------------------
Hi,
First of all thanks for testing Beta2 :)
What do you mean by "real" class ? If it's the implementation class it's
because you have annotated the implementation method {{ResourceBundleFacadeBean#get()}}
and not the contract method {{ResourceBundleFacadeBean#get()}}. As of 4.2.0.Beta1 some
changes have been made on method validation as you can see here HV-421. I think this issue
is a duplicate of HV-448.
Hope this help.
The MethodValidator could not handle Proxied objects like in EJB
environment
----------------------------------------------------------------------------
Key: HV-456
URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-456
Project: Hibernate Validator
Issue Type: Bug
Components: engine
Affects Versions: 4.2.0.Beta2
Environment: linux, java 1.6.0_24, hibernate-validator-4.2.0.Beta2,
JBoss-5.1.0.GA
Reporter: Ingo Bruell
Using the MethodValidator with proxied objects via an interceptor in an ejb environment
throws the following exception:
javax.validation.ConstraintDeclarationException: Only the root method of an overridden
method in an inheritance hierarchy may be annotated with parameter constraints. The
following method itself has no parameter constraints but it is not defined on a sub-type
of class de.enexoma.smartmeter.server.facade.config.ResourceBundleFacadeBean:
MethodMetaData [method=public abstract java.util.Map
de.enexoma.smartmeter.server.facade.ResourceBundleFacade.get(java.lang.String) throws
de.enexoma.smartmeter.server.error.EnexomaException, parameterMetaData=[ParameterMetaData
[type=class java.lang.String], [index=0], name=arg0], constraints=[], isCascading=false]],
constraints=[], isCascading=false, hasParameterConstraints=false]
The method in the "real" class has constraints defined:
public Map<Locale,List<ResourceBundle>> get(@NotNull @Size(min=1)final
String appName)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1 p.m.
New subject: [Hibernate-JIRA] Commented: (HV-456) The MethodValidator could not handle Proxied objects like in EJB environment
[
http://opensource.atlassian.com/projects/hibernate/browse/HV-456?page=com...
]
Gunnar Morling commented on HV-456:
-----------------------------------
Right, only the root method of an overridden method in an inheritance hierarchy may be
annoted with parameter constraints. HV-421 discusses the reason for this in detail. In
case of a session bean the interface (if there is one) must be annotated as Kevin says (I
think {{ResourceBundleFacade}} is the interface here).
If your situation is another one (I'm not sure how proxies/interceptors relate to the
problem) a complete example demonstrating the issue would be very helpful.
The MethodValidator could not handle Proxied objects like in EJB
environment
----------------------------------------------------------------------------
Key: HV-456
URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-456
Project: Hibernate Validator
Issue Type: Bug
Components: engine
Affects Versions: 4.2.0.Beta2
Environment: linux, java 1.6.0_24, hibernate-validator-4.2.0.Beta2,
JBoss-5.1.0.GA
Reporter: Ingo Bruell
Using the MethodValidator with proxied objects via an interceptor in an ejb environment
throws the following exception:
javax.validation.ConstraintDeclarationException: Only the root method of an overridden
method in an inheritance hierarchy may be annotated with parameter constraints. The
following method itself has no parameter constraints but it is not defined on a sub-type
of class de.enexoma.smartmeter.server.facade.config.ResourceBundleFacadeBean:
MethodMetaData [method=public abstract java.util.Map
de.enexoma.smartmeter.server.facade.ResourceBundleFacade.get(java.lang.String) throws
de.enexoma.smartmeter.server.error.EnexomaException, parameterMetaData=[ParameterMetaData
[type=class java.lang.String], [index=0], name=arg0], constraints=[], isCascading=false]],
constraints=[], isCascading=false, hasParameterConstraints=false]
The method in the "real" class has constraints defined:
public Map<Locale,List<ResourceBundle>> get(@NotNull @Size(min=1)final
String appName)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:56 p.m.
New subject: [Hibernate-JIRA] Commented: (HV-456) The MethodValidator could not handle Proxied objects like in EJB environment
[
http://opensource.atlassian.com/projects/hibernate/browse/HV-456?page=com...
]
Kevin Pollet commented on HV-456:
---------------------------------
Maybe we could provide two jar of the AP (the shaded and the original AP jar). I'm
thinking that the shaded is only a "distribution" artifact of the AP to simplify
the user setup in IDEs and the use with the maven annotation plugin (if the shaded jar is
deployed with the original jar). The original jar could be used when the AP is added to
the project class path (like a normal maven dependency). The disadvantage of this approach
is that it can be a source of misuse for the user.
WDYT ?
The MethodValidator could not handle Proxied objects like in EJB
environment
----------------------------------------------------------------------------
Key: HV-456
URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-456
Project: Hibernate Validator
Issue Type: Bug
Components: engine
Affects Versions: 4.2.0.Beta2
Environment: linux, java 1.6.0_24, hibernate-validator-4.2.0.Beta2,
JBoss-5.1.0.GA
Reporter: Ingo Bruell
Using the MethodValidator with proxied objects via an interceptor in an ejb environment
throws the following exception:
javax.validation.ConstraintDeclarationException: Only the root method of an overridden
method in an inheritance hierarchy may be annotated with parameter constraints. The
following method itself has no parameter constraints but it is not defined on a sub-type
of class de.enexoma.smartmeter.server.facade.config.ResourceBundleFacadeBean:
MethodMetaData [method=public abstract java.util.Map
de.enexoma.smartmeter.server.facade.ResourceBundleFacade.get(java.lang.String) throws
de.enexoma.smartmeter.server.error.EnexomaException, parameterMetaData=[ParameterMetaData
[type=class java.lang.String], [index=0], name=arg0], constraints=[], isCascading=false]],
constraints=[], isCascading=false, hasParameterConstraints=false]
The method in the "real" class has constraints defined:
public Map<Locale,List<ResourceBundle>> get(@NotNull @Size(min=1)final
String appName)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2 p.m.
New subject: [Hibernate-JIRA] Commented: (HV-456) The MethodValidator could not handle Proxied objects like in EJB environment
[
http://opensource.atlassian.com/projects/hibernate/browse/HV-456?page=com...
]
Kevin Pollet commented on HV-456:
---------------------------------
Oops, I've replied in the wrong issue :(
The MethodValidator could not handle Proxied objects like in EJB
environment
----------------------------------------------------------------------------
Key: HV-456
URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-456
Project: Hibernate Validator
Issue Type: Bug
Components: engine
Affects Versions: 4.2.0.Beta2
Environment: linux, java 1.6.0_24, hibernate-validator-4.2.0.Beta2,
JBoss-5.1.0.GA
Reporter: Ingo Bruell
Using the MethodValidator with proxied objects via an interceptor in an ejb environment
throws the following exception:
javax.validation.ConstraintDeclarationException: Only the root method of an overridden
method in an inheritance hierarchy may be annotated with parameter constraints. The
following method itself has no parameter constraints but it is not defined on a sub-type
of class de.enexoma.smartmeter.server.facade.config.ResourceBundleFacadeBean:
MethodMetaData [method=public abstract java.util.Map
de.enexoma.smartmeter.server.facade.ResourceBundleFacade.get(java.lang.String) throws
de.enexoma.smartmeter.server.error.EnexomaException, parameterMetaData=[ParameterMetaData
[type=class java.lang.String], [index=0], name=arg0], constraints=[], isCascading=false]],
constraints=[], isCascading=false, hasParameterConstraints=false]
The method in the "real" class has constraints defined:
public Map<Locale,List<ResourceBundle>> get(@NotNull @Size(min=1)final
String appName)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:22 a.m.
New subject: [Hibernate-JIRA] Updated: (HV-456) The MethodValidator could not handle Proxied objects like in EJB environment
[
http://opensource.atlassian.com/projects/hibernate/browse/HV-456?page=com...
]
Hardy Ferentschik updated HV-456:
---------------------------------
Comment: was deleted
(was: Maybe we could provide two jar of the AP (the shaded and the original AP jar).
I'm thinking that the shaded is only a "distribution" artifact of the AP to
simplify the user setup in IDEs and the use with the maven annotation plugin (if the
shaded jar is deployed with the original jar). The original jar could be used when the AP
is added to the project class path (like a normal maven dependency). The disadvantage of
this approach is that it can be a source of misuse for the user.
WDYT ?
)
The MethodValidator could not handle Proxied objects like in EJB
environment
----------------------------------------------------------------------------
Key: HV-456
URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-456
Project: Hibernate Validator
Issue Type: Bug
Components: engine
Affects Versions: 4.2.0.Beta2
Environment: linux, java 1.6.0_24, hibernate-validator-4.2.0.Beta2,
JBoss-5.1.0.GA
Reporter: Ingo Bruell
Using the MethodValidator with proxied objects via an interceptor in an ejb environment
throws the following exception:
javax.validation.ConstraintDeclarationException: Only the root method of an overridden
method in an inheritance hierarchy may be annotated with parameter constraints. The
following method itself has no parameter constraints but it is not defined on a sub-type
of class de.enexoma.smartmeter.server.facade.config.ResourceBundleFacadeBean:
MethodMetaData [method=public abstract java.util.Map
de.enexoma.smartmeter.server.facade.ResourceBundleFacade.get(java.lang.String) throws
de.enexoma.smartmeter.server.error.EnexomaException, parameterMetaData=[ParameterMetaData
[type=class java.lang.String], [index=0], name=arg0], constraints=[], isCascading=false]],
constraints=[], isCascading=false, hasParameterConstraints=false]
The method in the "real" class has constraints defined:
public Map<Locale,List<ResourceBundle>> get(@NotNull @Size(min=1)final
String appName)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:22 a.m.
New subject: [Hibernate-JIRA] Updated: (HV-456) The MethodValidator could not handle Proxied objects like in EJB environment
[
http://opensource.atlassian.com/projects/hibernate/browse/HV-456?page=com...
]
Hardy Ferentschik updated HV-456:
---------------------------------
Comment: was deleted
(was: Oops, I've replied in the wrong issue :()
The MethodValidator could not handle Proxied objects like in EJB
environment
----------------------------------------------------------------------------
Key: HV-456
URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-456
Project: Hibernate Validator
Issue Type: Bug
Components: engine
Affects Versions: 4.2.0.Beta2
Environment: linux, java 1.6.0_24, hibernate-validator-4.2.0.Beta2,
JBoss-5.1.0.GA
Reporter: Ingo Bruell
Using the MethodValidator with proxied objects via an interceptor in an ejb environment
throws the following exception:
javax.validation.ConstraintDeclarationException: Only the root method of an overridden
method in an inheritance hierarchy may be annotated with parameter constraints. The
following method itself has no parameter constraints but it is not defined on a sub-type
of class de.enexoma.smartmeter.server.facade.config.ResourceBundleFacadeBean:
MethodMetaData [method=public abstract java.util.Map
de.enexoma.smartmeter.server.facade.ResourceBundleFacade.get(java.lang.String) throws
de.enexoma.smartmeter.server.error.EnexomaException, parameterMetaData=[ParameterMetaData
[type=class java.lang.String], [index=0], name=arg0], constraints=[], isCascading=false]],
constraints=[], isCascading=false, hasParameterConstraints=false]
The method in the "real" class has constraints defined:
public Map<Locale,List<ResourceBundle>> get(@NotNull @Size(min=1)final
String appName)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:25 a.m.
New subject: [Hibernate-JIRA] Commented: (HV-456) The MethodValidator could not handle Proxied objects like in EJB environment
[
http://opensource.atlassian.com/projects/hibernate/browse/HV-456?page=com...
]
Ingo Bruell commented on HV-456:
--------------------------------
I moved the annotations to the interfaces and it works. Thank you!
The MethodValidator could not handle Proxied objects like in EJB
environment
----------------------------------------------------------------------------
Key: HV-456
URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-456
Project: Hibernate Validator
Issue Type: Bug
Components: engine
Affects Versions: 4.2.0.Beta2
Environment: linux, java 1.6.0_24, hibernate-validator-4.2.0.Beta2,
JBoss-5.1.0.GA
Reporter: Ingo Bruell
Using the MethodValidator with proxied objects via an interceptor in an ejb environment
throws the following exception:
javax.validation.ConstraintDeclarationException: Only the root method of an overridden
method in an inheritance hierarchy may be annotated with parameter constraints. The
following method itself has no parameter constraints but it is not defined on a sub-type
of class de.enexoma.smartmeter.server.facade.config.ResourceBundleFacadeBean:
MethodMetaData [method=public abstract java.util.Map
de.enexoma.smartmeter.server.facade.ResourceBundleFacade.get(java.lang.String) throws
de.enexoma.smartmeter.server.error.EnexomaException, parameterMetaData=[ParameterMetaData
[type=class java.lang.String], [index=0], name=arg0], constraints=[], isCascading=false]],
constraints=[], isCascading=false, hasParameterConstraints=false]
The method in the "real" class has constraints defined:
public Map<Locale,List<ResourceBundle>> get(@NotNull @Size(min=1)final
String appName)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:38 a.m.
New subject: [Hibernate-JIRA] Resolved: (HV-456) The MethodValidator could not handle Proxied objects like in EJB environment
[
http://opensource.atlassian.com/projects/hibernate/browse/HV-456?page=com...
]
Kevin Pollet resolved HV-456.
-----------------------------
Resolution: Fixed
The MethodValidator could not handle Proxied objects like in EJB
environment
----------------------------------------------------------------------------
Key: HV-456
URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-456
Project: Hibernate Validator
Issue Type: Bug
Components: engine
Affects Versions: 4.2.0.Beta2
Environment: linux, java 1.6.0_24, hibernate-validator-4.2.0.Beta2,
JBoss-5.1.0.GA
Reporter: Ingo Bruell
Using the MethodValidator with proxied objects via an interceptor in an ejb environment
throws the following exception:
javax.validation.ConstraintDeclarationException: Only the root method of an overridden
method in an inheritance hierarchy may be annotated with parameter constraints. The
following method itself has no parameter constraints but it is not defined on a sub-type
of class de.enexoma.smartmeter.server.facade.config.ResourceBundleFacadeBean:
MethodMetaData [method=public abstract java.util.Map
de.enexoma.smartmeter.server.facade.ResourceBundleFacade.get(java.lang.String) throws
de.enexoma.smartmeter.server.error.EnexomaException, parameterMetaData=[ParameterMetaData
[type=class java.lang.String], [index=0], name=arg0], constraints=[], isCascading=false]],
constraints=[], isCascading=false, hasParameterConstraints=false]
The method in the "real" class has constraints defined:
public Map<Locale,List<ResourceBundle>> get(@NotNull @Size(min=1)final
String appName)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:40 a.m.
New subject: [Hibernate-JIRA] Resolved: (HV-456) The MethodValidator could not handle Proxied objects like in EJB environment
[
http://opensource.atlassian.com/projects/hibernate/browse/HV-456?page=com...
]
Kevin Pollet resolved HV-456.
-----------------------------
Resolution: Rejected
The MethodValidator could not handle Proxied objects like in EJB
environment
----------------------------------------------------------------------------
Key: HV-456
URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-456
Project: Hibernate Validator
Issue Type: Bug
Components: engine
Affects Versions: 4.2.0.Beta2
Environment: linux, java 1.6.0_24, hibernate-validator-4.2.0.Beta2,
JBoss-5.1.0.GA
Reporter: Ingo Bruell
Using the MethodValidator with proxied objects via an interceptor in an ejb environment
throws the following exception:
javax.validation.ConstraintDeclarationException: Only the root method of an overridden
method in an inheritance hierarchy may be annotated with parameter constraints. The
following method itself has no parameter constraints but it is not defined on a sub-type
of class de.enexoma.smartmeter.server.facade.config.ResourceBundleFacadeBean:
MethodMetaData [method=public abstract java.util.Map
de.enexoma.smartmeter.server.facade.ResourceBundleFacade.get(java.lang.String) throws
de.enexoma.smartmeter.server.error.EnexomaException, parameterMetaData=[ParameterMetaData
[type=class java.lang.String], [index=0], name=arg0], constraints=[], isCascading=false]],
constraints=[], isCascading=false, hasParameterConstraints=false]
The method in the "real" class has constraints defined:
public Map<Locale,List<ResourceBundle>> get(@NotNull @Size(min=1)final
String appName)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:40 a.m.
New subject: [Hibernate-JIRA] Reopened: (HV-456) The MethodValidator could not handle Proxied objects like in EJB environment
[
http://opensource.atlassian.com/projects/hibernate/browse/HV-456?page=com...
]
Kevin Pollet reopened HV-456:
-----------------------------
The MethodValidator could not handle Proxied objects like in EJB
environment
----------------------------------------------------------------------------
Key: HV-456
URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-456
Project: Hibernate Validator
Issue Type: Bug
Components: engine
Affects Versions: 4.2.0.Beta2
Environment: linux, java 1.6.0_24, hibernate-validator-4.2.0.Beta2,
JBoss-5.1.0.GA
Reporter: Ingo Bruell
Using the MethodValidator with proxied objects via an interceptor in an ejb environment
throws the following exception:
javax.validation.ConstraintDeclarationException: Only the root method of an overridden
method in an inheritance hierarchy may be annotated with parameter constraints. The
following method itself has no parameter constraints but it is not defined on a sub-type
of class de.enexoma.smartmeter.server.facade.config.ResourceBundleFacadeBean:
MethodMetaData [method=public abstract java.util.Map
de.enexoma.smartmeter.server.facade.ResourceBundleFacade.get(java.lang.String) throws
de.enexoma.smartmeter.server.error.EnexomaException, parameterMetaData=[ParameterMetaData
[type=class java.lang.String], [index=0], name=arg0], constraints=[], isCascading=false]],
constraints=[], isCascading=false, hasParameterConstraints=false]
The method in the "real" class has constraints defined:
public Map<Locale,List<ResourceBundle>> get(@NotNull @Size(min=1)final
String appName)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:16 a.m.
New subject: [Hibernate-JIRA] (HV-456) The MethodValidator could not handle Proxied objects like in EJB environment
4269
days inactive
4853
days old
hibernate-issues@lists.jboss.org
11 comments
5 participants
participants (5)
-
Andrei Serea (JIRA) -
Gunnar Morling (JIRA)
-
Hardy Ferentschik (JIRA)
-
Ingo Bruell (JIRA)
-
Kevin Pollet (JIRA)