Could you write in the kind of JARs added and also the exact error message
you are getting?
===
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message signoff EJB-INTEREST. For general help,
Hi,
Can you please post what version of Weblogic are you using? I tried this
with WLS 9.1 version and it works fine for both cluster and standalone
server.
Thanks
===
To unsubscribe, send email to [EMAIL PROTECTED] and
It works neither in a cluster or in a
standalone server.
From: Saini, Deepak
Sent: Thursday, March 16, 2006
2:37 PM
To: Saini, Deepak
Subject: A question
Hi,
The class CachingLocalHome in Weblogic provides methods to
invalidate the read only entity bean instances. For
We currently have a DAO class contained in a common utility
jar within our EAR file. Up to this point most of our
Databases access has occurred through the use of entity
beans, but we're looking to move more to DAOs. Here is the problem:
While using entity beans, we employed a
that this answers your doubts on Entity Bean's performce.
AK.
- Original Message -
From: Dave Glasser [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, September 11, 2002 11:39 PM
Subject: Re: Newbie question: What is the benefit from Entity Beans?
On Sun, 8 Sep 2002 19:29:58 +0200, Kriss
On Sun, 8 Sep 2002 19:29:58 +0200, Kriss [EMAIL PROTECTED] wrote:
Hi all,
after having read some books and articles about ejb, I am wondering what´s
the benefit from [BMP]
Entity Beans and what would one loose if completely leaving them out.
I asked this same question here a while back and
JavaBeans development
[mailto:[EMAIL PROTECTED]] On Behalf Of Dave Glasser
Sent: Thursday, September 12, 2002 4:39 AM
To: [EMAIL PROTECTED]
Subject: Re: Newbie question: What is the benefit from Entity Beans?
On Sun, 8 Sep 2002 19:29:58 +0200, Kriss [EMAIL PROTECTED] wrote:
Hi all,
after
that is not an option - I gues my question can be
generalised like this - if a stateless session bean
takes resource like a db connection or jms
session/producers - then how does it make sure it can
close it?
Taking the resource locally and using it and then
closing it in a finally block is not
Bhattacharyya
Sent: Monday, August 12, 2002 2:31 PM
To: [EMAIL PROTECTED]
Subject: Re: ejbRemove question for StatelessSession bean
that is not an option - I gues my question can be
generalised like this - if a stateless session bean
takes resource like a db connection or jms
session
Anamitra,
According to the 2.0 spec, the only state transition from the method
ready pool to does not exist state requires that the ejbRemove method be
called. So your ejb container does not comply with the spec. Section
7.8.3 explicitly states that exceptions result in the transition to the
Of course, Chapter 18 contradicts this by saying that the container must
not call any call back methods when discarding an instance due to an
system exception. However, section 18.3.7 states that all resources
obtained from resource factories declared in the bean environment must
be released.
Hi Victor
thats a good point - So it seems that only those
resourses obtained from the resource factories
declared in the bean env will be released by the
container. But unfortunately mine is not - so I guess
I will have to think of another solution.
thanks
Anamitra
--- Victor Langelo [EMAIL
Title: Re: ejbRemove question for StatelessSession bean
What about using the finalize() method ?
Benjamin
Anamitra Bhattacharyya a écrit :
Hi Victor
thats a good point - So it seems that only those
resourses obtained from the resource factories
declared in the bean env
yeah - maybe I should consider that - or maybe create
my own pool of sessions.
thanks
Anamitra
--- Benjamin BONNET
[EMAIL PROTECTED] wrote:
What about using the finalize() method ?
Benjamin
Anamitra Bhattacharyya a écrit :
Hi Victor
thats a good point - So it seems that only those
Hi Anamitra,
Thanks for bring up this problem, which has bothered me too.
Not only with SLSB's but with all type of enterprise beans, because a system
exception from an enterprise bean will always make the container discard the
bean without calling ejbRemove or another callback method.
My best
I completely agree with you - and SUN should do
something to revise their spec for this. Whats the
pupose of an ejbRemove if I still have to have
finalize blocks or have to catch RuntimeExceptions in
an EJB framework?
Anamitra
--- Hardy Henneberg [EMAIL PROTECTED] wrote:
Hi Anamitra,
Thanks for
1. If the single method call involves multiple transactions
then instead of using multiple transactions in a single method call,
it is better to break the method into multiple methods,
with each of the multiple methods having its own container-managed
transaction.
Use 2 session
Amit,
You should never invoke Container callback methods from your
bean code. If your AppServer supports the Transaction Commit
Option C (we do :), then beans in the transactional state
(where business methods are executed) will return to the pool
at the end of the transaction. For beans to move
triggered programmatically by a bean
developer.
-krish
-Original Message-
From: A mailing list for Enterprise JavaBeans development
[mailto:[EMAIL PROTECTED]]On Behalf Of Amit Kumar
Sent: Friday, August 02, 2002 3:46 PM
To: [EMAIL PROTECTED]
Subject: Re: corected question on ejbActivate
in the create cycle
is that those instance specific things would be looked up as part of the
create method.
hth
cheers
dim
- Original Message -
From: Krishnan Subramanian [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, August 03, 2002 12:43 AM
Subject: Re: corected question
For one thing when you use the session facade you can use a local
interface for the entity. Also your session bean can act as a controller
for subsequent calls to other entity beans.
===
To unsubscribe, send email to [EMAIL
Possibly a CLASSPATH problem, where you have an older class of Business that did not
implement Serializable, which WL Classloader is picking up instead of the new one.
Try deleting all your classes, recompile, check the CLASSPATH of WL startup, and even
put
debug code in your SLSB
1 --- It depends upon trans-attribute of entity bean B, if it is required
or supported, EJB will execute entity bean B in same transaction of entity
bean A
2 --- Assuming entity bean B is not executing in same transaction context
of entity bean B, it will not affect the transaction of entity
in Entity Bean B
there is none as it is a Bean Managed Transaction
Correct me if I'm wrong.
Thanks
Nanik
From: Vikrama Ditya [EMAIL PROTECTED]
Reply-To: Vikrama Ditya [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Transaction question...
Date: Tue, 19 Feb 2002 16:53:53 -0800
1 --- It depends upon
, February 19, 2002 5:58 PM
To: [EMAIL PROTECTED]
Subject: Re: Transaction question...
Hi Vikram,
Thanks for the reply, but as you the transaction in Entity Bean B is Bean
Managed Transaction and not Container Managed Transaction, as you mention
that it all depends on the trans-attribute of the bean
list for Enterprise JavaBeans development
[mailto:[EMAIL PROTECTED]]On Behalf Of Biske, Todd
Sent: Friday, January 25, 2002 6:35 AM
To: [EMAIL PROTECTED]
Subject: Re: SFSB Question
The initialization parameter that's needed is a logging context object
that allows us to use the NDC in log4j
for Enterprise JavaBeans development
[mailto:[EMAIL PROTECTED]]On Behalf Of Toby Weston
Sent: den 28 januari 2002 15:57
To: [EMAIL PROTECTED]
Subject: Re: SFSB Question
I keep coming across this problem. Usually I solve it by passing parameters
to all methods in a SLSB.
However in EJB 1.0, I seem
Title: RE: SFSB Question
The initialization parameter that's needed is a logging context object that allows us to use the NDC in log4j across VM's. An example would be where we want the session id or user id associated with an HTTP request to be prepended to all log messages generated
Title: RE: SFSB Question
Passing a parameter in to stateless session bean will not help you, since
the container is free to pool the beans as it wishes. So when you are
doing an Home.create() call the container is simply picking on of existing free
session bean objects from it's pool. If you
Use an entity bean with BMP.
Take all the data you wanted to pass as a parameter, make a
primary key class containing that data.
ejbLoad/ejbStore can be empty, as you don't need any persistent fields.
In your business methods where you want to access the data that was passed
to ejbCreate, call
Title: SFSB Question
Stateless session beans imply that they cannot hold a state that is of
any meaning to the client. Thus it does not make sense for the client to
try to pass in any kind of initialization parameter. If you want to pass
extra information into the session, that should be
??
- Rajeev Dave
-Original Message-
From: Evan Ireland [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 25, 2002 4:39 AM
To: [EMAIL PROTECTED]
Subject: Re: SFSB Question
Use an entity bean with BMP.
Take all the data you wanted to pass as a parameter, make a
primary key class containing
how do you delete the article? from what you've said, I'm guessing the
session bean does a sql delete? if thats the case, then you're not using
it properly. the container will throw a NoSuchObjectException if there is
an entity bean in memory, but the record has been deleted from the
database.
The ArticleEJB is a CMP entitybean,so the remove() method is empty.
and ArticleManagerEJB is a sessionbean, he call the ArticleEJB's remove to delete a
article from database,the source code is :
public void deleteArticle(long id){
Article article;
try{
article = articleHome.findByPrimaryKey(new
hmmm... that is odd... not sure I'm going to be able to offer any more
immediately... from what I understand of what you're describing it all
should be ok...
both methods are in the session bean right? what app server are you
running on?
cheers
dim
On Mon, 3 Dec 2001, sharetop YC wrote:
The
keep the discussion ont he list so all can benefit (o:
On Tue, 4 Dec 2001, sharetop wrote:
Yes, deleteArticle() in the ManagerEJB( a stateful sessionbean) and
list() in the ShowerEJB(a stateless sessionbean).
I use the j2sdkee1.3,and database is mysql.what matter with them?
I dont know -
EJBException is a runtime exception. So why do you need to mention it in
throws clause of method signature.
regards
Nikhil.
-Original Message-
From: Cornel Antohi [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 17, 2001 3:20 PM
To: [EMAIL PROTECTED]
Subject: PetStore question
Visual Age tells me that it can't compile the sources because the exception
is not declared
- Original Message -
From: Nikhil sharma [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, October 17, 2001 11:31 AM
Subject: Re: PetStore question
EJBException is a runtime exception. So
JavaBeans development
[mailto:[EMAIL PROTECTED]]On Behalf Of Cornel Antohi
Sent: den 17 oktober 2001 14:44
To: [EMAIL PROTECTED]
Subject: Re: PetStore question
Visual Age tells me that it can't compile the sources because the exception
is not declared
- Original Message -
From: Nikhil
In fact if you add a throws EJBException to the interface you'll find you
can't deploy the beans on some app servers, JBoss comes to mind immediately.
Cheers
-Original Message-
From: Cornel Antohi
To: [EMAIL PROTECTED]
Sent: 10/17/01 8:44 AM
Subject: Re: PetStore question
Visual Age
Jerome,
IMHO, EJB's should never accept arguments that represent an XML document! The reasons
are simple:
- XML is fat and RMI serialzation does not help. The most popular method is for the
EJB to accept a String or File as a parameter which represents the XML document. The
number of bytes
]
Reply-To: Peter Braswell [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Design Question : XML descriptions session beans (LONG)
Date: Fri, 27 Jul 2001 15:39:51 GMT
Jerome,
IMHO, EJB's should never accept arguments that represent an XML document!
The reasons are simple:
- XML is fat and RMI
- Original Message -
From: John Harby [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, July 27, 2001 9:27 PM
Subject: Re: Design Question : XML descriptions session beans (LONG)
Currently EJB clusters are restricted to LAN usage
Isnt' this a limitation of a particular
Another option is to use instance fields of a stateless session bean as
cache. You will get one set of your country data for each instance in the
method-ready-pool, but is that actually a problem? It may be a good
trade-off between memory usage and concurrency conflicts.
/Johan
-Original
Kevin Mukhar wrote:
If you wanted to use a singleton to hold a reference to a bean ...
I am starting to understand what you mean by a singleton. The client
of the singleton enterprise bean does not access it using home.create.
Instead the singleton is implemented either in the client or via a
This is an interesting view of singletons initiated by Kent Beck -
http://c2.com/cgi/wiki?SingletonsAreEvil. I think it applies especially
in the case of distributed systems.
From: Glyn Normington [EMAIL PROTECTED]
Reply-To: Glyn Normington [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re
Kevin, the more dangerous issue isn't when your static initializer fires,
but if it could fire more than once simultaneously--I wrote a paper on this
topic, When is a static not a static?, at
http://www.javageeks.com/Papers/JavaStatics/index.html. The danger is that
if the server maintains
Ted,
Good points. You also have to watch out for class garbage collecrtion.
Ted Neward wrote:
Kevin, the more dangerous issue isn't when your static initializer fires,
but if it could fire more than once simultaneously--I wrote a paper on this
topic, When is a static not a static?, at
1. Write a regular old Singleton
This probably involves updating static contrary to the restriction in
section 18.1.2 of the EJB 1.1 spec and can lead to inconsistent runtime
semantics, although it can be argued that this restriction is only
intended to apply to fields of the enterprise bean
Glyn Normington wrote:
1. Write a regular old Singleton
This probably involves updating static contrary to the restriction in
section 18.1.2 of the EJB 1.1 spec and can lead to inconsistent runtime
semantics, although it can be argued that this restriction is only
intended to apply to
Kevin Mukhar wrote:
The classic pattern for the Singleton class uses a read-only static field to
hold the Singleton reference, ...
I suppose the initial expression for the static field would be like this:
BeanX singleton = ((BeanXHome)javax.rmi.PortableRemoteObject.narrow(
new
more
than the base java classes.
-Original Message-
From: Kevin Mukhar [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 08, 2001 6:20 PM
To: [EMAIL PROTECTED]
Subject: Re: A question about singleton
Glyn Normington wrote:
Kevin Mukhar wrote:
The classic pattern for the Singleton class uses
. But I do
not see the point to make remote object singleton. Am I missing something
here?
-Original Message-
From: Glyn Normington [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 08, 2001 9:17 AM
To: [EMAIL PROTECTED]
Subject: Re: A question about singleton
Kevin Mukhar wrote:
The classic
Hi,
EJBHomes are cluster-aware stubs, hence will round-robin on each subsequent
EJBHome.create() call. In fact, you SHOULD cache the EJBHome stub in your
client (stick it in HttpSession or ServletContext for your JSP, and as a
member var in your SSB); otherwise if you re-lookup the Home from
Actually, you might want to consider an even more important question:
In most application servers, the connections to a database are cached.
Since the cache is set up in advance, it uses a common username and password
which is shared by the entire server. The database, therefore, in most
cases
From my limited experience with the J2EE RI server, you don't need to
pass a Properties object to the InitialContext constructor, just:
Context initial = new InitialContext();
If your J2EE RI server is on a different machine than your client, you
have to set an environment property before
This is EJB interest and not SERVLET interest.
Amit Gupta wrote:
Since you guys are good in servlet, I am daring to ask this Question.
Is there any method defined in servlet API to find out the servlet
container's log file. I do not want to hard code the name of the file in my
code because
Sven,
Man, you don't have to be that rude just because the guy didn't send
the question to the right list !! :o)
Amit, as far as I know the log method of the servlet API doesn't let
you specify the name of the log file, as this is server dependent. If
you need it because you want to
Are you looking for container support for authentication/authorization
using JAAS or EJB support for authentication/authorization using JAAS ?
Thanks,
Anthony Nadalin
___
mailto:[EMAIL PROTECTED]
John Harby [EMAIL PROTECTED]@JAVA.SUN.COM on 01/24/2001 09:47:44 AM
go to this site--
http://www.execpc.com/~gopalan/java/ejb.html
cheers
srinivas
- Original Message -
From: Ripan Bansal [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, January 18, 2001 12:18 PM
Subject: Newbie Question
I am new to all this stuff. I have just started learning
Hi,
EJBObjects:
The client does not invoke a method directly on the actual bean instance.
Instead, the call is intercepted by the container and =
delegated to the bean instance. Reasons:
1. The EJB is not network enabled and the container handles the networking
for it (by wrapping the bean in
refer the book by EDRoman
-Original Message-
From: Srinivas K. R. [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 19, 2001 1:58 AM
To: [EMAIL PROTECTED]
Subject: Re: Newbie Question
go to this site--
http://www.execpc.com/~gopalan/java/ejb.html
cheers
srinivas
- Original Message
My doubts are inline
-Original Message-
From: Nitin Goyal [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 18, 2001 1:59 PM
To: [EMAIL PROTECTED]
Subject: Re: Newbie Question
Hi,
EJBObjects:
The client does not invoke a method directly on the actual bean instance.
Instead, the call
what exactly is EJBObject and how is it differnet from bean instance.
are container and ejb server different?
-Original Message-
From: Srinivas K. R. [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 19, 2001 1:58 AM
To: [EMAIL PROTECTED]
Subject: Re: Newbie Question
go to this site
to be changed.
If you still have doubts please feel free to contact me.
Ripan
-Original Message-
From: Gopi Krishna [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 18, 2001 2:41 PM
To: [EMAIL PROTECTED]
Subject: Re: Newbie Question
what exactly is EJBObject and how is it differnet from bean
.
Still out in the cold? :-)
Regards,
Nitin
- Original Message -
From: "Ripan Bansal" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, January 18, 2001 2:36 PM
Subject: Re: Newbie Question
My doubts are inline
-Original Message-
From: Nitin Goyal [mailto:[EMAIL
Hi,
See inline
-Original Message-
From: Nitin Goyal [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 18, 2001 3:54 PM
To: [EMAIL PROTECTED]
Subject: Re: Newbie Question
Hi,
An EJBObject is network enabled and callable from other JVMs as it
implements the Remote interface
Hi,
The EJB spec v2.0 can probably answer all your questions if you have the
patience to read it. I am learning it too. I got an eval copy of weblogic and if
you have the patience you can convert it into a full-fledged app server with
clustering, SSL and ejb deployment etc. enabled. It
The following is my batch file in unix:
Which complier all you source file and packed into jar file.
you can use it like this:
BB MyPackage MyJarFile
Chalres Guo
BB.sh
JAVA_HOME=${JAVA_HOME:-"/opt/java"}
WL_HOME=${WL_HOME:-"/app/project/weblogic"}
Hi Chua!
It is perfectly legal to use executeUpdate() method to check how many rows
have been affected by the query. You typically use execute() method to return
a ResultSet and execute() to return boolean value.
I hope this clarifies your doubt.
MKumaresan
Jerson Chua [EMAIL PROTECTED] wrote:
-Original Message-
From: A mailing list for Enterprise JavaBeans development
[mailto:[EMAIL PROTECTED]]On Behalf Of Kumaresan Manickavasagam
Sent: Tuesday, November 07, 2000 3:01 AM
To: [EMAIL PROTECTED]
Subject: Re: [JDBC Question]
Hi Chua!
It is perfectly legal to use executeUpdate() method
-
From: A mailing list for Enterprise JavaBeans
development
[mailto:[EMAIL PROTECTED]]On Behalf Of
Kumaresan Manickavasagam
Sent: Tuesday, November 07, 2000 3:01 AM
To: [EMAIL PROTECTED]
Subject: Re: [JDBC Question]
Hi Chua!
It is perfectly legal to use executeUpdate() method
to check how many
Thanks to everyone who replied.
Jerson
-Original Message-
From: A mailing list for Enterprise JavaBeans development
[mailto:[EMAIL PROTECTED]]On Behalf Of Ron Chan
Sent: Tuesday, November 07, 2000 11:19 AM
To: [EMAIL PROTECTED]
Subject: Re: [JDBC Question]
Hi,
Yes, for example if you
Hello Brendan,
So given product A and product B, I need to model a relationship or "link"
between A and B. My first impression was that the "link" was a dependant
object. So if I create A and "link" to B, the the "link" is a dependant
object of A. This implies that A is responsible for the
for Enterprise JavaBeans development
To: [EMAIL PROTECTED]
Sent: 8/29/00 11:18 PM
Subject: Re: Newbie question: How are keys generated?
When you ejbCreate a new bean, you create the PK object in this method
and
pass it out in the return; the server container the takes over and
does
the
"se
Hi Neil,
Where and how are the keys generated?
The answer to your question is really 2-layered. On the database side, the
primary key generation is based on the db implementation. For a SQL table
with a column declared as the PK, this sequence is generated and maintained
by the database.
When you ejbCreate a new bean, you create the PK object in this method and
pass it out in the return; the server container the takes over and does
the
"setting". This implementation is vendor-specific, but in general the
container would
1) create an EntityContext that refers to the pk
J2EE Reference implementation :
How to get and set up @
http://developer.java.sun.com/developer/onlineTraining/EJBIntro/exercises/Se
tupJ2EERI/index.html
-Original Message-
From: Jarzan [mailto:[EMAIL PROTECTED]]
Sent: Saturday, July 29, 2000 2:28 AM
To: [EMAIL PROTECTED]
Subject:
Well I think it is safe to say that all EJB servers are case-sensitive about
Java method names ;-)
the method is :
public int hashCode()
http://java.sun.com/products/jdk/1.2/docs/api/java/lang/Object.html#hashCode
()
cheers,
jmp
-Original Message-
From: A mailing list for
Well, if it comes down to between VCafe and JBuilder, I would say it is a no
contest. JBuilder it is.
Of the big three, VCafe, JBuilder and VAJ, only JBuilder has a runtime which
is 1.1 compliant as IAS is. VCafe is supposed to, but it is beset with
problems.
When it comes to tight integration
Tom,
By virtue of deploying both beans as TX_REQUIRED, the behavior you desire
(e.g. single atomic unit of work) is automatically provided by the EJB
server/container.
-Chris.
-Original Message-
From: Tom Preston [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, May 18, 2000 12:53 PM
To:
Paul Jones wrote:
Is there any possible way to set the message priority for a message when using a
QueueRequestor ?
This should be possible like this:
Message msg = ...
msg.setJMSPriority(prio);
queueRequestor.request(msg);
Best regards,
Bjarne.
John Smith wrote:
We want to take advantage of entity beans and CMP, but also want to
preserve
our Domain Object Model to the greatest degree possible. It is sometimes
suggested that an entity bean simply wraps the java object. The entity
bean
would then have two attributes of interest to
take them to the folks that plan such
things...
/vendor
Regards,
-Chris.
-Original Message-
From: Guillaume Rousse [SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, March 22, 2000 12:34 PM
To: [EMAIL PROTECTED]
Subject: Re: Design question: entity beans, wrapping domain objects
and su
But only on CD and for Windows NT :-(
[Randy Stafford] Acknowledged.
Why not put them online, if they're
really open source ?
[Randy Stafford] Stay tuned ;-)
RPS
Le jeu, 16 mar 2000, vous avez écrit :
John,
The FoodSmart example application in our
John,
vendor
The example application in GemStone/J's Developer's Guide does exactly this
(i.e. wraps domain objects with Entity Beans).
You can sign up for a copy at our WEB sute.
/vendor
-Chris.
-Original Message-
From: john smith [SMTP:[EMAIL PROTECTED]]
Sent: Friday, March 10,
they are lots of post here about domain objects. From what i've understood
sofar, domain object was a synonym for business object, and were to be
implemented using entity beans. Apparently, i'm a bit wrong on it.
I found noting on this subject (domain object) on Cetus Link. Has anyone good
-
From: john smith [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, March 14, 2000 10:51 AM
To: [EMAIL PROTECTED]
Subject: Re: Design question: entity beans, wrapping domain objects
and su ch...
Thanks for your response!
I understand you want to wrap entity bean access in session beans
Laird Nelson wrote:
Assaf Arkin wrote:
You need a more formal API to get into stage two. If you don't care
about these features or portability, just pick any EJB server that
allows you to start a thread (I believe most of them do), and use it.
But if you care about the container
We use entity beans to model our Domain Object Model. But the clients never
use those entity beans. Instead the clients use Session beans, which
internally use those entity beans. The session beans interfaces are modeled
to provide some sort of low-level-use-cases to the client. All information
dan benanav wrote:
Does this mean, for example, that I cannot use Hashtable or
Vector in my bean classes?
Yes you can, as long as they are not shared between two threads.
This answer doesn't make sense to me. Either you can use a hashtable
in an entity bean or you cannot.
It's not
Assaf Arkin wrote:
You need a more formal API to get into stage two. If you don't care
about these features or portability, just pick any EJB server that
allows you to start a thread (I believe most of them do), and use it.
But if you care about the container features in your threads, about
This answer doesn't make sense to me. Either you can use a hashtable in an entity
bean or you
cannot. Why should I worry about threads now?
Don't worry, just use it and be happy, but if you want to be on the safe
side, you should consider the 1.2 collections.
arkin
If you use a
Assaf Arkin wrote:
Mark,
So far the discussion has been about the useability of thread support,
and no one contradicted their usability. I'm not sure JMS is sufficient
for what developers have in mind, and connectors would be an overkill
for many applications.
It's clear that EJB 1.1
Rickard Öberg wrote:
I don't see any compelling reason to make another type of bean that
duplicates the functionality already available in JMX. JMX beans are
portable between different servers supporting JMX, they are manageable,
they can interact in whatever fashion you like with EJB's, etc
Laird Nelson wrote:
By this logic any time I use java.util.Vector in my bean code I am
violating the EJB 1.1 specification (beans can't use threads or
synchronization primitives; third-party classes used by beans can't
use them either; java.util.Vector uses synchronized all over the
place;
I find compelling Assaf Arkin's formulation of the problem: EJB
allows for synchronous processing; JMS allows for asynchronous
processing; neither allow for continous processing.
I wonder if parallel workflow requires continuous processing, as you
suggest. Consider a workflow with three
Assaf Arkin wrote:
People on this list have come up with usage scenarios where, you have to
agree, neither EJB 1.1 nor EJB 2.0 + JMS are sufficiently addressing
their needs.
The issue here is not about redoing thread pooling and thread management
instead of the container, but being able to
dan benanav wrote:
All I was asking about is what would happen if I create a new thread from within a
bean method and
then get an InitialContext in the same way that I would from a client thread. I was
wondering why
that wouldn't work.
As an example, the lookup method on the
Sorry, I don't see how instrumentation and SNMP agents are useful for
building an enterprise solutions where your operations are
transactional, involve complex objects, and require TP monitoring.
I was not referring to the ability to control services, but rather the
ability to control disributed
1 - 100 of 254 matches
Mail list logo
