Learning about the Oracle Cloud and the new Alta skin.

I had a conversation with +David Haimes on twitter the other day about blogging, and realized I have not been blogging for a long long time.

While I can find information about almost everything with Google or Stack Overflow, I realized that it's sometime hard to find the one piece of information which is relevant for you, in your current context.

It usually ends up being a compilation of multiple blog posts or answers; it's the curated content which brings most of the $$$ value.

As I go through the process to discover how to use the Oracle public cloud, I am going to blog about the learning process, here.

The first advise I'll share is this one:

For any sample you are using, start with Git

Here is why:

  1. Once you have a working version, commit and push to the remote.

    It give you the following benefits: easy to share with your peers - you have a backup for 'free' - in case the next set of changes break something in a bad way, rolling back is a breeze.
  2. Once you have a broken version, rollback is cheap - see above ;)
  3. Once you are happy with your work, it's ready for other to view and use

    You have no extra step required, and other may even find it valuable before you consider to be done with it. 
Here is my new GitHub account where I will start to follow the same rule in the coming days:

The specific blog post I wanted to reference today is this one: http://markchensblog.blogspot.com/2014/05/develop-and-deploy-jersey-restful.html

It's a great post, and I do not need to replicate it's content here. 

Only issue I had was that jersey-bundle-1.9.war was not present on the distribution I used to deploy to my cloud instance - I was using JDeveloper 11.1.1.7.1 and I could only find jersey-bundle-1.1.5.1.war on my local wlserver_10.3\common\deployable-libraries folder.

The fix is also trivial - get a newer version and install it as documented in the blog post referenced above.


Today, the sample I'll love to see in a Git repository, so I can Scan the code to learn how it was built before I Commit to it and run the sample on my local instance - it's the Oracle Alta demo.

There is a new code sample available on OTN for Alta skin - source: http://t.co/kZ0794V4R1 (or http://www.oracle.com/technetwork/developer-tools/jdev/index-098948.html#alta) It would have been nice to get it from https://github.com/oracle/Oracle-Cloud (or some other repo).

As I am proof reading my billet, I realized that this is the second advise I would have love to get from someone more knowledgeable -my mentor- with the Oracle public cloud development model.

It's give me an easy follow-up post for next year.

Comments

Post a Comment

Popular posts from this blog

Changing the version of JDK used by JDeveloper

I have recently learned a quick and lazy way to change the version of the JDK used to run JDeveloper 10g R3. I am sure there is an option somewhere in the configuration screen to do the same, which I couldn't find... While JDeveloper is not running, locate the embedded JDK on disk and rename (or delete) that directory. For me, it was C:\opt\jdev\jdk. Once it's done, restart and you will by asked to locate the version of the JDK you want to use. It's another step to get going with JAVA on Vista. -ecco
Read more

Connection reset from a WCF Web Service

Here is an error message you may see, when calling WCF Web Services from java: IOException retrieving the response: java.net.SocketException: Connection reset As it may not be obvious the first time you see it, this may save you some time. One reason for this behaviour is when the WCF endpint is expecting to see wsa:Action SOAP header in the request. To find out if you are facing this case, you have to look inside the WSDL, and search for the policy that describes the contract for your endpoint. <wsp:Policy wsu:Id="CustomBinding_Echo1_policy">   <wsp:ExactlyOne>     <wsp:All>       <wsaw:UsingAddressing/>     </wsp:All>   </wsp:ExactlyOne> </wsp:Policy> To make this a concrete example, here is a sample WSDL . To find the policy, you will need to follow the import as the policy are not always advertized in the top-level document. Here is how the import looks:   <wsdl:import namespace="http://example.org/" location="h
Read more

unexpected null value for literal data

There is a challenge that is hard to overcome at first; making sense of error messages. You can always Google with the text of the error, “unexpected null value for literal data” and hope to be lucky . If you are using Oracle Application Server 10.1.3.0, here is the explaination for the message and two ways out. The Exception: unexpected null value for literal data at oracle.j2ee.ws.common.util.exception.JAXRPCExceptionBase.<init>(JAXRPCExceptionBase.java:52) at oracle.j2ee.ws.common.encoding.SerializationException.<init>(SerializationException.java:26) ... The relevant schema: <complexType name="Customer"> <sequence> <element name="address" type="tns:Address"/> <element name="firstName" type="string"/> <element name="lastName" type="string"/> </sequence> </complexType> A sample code that will cause this exception: public void testServ() throw
Read more