Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript forum!

Damian FRACH

+ Follow
since Oct 18, 2004
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 Damian FRACH

Yes Prema, I know. Therefore I want to be a technical architect.

Only way how a technical guy can win a battle against managers.

I am curious, who is doing an architecture of your SW solutions in your company.

Managers .... ??? .... ))
15 years ago
>> Even WebLogic, Oracle, and Microsoft environments often use WebSphere MQ when it comes to messaging.
>> Greg Charles; Software IT Architect; IBM Viet Nam

Sorry Greg, but I could not helped my self :

SUN Java Message Service implementation 7 or more times faster than IBM MQSeries (

Damian FRACH
J2EE Support Team Leader
SUN Microsystems
15 years ago
I do not know, but J2EE architects in UK are earning more than low level managers ....
15 years ago
>>> I think IBM's been slowly eroding BEA, but JBoss has taken a few nibbles out of both. JBoss is free and has a pretty complete set of J2EE functions

- JBOSS documentation is not free

- SUN's app server 7 and 8 PE are free for production (including 3000 pages of docs) and they have also MQ

- and they are also SUN certified ...
15 years ago
>>> These companies are all about getting SOMEONE placed in a position and not YOU placed in a position.

These companies are trying to place their best candidate with the highest salary to get the highest commission

sounds logically for me

also the recruit agent market is quit big and stable, what can indicate that these companies do the right job ...

I do not clearly understand your concerns ...
15 years ago
SUN app server 7.x and 8.x PE can be used for FREE even for production

it is even cheaper than JBOSS, because you have to spend 100$ for JBOSS documentation

SUN app servers are J2EE 1.3 and 1.4 compatible, so for example MQ SW is also included

and rest of commercial versions of SUN's servers are based on PE edition, so you get same quality as SUN's customers
15 years ago
only way how to sort it out is another job interview ... ))))))
15 years ago
now in South Africa it is almost impossible for a white male to find a job if you do not have some super qualification

it is based on the local law called BEE (Black Economic Empowerment)
15 years ago
I have IT MSc and MBA and IMO it helps generally for any positions

also it can help you to grow to management/team leader/project management/architect roles ...
15 years ago
I would not go for the Spring/Hibernate, but for the EJB 3 (in 2 years) and stay now with EJB 2.1/J2EE 1.4

right now the ratio between Hibernate/EJB is 1:12 on
they will not make it in 2 years
and Hibernate 3 will implement the EJB 3
also EJB3 will have the same edvantages as Spring (POJO, ...)

I suppose that the biggest problem with the Spring/Hibernate is that is not a standart; what EJB 2.1/3 are/will be

also I found on jobServe that open sourced specialists have less then closed sourced ones
15 years ago
IMO you should go for the whole J2EE stack, not only for the MQ ...

15 years ago
EJB flaming is now very popular. Almost everybody does it ...

1) Check on, how much is demanded EJB and e.g. Hibernate (320:25)

2) go for Session EJBs 2.1 if:
- distributed architecture
- container managed transactions
- container managed security
- message driven beans
- monitoring (you can see the EJB object statistics in container)
- XML description file (everything on one place)

3) disadvantages of the Session EJBs 2.1:
- 2 interfaces and 1 class
- bloated API
- big XML description file (big, difficult to find)

- with right design patterns (ServiceLocator, BussinesDelegate) and right IDE you can avoid it

- most popular competition: Spring
- - not very demanded now on JobServe
- - EJB 3 will be very similar and will be here in 2-3 years
- - EJB 3 will be implemented by 10-20 vendors; Spring is only one implementation

4) State full Session Bean has similar performance and scalability characteristics as HTTP session (

StateLess and Message Driven Beans do not have almost any minuses

5) for any bigger app (performance + scalability) you need object-relational mapping (entity EJB, hibernate, JDO, toplink, ...) for a DB caching

6) BEA CMP entity EJBs have better or same performance as Hibernate (

7) Entity EJB pluses :
- performance is same as Hibernate
- they are implemented by JDO (SUN) or TopLink (Oracle) anyway
- Hibernate 3 will implement the EJB3
- EJB are still 10 time more demanded then Hibernate on now
- EJB 3 as EJB 2.1 will be/are implemented by 10-20 vendors; Hibernate+Spring is only one implementation

8) Entity EJB minuses:
- bloated API
- EJB QL is weak especially for rich OO domain model
- rich OO domain model is not fully supported (e.g. inheritance)

- do you want to hit your relational DB (Oracle) by rich OO domain model?
I personally for a big scalable application NO.

So IMO the EJB flaming is little bit unjustified and very often is based on personal feelings then on facts.
15 years ago

Is your official title "Architect/Project Manager" or equivalent in your organization? If not, this is BS you should not put on your resume.

Anyone can write a personal application in his free time and be his own boss. I am also writing a small Swing app for hobby and I am the CEO/CTO/CIO/COO of this project.

well, it is up to you ...

my official title is "J2EE support team leader"
but I am also developing out of my normal duties J2EE apps for about 1-2000 people in my department; the development team is me and 1 my colleague

so in my CV is:
- J2EE support team leader (official work title)
- J2EE/database architect
- project manager

I can prove I DO all 3 jobs described above
of course I am not full time project manager or architect...

but I will NEVER write to my CV I was only "J2EE developer", because I need to sustain my senior expert level in my CV

IMO this "type" of laying in CVs is common and useful, but:
- you have to be able to prove it (let's say your previous manager will give you this reference)
- you have to be able to speak about that: why/why NOT EJBs, Hibernate, JDBC, EJB3, AOP, bla bla bla

BTW my friend asked me to check his CV: he was 4 years "JAVA test/QA engineer"; I told him to change it: "senior JAVA test/QA specialist"
- is it laying? can they prove you are laying?
- what is a "difference" between an engineer and specialist???
- especially if your company does not use this title
- of course you have to able to speak like "senior specialist" at least for 20 minutes; why/why not JUnit, Cactus, future technologies, JAVA tuning, different garbage collectors, bla bla bla

Other my friend worked with Americans for about 2 years. During job interview he was told that his English CV is quite OK. He answered that written English it is much more easier then spoken English ... Well he did not get the job
- so should you say your english is good or bad?
- IMO if your english is bad, you can still say your english is good, but also you have to be able to prove it. E.g. my English is good, because I worked with Americans 2 years and I have not had any problems ...

IMO the CV is about personal marketing and PR and clever manipulating of facts. Like politics.

I do not say it is good, I do not say it is bad.
15 years ago
- Instead of putting "Web app developer" on my resume,
- can I put Java/J2EE Software Developer?

what about "Senior J2EE Specialist" ???

same job as a web developer, but sounds better ...

also in my free time I am developing with my friend a small app for our department; so in my CV I have: "J2EE/Database Architect and Project Manager" ...
15 years ago