Diana Finis

Greenhorn
+ Follow
since Jan 27, 2003
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
In last 30 days
0
Forums and Threads

Recent posts by Diana Finis

Oh sorry, I've mixed oranges with apples :-). It looks like Tomcat looks for ant library, and either it doesn't find any or it finds one of a wrong version.
Hope it helps.
20 years ago
Add to PATH Ant/bin directory
20 years ago
Hi all,
Recently I was going through some mock exam and faced the following question:
----------------------------------------------------
"Consider the following method of a stateless session bean. Which of the given options are correct regarding this method?"


Code :

public xxxx() throws
{
try
{
InitialContext ctx = new InitialContext();
QueueConnectionFactory queueConnectionFactory = (QueueConnectionFactory) ctx.lookup("java:comp/env/jms/myQueueConnectionFactory");
...//other valid code.
}
catch(Exception e)
{
throw new EJBException(e.getMessage());
}
}

Options :

Select 1 correct option.

1. It may be ejbCreate() method.

2. It may be ejbRemove() method.


3. It may be a business method.


4. It may be setSessionContext() method.


5. This code is invalid in any stateless session bean method.
----------------------------------------------------
The correct answer was "3. It may be a business method."
For me it doesn't look rigth. Resource Manager is registered via resource-ref tag, hence it's available in "java:/comp/env" scope. And JNDI access to "java:/comp/env" IS ALLOWED for all methods listed above.
Can somebody clarify this point to me?
Thanks in advance.
Diana
Thanks Andrew,
It makes sense now. So even if bean throws an AppException without ending a tx, container will respond as you described instead of propagating AppException to the client.
Am I right?
Thanks,
Diana
Hi All,
For Stateless bean with BMT:
If a bean method in tx neither commits nor rollbacks the tx and throws an Application Exception, what happens to tx and what exception client receives?
1.From one side App Exception doesn't automaticly causes tx to rollback, 2.from another side Stateless must to end the tx before returning from the method.
Spec says that App Exception is propagated to client always, but this is contradicting to side 2.
So what is the answer?
Thanks, :roll:
Regarding Entity beans: I understand that concurrent access is allowed to entity object, and not entity instance, right? So if we are talking about entity instance the answer includes C too? Is that right?
Thanks,
Could you submit an output of the program?
And also part if DD where you define transaction types for session bean & entity bean?
It looks to me that it's related to transaction settings. The fact that other clients (running in other transactions) do not see the new value, could mean that transactions are not commited when they should.
This is interesting...
Hi Sami,
I'm a little bit new to it, but I have a question
Do your setter/getter methods set/getValor() participate in transaction? (Defined in DD).
I've passed with 71!! Thanks all for Info!!
Thanks Karina for info.
Regarding Web Services and Personalization - did you have teoretical or practice questions? I mean did you have to know WSDL syntax etc.?
Did you practiced all the issues in Writing Portlet section before the exam?
Did you see any surprises? I mean was there anything not specified in Objectives?
Thanks!
Diana
Hi Kareena,
I'm currently preparing for this exam.
I'm using red books from IBM : WebSphere Portal Handbook Volumes 1,2,3 ,Developers Handbook and InfoCenter as well.
Could you suggest some roadmap and additional resources to pass the exam?
And if it's not a secret, what was your score?
Thanks,
Diana