liao Yang

Ranch Hand
+ Follow
since Dec 27, 2006
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 liao Yang

Hi Craig

Thank you for coming and help.

I have some experience of Spring 2.5 and EJB3. What I'd like to ask are:

1) What are the major the improvements from Spring 2.5 to 3.0?

2) as EJB are getting better and better since version 3.0, are there any big points the makes people choosing Spring rather than EJB? Or the choice will become a personal preference?

Best regards

12 years ago

I'm interested in this topic and have a question to ask.

When you say "you have to use java 1.6" whether this means that you have to use the new language features in java 1.6 or it is enough that you just use the java jdk, i.e. parser, but still use language features from old versions?

Thank you
"Filters are called in the order they appear in the deployment descriptor Correct" is partially true. The order of filters being called is determined by both the order they appear in the DD and whether they are mapped to a url-pattern or to a single servlet.
I'm confused by these two concepts, what's the difference?

Thank you
EL is about using attributes and implicit objects. It has no access to local variables.

Hope this helps.
Sorry, when I say "empty <auth-constraint>" I mean there is no <auth-constraint> in a <security-constraint>.

I also tested <auth-constraint/> with <auth-constraint>*</auth-constraint> combination, the result is that the request is refused after .authentication. So NO <auth-constraint> is not equivalent to <auth-constraint>*</auth-constraint> when combined to <auth-constraint/>.
Thanks Christophe

Here is another one, the combination of <auth-constraint/> with no <auth-constraint>.

The spec and HFSJ both mentioned the combination of <auth-constraint/> with others and empty <auth-constraint> with others, but didn't mention which wins when these two are combined.

I tested in tomcat 5.5, the result is that the request is allowed without authentication.

Anyone can confirm this is the behaviour of the spec? Did I miss something form the spec?

Thank you.




If the two apply to the same web resource collection and http method, will all the roles allowed to access or no roles allowed to access?

I think that no user is allowed to access, since the spec says: "The special case of an authorization constraint that names no roles shall combine with any other constraints to override their affects and cause access to be precluded."

Am I right?

B is not correct. HttpSessionBindingListener are only notified when an attribute is bound/unbound to the session, they are not notified when the session migration happens.
I also did a similar test on tomcat 5.5.23 and got the same result.

I think the container (at least) Tomcat is treating the class as a java bean directly, not using the inhertance hierarchy. I didn't check the spec though.
With the declaration of

<jsp:useBean id="strName" class="java.lang.String"/>

I can't figure out a way to get the value of strName by using <jsp:getProperty>. Is it possible?

Thank you Charles for the clear explanaion.
Thank you for your reply, Marc.

Can you let me know the new topics in the second mock exam?


Hi All

Are they the same, similar or quite different? I'm thinking use one now and another as the final test before exam. Will they serve the purpose?


Hi Ankit and Deepak

Thank you for your replies. I know that 1 servlet instance per web app, but this still didn't answer the question of "how amny JVMs".

Ankit, what did you mean by "there is only one JVM per jvm."? I know it's a typo, but what were you trying to say?