Re: @EJB annotation during junit testing doesn't work

2008-12-03 Thread jolero

The problem is:
- when running hosted mode manually I can specify -noserver mode with
address of server where my server side is deployed instead of embedded
Tomcat
- TestRunner fires hosted mode without this option and I haven't found
how can I make it to call hosted mode with additional parameters.
Does anybody know how to do that?

On Dec 1, 12:24 pm, jolero [EMAIL PROTECTED] wrote:
 Hello
 Thanks for your reply

 The thing is when I run hosted mode everything works fine.
 Hosted mode runs gwt embedded instance of tomcat, so does GWTTestCase.
 This is why I believed it was connected with GWT.

 Anyway, in this situation, how can I run tests in the container?

 On Nov 30, 12:37 am, medgey [EMAIL PROTECTED] wrote:

  If you are running outside of a container then you will need to
  instantiate your EJBs yourself ('new).  This is unrelated to GWT.

  On Nov 27, 7:53 am, jolero [EMAIL PROTECTED] wrote:

   Hello everybody.

   While developing junit tests in GWT app I have stucked on a problem
   that I cannot solve for couple of days now.
   In normal runtime I can normally call RPC services that use JPA
   (Toplink and Glassfish Appserver) for data access purposes, but during
   Junit tests (My tests extends GWTTestCase and use delayTestFinish and
   finishTest for asynchronous calls as described in GWT documentation)
   RPC methods that use injected objects are failing with
   NullPointerException. In other words @EJB annotatnion doesn't work,
   Beans are not injected and references to them are nulls.

   Have anybody had that issue? Does anybody know a solution? Thx in
   advance.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---



Re: @EJB annotation during junit testing doesn't work

2008-12-01 Thread jolero

Hello
Thanks for your reply

The thing is when I run hosted mode everything works fine.
Hosted mode runs gwt embedded instance of tomcat, so does GWTTestCase.
This is why I believed it was connected with GWT.

Anyway, in this situation, how can I run tests in the container?

On Nov 30, 12:37 am, medgey [EMAIL PROTECTED] wrote:
 If you are running outside of a container then you will need to
 instantiate your EJBs yourself ('new).  This is unrelated to GWT.

 On Nov 27, 7:53 am, jolero [EMAIL PROTECTED] wrote:

  Hello everybody.

  While developing junit tests in GWT app I have stucked on a problem
  that I cannot solve for couple of days now.
  In normal runtime I can normally call RPC services that use JPA
  (Toplink and Glassfish Appserver) for data access purposes, but during
  Junit tests (My tests extends GWTTestCase and use delayTestFinish and
  finishTest for asynchronous calls as described in GWT documentation)
  RPC methods that use injected objects are failing with
  NullPointerException. In other words @EJB annotatnion doesn't work,
  Beans are not injected and references to them are nulls.

  Have anybody had that issue? Does anybody know a solution? Thx in
  advance.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---



Re: @EJB annotation during junit testing doesn't work

2008-11-29 Thread medgey

If you are running outside of a container then you will need to
instantiate your EJBs yourself ('new).  This is unrelated to GWT.

On Nov 27, 7:53 am, jolero [EMAIL PROTECTED] wrote:
 Hello everybody.

 While developing junit tests in GWT app I have stucked on a problem
 that I cannot solve for couple of days now.
 In normal runtime I can normally call RPC services that use JPA
 (Toplink and Glassfish Appserver) for data access purposes, but during
 Junit tests (My tests extends GWTTestCase and use delayTestFinish and
 finishTest for asynchronous calls as described in GWT documentation)
 RPC methods that use injected objects are failing with
 NullPointerException. In other words @EJB annotatnion doesn't work,
 Beans are not injected and references to them are nulls.

 Have anybody had that issue? Does anybody know a solution? Thx in
 advance.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---



@EJB annotation during junit testing doesn't work

2008-11-27 Thread jolero

Hello everybody.

While developing junit tests in GWT app I have stucked on a problem
that I cannot solve for couple of days now.
In normal runtime I can normally call RPC services that use JPA
(Toplink and Glassfish Appserver) for data access purposes, but during
Junit tests (My tests extends GWTTestCase and use delayTestFinish and
finishTest for asynchronous calls as described in GWT documentation)
RPC methods that use injected objects are failing with
NullPointerException. In other words @EJB annotatnion doesn't work,
Beans are not injected and references to them are nulls.

Have anybody had that issue? Does anybody know a solution? Thx in
advance.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---