[EJB 3.0 Development] New message: "Re: Externalizing Scope: Resolving EJB References and Endpoints"
by Pete Muir
User development,
A new message was posted in the thread "Externalizing Scope: Resolving EJB References and Endpoints":
http://community.jboss.org/message/523217#523217
Author : Pete Muir
Profile : http://community.jboss.org/people/petemuir
Message:
--------------------------------------------------------------
The motivation for this is to allow Weld to cluster with EJBs in JBoss AS - currently it won't work.
CDI specifies the session and conversations contexts as being passivation capable, both of which are ultimately backed by the HTTP session. The appraoch Weld uses with Managed Beans is to put an object into the HTTP session which references both the Bean (the metadata) and the contextual instance. We take the same approach with EJBs - except that in this case the contextual instance contains not the "real" instance, but a SessionObjectReference which Weld uses to retrieve the underly EJB.
I'm not fussed how we solve this problem, whether by changing the way Weld works, or adding something to EJB 3. I don't have a good idea how to change this in Weld tho ;-)
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/523217#523217
16 years, 2 months
[EJB 3.0] New message: "Re: EJB3 slower than EJB2"
by No Name
User development,
A new message was posted in the thread "EJB3 slower than EJB2":
http://community.jboss.org/message/523211#523211
Author : No Name
Profile : http://community.jboss.org/people/ekric
Message:
--------------------------------------------------------------
Okay. The answer is clear, it has something to do with the traffic caused by the Server and it's protocols and has nothing to do with the programming model.
I allready thought about doing some other tests, that show that the new Implementations used aren't slower.
But it was my task to do exactly these tests. So I was the unlucky one to find that bottleneck...
Would you advise me to do some other tests? If yes, which ones would you do?
Thank you and have a nice sunday evening.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/523211#523211
16 years, 2 months
[EJB 3.0] New message: "Re: EJB3 slower than EJB2"
by Andrew Rubinger
User development,
A new message was posted in the thread "EJB3 slower than EJB2":
http://community.jboss.org/message/523208#523208
Author : Andrew Rubinger
Profile : http://community.jboss.org/people/ALRubinger
Message:
--------------------------------------------------------------
> ekric wrote:
>
> Thank you for your reply.
>
> Is there a chance for me to test that new implementation?
>
> I'm at the moment working on my bachelor thesis: Migrating from EJB2 to EJB3.
>
> At this point of my testing work it's hard to explain why EJB3 is slower, while we thought it should be faster.
>
> Any Ideas?
>
> Thank you very much.
Unfortunately we don't yet have this in place to test. Requires some more discussion, work/coding, then integration.
As a general issue though:
What would lead you to conclude that EJB3 is necessarily faster than EJB2? They're different specification versions of a programming model, and speed is a function of the underlying implementation. In many scenarios we've found that our EJB3 implementation is faster than in previous versions, and we work to improve this as time goes on. This case here is clearly slower, but that's not a function of the programming model itself.
S,
ALR
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/523208#523208
16 years, 2 months
[EJB 3.0] New message: "Re: EJB3 slower than EJB2"
by No Name
User development,
A new message was posted in the thread "EJB3 slower than EJB2":
http://community.jboss.org/message/523203#523203
Author : No Name
Profile : http://community.jboss.org/people/ekric
Message:
--------------------------------------------------------------
Thanks for your respond. What difference do you mean? It takes longer (almost twice as long) for the 10000 creates to finish in EJB3.
As you can see in my first post.
I'm using normal Entity Beans in both Versions.
*EJB3:*
+package de.ibs.profi.hilfetext;+
+import java.sql.Date;+
+import javax.persistence.Column;
import javax.persistence.Entity;
import javax.persistence.Id;
import javax.persistence.Table;
import javax.persistence.Transient;+
+@Table(name = "...")
@Entity(name = "...")
public class ...$$$ implements java.io.Serializable {+
+ /**
* private static final long serialVersionUID = -5953089278565486983L;
*/+
+ boolean bLocked;
private Integer id;
...
+
+ public void setBLocked(boolean bLocked) {
this.bLocked = bLocked;
}+
+
+
+ ...
+
+ @Id
@Column(name = "ID")
public Integer getId() {
return id;
}+
+ @Transient
public boolean getBLocked() {
return bLocked;
}+
+ ...
}+
*EJB2:*
+package ...;+
+import javax.ejb.EJBLocalObject;
import java.sql.Date;+
+public interface ... extends EJBLocalObject {+
+ public void setBLocked(boolean bLocked);+
+ public boolean getBLocked();
+
+ ...+
+}+
+
+
+package de.ibs.pakt.hilfetext;+
+import javax.ejb.EntityBean;
import javax.ejb.EntityContext;
import javax.ejb.CreateException;
import javax.ejb.RemoveException;
import java.sql.Date;
import javax.ejb.FinderException;
import java.util.Collection;+
+public abstract class ...Bean implements EntityBean {+
+ EntityContext entityContext;
boolean bLocked;+
+ public Integer ejbCreate() throws CreateException {
+
+...+
+}+
I hope that answers your question.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/523203#523203
16 years, 2 months
