Re: Re: some problems with EAR deployment

Hi Florent,

Thank you, for your quick answer,
you were right, I was formated persistence.xml file with
Eclipse-formating, that format body, start and end
provider's tags in different rows.  When I set all in the
one row without  blanks/whitespaces chars ... deployment was
successful.

By the way, when I made this tests I noticed one strange
d-effect.
When I made some changes in classes in the web-tier (in my
WAR-file in EAR) and redeploy EAR (EAR file contains one JAR
file (entity and session beans) and one WAR file) file –
redeploy processing work without problems, but when I
invoked over web-page session bean that  use entity bean, I
received ClassCastException in my session bean - that is not
changed and work without problems before redeploy. My
session bean contains following code in business method that
– throws Exception :
 
public  RBEntity getFirstRB(...) { 
....
List<RBEntity> rb;
...
rb = (List<RBEntity>) query.getResultList();
...
return rb.get(0);             <--- this is place that
throws  ClassCastException
}

After exception when I restart Tomcat-EasyBeans server or
restart after redeploy - all work without problems !

I have one question for access of  local-session bean from
web-tier. I see in your example  - code
...
(SBLocal) initialContext.lookup(SB.class.getName() +
"_" + SBLocal.class.getName() + "Local")
...
that use InitialContext to do this. This work well. 
I try as well to inject session bean with EJB –
annotation, but annotated session-object is null.

Is released this annotation-injection in M6-version of
EasyBeans ?

That is all for today. 

Regards,
G.Dimitrov


>Hi Georgi,
>
>I think that there is a missing trim() call in EasyBeans
for the XML property of the Persistence >provider. (that
needs to be fixed).
>Could you set the persistence provider without any extra
blanks/whitespaces ?

>For your other post, specification is allowing this
case, so EasyBeans needs to be improved on this >part.
>
>Regards,
>
>Florent 

     Hi Georgi,

Sorry, I forgot to answer to your mail.


g_dimitrovxsmail.com wrote:
> Hi Florent,
>
> Thank you, for your quick answer,
> you were right, I was formated persistence.xml file
with Eclipse-formating, that format body, start and end
provider's tags in different rows.  When I set all in the
one row without  blanks/whitespaces chars ... deployment was
successful.
>   
This is fixed in the current SVN version/nightly build of
EasyBeans 
(also there are new tests about this).

> By the way, when I made this tests I noticed one
strange d-effect.
> When I made some changes in classes in the web-tier (in
my WAR-file in EAR) and redeploy EAR (EAR file contains one
JAR file (entity and session beans) and one WAR file) file –
redeploy processing work without problems, but when I
invoked over web-page session bean that  use entity bean, I
received ClassCastException in my session bean - that is not
changed and work without problems before redeploy. My
session bean contains following code in business method that
– throws Exception :
> [...]
> After exception when I restart Tomcat-EasyBeans server
or restart after redeploy - all work without problems !
>   
Well, I need to reproduce this test case in order to tell
you what is 
happening.

> I have one question for access of  local-session bean
from web-tier. I see in your example  - code
> ...
> (SBLocal) initialContext.lookup(SB.class.getName() +
"_" + SBLocal.class.getName() + "Local")
> ...
> that use InitialContext to do this. This work well. 
> I try as well to inject session bean with EJB –
annotation, but annotated session-object is null.
>
> Is released this annotation-injection in M6-version of
EasyBeans ?
>   
In this version of EasyBeans, there is no handling of EJB for
the 
WebContainer part.
The EJB in servlets are handled by Tomcat but there is no
hook yet 
between Tomcat and EasyBeans about this.

Best Regards,

Florent