There are so many books out there that are of great value. Being an architect is not specific to one book or one type of technology. Even the SCEA understands the concept of using J2EE in the right context.
There are also a number of different types of architect and therefore you need to decide which path to take. The SCEA refers to Enterprise Architect but in fact it is actually more specific to Application Architecture while the Sun Enterprise Architect course covers application, data and technical architecture from a software and system architect perspective - confused - its gets worse! An Enterprise Architect is at a much higher abstraction and covers business and technical architecture but not at a detail required to define components (i.e. the EA is more interested in conceptual system relationships and how they enable the business enterprise).
The SCEA is actually [enterprise] application architecture from the perspective that it provides a level of measurement to the understanding of developing enterprise applications - but not enterprise architecture, which is someone very different.
Two years is a very short time but identifying your career path now is a very healthy and positive approach. It took me twenty years of knowledge building and experience to become an architect - although it is only the last five years that I've aimed for that specific role because I was enjoying myself too much as a designer/developer! My first two years as a programmer was so intensive and concentrated that I didn't have time to think about learning skills beyond foundation principles.
Ian Roberts<br />Application Architect<br />SCJP, SCJD, SCEA, OCUP Fundamental
catch it before it slithers away! Oh wait, it's a tiny ad: