[
http://jira.jboss.com/jira/browse/JBSEAM-1626?page=all ]
Norman Richards closed JBSEAM-1626.
-----------------------------------
Resolution: Done
This is not a problem with Seam proxied classes - only for EJB3 components. In the case
of EJB components, the proxy implements the business interfaces and there is no way to
navigate to the bean class from the business interface. In these cases, I extended
validators to try and determine the business class from the seam component that implements
that interface. Obviously this assumes only one implementation.
As a side note, the validators cache will probably fail in the case of hot redeployment,
but since EJB3 components and entities are not yet hot deployable, that's not an issue
yet.,
Validation and non-entity components
------------------------------------
Key: JBSEAM-1626
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1626
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.0.0.BETA1
Environment: jboss 4.2 jboss 2.0.0.B1
Reporter: Zalder R
Assigned To: Norman Richards
Priority: Critical
Fix For: 2.0.0.CR1
a simple seam backing bean (not an entity bean) with hib validators allow non valid
expression input (ie does not work) :
eg :
@AssertTrue
private boolean agreeTos;
public boolean isAgreeTos() {
return agreeTos;
}
public void setAgreeTos(boolean agreeTos) {
this.agreeTos = agreeTos;
}
the @AssertTrue does not work anymore (this worked in seam 1.2) ...
--
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