Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

EPractize Labs SCEA Part I mock exam

 
Stefan Popa
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Folks,
i'm preparing for scea for jee5 and bought the exam generator from EPractize Labs for scea part I.
I can not recommend the product, because it is full of errors.
The errors are:
- orthographical, to the point that you can not guess what they mean
- technical. The Update functionality of the software produces an error every time you use it.
- Wrong answers and explanations. Example Explanation: "Payment processing system requires transaction, therefore cmp entity beans are used to handle the transaction."
This is wrong, the transaction of a business process must be handled in a business component (session bean) not in an entity bean.
- In one Mock exam they ask the same question three times.
- Sometimes they give the right explanation but don't count it right, so you fail.
- There is a button in there exam application "Send Query". That's a good idea, so you can tell them when something is wrong. But you never get an answer and i guess they never read the "query"

One more example:
You have to implement a rich client gui for your legacy system and read only data.
Which technology will be used here:
1)JSF
2)DAO
3)JPA
4)Swing
5)AWT
6)SWT

I choosed 3 and 4. I'm wrong
Explanation: 1) and 2) are right
Why: JSF and DAO
Why not: explained above

Sometimes they wright a little more, but you can see that it is copy / pasted from a specification.

In my opinion this product is absolutely useless, and leads to confusion.
So i try to get my money back from them
Please report your experiences with other Mock exams, so that nobody has to waste his money
for such miserable products.
Kind regards
Stefan


 
Dmitri Ericsson
Ranch Hand
Posts: 109
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
JPA is not suitable in this case, beacuse for legacy read-only data DAO is more appropriate. What about Swing - you are right, if there in the question not mentioned that it should be thin client
 
Stefan Popa
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Dmitri Ericsson wrote:JPA is not suitable in this case, beacuse for legacy read-only data DAO is more appropriate. What about Swing - you are right, if there in the question not mentioned that it should be thin client


They say it must be a rich client gui. In my opinion JSF is not a rich client, but a thin client (framework for developing web (thin) clients).
Wikipedia says:
A fat client or rich client is a computer (client) in client-server architecture networks which typically provides rich functionality independently of the central server

But JSF is a server - side framework wich produces web clients.
Question: is jsf a framework for developing rich client gui's ?

You are right with the usage of Dao for read only issues.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic