Re: Five Oracle Wishes
A little while ago Brian Duff posted five wishes and asked other bloggers to post theirs. So here I go:
5. JDeveloper offers the same database support as SQLDeveloper.
Right now, I need two tools whenever I am developing an application and need to do something in the database that goes beyond select * from dept. It would be great if I only needed one tool for all my development (Java, BPEL, XSLT, PL/SQL etc)
4. Delete in JDeveloper does what it says it does: delete a file or component, …….not filter it!
When I develop, I create files and components, that I very regurlarly delete again. Especially when I am researching a specific topic. My source control will save me: if I accidently throw away something I can retrieve it from the source control system. Or even from the recyclebin in Windows. In Eclipse, when you press delete, it will physically delete the file from your system, exactly what you expect. In JDeveloper, pressing delete will filter the file from the workspace! Arrrrgh! It is and alway has been a real hassle to actually delete something from the filesystem using JDeveloper!
3. Maven support in JDeveloper
Managing libraries in JDeveloper is not very user friendly when you are working in a team. I like the Ant support in JDeveloper. But you end up writing the same type of buildfiles, that get extremely large, over and over again. Most of that is much easier using Maven. Another scripting tool would be fine too, but a lot of developers already know and use Maven, so why reinvent the wheel?
2. Versioning of ESB services
Right now, you can version stuff that is deployed in the BPEL process manager, but not in ESB. However, this is really needed in a production system: you need to know what version of a transformation service or adapter you are calling.
1. One (SOA) governance solution
Oracle has a strong SOA Governance package. If you want to secure, monitor, version, lookup your service, application or adapter you need several tools: ESB control, UDDI register, BPEL control, Enterprise Manager, Webservices manager. It would be great if this would be intergrated into one tool!
Comments: (2)
5. Cool, i checked it out. I can even update SQLDeveloper from the update center. Great!
4. Yes that is the difference I am referring to. I tried your suggestion, it works. But only for files, not for components like a bean. IMHO you should really change the meaning of ‘delete’. I have seen that with new users (that are experienced Java developers), this is unexpected behavior that causes a lot of confusion.
3. This plugin is a very good starting point, thanks for pointing it out. It is not exactly what I meant: it would be nice if this would be intergrated in JDeveloper, like an extension.
Blogs
- 26 Jul
- 10 Jun
- 02 Jun
- 26 Mar
- 25 Feb
-
05 Nov
Some tips & tricks on migrating SOA Suite 10g to 11g – Part 2
- 04 Nov
- 02 Nov
- 25 Oct
- 20 Oct
- Best practices 2 - Web Services
- Fault handling in Oracle SOA Suite 11g - Part II
- Fault handling in Oracle SOA Suite 11g
- Experiences with Vista and Oracle software (2)
- Migrating Web Services from JDeveloper 10g to 11g
- Migrating EJB 3 applications from OC4J to WebLogic
- Best practices for BPM, SOA and EDA
- Some tips & tricks on migrating SOA Suite 10g to 11g - Part 2
- Logging messages in Oracle SOA Suite 11g using OWSM
Loading ...
5. This is already in there in the technology preview of JDeveloper 11.
4. I guess this is the difference between “remove from project “and erase from disk – an option under the file menu.
You can probably create a very simple delete file context menu using the tools->external tools option and adding
a delete command passing in the file name as a parameter.
3. see this one