[GLASSFISH-1398] Bad error message for failure in CmpFieldsAccessorExposition test Created: 30/Oct/06  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: verifier
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: wfay Assignee: Sanjeeb Sahoo
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 1,398

 Description   

Failure reported by verifier:
Test Name : tests.ejb.entity.cmp2.CmpFieldsAccessorExposition
Test Assertion : Set accessor method for primary key fields should not be
exposed in the remote interface.
Test Description : For [ C:\dev\glassfish\glassfish-v2-b22\domains\domain1
\applications\j2ee-modules\ejb-1#PD ]
Error: Primary key field set accessor method [ id ] is exposed through the
remote interface [ ejb.entity.pd.PDLocal ].

The error is correct, I did have a few setXXX methods including setId in my
interface, but it was actually my LOCAL interface (as correctly identified
PDLocal) and not the remote interface PDRemote.

The problem is in LocalStrings.properties and in the test itself. The test does
not really look to see if this is a local or remote interface (extends
EJBLocalObject vs EJBObject) but instead always reports "through the remote
interface".

Ideally this test would determine if it was in fact a local or remote interface
and remote properly. A relatively minor issue but it had me scratching my head
for a while last week!

com.sun.enterprise.tools.verifier.tests.ejb.entity.cmp2.CmpFieldsAccessorExposit
ion.failed=\
Error: Primary key field set accessor method [

{0} ] is exposed through the
remote interface [ {1} ].
com.sun.enterprise.tools.verifier.tests.ejb.entity.cmp2.CmpFieldsAccessorExposit
ion.passed=\
Primary key field set accessor method [ {0}

] is not exposed through the remote
interface [

{1}

].



 Comments   
Comment by gfbugbridge [ 17/Jan/07 ]

<BT6514430>

Comment by Sanjeeb Sahoo [ 19/Feb/07 ]

Won't fix in V2 because CMP is not that important in Java EE stack any more.

– Sahoo

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

Generated at Tue Apr 28 12:04:53 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.