ANN: DBPrism CMS 2.1.0 production released

A long awaited new release of DBPrism CMS was released last month.
This code base is a completed rewritten version of the previous one using native support of Oracle XMLDB and OracleJVM.
DBPrism CMS is the first Open Source Database Oriented CMS using all native implementation of Oracle XMLDB repository 10gR2. It means that DBPrism CMS will provides powerful CMS functionality using two bigger players, Apache Cocoon presentation framework and Oracle XMLDB repository.
The core code of the CMS is around of 960 lines of Java running as Stored Procedures, this code is called by Apache Cocoon presentation framework using DBPrism Generator.
More information at: http://www.dbprism.com.ar/j2-CMS/index.html

Can I ask you why the documentation doesn't mention any BUG fixes?
Don't tell me that you haven't find any bugs?
The XSLPROCESSOR package kills your session after you use it..

Similar Messages

  • ANN: XDK 9.2.0.2 Production Releases

    XDK 9.2.0.2 Production Releases are available online at:
    http://technet.oracle.com/tech/xml
    and
    http://xdk.us.oracle.com/
    In addition to the bugs fixes, the following new demos and documents are
    online:
    * New XML Sample Code and Paper is online at:
    http://otn.oracle.com/tech/xml/sample.html
    - XML Data Streaming for Enterprise Applications Using PL/SQL and SAX
    Analyze the fundamental strategies for XML processing in enterprise
    applications and discuss an efficient XML data-streaming solution that
    makes use of the SAX, PL/SQL interfaces and Oracle8i/9i Database
    * New 9iXDK Demonstrations are online at:
    http://otn.oracle.com/tech/xml/sample.html
    - Product Catalog Application with New Oracle9i Database XML Features
    and the 9i XDK
    Demonstrates using the XML Developers' Kit(XDK) and the new Oracle9i
    XML features for storing and searching XML data.
    - Customer Management Application with New Oracle9i Database XML Features
    and the 9i XDK
    Demonstrates using XML Developers' Kit APIs and the new Oracle9i XML
    features for storing and searching XML data. Also demonstrates the
    Server-Side XML Schema Validation from PL/SQL
    - Employee Information Management using the XSQL page publishing framework
    Shows how the XSQL Page Publishing Framework could be used to perform
    different database operations and to handle dynamic content using SQL,
    XML and XSL.
    - Building Product Orders with New Oracle9i Database XML Features and the
    9i XDK
    Demonstrates using Class Generator for Java in generating Product Orders
    and uses the XSQL Page publishing Framework for storing the generated
    orders XML inside an Oracle9i database

    Can I ask you why the documentation doesn't mention any BUG fixes?
    Don't tell me that you haven't find any bugs?
    The XSLPROCESSOR package kills your session after you use it..

  • SQl Developer 3.1 / Data Miner Production Release is now available

    Hi,
    The SQL Developer 3.1/Data Miner Production Release is now available.
    For more details see the OTN Forum announcement:
    https://forums.oracle.com/forums/ann.jspa?annID=1747
    Thanks, Mark

    It will be there when the Oracle Cloud is released.
    -kris

  • Visual Studio 2010 Production Release Version Numbers

    I uninstalled the beta and installed the production release.  After letting it convert my projects, I noticed that the version numbers for the .NET assemblies appear to be 13.0.2000.0 and in the beta version they were 14.0.2000.0.
    Can someone from SAP confirm the version numbers for the production release?

    Hello,
    You are correct. The final build is version 13. Long story due to download sizes and integration. I've updated 4 Images now both 32 and 64 bit and had no problems. Other major change is there is no connectivity to BOE Enterprise and no plans to add it.
    See this [Link |Crystal Reports for Visual Studio 2010 Production Release Now Available;for more info and known issues.
    Thank you
    Don

  • What is the ETA on the production release? Can we pay to remove the graph watermarks?

    I can't figure out the ETA on the production release.
    Meanwhile, because of the graph watermarks in Beta 3, we have had
    to stop getting feedback from customers! Anyone from Macromedia
    please explain what we are supposed to do?

    Currently, there is no way to remove the watermarks, and the
    product is not yet available for purchase so it isn't possible to
    let you purchase a serial number.
    We haven't given out a specific date for the release, but
    beta 3 was our last public beta release before shipping. Hopefully,
    the imminent release will let you re-engage with customers.
    Phil Costa
    Group Product Manager, Flex

  • OraOLEDB 9.2.0.4.0 production release is available

    OraOLEDB 9.2.0.4.0 production release is available for download from OTN. Broken download link issue has been fixed.
    What's new in this release?
    ===========================
    New Data Types Support
    Oracle9i and later versions data types:
    - TIMESTAMP
    - TIMESTAMP WITH TIME ZONE
    - TIMESTAMP WITH LOCAL TIME ZONE
    - INTERVAL YEAR TO MONTH
    - INTERVAL DAY TO SECOND
    TIMESTAMP, TIMESTAMP WITH TIME ZONE, and TIMESTAMP WITH LOCAL TIME ZONE data types are mapped to OLE DB DBTYPE_DBTIMESTAMP; INTERVAL YEAR TO MONTH and INTERVAL DAY TO SECOND are to DBTYPE_STR.
    OLE DB DBTYPE_DBTIMESTAMP data type does not have TIME ZONE information. For data insertion into a TIMESTAMP WITH TIME ZONE or TIMESTAMP WITH LOCAL TIME ZONE, the client's time zone setting is used. For data retrieval, TIME ZONE is dropped for TIMESTAMP WITH TIME ZONE columns, but TIME ZONE is used for TIMESTAMP WITH LOCAL TIME ZONE columns.
    For TIMESTAMP, TIMESTAMP WITH TIME ZONE, and TIMESTAMP WITH LOCAL TIME ZONE, ADO consumers must specify the CursorLocation as adUseServer and use Recordset for DML operations.
    Fractional second is not supported for TIMESTAMP binding with Command objects. Note that using ALTER SESSION to change time zone information will not change the time zone information in the new and existent Recordsets. Recordsets use the client's time zone setting in Operating System's Regional Options.
    Supported INTERVAL Formats:
    - INTERVAL YEAR TO MONTH: "(sign)years-months"
    Example:
    "2-3" (2 years and 3 months)
    "+2-3" (2 years and 3 months)
    "-2-3" (negative 2 years and 3 months)
    - INTERVAL DAY TO SECOND: "(sign)days hours:minutes:seconds.fraction"
    Example:
    "7 10:20:30.123456"
    (7 days, 10 hours, 20 minutes, and 30.123456 seconds)
    "+7 10:20:30.123456"
    (7 days, 10 hours, 20 minutes, and 30.123456 seconds)
    "-7 10:20:30.123456"
    (negative 7 days, 10 hours, 20 minutes, and 30.123456 seconds)
    OraOLEDB-specific Connection String Attributes
    ==============================================
    UseSessionFormat - specifies whether to use the default NLS session formats or let OraOLEDB override some of these formats for the duration of the session.
    Valid values are 0 (FALSE) and 1 (TRUE). The default is FALSE which lets OraOLEDB override some of the default NLS session formats. If the value is TRUE, OraOLEDB uses the default NLS session formats.
    Note that this connection attribute does not appear under the OLEDB registry key.
    BUG FIXES (in 9.2.0.4.0)
    ========================
    1. -2147217887 is generated when inserting data using accessor class (Bug #3114560)
    2. Calls to OpenSchema leak memory (Bug #3038113)
    3. Fraction gets truncated for FLOAT column when decimal separator changed to comma (Bug #1633090)
    4. Returns incorrect data for LONG-RAW columns with default ChunkSize 100 bytes (Bug #3069807)
    5. Failures and access violation occur on 'SELECT CASE' queries (Bug #2910141)
    6. Memory leaks during connect/disconnect (Bug #2794171)
    7. Oracle OLE DB Provider returns DBTYPE_STR when it should return DBTYPE_WSTR (Bug #2651518)
    8. SELECT with a parameter bind of type number in WHERE clause causes ORA-1722 error (Bug #2391768)
    9. Corrupts data when using multi-threaded application (Bug #2822641)
    10. Does not return DBSTATUS_S_TRUNCATED appropriately (Bug #2743415)
    11. Memory leaks when using "SELECT DISTINCT" and aduseclient (Bug #2626329)
    12. ORA-01036 error occurs when using bind variable (Bug #2665941)
    13. 'SELECT CASE' returns ORA-923: FROM keyword not found (Bug #2457001)
    14. Wrong order of ADO output parameters crash appl/vb when one param is of Timestamp type (Bug #3158709)
    15. ALTER SESSION SET NLS_NUMERIC_CHARACTERS = ', ' truncates float after decimal (Bug #3158709)
    16. Date values cause intermittent DB_E_ERRORSOCCURRED in COM+ application (Bug #3209734)
    17. OraOLEDB crashes with 800 bind parameters and PL/SQL anonymous block (Bug #2744164)
    18. Oraoledbgmr!odbcsqltoorclsql crashes with COM+ under load (Bug #2730995)

    Is the recommended 9.2.0.4 patchset needed for the Database Server only? Is there a patchset to upgrade the 9i Client to 9.2.0.4 also?

  • OO4O 9.2.0.4.8 production release is available

    OO4O 9.2.0.4.8 production release is available for download on OTN.
    New Features
    ============
    New Features supported for the 32-bit In Process OLE Automation Server:
    With this release, OO4O provides four new objects that enable developers to access and manipulate the new datetime and interval datatypes introduced in Oracle9i.
    OO4O Objects Oracle Datatypes
    OraIntervalD INTERVAL DAY TO SECOND
    OraIntervalY INTERVAL YEAR TO MONTH
    OraTimeStamp TIMESTAMP
    TIMESTAMP WITH LOCAL TIME ZONE
    OraTimeStampTZ TIMESTAMP WITH TIME ZONE
    Instances of these types can be fetched from the database or passed as input or output variables to SQL statements and PL/SQL blocks, including stored procedures and functions.
    These new datatypes are not supported as elements in collections such as PL/SQL Indexed Tables, VARRAYs, or Nested Tables. Please refer to the OO4O doc for more information.
    Summary of problems fixed
    =========================
    2797039 - SIGNIFICANT DELAY IN MONITORSTART DETECTING AN ENQUEUED MESSAGE
    3049591 - OOBJECT.GETATTRVALUE() RETURNS NAME OF ATTRIBUTE TO BE RETRIEVED INSTEAD VALUE
    2843494 - 0040 VB APPLICATION FAILS WITH ACCESS VIOLATION
    2647144 - SETTING ORACOLLECTION NOTHING CAUSE ACCESS VIOLATION
    2787093 - GETFIELDCHUNK FUNCTION DOES NOT READ MORE THAN 4096 BYTES
    2614824 - ACCESSING VARRAY OBJECT OF DEQUEUED MESSAGE THROWS EXCEPTION
    2594695 - OFIELD::SETXMLASATTRIBUTE(TRUE) HAS NO EFFECT
    2594037 - USING OFIELD::SETXMLTAGNAME RESULTS IN A OIP-04096: INVALID ADVISORY CONNECTION
    2594032 - OFIELD::GETXMLTAGNAME RESULTS IN AN INVALID CHAR*
    2457000 - MEMORYLEAK HAPPENS WHEN EXECUTING "ODYNASET.OPEN" AGAINST LOB ON OO4O+VC
    2391180 - OO4O RETURNS OIP-4117 WHEN UPDATING FOR CASE SENSITIVE COLUMNS.
    2555543 - UNNECESSARY FETCH OBSERVED IN SQL TRACE WHEN USING UPDATABLE DYNASET
    2311470 - IF CREATING DYNASET "SELECT BLOB,LONGRAW FROM TAB", GPF OCCURS AT GETCHUNKBYTEEX

    Is the recommended 9.2.0.4 patchset needed for the Database Server only? Is there a patchset to upgrade the 9i Client to 9.2.0.4 also?

  • Stack overflow error with production release

    Hi,
    I am using Flex 4.5.1 and I am getting a weird error upon exporting a production release. Here is the stack trace:
    VerifyError: Error #1023: Stack overflow occurred.
              at spark.components.gridClasses::GridLayout/intializeGridVisualElement()
              at spark.components.gridClasses::GridLayout/layoutIndicator()
              at spark.components.gridClasses::GridLayout/layoutCaretIndicator()
              at spark.components.gridClasses::GridLayout/updateDisplayList()
              at spark.components.supportClasses::GroupBase/updateDisplayList()
              at spark.components::Group/updateDisplayList()
              at spark.components::Grid/updateDisplayList()
              at mx.core::UIComponent/validateDisplayList()
              at spark.components::Group/validateDisplayList()
              at mx.managers::LayoutManager/validateDisplayList()
              at mx.managers::LayoutManager/doPhasedInstantiation()
              at mx.managers::LayoutManager/doPhasedInstantiationCallback()
    As you can see there is no trace of our own classes anywhere. I don't get this error if I use the normal debug version. We are very close to going live and we can't use the debug version files as they are bulky and are increasing the initial load time of the application.
    Please help!
    Thanks.
    Manoj

    Hey I get this suddenly in an app that's been running and working fine.  We just updated with a release build for some other updates and I get this error.  Here's the context:
    I am using Flex 4.6, have a component that extends the Flex 3 AdvancedDataGrid for some lightweight customization of how column resising work.  The component is used in several of our apps.  But, for some reason, and with no code updates to this particular component in a while, when I click on a row in the grid, I get this stack overflow exception too.  The exact same stack trace as the one mentioned by the original poster.
    Anyone have a clue why I would be seeing "spark.components.gridClasses::..." in my stack trace to begin with when the component that is being clicked on is a Flex 3 AdvDataGrid component?  I've seen some mention of the compiler error that somehow bashes the stack under the perfect circumstances.  But, in our case, we've eliminated all of our own event handlers (click/etc) from the grid and we still get this error and only in the release build.  So, there's no way to change any of our code to fix it b/c none of our code is executing when the error occurs.
    This is very very odd stuff.  Any ideas???

  • WebUtil production release and support

    Hi
    I've been trying to find a release date for forms 10g patch 1 which is supposed to contain a production release of WebUtil. I have found many different dates, all of which have passed already and yet there seems to be no product available. Can someone let me know when this will now be available?
    Also, will the production WebUtil be supported for use with forms 9i/9iAS R2? Is it a new version of the existing package that can be plugged in similarly or is it integrated into the 10g release? If it can't be used with 9i then does it matter - Is there much changed between the two versions?
    Thanks,
    Patrick

    Patrick,
    WebUtil will be released sometime between patch 1 and patch 2 and accessible for download here on OTN. WebUtil will be certified and supported with Oracle Developer Suite 10g and Oracle Application Server 10g. In successiv patch sets WebUtil will be bundled with the Oracle Developer Suite.
    WebUtil production will contain bug fixes that we collected from pre-releasing it for 9i. If you are currently using WebUtil, then upgrading to Forms 10g WebUtil is just a matter of configuration (and even this hasn't changed)
    Unfortunately I don't have a release date, but I am sure Grant will pick up this posting and provide more information if he has.
    Frank

  • Production release process using headstart.

    Hello,
    I am completley new to headstart. I have been given a new project to work on which has forms 9i, desginer 9i, oracle 9i AS and headstart 6.5.3.0 for 9i.
    I would like to know how do I go about using headstart to generate forms. Specifically, I would like to know how do I develop using headstart and then deploy them to test and production environment. Do I need to install headstart( Middle tier and database objects ) in my production setup ?
    I would highly appreciate if anybody can me a brief overview of development and production release process using headstart.
    Many thanks,

    Hi,
    The headstart user guide probably has all the info you need. Specifically Part VI, Deploying your Applications, is just what you're looking for. You can find the user guide (along with other useful documentation in the <hsd65_home>\docs directory.
    Grtz
    Bram Schiltmans

  • Life time of Product releases

    Dear Folks,
    Please guide me from where I can get details about the Life time of Product releases...
    Oracle 9.x.x.x.x / 10.x.x.x.x / 11.x.x.x.x, ...

    Hi;
    Please review:
    life cycle of database
    Product Dependencies
    PS:Please dont forget to change thread status to answered if it possible when u belive your thread has been answered, it pretend to lose time of other forums user while they are searching open question which is not answered,thanks for understanding
    Regard
    Helios

  • Product Release Date being default set to 01-Jan-2000 when exporting and importing product file

    Hi there,
    Just putting this out there to see if anyone else has experienced this problem.
    We've just redeveloped an art site that relies on the product release date to order work, newest first, by the date they added it  {tag_productlist,,,20,releasedate,true,true}
    However, we've hit an issue whereby the 'release date' field is set to 01-Jan-2000 when we export and then import the product file, thus chnaging the ordering. The date can't be set on the import file (unlike web apps) and we haven't changed thousands of products manually. BC support have been stumped, suggesting it's our Mac's system date, but this is set automatically and accurate...and we don't want to change the release date anyway, that should just be the date the product was originally released.
    Any thoughts or help would be greatfully received as this was a key part of the site design/development. This is the site http://hanguppictures.com
    Cheers
    Paul

    Ran into the same issue. I was using the release date to flag latest products, regardless of ordering. Unfortunately running a product import then destroyed all that work.
    Found this thread with a staff reponse regarding it not being possible to set release dates using import, but it doesn't explain why release dates get reset.

  • Production release of ODT now available

    I'm happy to announce that the production release of ODT is now available for download here:
    http://www.oracle.com/technology/tech/dotnet/tools/index.html
    There have been alot of enhancements over the beta. A few of the more interesting ones include:
    * support for generating typed datasets
    * ad hoc SQL Query Window with script support
    * enhanced PL/SQL editing
    * integrated error manual
    Keep the feedback coming!
    Christian Shay
    Oracle

    Here are some first impressions of the "Query window". This is just a list of the problems, so it seems quite negative. Some of the problems are small and some are larger. The thing that I think will annoy me most from day-to-day is the lack of a hotkey for execute and that bind-variables are not supported (but we all have our pet-bugs/problems):
    - In the context menu for the connection move the "Query Window" up under open (I quite sure the query window is more used than both "Delete" and "Close").
    - You shouldn't call the feature "Query Window" in the context menu and "Query Editor" in the title of the window. Be consistent.
    - You might want to rename the "Query Window" to "Query Analyser" (for compatibility with sql server)
    - A explain window (or rather a explain tab) should be added (like every other query tool).
    - Sql-statements should be timed, the time should be shown in milisecounds(!) and rounded/truncated (it might not be that percise but it invaluble as a quick guage when rewriting a sql to see if you a going in the right direction). For extra points show any "long ops" messages/status at regular intervals. Maybe it would be very interesting (powerfull) to see "buffer gets" next to the elapsed time.
    - "Execute" really need a hotkey. I would suggest either "Ctrl+Enter" (for compatibility with Toad), "Ctrl+E (for compatibility with Sql Server) or F5 (for compatibility with Sql Server and Visual Studio). The hot key sould be shown in a tooltip when hovering the execute button.
    - I overlooked the execute button at first. Move it to a toolbar and make it a green "Play"-button (for compatibility with Toad, Tora and Sql Server).
    - When having 2 sql-statements in a query window you seem to execute the last one. Please execute the one under the cursor. Sql statements should be seperated by empty lines (ie. containing only white space) or a semicolon.
    - The "Toggle Query Output" is non-descriptive. Change it to "Hide Query Output" (and "Show Query Output" respectively) and add the little black cross that e.g. the "Task List" have.
    - When having e.g. "select * from dual;" the Query Window and going to the line before that statement and typing "/*test" the whole window turns green (so far, so good), but when adding the closing "*/" after "test" the select-statement stays green.
    - Line and collumn-numbers in the error messages would be really usefull.
    - It seems that you don't provide help to the keywords? it thought that was one of the "selling points"?
    - Intellisense would be nice (but maybe mostly a "cool"/"demoware" feature). But maybe a hotkey for opening the "Oracle Explorer" with the active (eg. where the cursor is on or a the right of) table/view/function/package/... expaned would be more usefull. If the cursor is at the right of the keyword "FROM" a list of tables should be shown but if it is on "FROM" the help with the syntax should be shown. Escape should return focus to the query.
    - Ctrl+L should make the selection lowercase and Ctrl+U make it uppercase (or Ctrl+U and Ctrl+Shift+U for compatibility with the rest of VS.NET). I find that the code, I use the editors "change case"-feature most on is sql sinse I really like sql keywords upper case and identifiers lower case (and oracle ofthe make everything uppercase).
    - Now I see that there is a execute button on the toolbar, but (a) you have made it a strange brownish green (please make it greener) (b) you have placed it in the far left (or that is where it showed for me) in the top toolbar, where I had expected it to the left of the text "Query Editor" (inside the "ORACLE://<shema>.<datasource>/Query" pane).
    - Move the title "Query Editor" to the Tab (that says "ORACLE://<shema>.<datasource>/Query"). This will save some vertical space and make space for the toolbar. The title "Query Output" might be remove altogether.
    - Bind variables doesn't seem to be supported. I think that this is really a problem since *you should make it easy for developers to do the right think* and bind variables certainly is the right thing. You should bring up a window with the binds that are used in the query and enable me to set their type (if you can't figure it out from context (eg. emp.id=:emp_id would probably mean that :emp_id is a number) and their value. Also please persist the type/value for each variable name so I don't need to figure out the id of that employee I usally test with.
    A few non-query window notes:
    - In the spirit of "make it easy to do the right thing", what would be the easy way to call (and get intellisense on) a package function in a the cs-file?
    - In the context menu for a procedure "Run" should be "Run..." sinse it just brings up a window. And you probably want to "Delete" at the bottom (above the line).
    - In the context menu for a view "Retrive Data..." should be "Retrive Data" sinse it doesn't bring up a dialog. I accidentally selected it for a rather large/slow view and really wanted a "Stop" button (thanks for the option to stop after 30 seconds). I think you shouldn't retrive more than, say, 50 rows without the user explicitly saying so (and never blob/long raw columns or more than eg. 100 chars from a clob/long column).
    - The default action when dobbelt clicking a table shouldn't be "Retrive Data..."(!), it should be "Design...".
    - Choosing "Generate Create Script..." (which might just be called "Generate Script") on a produce, funciton or package, should bring up a preview window with a save-button.
    - When opening a function in the "Oracle Explorer", setting the cursor on eg. the keyword FUNCTION and hitting F1, the help index opens searching for "Oracle.ODT.SQL.CREATE FUNCTION", but there is (of cause?) no such topic. If I select the any part of the text in the help index search box and hit delete, I am asked "Oracle Explorer, Are you sure that you want to permanently delete '<shema>.<datasource>.<function name>' from the database ?" which is definetly not was I want to do!
    With regards to the rest of the add-in, what is was really hoping for was Visual Source Safe integration and easy procedure calling, but that doesn't seem to be implemented. But then I don't know what the problem statement for this add-in was.

  • JSP JSF template no more present in production release

    In Beta version of jdev there was a menu to make a JSP JSF template page.
    Is this option available in production release and how to access this feature ?

    It has been disabled at the moment since JSP already has many standard mechanisms for reuse - includes, segments, or tiles, e.g. http://www.oracle.com/technology/oramag/oracle/04-may/o34dev_struts.html to name a few. However, we'll be interested to know whether it's useful enough to be restored.

  • Production release of 10.1.3

    Can you tell me when the production release of the 10.1.3 version of Jdeveloper (currently early access) is scheduled for? The current release is too buggy for me, but I am not sure if I should take the time to migrate my project back to 10.1.2
    Thanks

    Hi,
    Yes, by the end of december (this week Oracle roadshow speakers)
    Jamil

Maybe you are looking for