I have been working with the new developer release for a while now and have found it to be very stable. There are some really nice problems that were corrected from the previous version like XPath specifications in XSL document. You may ask, "what do I care about JDeveloper if I am using Siebel?" Good question, with lots of answers:
- JDeveloper is FREE! Not only can you use it but so can your clients.
- Editing XSD is a real pain without an editor. However, make sure you also set up the WS-I validation tool.
- Editing WSDL is also a real pain unfortunately even with an editor. But hey, you really need to get to know this at a low level anyway. Once you get used to the JDeveloper editor it is pretty good. Unfortunately the validation is not as strong as I would like to see.
- XSL TRANSFORMS!!! One of the biggest features is that you can use the XSL editor which is a huge time saver. I have to admit though that it is easy to confuse the editor via hand edits. Still working on how to avoid that.
- Remote debugging. You need a real editor to debug you Siebel business servies. WHAT!? You say you are not using Java business services? Shame on you.
Comments (5)
Richard,
We used JDev for the Siebel WebUIDDK session at OOW Xtreme weekend. Bob Taylor wrote a nice batch file to move the output from the DDK wizard to the appropriate JDev folders.
Posted by Scott Hall | November 15, 2006 9:20 AM
Posted on November 15, 2006 09:20
Another couple of things it's great at are BPEL diagrams (we've been talking to the Business Analysts about these) and also UML diagrams. Again, Siebel might not use the full end-to-end UML "Transformation" functionality that lets you generate classes from a Class Diagram (which is great for documentation) but it works well and can output the diagrams as pictures for insertion into a design doc!
Posted by Graham Nicol | January 9, 2007 12:40 PM
Posted on January 9, 2007 12:40
mmmmm.....
Using a Java Business Service in Siebel. Ok, I'll bite: Why would I use a Java BS instead of JavaScript?
Posted by Gino Fortunato | January 23, 2007 10:50 AM
Posted on January 23, 2007 10:50
Personally I like to use a Java BS so that I have access to the full capabilities of the language and IDE. The full cpabilities fo the Java langues speaks for itself. The IDE comment has a couple specific points. First, I can use the IDE debugger to tune my code. This can be done first when running JUnit tests and then via remote debugging when the JBS is running in Siebel. JDeveloper lets me attach to a remote JVM for debugging like the one running in Siebel. In my eyes the JDeveloper debugger is far superior to the one in tools. One other nice thing is that the Siebel runtime does not cache the Java classes or JAR files it uses. So when you are testing and find a bug, you can recompile and package into a JAR prior to re-executing the tesst. No need to re-start the application. Even if that characterisitc is not runtime efficient, it is convenient!
Posted by Richard Naszcyniec | January 23, 2007 12:00 PM
Posted on January 23, 2007 12:00
Ok, so now I think I get it: 1) 100% agree regarding the capabilities of Java language and 250% on capabilities of JDeveloper Debugger. 2) in BC event, call the java business service as you would with any other BS and 3) (this is the one I was missing) Java does not need to know about Siebel objects because the values are passed to it via a property set! It's amazing what I can learn reading about the Java Business Service in Bookshelf!
Posted by Gino Fortunato | February 22, 2007 11:46 AM
Posted on February 22, 2007 11:46