Andrew Spruce

+ Follow
since Feb 27, 2001
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 Andrew Spruce

I'm with Walter on this. The use cases are the same. Why develop different components that perform exactly the same task?
Is this not a little detailed for the architect exam. After all a deployment diagram is not part of the deliverables
I would guess that the design should avoid making assumptions for vendor specific features if possible, where unavoidable they should be stated in the assumptions.
The requirements usually indicate a need for scalability.
This is often done horizontally through clustering and therefore requires remote interfaces. Clustering doesn't always achieve an improvement in performance but it is one of the scalability features of J2EE that I guess the Sun people are looking for
I guess you don't even need to mention which method because as already mentioned, the lookup logic should be hidden behind a BusinessDelegate.
Just my two-penneth
Try for their community edition. You need to put the sequence/collab diagrams into seperate projects as it only supports one diagram of each type per project but it works well and provides the image export required for part II submission.
Surely Authentication is not an all or nothing thing. Like a previous poster said, gaining access to the admin console presumes some sort of authentication has taken place (although there is nothing to say this screen is not available to all logged in users).
We use JAD. Very quick with useful integration into JBuilder via an OpenTool.
We use JBuilder with WLS 6.1 SP2 but because of poor support of WLS in JBuilder 4 we integrated Apache's Ant build tool and use AntRunner a JBuilder OpenTool. This works well for our rather complicated build.
Looking at WLS support in JB7 though the support seems much better.
I share his enthusiasm. The ability to browse to class definitions using ctrl-enter, to view references to a given instance or class using ctrl-shift-enter and the ability to automatically open a class definition by name using ctrl-minus rather than having to remember which package it is in is extremely useful.
The "suggestion" import of undeclared but required packages also "rocks".
I think you could either :
1) Add throws FredException to fred() in derived.
2) Have SomeOtherException extend FredException.
17 years ago
Were you aware that there is a Properties class in the standard libraries with correspoding load() and store() methods to write to and read from an OutputStream/InputStream.
This would probably be cleaner than trying it yourself
17 years ago
I noticed that instead of the apache xalan packages, there are weblogic supplied versions e.g.
instead of
When I used these, things went sweet.
18 years ago
Doesn't this syllabus overlap with the Sun Certified Enterprise Architect exam ? I thought SCEA covered Servlets, Applets, EJBs and JSP, that only leaves Java Beans that is different.
Well done !
Just one quickie.
I see you got 100% on the documentation.
Did you allow javadoc to copy documentation for public methods from comments defined in the interface (where they exist) or did you write comments for all public methods yourself ??
I think these methods all work ok if no security manager is used.
However if you define a security manager, either explicitly in your code or through the option then java starts to get picky about permissions.
I have chosen not to use the AllPermissions option as this seems to be the same as not bothering with the security manager at all.
I think the policy file is useful if the user would like to review the permissions granted to the application and make the decision whether or not the code could be malicious.
By allowing all permissions it could delete his home directory for instance.
But if you are explicit in the policy file, by say defining that the app can only create or delete files in the current directory and all subdirectorires. Then the user has a bit more confidence.
Anyone disagree ?
[This message has been edited by Andrew Spruce (edited April 26, 2001).]
How complex should the GUI be ?
I am unsure as to how sophisticated I should make the user interface. Is it wise to play exactly to the spec e.g.
Only allow searching on the 2 fields cited or provide more ?
Do I provide sorting or not - this is particularly worrying as there is a mention in the spec that elaborate algorithms should not be used where standard solutions already exist, but on the other hand it would seem a natural feature to include for a JTable.
Are toolbars necessary given the limited functionality ?
Do I bother with status bars, MicroHelp About boxes etc ?
Should I provide asynchronous requests to the remote client by implementing multithreading ?
Does any of this matter much ?
Also thought I'd sound this one out.
With a mind to anticipating future requirements (referred to in the spec)
I was going to provide an xml file that defined the JComponents, fields to be queried on, validation required, data type etc along with code to dynamically build these as controls at run time.
I think I have decided against this, partly due to a lack of confidence in whether the org.xml.* packages are admissable (despite being part of the Production JDK) and partly because I feel it may be seen as over-engineering.
Also, there are 2 perfectly reasonable implementations of JTable utility classes provided in the demos section of the JDK. In the spirit of code reuse It would seem sensible to include these (With accreditation of course), but I have doubts the examiners would see it that way.
Any thoughts ?
Wouldn't it make sense to declare the class abstract anyway? given that it has no method implementations.
This would stop it from being used directly.

[This message has been edited by Andrew Spruce (edited March 27, 2001).]
[This message has been edited by Andrew Spruce (edited March 27, 2001).]