JDeveloper: An expected severe error has occured

Popup to show An expected severe error has occured in JDeveloper

The program may be unstable, which could result in data loss. Decide how you want to proceed and click OK.

• Save and exit
• Exit without saving
• Continue

Error details

Uncaught exception
java.lang.OutOfMemoryError: Java heap space
  j.util.Arrays.copyOf(Arrays.java:2882)
  j.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:100)
  j.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:390)
  j.lang.StringBuffer.append(StringBuffer.java:224)
  org.tmatesoft.svn.core.SVNErrorMessage.getFullMessage(SVNErrorMessage.java:257)
  org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:58)
  org.tmatesoft.svn.core.internal.wc.admin.SVNAdminAreaFactory.open(SVNAdminAreaFactory.java:163)
  org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.doOpen(SVNWCAccess.java:364)
  org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.open(SVNWCAccess.java:272)
  org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.open(SVNWCAccess.java:265)
  org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.openAnchor(SVNWCAccess.java:145)
  org.tmatesoft.svn.core.wc.SVNStatusClient.doStatus(SVNStatusClient.java:320)
  org.tmatesoft.svn.core.javahl.SVNClientImpl.status(SVNClientImpl.java:296)
  org.tmatesoft.svn.core.javahl.SVNClientImpl.status(SVNClientImpl.java:278)
  org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.getStatus(AbstractJhlClientAdapter.java:480)
  org.tigris.subversion.svnclientadapter.svnkit.SvnKitClientAdapter.getStatus(SvnKitClientAdapter.java:141)
  org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.getStatus(AbstractJhlClientAdapter.java:466)
  o.ji.vcs.svn.SVNURLInfoCacheSimpleStrategy.getURLInfo(SVNURLInfoCacheSimpleStrategy.java:79)
  o.ji.vcs.svn.SVNURLInfoCache.getPropStatus(SVNURLInfoCache.java:59)
  o.ji.vcs.svn.SVNStatusResolver.getStatus(SVNStatusResolver.java:159)
  o.ji.vcs.svn.SVNStatusResolver.populateStatuses(SVNStatusResolver.java:82)
  o.ji.vcs.generic.GenericClient$2.getImpl(GenericClient.java:531)
  o.j.vcs.spi.VCSStatusCache.getValuesImpl(VCSStatusCache.java:31)
  o.j.vcs.spi.VCSURLBasedCache.getValuesImpl(VCSURLBasedCache.java:204)
  o.j.vcs.changelist.ChangeListLocalStatusCache$2.call(ChangeListLocalStatusCache.java:78)
  o.j.vcs.spi.VCSURLBasedCache.callUnderWriteLock(VCSURLBasedCache.java:224)
  o.j.vcs.changelist.ChangeListLocalStatusCache.getValuesImpl(ChangeListLocalStatusCache.java:73)
  o.j.vcs.spi.VCSURLBasedCache.getValues(VCSURLBasedCache.java:107)
  o.j.vcs.changelist.ChangeListEventQueue.filterByStatus(ChangeListEventQueue.java:513)
  o.j.vcs.changelist.ChangeListEventQueue.processRequeryEvent(ChangeListEventQueue.java:373)
  o.j.vcs.changelist.ChangeListEventQueue.processEvent(ChangeListEventQueue.java:258)
  o.j.vcs.changelist.ChangeListEventQueue.processEvents(ChangeListEventQueue.java:685)

When you get this error, probably there is an error with your application too, close the application and JDeveloper and start from scratch.

Tips to avoid this:
1. While working with JDeveloper, you need to close and open application so many times. When I want to delete an application, I will choose to Close Application rather from Jdeveloper and then delete the application folder physically later after closing JDeveloper.
2. After running JDeveloper for long, it starts consuming more memory, give it a break, close the JDeveloper and open it again.
3. Always refer the external jars as user library, create a library name to your physical path and then extend the library to add external jars to the classpath.

SOA Composite Cheat sheet

Declaring a new variable of XMLType
Technically it can be defined in any scope of any XMLType (if not found import it), but it is recommended to define it where it is really needed.
Create a new scope in the block where it is needed and define it, otherwise it may throw totally unrelated exceptions - you will not be able to figure out.

Initializing a new variable of XMLType already declared
Any XMLType variable must be initialized before it is getting used.


How to avoid generation of xmlns="" while doing mapping in xpaths
Declare and initialize the parent XMLType variable and while assigning or appending use the child of the newly defined variable to avoid getting xmlns="" in the xml tag.


How to append instead of assign while mapping xpaths
Do the mapping as you normally do first. Once mapping is done then right click the mapped path and convert it to append, it should create a + plus icon in the left xml xpath which shows that it got converted to append instead of assign.

Oracle Business Rules Cheat sheets

Section 1: Oracle Business Rules

Details:

• When facts are modified as part of action inside business rules, business rules are getting fired again based on the new data
• Priority/Order can be set in business rules in order to call them in a particular order
• Business rules can be made active/inactive by checking the "Rule Active" check box
• Inactive business rules are not getting fired and are same as commented code

Section 2: Oracle Business Rule Facts

Details:

• Facts can be defined as RL Facts and properties (one or more) can be added to the fact.
• While defining a property as an ArrayList, defining the property's array list item type (e.g. Person type fact) throws an undefined fact error, so its better to leave the array list item type as blank.
• Facts can be asserted using assert new action in initial action, these assertions will not be maintained by names -
• Facts can be created using assign new and then can be asserted, these will be available by names as well
• Facts are directly accessible in Oracle Business Rules
• Facts are not accessible in BRE Functions
• Collection of facts or fact itself can be passed from Oracle BRE to function while calling the function
• Facts need to be used in BRE, if they are not used in BRE, BRE cannot be compiled and deployed even if they are used in initial actions

Section 3: Oracle Business Rule Functions

Details:

Section 4: Oracle Business Rule Initial Action

Details: