Intellisense for BPEL development

Hi guys,
Just wondering when Jdev will have intellisense(microsoft term) built into the BPEL development? eg.Java embedded activity, it's a nightmare, just like writing code in a notepad.
Regards
James

Hi,
I'm unfamiliar with the BPEL design time, so can't comment on why it doesn't provide this functionality. You may want to post this over on the BPEL forum (BPEL JDeveloper provides core capabilities for intellisense (we call it "code insight" in JDeveloper), for example you can see it in the code editor.
Thanks,
Brian

Similar Messages

Eclipse plug-in for BPEL development

Hi
I have downloaded an Eclipse plug-in for Oracle BPEL process manager around 2 years ago. I don't see the plug-in on the downloads page anymore so I was wondering whether this plug-in is still supported/enhanced. We are solely using Eclipse in our organization and JDeveloper is not an option- so does anyone know of any other plug-ins for BPEL development for Eclipse?
Thanks.

There hasn't been a new Eclipse plug-in for BPEL in long time. The old ones available are out of sync of the new functionality and are supported on only the older versions of Eclipse. You can google for exact details.
But my advise is that if you are using the Oracle BPEL PM, then use Jdeveloper.
--Shiv

Urgent Need in Dallas Texas for a Sr. Oracle BPEL Developer

$$$$$$$$$$$$
I have an urgent need for a Sr, Oracle BPEL Developer in the Dallas Texas area. With this position, you can interview and start immediately. If you are interested or know of anyone looking please send my way. Or know of companies that use BPEL would be helpful too.
Warm regards,
Kim Dobson
Sr. Account Manager
Eventus Group Technology Resources
10100 N. Central Expressway
Suite 150
Dallas, TX 75231
Office 469.916.4857
Mobile 214.277.2097
Fax 469.916.3861
[email protected]

I was told by Dave Shaffer, Director Product Management, Oracle BPEL Process Manager to do this posting here. I am sorry but this is a critical need for me and was just looking for help.
Kim Dobson

XSLT and XQuery recommendation for BPEL and OSB

Hi,
1. Why is XQuery recommeded for OSB and XSLT for BPEL. Are there any specific performance optimization reason behind this.
2. Apart from OSB and BPEL, both XSLT and XQuery has xml transformation options and creating HTML. What is the difference between these two.
Thanks in advance!

you can create the graphical view of Xquery in Eclipse but not for XSLT
Xquery is much faster than XSLT in OSB.
Through XSLT however you can achieve more complex transformation.
OSB has its historic origins in BEA Aqalogic stable and so Xquery was widely used used even though XSLT is supported. It is a matter of choice(your standards in your organization,your developer skillsets,your re-usable libraries etc )
In Jdeveloper you can develop xslt in graphical mode though and attain complex transformation

How to set password for BPEL domain

Hi,
I am new to SOA.
I want to setup client-server environment for few developers.
I installed SOA 10.1.3.3 in the server machine.
And I created few domains in BPEL, one for each developer.
It didn't ask me to set the password while creation of the domain.
Please let me know how to set password for newly created domain so that each developer login to his/her own domain and manage processes.
Thanks!!!

Thanks for the prompt response.
What roles should I give to my developers to allow them to manage their services in ESB control, BPEL control, WSM control.
And I would like to know how to set the password for a BPEL domain too.
Message was edited by:
user644377

[svn] 3680: Modifying ant build.xml to allow for a local. properties for individual developer build config.

Revision: 3680
Author: [email protected]
Date: 2008-10-16 07:58:21 -0700 (Thu, 16 Oct 2008)
Log Message:
Modifying ant build.xml to allow for a local.properties for individual developer build config. Also moving ja_JP locale to the other.locales target (this is called during build machine packaging and isn't needed by dev by default).
QE: No
Doc: No
Checkintests: Pass
Reviewer: Discussed with Jim
Modified Paths:
flex/sdk/trunk/build.xml
flex/sdk/trunk/frameworks/projects/airframework/build.xml
flex/sdk/trunk/frameworks/projects/framework/build.xml
flex/sdk/trunk/frameworks/projects/rpc/build.xml

I tried
ant deployTestSuites
this works. If i do that with the wrong domain (dep_cotrol vs dep_me) name it fails with
ORABPEL-02052Cannot lookup BPEL domain.The BPEL domain "dep_cotrol" cannot be found; the domain may not have initialized properly.Please verify that the BPEL domain loader has a valid set of initialization properties in the application properties file.
So i think my config is ok. There is a bug in this ant bpelTest which ignores the domain?

Jdeveloper CVS for BPEL & ESB projects

Hi All,
In my project, we have decided to use CVS (integrated with Jdeveloper 10.1.3.4) as version control system for BPEL & ESB project codes.
In this regard, I would like to know what are the best practices followed in scenario like this,
I have 8 to 10 BPEL & ESB projects related/dependent on each other which were developed for a project release XYZ. We would like to organize the code in CVS based on project's release. For example group BPEL & ESB projects under one logical group name.
XYZ
|--> BPEL Project 1
|--> BPEL Project 2
|--> ESB Project 1
|--> ESB Project 2
|--> BPEL Project 3
My question is, should I treat each BPEL & ESB project as a module or should I treat project release XYZ as a module.
In later case, I think I would end up checking out/in all BPEL & ESB projects under XYZ eventhough I wanted to work on only one BPEL/ESB code. Not sure if this is acceptable.
In former case, I would be able to checkout & checkin only the BPEL & ESB code which I would like to update without impacting any other code.Which I believe as acceptable. Since I already have a parent repository 'PQR' should I have to define XYZ as a sub repository to PQR. At end of the day,we would like to make CVS appear something like this. Since I am new to CVS do you see any disadvantage with this approach.Your help is greatly appreciated.
PQR
|-->XYZ
|--> BPEL Project 1
|--> BPEL Project 2
|--> ESB Project 1
|--> ESB Project 2
|--> BPEL Project 3
|-->YYY
|--> Java Project 1
|--> Java Project 2
Thanks,
RA

Hello Naresh,
As per my knowledge you can migrate through instances in two ways.
One way is to modify the build.properties file with the host information of you destination systems, changing the build.xml file with the proper wsdls. In this case you would risk providing the PROD passwords as you need to provide them in the build.properties file.
The second way is to build ant scripts which are run on the server and the processes get deployed on the Application server.
Thanks
kris

Flash tutorial for BPEL and ESB stuff

Hi
Thank you for reading my post
is there any flash tutorial for BPEL and ESB support of Jdeveloper ?
something step by step which helps me to learn these features of jdeveloper.
thanks

Thank you for the link, it was good.
I want to ask something that i found confiusing.
there are more than one BPEL designer (development environment) available from ORacle.
One is Eclipse based, one is Jdeveloper,...
i want to know, which one is mature?
thanks

BPEL development

Hi,
I'm entirely new with BPEL development. I need to change a BPEL process parameter which is already deployed in production. Development env is available for me to play around BPEL. I need to know what are the required tools and whats the right approach to make this modification.
I installled JDeveloper and created new Application Server connection (Dev environment) and Integration Server conncection successfully. Do I have to install BPEL process manager also?
Is it possible to modify the BPEL process online or do I have to do it locally? In any case, how to do that?
I went through BPEL process manager quick start guide and found they are doing everything locally (installing SOA, JDev in local PC). In my case what should I do?
Pls tell me if Im missing something that i need to provide. Thanks in advance.
Lisan

Hi Lisan,
I suppose you are trying to change the input/output for the BPEL
If you have the dev env then you just need the Jdev installed locally and create the connection for integration and application server.
You cant change the input/output online for the BPEL, you will have to locally modify the BPEL process (Project), you can change the
XSD which are being used by the BPEL process.
First get the project of that BPEL process and then modify it inside the Jdev.
-Yatan

Inbound security for BPEL processes

Hello,
I am trying to enable Inbound security for BPEL processes. i made changes to message-handlers.xml as specified in the document.
However when i sent a test message using AXIS API, i am getting the below error.
Error while invoking inbound message handler.
An error has occurred while attempting to invoke the inbound message handler class "class com.collaxa.cube.security.Authenticator" for the message "". The exception reported was: Could not apply security [No username provided, security expects user]
I am using one of User Ids specified in system-jazn-data.xml and I can see that input soap message has a usernametoken . Any Inputs please?
Thanks

If you want to use the BPEL tool you can simulate some load using the initiate option. There is a checkbox where you can specify the load you want to perform.
Otherwise you need to use products such as Mercury (now HP) Load Runner. This is an expensive option but gives you very good output. The other option is to develop your own scripts to test the performance.
cheers
James

Intellisense for tablename alias

Hello,
why is it not possible to use intellisense in the PL/SQL editor for the alias of a tablename?
Frank

Hi,
Welcome to MSDN.
I am afraid that this is not the proper forum for this issue, I suggest you consider posting it in the following forum which is dedicated for web development issues:
http://forums.asp.net/15.aspx/1?Getting+Started
Thanks for your understanding.
Regards.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

GeoRaptor 3.0 for SQL Developer 3.0 and 2.1 has now been released

Folks,
I am pleased to announce that, after 5 months of development and testing, a new release of GeoRaptor for SQL Developer 2.1 and 3.0 is now available.
GeoRaptor for SQL Developer 3 is available via the SQL Developer Update centre. GeoRaptor 3 for SQL Developer 2.1 is being made available
via a download fro the GeoRaptor website.
No release notes have been compiled as the principal developer (oops, that's me!) is currently busy doing real work for a change (another 3 weeks), earning a living
and keeping the wolves at bay. More extensive notes (with images) will be compiled when I get back. (Unless anyone is offering! See next.)
We are still looking for people to:
1. Provide translations of the English dialog menus etc.
2. Write more extensive user documentation. If you use a particular part of GeoRaptor a lot and think
you have found out all its functionality and quirks, contact us and offer to write a few pages of
documentation on it. (Open Office or Microsoft Word is fine.) Easiest way to do this is to simply
make screen captures and annotate with text.
3. Conduct beta testing.
Here are the things that are in the new release.
New functionality:
Overhaul of Validation Functionality.
1. User can specify own validation SELECT SQL as long as it returns three required columns. The SQL is thus totally editable.
2. Validation update code now allows user to associate a PL/SQL function with an error number which is applied in the UPDATE SQL.
3. UPDATE SQL can use WHERE clause of validation SELECT SQL (1) to update specific errors.
   NOTE: The generated UPDATE statement can be manually edited. It is NEVER run by GeoRaptor. To run any UPDATE, copy the statement
   to the clipboard and run in an appropriate SQL Worksheet session within SQL Developer.
4. Main validation table allows:
   a. Sorting (click on column header) and
   b. Filtering.
   c. Copying to Clipboard via right mouse click sub menu of:
      - Geometry's SDO_ELEM_INFO array constructor.
      - SDO_GEOMETRY constructor
      - Error + validation string.
   d. Access to Draw/Zoom functions which were previously buttons.
   e. Added a new right mouse click menu "Show Feature's Individual Errors" that gathers up all the errors
      it can process - along with the ring / element that is host to the error (if it can) - and displays
      them in the Attribute/Geometry tabs at the bottom of the Map Window (where "Identify" places its results).
      The power of this will be evident to all those who have wanted a way of stepping through errors in a geometry.
   f. Selected rows can now be deleted (select rows: press <DELETE> key or right mouse click>Delete).
   g. Table now has only one primary key column, and has a separate error column holding the actual error code.
   h. Right mouse click men added to table menu to display description of error in the new column (drawn from Oracle documentation)
   i. Optimisations added to improve performance for large error lists.
5. Functionality now has its own validation layer that is automatically added to the correct view.
   Access to layer properties via button on validation dialog or via normal right mouse click in view/layer tree.
Improved Rendering Options.
1. Linestring colour can now be random or drawn from column in database (as per Fill and Point colouring)
2. Marking of SDO_GEOMETRY objects overhauled.
   - Ability to mark or LABEL vertices/points of all SDO_GEOMETRY types with coordinate identifier and
     option {X,Y} location. Access is via Labelling tab in layer>properties. Thus, coordinate 25 of a linestring
     could be shown as: <25> or {x,y} or <25> {x,y}
   - There is a nice "stacked" option where the coordinate {x,y} can be written one line below the id.
   - For linestrings and polygons the <id> {x,y} label can be oriented to the angle between the vectors or
     edges that come in, and go out of, a vertex. Access is via "Orient" tick box in Labelling tab.
   - Uses Tools>Preferences>GeoRaptor>Visualisation>SDO_ORDINATE_ARRAY bracket around x,y string.
3. Start point of linestring/polygon and all other vertices can be marked with user selectable point marker
   rather than previously fixed markers.
4. Can now set a NULL point marker by selecting "None" for point marker style pulldown menu.
5. Positioning of the arrow for linestring/polygons has extra options:
   * NONE
   * START    - All segments of a line have the arrow positioned at the start
   * MIDDLE   - All segments of a line have the arrow positioning in the middle.
   * END      - All segments of a line have the arrow positioning in the END.
   * END_ONLY - Only the last segment has an arrow and at its end.
ScaleBar.
1. A new graphic ScaleBar option has been added for the map of each view.
   For geographic/geodetic SRIDs distances are currently shown in meters;
   For all SRIDs an attempt is made to "adapt" the scaleBar units depending
   on the zoom level. So, if you zoom right in you might get the distance shown
   as mm, and as you zoom out, cm/m/km as appropriate.
2. As the scaleBar is drawn, a 1:<DEMONINATOR> style MapScale value is written
   to the map's right most status bar element.
3. ScaleBar and MapScale can be turned off/on in View>Properties right mouse
   click menu.
Export Capabilities.
1. The ability to export a selection from a result set table (ie result of
   executing ad-hoc SQL SELECT statement to GML, KML, SHP/TAB (TAB file
   adds TAB file "wrapper" over SHP) has been added.
2. Ability to export table/view/materialised view to GML, KML, SHP/TAB also
   added. If no attributes are selected when exporting to a SHP/TAB file, GeoRaptor
   automatically adds a field that holds a unique row number.
3. When exporting to KML:
   * one can optionally export attributes.
   * Web sensitive characters < > & etc for KML export are replaced with > < & etc.
   * If a column in the SELECTION or table/view/Mview equals "name" then its value is
     written to the KML tag <name> and not to the list of associated attributes.
     - Similarly for "description" -> <description> AND "styleUrl" -> <styleUrl>
4. When exporting to GML one can optionally export attributes in FME or OGR "flavour".
5. Exporting Measured SDO_GEOMETRY objects to SHP not supported until missing functionality
   in GeoTools is corrected (working with GeoTools community to fix).
6. Writing PRJ and MapInfo CoordSys is done by pasting a string into appropriate export dialog box.
   Last value pasted is remembered between sessions which is useful for users who work with a single SRID.
7. Export directory is remembered between sessions in case a user uses a standard export directory.
8. Result sets containing MDSYS.SDO_POINT and/or MDSYS.VERTEX_TYPE can also be written to GML/KML/SHP/TAB.
   Example:
   SELECT a.geom.sdo_point as point
     FROM (SELECT sdo_geometry(2002,null,sdo_point_type(1,2,null),sdo_elem_info_array(1,2,1),sdo_ordinate_array(1,1,2,2)) as geom
             FROM DUAL) a;
   SELECT mdsys.vertex_type(a.x,a.y,a.z,a.w,a.v5,a.v6,a.v7,a.v8,a.v9,a.v10,a.v11,a.id) as vertex
     FROM TABLE(mdsys.sdo_util.getVertices(mdsys.sdo_geometry(2002,null,null,sdo_elem_info_array(1,2,1),sdo_ordinate_array(1,1,2,2)))) a;
9. A dialog appears at the end of each export which details (eg total) what was exported when the exported recordset/table contains more
   than on shape type. For example, if you export only points eg 2001/3001 from a table that also contains multipoints eg 2005/3005 then
   the number of points exported, and multipoints skipped will be displayed.
10. SHP/TAB export is "transactional". If you set the commit interval to 100 then only 100 records are held in memory before writing.
    However, this does not currently apply to the associated DBASE records.
11. SHP/TAB export supports dBase III, dBase III + Memo, dBase IV and dBase IV + Memo.
    Note: Memo allows text columns > 255 characters to be exported. Non-Memo formats do not and any varchar2 columns will be truncated
    to 255 chars. Some GIS packages support MEMO eg Manifold GIS, some do not.
12. Note. GeoRaptor does not ensure that the SRID of SDO_GEOMETRY data exported to KML is in the correct Google Projection.
    Please read the Oracle documentation on how to project your data is this is necessary. An example is:
    SELECT OBJECTID,
           CODIGO as name,
           NOME as description,
           MI_STYLE,
           SDO_CS.TRANSFORM(shape,'USE_SPHERICAL',4055) as shape
      FROM MUB.REGIONAL;
13. NOTE: The SHP exporter uses the Java Topology Suite (JTS) to convert from SDO_GEOMETRY to the ESRI Shape format. JTS does not handle
    circular curves in SDO_GEOMETRY objects you must "stroke" them using sdo_util.arc_densify(). See the Oracle documentation on how
    to use this.
Miscellaneous.
1. Selection View - Measurement has been modified so that the final result only shows those geometry
   types that were actually measured.
2. In Layer Properties the Miscellaneous tab has been removed because the only elements in it were the
   Geometry Output options which have now been replaced by the new GML/KML/etc export capabilities.
3. Shapefile import's user entered tablename now checked for Oracle naming convention compliance.
4. Identify based on SDO_NN has been removed from GeoRaptor given the myriad problems that it seems to create across versions
   and partitioned/non-partitioned tables. Instead SDO_WITHIN_DISTANCE is now used with the actual search distance (see circle
   in map display): everything within that distance is returned.
5. Displaying/Not displaying embedded sdo_point in line/polygon (Jamie Keene), is now controlled by
   a preference.
6. New View Menu options to switch all layers on/off
7. Tools/Preferences/GeoRaptor layout has been improved.
8. If Identify is called on a geometry a new right mouse click menu entry has been added called "Mark" which
   has two sub-menus called ID and ID(X,Y) that will add the labeling to the selected geometry independently of
   what the layer is set to being.
9. Two new methods for rendering an SDO_GEOMETRY object in a table or SQL recordset have been added: a) Show geometry as ICON
   and b) Show geometry as THUMBNAIL. When the latter is chosen, the actual geometry is shown in an image _inside_ the row/column cell it occupies.
   In addition, the existing textual methods for visualisation: WKT, KML, GML etc have been collected together with ICON and THUMBNAIL in a new
   right mouse click menu.
10. Tables/Views/MViews without spatial indexes can now be added to a Spatial View. To stop large tables from killing rendering, a new preference
    has been added "Table Count Limit" (default 1,000) which controls how many geometry records can be displayed. A table without a spatial
    index will have its layer name rendered in Italics and will write a warning message in red to the status bar for each redraw. Adding an index
    which the layer exists will be recognised by GeoRaptor during drawing and switch the layer across to normal rendering.
Some Bug Fixes.
* Error in manage metadata related to getting metadata across all schemas
* Bug with no display of rowid in Identify results fixed;
* Some fixes relating to where clause application in geometry validation.
* Fixes bug with scrollbars on view/layer tree not working.
* Problem with the spatial networks fixed. Actions for spatial networks can now only be done in the
schema of the current user, as it could happen that a user opens the tree for another schema that
has the same network as in the user's schema. Dropping a drops only the network of the current connected user.
* Recordset "find sdo_geometry cell" code has been modified so that it now appears only if a suitable geometry object is
in a recordset. Please note that there is a bug in SQL Developer (2.1 and 3.0) that causes SQL Developer to not
register a change in selection from a single cell to a whole row when one left clicks at the left-most "row number"
column that is not part of the SELECT statements user columns, as a short cut to selecting a whole row. It appears
that this is a SQL Developer bug so nothing can be done about it until it is fixed. To select a whole row, select all
cells in the row.
* Copy to clipboard of SDO_GEOMETRY with M and Z values forgot has extraneous "," at the end.
* Column based colouring of markers fixed
* Bunch of performance improvements.
* Plus (happily) others that I can't remember!If you find any bugs register a bug report at our website.
If you want to help with testing, contact us at our website.
My thanks for help in this release to:
1. John O'Toole
2. Holger Labe
3. Sandro Costa
4. Marco Giana
5. Luc van Linden
6. Pieter Minnaar
7. Warwick Wilson
8. Jody Garnett (GeoTools bug issues)
Finally, when at the Washington User Conference I explained the willingness of the GeoRaptor Team to work
for some sort of integration of our "product" with the new Spatial extension that has just been released in SQL
Developer 3.0. Nothing much has come of that initial contact and I hope more will come of it.
In the end, it is you, the real users who should and will decide the way forward. If you have ideas, wishes etc,
please contact the GeoRaptor team via our SourceForge website, or start a "wishlist" thread on this forum
expressing ideas for future functionality and integration opportunities.
regards
Simon
Edited by: sgreener on Jun 12, 2011 2:15 PM

Thank you for this.
I have been messing around with this last few days, and i really love the feature to pinpoint the validation errors on map.
I has always been so annoying to try pinpoint these errors using some other GIS software while doing your sql.
I have stumbled to few bugs:
1. In "Validate geometry column" dialog checking option "Use DimInfo" actually still uses value entered in tolerance text box.
I found this because in my language settings , is the decimal operators
2. In "Validate geometry column" dialog textboxs showing sql, doesn't always show everything from long lines of text (clipping text from right)
3. In "Validate geometry column" dialog the "Create Update SQL" has few bugs:
- if you have selected multiple rows from results and check the "Use Selected Geometries" the generated IN-clause in SQL with have same rowid (rowid for first selected result) for all entries
Also the other generated IN clause in WHERE-clause is missing separator if you select more than one corrective function
4. "Validate geometry column" dialog stays annoyingly top most when using "Create Update SQL" dialog

GeoRaptor 3.2.1 Released for SQL Developer 3.x

Spatialites!
After 6 months of development and testing, GeoRaptor 3.2.1 has been released for SQL Developer 3.x (tested on 3.0, 3.1 and 3.2). This release no longer supports SQL Developer 1.x or 2.x releases due to internal changes to the SQL Developer APIs.
GeoRaptor can be downloaded from the GeoRaptor project's sourceforge page: http://sourceforge.net/projects/georaptor and installed via Help>Check for Updates>Install from Local File. Installation via SQL Developer's update mechanism should be available soon.
The release notes for this release are:
* Fixed issues with validate geometry functionality in particular the update dialog box.
* Revamped "About GeoRaptor" form. Includes clickable URLs, links to mailing lists, version number listing, thanks to testers etc.
* Placed "About GeoRaptor" icon on GeoRaptor's map toolbar.
* SQL Developer NLS settings accessed: improvements in the display and entry and numeric data.
-- Tolerances in Spatial Layer properties will display with the NLS decimal separator eg 0,05.
     Some parts of GeoRaptor such as Validation that show and accept numbers have not been changed from when someone else modified the code.
     If you double click on the left MBR/right MBR icon in the map at the bottom, the current centre position will display according to the NLS settings.
     Editing the value to jump the map to that point works even with grouping separators and decimal separators being commas!
* Spatial Layer Draw has been modified to use NLS based decimal formatting.
* New geometry marking/labelling options have been added. In particular you can now label the vertices of a linestring/polygon with the following additional elements:
-- Cumulative length
-- Measure (M)
-- Z value
-- Labelling of vertices with <id>{X,Y} now also honours 3/4D geometries. If geometry has XYY then it will be labelled as {X,Y,Z} etc.
* You can also label each vector/segment of a linestring/polygon with:
-- Length
-- Cumulative Length
-- Bearing (approximate for geodetic/geographic data)
-- Distance (approximate for geodetic/geographic data)
-- Bearing and Distance (approximate for geodetic/geographic data)
* The font properties of the mark text can be changed independently of the feature label. This includes the offset and label position (CC, LL, UR etc).
* New feature labelling options have been provided:
-- First/middle/last vertex,
-- Any supplied sdo_point within a line/polygon's sdo_geometry object, or
-- Calculated by GeoRaptor on the client side using Java Topology Suite.
* Result sets now have the ability to:
-- Copy to clipboard all geometries across many rows and columns.
-- Display one or more (selected) geometries in a popup image window. This functionality is also available in the result set generated by an Identify command.
* New GeoRaptor Preferences:
-- Width and height in pixels of the new popup image window (displaying one or more geometry objects) can be set;
-- Colours of orphan, missing and correct metadata entries for Metadata Manager;
-- Prefixing with MDSYS for all currently supported spatial objects - sdo_geometry, sdo_point, sdo_elem_info, sdo_ordinates, sdo_dim_info - has been made an option.
-- There is now a new property called "Show Number Grouping Separator" in Tools>GeoRaptor>Visualisation.
     If it is ticked a number will be formatted with the thousands separator in Tools>Database>NLS eg 10000.000 will display as 10,000.000.
* Sdo_Geometry display of all spaces in text between elements of the sdo_geometry array have been removed.
   This was done mainly to compact the sdo_geometry strings so that they are as small as possible when displaying or copying to clipboard.
* Help pages added to the following dialogs with more to follow:
-- Metadata Manager,
-- Shapefile Importer and
-- Layer Properties dialogs.
* GeoRaptor menu entries renamed. New "Manage All Metadata" entry added to View>GeoRaptor menu.
* Spatial Index creation dialog now supports additional index parameters and parallel build settings.
* Metadata Manager overhauled:
a. Shows:
     1. Metadata entries which have no underlying oracle object (orphan)
     2. Metadata entries for existing underlying objects (existing case)
     3. Database objects with sdo_geometry for which no metadata entry exists (new)
b. All orphan/existing/missing colours for (a) can be set via Preferences>GeoRaptor>Visualisation
c. All actions for main (bottom) metadata table are in a single right mouse click menu.
     Some entries will only appear if a single row is selection (metadata copy), others (delete and copy to clipboard) will appear for one or more.
d. Can now switch between open connections to modify metadata of other objects in schemas other than the starting object.
e. Buttons revamped.
* Tab/Shapefile export:
a. Export now supports NULL valued columns. Can be exported as an empty string (if DBase override in GeoRaptor Preferences is ticked) or
     as a predefined value eg NULL date => 1900-01-01 (set in new GeoRatptor Import/Export Preferences).
b. Some work attempted on export of NLS strings (still not corrected).
c. Objects with no rows now correctly processed.
* Shapefile Import
-- Bug relating to Linux file names corrected.
* Fixed issue (identified by John O'Toole) with spatial index underlying a view not being used in map display.
* Reinstated sdo_nn as the principal method for Identify (requested by John O'Toole).
* Fixed problem with handling single click zoom in and out in GeoRaptor map etc.
* Fixed problem with rendering lines from database item (identified by Vladimir Pek).The new "About GeoRaptor" should be read by all people installing GeoRaptor.
Please, please consider registering your email address with our private email list so that we can get a feel for the sorts of people downloading and installing GeoRaptor.
Please consider helping us with documentation or the internationalisation via translating properties files from English to your native language.
GeoRaptor is written and maintained by people who use SQL Developer and Spatial every day but we don't pretend we know everything that users want: please let us know via our feature request page at SourceForge.
We don't get paid for what we do so are always looking for additional help.
Here are some of the requests we have had for improvements:
1. MySQL access
2. WMS access;
3. Ability to import shapefile data into an existing table;
4. Ability to processing multiple shapefiles into separate tables (current version can import one or more into a single target table);
5. Ability to export/import layer definitions to give to others;
6. Support for non-English character sets for varchar exports to shapefiles.Some are relatively simply, some require a lot of engineering work. For the latter, we are considering alternative funding methods to the currently completely free development approach.
Thanks to the following for their invaluable assistance:
Holger Labe, Germany
John O'Toole, Ireland
Vladimir Pek, Czech Republic
Pieter Minnaar, Holland
Olaf Iseeger, Germany
Sandro Costa, Brazil;
Marco Giana, Australia.regards
Simon Greener
Principal GeoRaptor Developer
Edited by: Simon Greener on Sep 10, 2012 2:43 PM

Simon,
I will admit, I almost never use SQL Developer. I have been a long time Toad user, but for this tool, I fumbled around a bit and got everything up and running quickly.
That said, I tried the new GeoRaptor tool using this tutorial (which is I think is close enough to get the jist). http://sourceforge.net/apps/mediawiki/georaptor/index.php?title=A_Gentle_Introduction:_Create_Table,_Metadata_Registration,_Indexing_and_Mapping
As I stumble around it, I'll try and leave some feedback, and probably ask some rather stupid questions.
Thanks for the effort,
Bryan

How to set naming standards for SQL Developer

I am using SQL Developer version 3.0.04.
In the newly integrated and very useful Data Modeler, we can set preferences for the naming standards to be applied when creating logical and relational model objects ( primary keys, foreign keys, et cetera). I would like to know if there is a way to set naming standards for the relational objects we create in SQL Developer on existing tables ( ( primary keys, foreign keys, et cetera).
Any help in setting such preferences would be appreciated.

Hi,
If you want to set up a diagram for an existing database, you can use File/Data Modeler/Import/Data Dictionary to import its definitions.
Alternatively you can open a Data Modeler Browser (using View/Data Modeler/Browser), expand the node for Design "Untitled_1",
expand the node for Relational Models, and select Show from the Right-click drop-down menu for "Relational_1" to create a Relational Model diagram.
You can then drag Tables from SQL Developer's Connections tree onto the diagram.
Once you have a Relational Model you can reverse engineer it to an Entity-Relationship model using the << button in the button bar
(or by selecting "Engineer to Logical Model" from the drop-down menu for the Relational Model).
Note that there is now a separate forum for SQL Developer Data Modeler topics: SQL Developer Data Modeler
David

Hi, we are using mac mini's for our developement purpose. connecting the same through using Real VNC. Mac mini's are late 2009 and 2010. Now we have upgraded them to 10.8.5. after upgrading having display issues after launching the simulators

hi, we are using mac mini's for our developement purpose. connecting the same through using Real VNC. Mac mini's are late 2009 and 2010. Now we have upgraded them to 10.8.5. after upgrading having display issues after launching the simulators, we are unable to view the icons we need to move the simulator (into different places) to view the icons.
Also we are having Mac book pro's (Late 2009 & 2010) after upgrading them to 10.8.5. Unable to launch the mac, getting only white screen with apple icon.
Let me know is there any specific Hardware (Graphic Cards) we need to use for the same.
Please provide me the early solutions.
Regards,
Suresh.

Hi, try this first...
Bootup holding CMD+r, or the Option/alt key to boot from the Restore partition & use Disk Utility from there to Repair the Disk, then Repair Permissions.

Intellisense for BPEL development

Similar Messages

Maybe you are looking for