Is there any particular reason why the property setters are restricted to
having a 'void' return type?
It is sometimes convenient to have a class like:
| @Name(user)
| public class User {
| private String username;
| private String password;
|
| public String getUsername() {
Are there plans to make Seam an integral component of JBoss Tools in the near
future? An integration which does away with the awkward Seam-Gen in favour of
more integrated Eclipse capabilities?
I strongly believe that if/when this happens, there will be a huge increase in
adoption of Seam. Un
"[EMAIL PROTECTED]" wrote : Component.getInstance("entityManager")
|
Unfortunately that doesn' t work, at least not on its own. Is there some
additional initialization code that needs to be added to the test class for
this to work?
| FAILED: theTest
| java.lang.IllegalStateException: N
Thanks Gavin. Would you agree that this would be a useful thing to be able to
do, or is there a better way to write unit tests that need to access to the
EntityManager?
I'm not sure exactly how the annotations are implemented but your reply seems
to imply that the @In would only be looked at w
I'm trying to cause the EntityManager to be injected into a unit test class
running via TestNG, but am having no luck. I'm hoping someone here can shed
some light as to why.
Here's the steps I took (using Seam 1.2.1GA, JBoss4.2.0GA, JBossIDE 2.0.0Beta2)
| 1. "seam setup" to create a brand ne
