Productive Java Based Application development
Oracle JDeveloper is a free integrated development environment that
simplifies the development of Java-based SOA and Java EE applications.
JDeveloper offers complete end-to-end development to Oracle Fusion Middleware
and Oracle Fusion Applications with support for the full development life
cycle.
Integerated Development Environement
Oracle JDeveloper integrates development features for Java, SOA, Web
2.0, Database, XML and Web services into a single development tool. The various
artifacts share the same project structure and development experience,
simplifying both the learning curve and the development process of composite
applications that leverage a multitude of technologies.
Full Life Cycle Support
Oracle JDeveloper covers the full development lifecycle from initial
design and analysis, through the coding and testing phases, all the way to
deployment. Developers can design, generate, and visualize their code with UML,
Java and database diagrams. An advanced coding environment and declarative and
visual editors facilitate faster code development. Integrated testing,
profiling, and code auditing features ensure the quality of the applications.
Interfaces with versioning, build, and deployment tools enable packaging and
deployment of the applications.
Additionally, the new Oracle Team Productivity Center product adds an integrated hot-pluggable application lifecycle management (ALM) solution into JDeveloper. Developer can directly interact with a host of requirement-gathering and progress tracking solutions Visual Declarative
Oracle JDeveloper focuses on increasing developers productivity by
offering a visual and declarative approach to application design. A combination
of visual editors, property inspectors, structure panes, and editing dialogs
simplify and eliminate tedious coding. These declarative features provide a
simpler way to define the components that construct an application. The
application’s code is always accessible for direct manipulation as well. Changes
can be made by either the declarative means or directly in the code and are
reflected in both simultaneously.
Productive Development Framework
Oracle JDeveloper is the development environment for the Oracle
Application Development Framework (Oracle ADF). Oracle ADF is an end-to-end
development framework, built on top of the Enterprise Java platform, and
offering unparalleled productivity. The framework provides integrated
infrastructure solutions for the various layers of the application including
data access, business services development, a controller layer, rich Web, mobile
and desktop interfaces, data binding, and security.
Oracle JDeveloper offers features that simplify the development of ADF based application through its visual and declarative editors. Complete Development ToolOracle JDeveloper integrates the full set of features needed for developing composite applications with specific features that address the following technologies:
|
Saturday, 12 January 2013
JDeveloper - Integerated Developer free application tool
Monday, 19 December 2011
Simple Detail Stamp in af:Table
In this Post i am going to do a Simple DetailStamp in af:Table
I had created a EmployeeVO and DepartmentVO I had also created a ViewLink between these two VO's Such as
Employee.deptid = Department.deptid
Drag and drop departmentVO in jspx page as a af:table. In the Structure if you expand af:table there would be a table facet Now drag and drop DepartmentVO as af::form in Detailstamp So that for particular department if we expand the node we would get the employees list of that department
Thus the simple detail stamp had been emerged
I had created a EmployeeVO and DepartmentVO I had also created a ViewLink between these two VO's Such as
Employee.deptid = Department.deptid
Drag and drop departmentVO in jspx page as a af:table. In the Structure if you expand af:table there would be a table facet Now drag and drop DepartmentVO as af::form in Detailstamp So that for particular department if we expand the node we would get the employees list of that department
Thus the simple detail stamp had been emerged
Thursday, 15 December 2011
Navigating from af:Quick Query To af:query
This was my first post regarding the navigation of af:quickQuery panel to af:query panel
Initially i had created my ViewCriteria in my VO namely GlJrnlHdVOCriteriaQuery.I had dragged and dropped my ViewCriteria as my af:query in my jspx page and add a command button in that tool bar such that if user press the command button it can be navigates to af:quick query.
<af:query id="qryId1" headerText="Search" disclosed="true"
Now Drag and drop an adf:quickQuery to your jspx page and provide value,model,querylistner and query operation listner ., In this i simply copied and pasted all this from af:query.Initially the command link advance property will be false make it as true so it will be visible in the UI.
Here i had two methods quick2advanced and advance2quick which provides the render property in the UI
Here is the following methods that had been used in the Managed Bean
Initially the rendering property of af:quickQuery quickQueryVisible is true such that it would be visible in the UI Now when the user clicks the advance button the rendering property of af:quickquery will get false such that it enables the af:query to be visible in UI. Now we are using Switcher Component to switch from af:quickquery to af:query
Thus the following result is obtained
Now if the user clicks the Advance button it navigates from af:quickquery to af:query Then if the user clicks Basic button it navigates from af:query to af:quickQuery
Initially i had created my ViewCriteria in my VO namely GlJrnlHdVOCriteriaQuery.I had dragged and dropped my ViewCriteria as my af:query in my jspx page and add a command button in that tool bar such that if user press the command button it can be navigates to af:quick query.
<af:query id="qryId1" headerText="Search" disclosed="true"
value="#{bindings.GlJrnlHdVOCriteriaQuery.queryDescriptor}"
model="#{bindings.GlJrnlHdVOCriteriaQuery.queryModel}"
queryListener="#{bindings.GlJrnlHdVOCriteriaQuery.processQuery}"
queryOperationListener="#{bindings.GlJrnlHdVOCriteriaQuery.processQueryOperation}"
binding="#{backingBeanScope.GeneralJournal.qryId1}"
rendered="#{backingBeanScope.GeneralJournal.queryVisible}"
modeChangeVisible="false" rows="1" maxColumns="5">
<f:facet name="toolbar">
<af:commandButton text="Basic"
binding="#{backingBeanScope.GeneralJournal.cb2}"
id="cb2"
actionListener="#{backingBeanScope.GeneralJournal.advanced2Quick}"/>
</f:facet>
Now Drag and drop an adf:quickQuery to your jspx page and provide value,model,querylistner and query operation listner ., In this i simply copied and pasted all this from af:query.Initially the command link advance property will be false make it as true so it will be visible in the UI.
<af:quickQuery label="Search"
value="#{bindings.GlJrnlHdVOCriteriaQuery.queryDescriptor}"
model="#{bindings.GlJrnlHdVOCriteriaQuery.queryModel}"
queryListener="#{bindings.GlJrnlHdVOCriteriaQuery.processQuery}"
queryOperationListener="#{bindings.GlJrnlHdVOCriteriaQuery.processQueryOperation}"
binding="#{backingBeanScope.GeneralJournal.qq1}" id="qq1"
rendered="#{backingBeanScope.GeneralJournal.quickQueryVisible}">
<f:facet name="end">
<af:group binding="#{backingBeanScope.GeneralJournal.g1}" id="g1">
<af:commandLink text="Advanced" visible="true"
binding="#{backingBeanScope.GeneralJournal.cl1}"
actionListener="#{backingBeanScope.GeneralJournal.quick2Advanced}"
id="cl1"/>
</af:group>
</f:facet>
Here i had two methods quick2advanced and advance2quick which provides the render property in the UI
Here is the following methods that had been used in the Managed Bean
public boolean isQuickQueryVisible()
{
return _quickQueryVisible;
}
public boolean isQueryVisible()
{
return !_quickQueryVisible;
}
public String getVisibleComponent()
{
if(_quickQueryVisible)
return "quick";
else
return "advanced";
}
private boolean _quickQueryVisible = true;
public void quick2Advanced(ActionEvent actionEvent) {
// Add event code here...
_quickQueryVisible = !_quickQueryVisible;
}
public void advanced2Quick(ActionEvent actionEvent) {
// Add event code here...
_quickQueryVisible = !_quickQueryVisible;
}
Initially the rendering property of af:quickQuery quickQueryVisible is true such that it would be visible in the UI Now when the user clicks the advance button the rendering property of af:quickquery will get false such that it enables the af:query to be visible in UI. Now we are using Switcher Component to switch from af:quickquery to af:query
<af:switcher facetName="#{demoQueryToggle.visibleComponent}" defaultFacet="quick"
id="s4">
<f:facet name="advanced">
<af:outputText id="resultTextId"
value="Query statement is as folows: #{demoQuery.sqlString}"/>
</f:facet>
<f:facet name="quick">
<af:outputText value="#{demoQuickQuery.sqlString}" partialTriggers="search"
id="ot5"/>
</f:facet>
</af:switcher>
Thus the following result is obtained
Now if the user clicks the Advance button it navigates from af:quickquery to af:query Then if the user clicks Basic button it navigates from af:query to af:quickQuery
Subscribe to:
Posts (Atom)
