Walid Abd Elsalam

Greenhorn
+ Follow
since Feb 26, 2010
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Walid Abd Elsalam

Thanks for the response.
Yes, that's the exact problem I had.
It doesn't matter much to me, but again, someone might fail because of this. These 2 questions were easy and I would have gotten them right which would have put my score at 89%.
I really don't want to go looking for a sun email address to write to.
I noticed that Bret was willing to look into this in the other thread. If he would like I can provide details about my test.

Cheers
I took the exam today and passed with 86% score. My score could have been higher if it wasn't for 2 drag and drop questions that had all labels blank. So basically there was nothing to drag to the boxes.
I let the supervisor know and all she could do was ask me to add a note for these questions.
While it's no big deal for me, it could mean failure for someone else.
Does Sun rectify the score later on?
Anyone been in a similar situation?
You can delete this post. I think it's the proxy thing at work.
Will try from home later.
I just downloaded the software and set it up. Downloaded the trial bank. When I open the app, it's not asking for a license and I'm not getting the questions. I've updated the proxy settings and it should be correct because when I check for the latest version of the software, it's connecting and letting me know that I have the latest version of the exe.
Is the licensing server down?
From the Servlet Spec



SRV.10.5 Listener Instances and Threading
The container is required to complete instantiation of the listener classes in a Web
application prior to the start of execution of the first request into the application. The
container must maintain a reference to each listener instance until the last request is
serviced for the Web application.
Attribute changes to ServletContext and HttpSession objects may occur
concurrently. The container is not required to synchronize the resulting
notifications to attribute listener classes. Listener classes that maintain state are
responsible for the integrity of the data and should handle this case explicitly.



Seems to be a new thread of execution per request then. Just like servlets?
But what about context listeners?
And is only referring to thread safety for attributes, but how about Listener instance and class variables?
This is still a bit fuzzy for me
Is it vendor specific?
Is there any document out there about the lifecycle of a listener. In particular whether we have a pool of instances or threads of execution or a single instance running?

Anyone with some more info on this?
It should work of course.
What I'm really wondering about is the lifecycle of a Listener. Meaning do we have several instances running each per request (maybe a pool from which we draw a listener as an event occur to handle the event and then it's returned).
Or is it a single instance with events triggered queued for processing one by one. In that case it would be thread safe, except that you might want to re-initialize instance variables each time you process a new request.

The same goes for session and context listeners.

Can you try it again after replacing OutputStream with ServletOutputStream. I'm just wondering if it would make a difference as the api documentatio for OutuptStream.flush() says it does nothing.
Just wondering. I'm reading the HFSJ chapter on event Listeners (Context, Session, Request) and was wondering what's the verdict in terms of thread safety. Do they pretty much follow the same rules as per servlets?

For example:
Let's say that I have a static variable defined in a ServletRequestListener that keeps track of number of requests created. Would that be safe without having to synchronize on the class's lock?

The book doesn't say much about the lifecycle of a listener.
Did anyone else have the same problem?
When you answer a question, mark it for review, then go back to it and try to open the exhibit window again to review your answer it alerts you that your previous answer will be gone. Thus, you would have to do the drag and drop exercise once more.
In my case most of the questions marked for review were D&D and after reviewing the first question and realizing this, I was like damn it ... I have to do it for all. Forget it. Hence my score ...
Hi John,

It depends on which interface your implementing (Your assignment)
Some people don't have a cookie defined as part of their interface method signature, thus they need to identify the client to use that for locking.
In your case you can use the generated cookie. No need to track clients.
I'm not sure about using a sequential number though.

Dennis Grimbergen wrote:Hi Roel,

Although my name indicates to be a Belgian, I'm Dutch. I just love the Belgium beers



Is it true that the Dutch and the Belgain don't get along very well
My Ex-GF was Belgain and she couldn't stand the Dutch.

Roberto Perillo wrote:Howdy, Walid!

However, your application should be free - and expected - to change the data in there.



Which is, the IDs of the clients being placed in each booked record when the records are updated. Is that what you mean? If so, yes, that's correct!



This and being able to mark records deleted or updating the contents of each. That's what the interface dictates. The GUI part requirements is a bit fuzzy here, so my intention for the moment is to provide the ability for the user to execute all operations provided by the interface.

In reponse to the previous post, my point is that the requirements are clear that what should not change is the structure of the file. The data for each record is expected to change as user interacts with DB of course (updates/marking for deletion ..etc).

Of course you guys who have done the assignment before can correct me on this.
My understanding is that you're not supposed to change the format of the db file. Meaning record structure. However, your application should be free - and expected - to change the data in there.
You're not supposed to change the structure because the company has other applications using the same file. So, structure has to be maintained.