Hello Roman, EJB 1.x class method throwing RemoteException will be marked as warning since build #637 Thank you for report -- regards, Alexey Kudravtsev. JetBrains, Inc http://www.intellij.com "Develop with pleasure!"
PS Could you please post EJB related messages to the j2ee group ?
Please, make the highlighting of EJB-specific errors customizable. I'm particulary worried by the "throws RemoteException" being highlighted as
an
error by IDEA. We have EJB 1.1 code where this is legal (even though deprecated) and I don't like to see it's being highlighted as an error in all my business methods. I'd like to be able to turn off highlighting of this specific error (which is not an error in EJB 1.1 !!!)
Hello Roman, EJB 1.x class method throwing RemoteException will be marked as warning since build #637
That is much better. But even better is to have an option to turn even warning off, because we have no way to elegantly get rid of those bugging warnings/errors:
In EJB 1.x Local interfaces does not exist, thus you have to always call other beans via remote interfaces that throw RemoteException. If we write code to catch and wrap those remote exceptions everywhere, our code will simply look ugly. We don't want to do that. There's no other way to write elegant EJB 1.x beans as to declare their business methods to throw RemoteException.
Hello Roman,
EJB 1.x class method throwing RemoteException will be marked as warning
since build #637
Thank you for report
--
regards,
Alexey Kudravtsev.
JetBrains, Inc
http://www.intellij.com
"Develop with pleasure!"
PS Could you please post EJB related messages to the j2ee group ?
"Roman Elizarov" <elizarov@acm.org> wrote in message
news:ah36re$r9c$1@is.intellij.net...
>
an
>
>
>
>
That is much better. But even better is to have an option to turn even
warning off, because we have no way to elegantly get rid of those bugging
warnings/errors:
In EJB 1.x Local interfaces does not exist, thus you have to always call
other beans via remote interfaces that throw RemoteException. If we write
code to catch and wrap those remote exceptions everywhere, our code will
simply look ugly. We don't want to do that. There's no other way to write
elegant EJB 1.x beans as to declare their business methods to throw
RemoteException.
Roman Elizarov