Ulf Dittmer wrote:I wouldn't hold my breath waiting for a book for this particular exam. The exam is behind the times of WS trends, and IMO the lack of a book reflects that. For example, JAXR/UDDI never caught on (except behind closed doors in a few large companies), but it's still part of the exam. And there's very little about REST (and nothing about JAX-RS, I believe), which is the preferred choice for new WS projects these days. Also, the SOA hype has subsided, and WS are no longer seen as the panacea they once were, so the general level of interest in the exam (and its value) is probably less than it once was.
Katrin Perry wrote:Hi,
Just in case you still not sure.
b) is not correct.
According to EJB core specification: - "Timers can be created for stateless session beans, message-driven beans, and 2.1 entity beans.
Timers cannot be created for stateful session beans or EJB 3.0 entities"
Kengkaj Sathianpantarit wrote:Even Sun is not acquired by other company, it doesn't guarantee that EJB 3 will be popular, Spring Framework can compete with EJB 3 in almost every aspect.
Reza Rahman wrote:Kram,
The point is that the SCBD is unlikely to change (the same is also true of Java/Java EE as a whole) with or without Sun. Also, as I said, I don't see the wisdom in dwelling too much on something that is a rather distant possibility and more or less looks like a media hoax at this point.
PS: I think a Sun merger with a more stable company is inevitable and a good thing. I am not sure IBM would be the most developer/community friendly choice, though. I was personally hoping for Apple or Red Hat with the hardware part going to some other company like Fujitsu or HP perhaps.
Jothi Shankar Kumar wrote:
Kram Nart wrote:Does pursuing the SCBCD still make sense if Sun gets bought out by another company such as IBM? How true is the comment about the JavaBeans folks getting fired from Sun? What's your thought on this?
What has Javabeans or SCBCD got to do with it?