According to me you should only change these settings if you are facing some problems with the application server, because this is the default J2EE classloading mode.
I always had the impression that PARENT_LAST was the class loading mode recommended by the J2EE spec (at least for war files, i.e. WEB-INF/lib). Anybody an idea where it states in the spec what the default mode should be?
I have a web-app with several env-entry's. I would like to configure the values for the env entries after I have deployed the application (Websphere 5.0/5.1). Is this possible?
I tried to find documentation for "Resource Environment Providers" and "Referenceables", if this solves my problem, but no luck. Has anybody an idea how to use this feature?
I think one problem of Byte Code modification (especially when used with Hibernate) is that modified classes can't be serialized, i.e. if you use the hibernate classes as transfer object in a distributed environment.
The reason for that is, that a client doesn't know anything about the dynamic generated classes on the server.
I don't see how this would be done, i.e. if I want to get notified when a login has failed (because a user is not in the appropriate role), which method do I have to implement in the user registry to get this information? the user registry has methods like getUsers, getGroupsForUsers but nothing relating to failed web logins. there is a opensource framework (seraph) which does the job (by providing LoginInterceptor and LogoutInterceptor), but it is still beta.
I would like to log login events (login, logout of application, invalid login etc.) in a (custom) database table. Is this possible using Websphere security (web.xml roles, user registry) ? I.e. can I write something like AuditLogger and plug it into WS (this is possible in Weblogic).
Yeah. Giving it a second thought I think E must be right. It just means somebody has compilation problems all over the place (in his ejb project) and then tries to run the Test environment. I wouldn't even try to do that - lame question in my opinion.
to 5: I think you are right. Option B is not recommended because it attaches a reference to a node instead of a cell. to 27: I reconn the correct answer is A. But I think the question is not that brilliant. The exception you get if you fail to run the "generate->" is a ClassNotFoundException (and not the message "Unresolved compilation problems", which rather suggests a problem compiling some source classes). In order to create a jar file you have to fix all compilation problems.
I think the answer to 14) should be A and B. I don't think it is valid that a Customer bean invokes a private method (ejbStore) on a related bean (Address Bean). Any thoughts ?
Is this behaviour according to the JAAS spec? I guess the method you mean is "doAsPrivileged" rather than "runAs". As far as I know, the runAs is specified in the ejb DD.
I think getting messages asynchronously in an SessionBean would break about every rule in the ejb spec possible. Honestly, once the method call in a session bean is finished you are not allowed to reference the same instance via a MessageListener Interface (just calls over the remote interface are allowed). Perhaps if you bend the rules a little bit and introduce a Singleton etc. you could make it work. Why not try to solve it with a MDB instead ?
Peter ---------------------- SCJP, SCJD, SCEA, WL7
Weblogic 7 Security is not part of the exam (and there was no question for it), I just had a quick look through the weblogic security documents. I would certainly learn about EJBs DD and the weblogic-ejb.xml file (I think there was one question related to it). JMS was covered by several questions in the exam. The Weblogic Whiz Test covers all of these topics very detailled. As I mentioned before - I think they go into more detail than the real questions. Peter.
Ranch Hand Scavenger Hunt
Number Posts (57/100)
First Post