Win a copy of Machine Learning with TensorFlow this week in the Artificial Intelligence and Machine Learning forum!

Sumitro Palit

Ranch Hand
+ Follow
since Dec 13, 2003
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Sumitro Palit


Class Diagram (44 maximum) .......................... 36
Component Diagram (44 maximum) ...................... 40
Sequence/Collaboration Diagrams (12 maximum) ........ 12

Realized after submitting the assignment that I had updated a diagram in my EA model but forgot to update the image in the html

I have been putting this off for a while being busy with work but I think its been a good exercise to go through - all 40 hours of it. In real world situations we end up cutting corners (listening to bosses who think they know) but for this assignment you are expected to follow appropriate design patterns and create a true n-tiered distributed application.

12 years ago
You might have a very long running process that is causing a timeout.
Try to handle it in smaller slices.

I have seen a similar issue being addressed here:
Look for CR105337

Originally posted by Kia Phia Ben:
Hi all
Please tell me why the error
and how to fix this problem. I using Weblogic 8.1 SP4 and oracle 8.1.7 for windows.
I run my program the error print:
Caused by: weblogic.jms.common.TransactionRolledBackException:
at weblogic.jms.backend.BEConsumer.expireTimeout(
at weblogic.jms.backend.BEXATranEntryBlockingConsumer.startRollback(
at weblogic.jms.backend.BEXATranEntry.execute(
at weblogic.kernel.ExecuteThread.execute(
Thank for help me

[ January 30, 2007: Message edited by: Sumitro Palit ]
14 years ago
Thanks for clarifying that -- good to know that EJB 3 has finally provided a default transaction attribute.

The EJB3 specs - "JSR220: Section 13.3.7 - Specification of the Transaction Attributes for a Bean�s Methods" covers this in details incase anyone wants to go into the details.
The specs don't provide any default transaction attribute - so developers are expected to provide one. The individual vendors usually provide a default (which varies, eg Weblogic might default to Supports while another vendor might set Required)- so if you don't provide a transaction attribute yourself, your code might not be portable between containers wrt transaction.
>>For entity bean , if the beans are representing the same entity in DB and >>we are checking their EJBObjects using isIdentical,they are meaningfully >>equal.So it will return true.

If there are 2 different entitybean "types" associated with the same entity data in the DB (say AddrBean1 & AddrBean2 for arguments sake), then even if there are 2 instances , one corresponding to each home, representing the same entity data in the DB, isIdentical will return false => they must be from the same home to be treated as identical.
DISTINCT implies duplicates will be avoided - it can still return a collection of unique records staisfying the QL statement.
How about creating an empty custom tag called myBreak.
Just implement the Tag interface, make doStartTag return SKIP_BODY and doEndTag return SKIP_PAGE. (You can do the same by extending TagSupport and implementing doEndTag to return SKIP_PAGE).

This will will give you a clean way of stopping execution at any point of your JSP and has the advantage of being reusable. You might want to output some message to indicate that you are using this tag to break, so that if you leave it in by mistake you'll be able to spot it quickly.
16 years ago
In JSP 2.0 you can use EL to achieve this.
The syntax is ${wookie.wookiename}.
So, if your wookie name is id and stores a value 20,
${} will output 20.

Please replace "w" in all "wookie"s with 'c'
16 years ago
16 years ago
Hi y'all,

Had to take the SCWCD1.4 exam due to meet a deadline (didn't want to expire my voucher).
I had been away from working with J2EE for a while, so SCWCD1.3 would have been a better option for me because I have practical experience with it, but when I decided to sign up for 1.3 on Dec 17, I was told Sun had discontinued it on dec 15 - looked in the mirror and saw a jackass.

Back to the bookstore for the Head First book, 3 weeks of studying and passed it with 89%. (Hey ? why do they floor the results and not round them? 62/69 = 89.8% = 90% in my book - but 89% according to Sun - just lost my bragging rights.)

BTW thanks to Basham et al for another book that helps you stay awake :-)

Tip for future test takers :

1. Don't ignore any question in the chapter-end tests or the final mock exams - even if you see a question that is based on a topic not covered at
all in the book.

2. SCWCD1.4 is not more difficult that SCWCD1.3 in my opinion - thats a myth. You have less memorization to do - which is a good thing. There are more questions where you have to analyze code which means if you understand the subject you will be able to answer them. The new topics like EL and the SimpleTag implementations are supposed to make life easier and they are much easier to handle in real life and in the exam.

Have fun!

- ortimus
SCJP1.4 - 96%
SCWCD1.4 - 89%
16 years ago
Thx Nate,

I didnt read Harshad's original question too carefully.
Thx for the idea to use property="*" to map common properties and add params to the request for different values that need to get mapped to the same property on 2 different instances.

- ortimuS
16 years ago

What you did will work.
Look at the id attribute of jsp:useBean as the variable name of the bean instance.
So you have created 2 new instances of com.nexor.LoggingBean,
have one reference to each - verifyloggingBean & secureloggingBean
- and you have added these as attributes to the session.
verifyloggingBean & secureloggingBean refer to 2 different instances of com.nexor.LoggingBean and thats what you were trying to achieve.

- ortimuS
16 years ago
You probably forgot to import the class :
<%@ page import = "UserDatabean" %>

- ortimuS
[ June 09, 2004: Message edited by: ortimus tilap ]
16 years ago

Your question was:
Greately appriciate if you can tell me why case 1: is not dir/B.jsp.
I think the question should be why isnt it dir/C.jsp

We have A.jsp, C.jsp, dir/B.jsp and dir/C.jsp,
Lets see what Case 1: does:

A.jsp says <%@ include file=�dir/B.jsp�%>
There is no ambiguity here - dir/B.jsp is "statically" included in A.jsp
But note that this is a statical inclusion - so the dir/B.jsp code is now part of the A.jsp code.
This implies that the current jsp location in not the dir folder but the same folder as A.jsp is in
dir/B.jsp says <jsp:include page=�C.jsp�/>.
Using the explanation in (i), in this case, the current dir of B.jsp is NOT dir, so the relative specification C.jsp resolves to C.jsp and NOT dir/C.jsp.

Compare this with:
(i) A.jsp says <jsp:include page=�dir/B.jsp�%>
(ii)dir/B.jsp says <jsp:include page=�C.jsp�/>

Here both are dynamic includes,
so (i) is including dir/B.jsp into A.jsp, dynamically.
When dir/B.jsp is executing, it current page folder IS dir, so it interprets the inclusion of C.jsp relative to dir => dir/C.jsp

There are 2 things to note here:
1. Both, page attribute of the include standard action & file attribute of the include directive are relative to the current jsp page.
2. There is a difference between the way a static include and dynamic include are handled, not just the time at which the include occurs (translation vs run-time) but in the "scope" of the inclusion.

BTW, you can avoid confusion by giving the relative path as "/x/y/z/myjsp.jsp". If you start with "/" then the path is interpreted from the root of your web application and not the current page, then there is no scope for ambiguity between a static vs dynamic include.

Hope this helps,

- ortimuS
16 years ago
Question for Jitin (whizlabs):

For those who have already bought the SCWCD 1.3 simulator, do you have any plans to offer them a SCWCD 1.4 upgrade at a dicounted price? Even providing a "diff" version just for the additional topics might be a good idea.


- ortimuS