Michael,
In response to your questions:
1. Will we have to comment out the CONFIG_FILES
content parameter every time we open Jdeveloper? Is
this something that you would use a scripting tool
for?
Yes, you would have to do this every time. The chances that it will be fixed in a future JDeveloper release increase with each customer that logs a Service Request for it in MetaLink (
http://metalink.oracle.com).
We haven't used a scripting tool for this. If you find a way to automate it, please share it with us!
2. I'm sure I have read that JDeveloper is optimized
for 1GB internal memory. Has this changed with later
releases, or does this become insufficient when the
JHeadstart extension is installed? From the feedback
in the Jdeveloper forum, it would seem that
performance issues are not as common as they used to
be, so I'm a bit suspicious!
It's true that each JDeveloper extension increases the amount of internal memory used, so you could optimize by installing as little extensions as possible (see also
http://blogs.oracle.com/duffblog/2006/08/22#a346). Running Embedded OC4J also increase the amount of memory used.
You can check how much memory JDeveloper is using by turning on the Memory Monitor (see
http://blogs.oracle.com/duffblog/2006/09/10#a355 how to do that).
Of course the required memory also depends on what other programs you want to run simultaneously (browser, editor, email, SQL tool, etc).
3. I can see that opening jspxs by default in the
Source editor is handy if you only want to look at
code or version history, but there doesn't seem to be
a benefit when using the design editor - is that what
you would expect?
The only benefit is that you save the time of opening the Design editor if you are not going to need it for that particular file. Not only for the jspx files, but also for the faces-config files. If a faces-config file does not contain any navigation rules but only managed beans, the visual design is not useful anyway.
4. I have already tried to install KeepResident, but
it doesn't work with our configuration. I think this
is because our Jdev_User_home is not the same as the
JDeveloper home directory. Would you expect a big
performance improvement from this, or is it just to
deal with the problems when you have minimised
Jdeveloper and it takes a long time to redraw?
The latter, and probably also when you switch between applications without actually minimizing JDeveloper.
5. Have you experienced the problems we are having
when changing properties in the jspx design editor?
Yes, and that's why we prefer to make changes in the source code instead.
Hope this helps,
Sandra Muller
JHeadstart Team
