Re: [JBoss-dev] Is the verifier too restrictive?

2002-08-20 Thread Scott M Stark

Yes, the subclasses of RuntimeException and Error should not be checked
for in the bean interfaces.


Scott Stark
Chief Technology Officer
JBoss Group, LLC

- Original Message -
From: Ole Husgaard [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, August 20, 2002 2:02 AM
Subject: [JBoss-dev] Is the verifier too restrictive?


 Hi,

 In the testsuite, in the JCA test, the verifier warns:
   2002-08-19 16:51:14,760 WARN  [org.jboss.ejb.EJBDeployer.verifier] EJB
spec violation:
   Bean   : Teller
   Method : public abstract Account createAccount(Integer) throws
RemoteException
   Section: 7.10.5
   Warning: All the exceptions defined in the throws clause of the matching
method of the session beanclass must be defined in the throws clause of
the method of the
 remote interface.

 Reason for this is that the Teller implementation declares
 EJBException to be thrown from this method.
 The remote interface is generated by EJBDoclet, and EJBDoclet
 does not declare EJBException to be thrown there, since it
 is not needed to declare a RuntimeException.

 Fixing that problem is trivial, but:
 I wonder if the verifier is too restrictive here, and if it
 would be better if the verifier ignored all Throwable that
 do not need to be declared before comparing declared
 exceptions.

 What do you think?


 Best Regards,

 Ole Husgaard.


 ---
 This sf.net email is sponsored by: OSDN - Tired of that same old
 cell phone?  Get a new here for FREE!
 https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development




---
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] Is the verifier too restrictive?

2002-08-20 Thread Christian Riege

hi,

i applied a change in 3.2 and HEAD that doesn't check these in the
interfaces anymore.

regards,
christian


On Tue, 2002-08-20 at 15:36, Scott M Stark wrote:
 Yes, the subclasses of RuntimeException and Error should not be checked
 for in the bean interfaces.
 
 
 Scott Stark
 Chief Technology Officer
 JBoss Group, LLC
 
 - Original Message -
 From: Ole Husgaard [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Tuesday, August 20, 2002 2:02 AM
 Subject: [JBoss-dev] Is the verifier too restrictive?
 
 
  Hi,
 
  In the testsuite, in the JCA test, the verifier warns:
2002-08-19 16:51:14,760 WARN  [org.jboss.ejb.EJBDeployer.verifier] EJB
 spec violation:
Bean   : Teller
Method : public abstract Account createAccount(Integer) throws
 RemoteException
Section: 7.10.5
Warning: All the exceptions defined in the throws clause of the matching
 method of the session beanclass must be defined in the throws clause of
 the method of the
  remote interface.
 
  Reason for this is that the Teller implementation declares
  EJBException to be thrown from this method.
  The remote interface is generated by EJBDoclet, and EJBDoclet
  does not declare EJBException to be thrown there, since it
  is not needed to declare a RuntimeException.
 
  Fixing that problem is trivial, but:
  I wonder if the verifier is too restrictive here, and if it
  would be better if the verifier ignored all Throwable that
  do not need to be declared before comparing declared
  exceptions.
 
  What do you think?
 
 
  Best Regards,
 
  Ole Husgaard.
 
 
  ---
  This sf.net email is sponsored by: OSDN - Tired of that same old
  cell phone?  Get a new here for FREE!
  https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 
 
 
 ---
 This sf.net email is sponsored by: OSDN - Tired of that same old
 cell phone?  Get a new here for FREE!
 https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
-- 
Riege Software International GmbH Phone: +49 (2159) 91 48 - 0
Mollsfeld 10  Fax  : +49 (2159) 91 48 - 11
40670 Meerbusch, Germany  http://www.riege.com/



---
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] Is the verifier too restrictive?

2002-08-19 Thread Ole Husgaard

Hi,

In the testsuite, in the JCA test, the verifier warns:
  2002-08-19 16:51:14,760 WARN  [org.jboss.ejb.EJBDeployer.verifier] EJB spec 
violation: 
  Bean   : Teller
  Method : public abstract Account createAccount(Integer) throws RemoteException
  Section: 7.10.5
  Warning: All the exceptions defined in the throws clause of the matching method of 
the session beanclass must be defined in the throws clause of the method of the
remote interface.

Reason for this is that the Teller implementation declares
EJBException to be thrown from this method.
The remote interface is generated by EJBDoclet, and EJBDoclet
does not declare EJBException to be thrown there, since it
is not needed to declare a RuntimeException.

Fixing that problem is trivial, but:
I wonder if the verifier is too restrictive here, and if it
would be better if the verifier ignored all Throwable that
do not need to be declared before comparing declared
exceptions.

What do you think?


Best Regards,

Ole Husgaard.


---
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development