Template to create the API index page

I saw some people having their own API page exactly like java's api doc, so i guess there must be a creatable template to create my own api doc...i wonder anyone knows how to create??..

They used the javadoc tool provide with the any JDK....
http://java.sun.com/j2se/1.3/docs/tooldocs/win32/javadoc.html
Floweb

Similar Messages

I have created a version of my website with muse for tablet but the home/index page is not centered

I have created a version of my website with muse for tablet but the home/index page is not centered (leave some space on the right ) when see it on my ipdad which is weird as the other pages are centered .Please help!
thanks

See my post here <http://forums.adobe.com/message/5410674#5410674>

Unable to create the Rule Index (SEM_APIS.CREATE_RULES_INDEX) getting error

Hi,
I am trying to create the Rule Index with the below script its giving the temp table space error.
The number of records in that specific table is 17473708 (17+ M) and the available temp space is 120GB.
Execute SEM_APIS.CREATE_RULEBASE('ecc_md_rb')
--Insert to mdsys.semr_ecc_md_rb Values(.............)
BEGIN
SEM_APIS.CREATE_RULES_INDEX(
'ecc_rule_indx',
SEM_Models('FOUNDATION'),
SEM_Rulebases('RDFS','ecc_dm_rb'));
END;
Create rule index statement is running more than 8hrs and i tried with the sem_apis.create_entailment its also giving the same Temp table space error.
Please find the below error details
BEGIN sem_apis.create_entailment('ecc_rule_inx', sem_models('FOUNDATION'), sem_rulebases('OWLPRIME','ecc_dm_rb'),SEM_APIS.REACH_CLOSURE,'RDFS2-, RDFS3-, RDFS4a-, RDFS4b-, RDFS5-, RDFS6-, RDFS7-, RDFS8-, RDFS9-, RDFS10-, RDFS11-, RDFS12-, RDFS13-','USER_RULES=T'); END;
Error at line 1
ORA-29532: Java call terminated by uncaught Java exception: oracle.jdbc.driver.OracleSQLException: ORA-01652: unable to extend temp segment by 64 in tablespace TEMP
ORA-06512: at "MDSYS.SDO_SEM_INFERENCE";, line 4866
ORA-06512: at "MDSYS.RDF_APIS";, line 16
ORA-06512: at line 1
Please Help me to create rule index.
Note: I am using Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
Regards,
Kavitha.

Hi,
Please use the create_entailment API.
As far as temp tablespace goes, please create a bigfile temp tablespace. You can follow Slide #36 of the
following document.
http://download.oracle.com/otndocs/tech/semantic_web/pdf/2010_ora_semtech_wkshp.pdf
Thanks,
Zhe Wu

DSO activation problem after creating the secondary indexes

Hi,
I am facing the problem with DSO activation after creating the secondary indexes.
Compared with Info Cubes there is no functionality available which allows dropping and recreating a secondary index before/after the data activation.
As a workaround I can write a simple report which drops and creates the indexes on database level.
By using a process chain, we can simply insert the drop index report before data activation and the create index report after the data activation process.
Can any body help me step by step procedure or Material to write the programs for delete index and create index reports on DSO object?..
Thanks in advance for your help.
Thanks & Regards,
Bala

hi,
in BI if you are using the dso for reporting then you can simply chk the settings of dso for SID generation.
no need to create the indexes or delete it.
if the dso is not used for report then no need to use indexes.
Ramesh

Error while creating the CTXXPATH Index

Hi,
I tried to create the CTXXPATH index on my table, which has XMLTYPE column. But while creating the index i m getting the below error,
Error report:
SQL Error: ORA-29958: fatal error occurred in the execution of ODCIINDEXCREATE routine
ORA-29960: line 1,
DRG-11304: function-based indexes are not supported by this indextype
29958. 00000 - "fatal error occurred in the execution of ODCIINDEXCREATE routine"
*Cause: Failed to successfully execute the ODCIIndexCreate routine.
*Action: Check to see if the routine has been coded correctly.
I m using oracle 11g version. Could anyone please help me in resolving it.

Hi,
you can have a look at document "How to Create a Context Index Using a Function [ID 1063279.1]" at Oracle Support. You tried to create a CONTEXT index using a function but a function-based index is not supported. Workaround given in the document is to use a Multi_Column_Datastore.
CTXXPATH is deprecated in Oracle 11.1, better is to use XMLINDEX, see http://download.oracle.com/docs/cd/B28359_01/appdev.111/b28369/whatsnew.htm.
Herald ten Dam
http://htendam.wordpress.com

I maintain a website on which the main (index) page is frequently updated.

I maintain a website on which the main (index) page is frequently updated. In order to make sure that the latest version is displayed, I use the following in the Head of the page:
<META HTTP-EQUIV="Pragma" CONTENT="no-cache" />
This works on all web browsers, but no longer works with Firefox 5.0. Is there an alternative to this Meta statement that can be used to make sure that visitors to the site always view the newest version of the page?

See my post here <http://forums.adobe.com/message/5410674#5410674>

Have changed the "Index" of my website in Dreamweaver and followed the "Put" instructions to upload it back to the "Remote Server," but when I go onto the web to check it, the main (Index) page has not changed. Help!

Have changed the "Index" of my website in Dreamweaver and followed the "Put" instructions to upload it back to the "Remote Server," but when I go onto the web to check it, the main (Index) page has not changed. Help!

This is a duplicate post; see How do I upload from Dreamweaver CS6?

How do I make a page that is currently in my "pages" folder into the new Index page?

I've been developing an updated site within the currently live site. All new pages, including the potential index page, are inside the "pages" folder. When it's time to go live with the updated version, how do I deactivate the current index page and make the one residing in the "pages" folder the new, active index page?

To make GoLive know what page you want to be the "home page" ... right-click on the page in the site window and chose "Set as home page"
To make server/browser know what the homepage is that page shud be named "index" or "default" (and is best placed in the root)
So rename the old and new "homepage"

Error while creating the Unique Index of the Primary Key of an Item

Hi all,
I have deployed a new item (CO_CONTRACTUNIT_PRODUCT) in my publication. The deploy appears to be successfull as the item can be seen in the repository through the Mobile Manager.
The problem occurs when i sync my local DB to get the item offline. While synchronizing, the following error appears, both in the sync window and the log file ol_sync.log.
"ERROR",POL-5130,"11/09/2010 11:43:52","table or view %s.%s not found:CO_CONTRACTUNIT_PRODUCT,CO_CONTRACTID,OD_PRODUCTID,CO_CONTRACTUNITID","DB_ROSHNI"
However, the debug file gives this other error regarding this table.
ALL_INDEX:CREATE UNIQUE INDEX "TPCO_CONTRACTUNIT_PRODUCT_PK" ON CO_CONTRACTUNIT_PRODUCT (CO_CONTRACTID,OD_PRODUCTID,CO_CONTRACTUNITID) -5130Error at C:\ADE\omeprod_ol103021\olite\db\build\win\ocapi\..\..\..\src\ocapi\allindexes.cpp line:329 rc:-5130
Build date Mar 29 2010
okErr=(table or view %s.%s not found)
mess=(CO_CONTRACTUNIT_PRODUCT,CO_CONTRACTID,OD_PRODUCTID,CO_CONTRACTUNITID)
AddLog(-5130 "ERROR",POL-5130,"11/09/2010 11:43:52","table or view %s.%s not found:CO_CONTRACTUNIT_PRODUCT,CO_CONTRACTID,OD_PRODUCTID,CO_CONTRACTUNITID","DB_ROSHNI")
But the index that is being created and is giving the error is the index created automatically with the Primary Key of the table, and so nothing has been modified in that.
The primary key of the table is created with the three columns that are part of the index that is returning the error.
As I could not solve the error, I tried to drop and re-create the item in the repository, but no luck. As a last option, i tried to remove the item from the repository to be able to sync properly again (just like before creating the item), but the error still happens.
Another weird point is that i have tried creating the item in another publication of another database (but with almost equal items), and the item could was downloaded to my local DB without any problem, which makes this problem still more bizarre.
What can it be?
Any help would be great!
Roshni

have you tried unistalling the client and reinstalling it?
schema evolution changes are not always handled correctly please check thread:
Modification of publication item into Mobile Server
i quote from rekounas instructions:
If you are just adding a field, you should only have to run the alter publication item API call.
Here is an old note on schema evolution on different scenarios. The names for the APIs that they use are now deprecated. Use the ConsolidatorManager class and call the method alterPublicationItem("PUBLICATION_ITEM_NAME", "SELECT STMT") :
A) Add column
1. Upload all client data. Clients should not add new data until they are told by the administrator to sync again!!
2. Stop Mobile Server listener
3. Change the Oracle8i/9i database schema (add column)
4. Create a Java program to call the Consolidator Admin API AlterPublicationItem()
5. Start Mobile Server
6. Execute a sync from the client
7. The new column should be seen on the client. Use MSQL to check snapshot definitions.
B) Drop column
1. Upload all client data. Clients should not add new data until they are told by the administrator to sync again!!
2. Stop Mobile Server listener
3. Delete column of the base table in the Oracle database schema
4. Create a Java program to call the Consolidator Admin API DropPublicationItem()
5. Create a Java program to call the Consolidator Admin API CreatePublicationItem() and AddPublicationItem().
6. Start Mobile Server
7. Execute a sync from the client
8. The new column should be seen on the cliet. Use MSQL to check snapshot definitions.
C) Change column datatype
Changing datatypes in a repliatated system is not an easy task. You have to follow certain procedures in order to make it to work. Use DropPublicationItem, CreatePublicationItem and AddPublicationItem methods from the Consolidator Admin API. You must stop/start Mobile Server listener to refresh the cache.
1. Client syncs. Clients should not add new data until they are told by the administrator to sync again!!
2. Stop Mobile Server listener
3. Drop/create column (do not use conversion procudures) at the base table
4. Call DropPublicationItem(). Check if the ErrorQueue and InQueue no longer exist.
5. Call CreatePublicationItem() and AddPublicationItem(). Check if the ErrorQueue and InQueue reflect the new column datatype
6. Start Mobile Server. This automatically resumes application
7. Client executes sync. This should drop the old snapshot and recreate the new snapshot. Use MSQL to check
snapshot definitions.
D) Drop table
1. Client syncs. Clients should not add new data until they are told by the administrator to sync again!!
2. Stop Mobile Server listener
3. Drop base table
4. Call DropPublicationItem(). Check if the ErrorQueue and InQueue no longer exist.
5. Start Mobile Server. This automatically resumes application
6. Client executes sync. This should drop the old snapshot. Use MSQL to check snapshot definitions.
E) Add table
1. Client syncs. Clients should not add new data until they are told by the administrator to sync again!!
2. Stop Mobile Server listener
3. Add new base table
4. Call CreatePublicationItem() and AddPublicationItem() method
5. Start Mobile Server. This automatically resumes application
6. Client executes sync. This should add the new snapshot. Use MSQL to check snapshot definitions.
F) Changing Primary Keys
Chaning PK is a severe operation which must be executed manually. A snapshot must be deleted and recreated to propagate the changes to the clients. This causes a full refresh on this snapshot.
1. Client syncs. Clients should not add new data until they are told by the administrator to sync again!!
2. Stop Mobile Server listener
3. Drop the snapshot using DropPublicationItem() method o
4. Alter the base table
5. Call CreatePublicationItem()and AddPublicationItem() methods for the altered table
6. Start Mobile Server. This automatically resumes application
7. Client executes sync. The old snapshot will be replaced by the new snapstot using a full refresh. Use MSQL to check snapshot definitions.
G) To Change a Table Weight =>
Follow the procedure below to change the Table Weight parameter. The table weight is used by the Mobile Server/Synchronization to determin the sequence in which client records are applied to the Oracle database.
1. Run MGP to apply any changes in the InQueue to the Oracle databse
2. Change table weight using SetTemplateItemMetadata() method
3. Add/change constraint on the the base table which reflects the change in table weight
4. Synchronize
gl m8

Unable to see my project template after creating the same

Hi All,
I Created one (Multi Org)Organization and enable all the required secutiry profiles (HR: Business Group, HR:Security Profile, HR:User Type,MO:Security Profile),When i am creating the Project Template unable to see the same template its moving to some other Org its showing.
what i have to check in setups. could you please any one.
Thanks

Hi Murali,
Can you check whether you have setup the following profile options for that responsibility to see the created templates.
PA: Cross Project User -- Update
This option allow you to update the project with out assignment on the project.
PA: Cross Project User -- View
This option allow you to view the project templates by using that responsibility.
Best Regards,
Sreenath

Unable to Create the Secondary Index for ODS, Please..

Hi All,
The ODS 'A' has two Secondary Indexes ('010' & '020') and I want to create a third index with characteristics X & Y. X is there in both '010' & '020' Indexes.
RSA1 --> Info Provider --> Double click on ODS 'A' --> Right Click on last folder 'Indexes' --> Create --> '030' assigned by the system for the new Index.
I am having all the Characteristics in the left window after clicking the InfoObject Catalog and Characteristics
When I try to drag the 'X' from the left window to keep it under 'Indexes' folder or '030' Index, it gives 'NO'
symbol (a circle with cross line). I am not able to find the cause. I could drag it on to 'Key fields' of 'Data Fields' , but not 'Indexex' folder. Am I doing something wrong, please ?
Thanks,
Venkat.

This appeared in one of the earlier threads..
I think u need to go to se11..there enter the name of the active table of the ODS..name will be../BIC/A<ODS tech name>00'.
Once the table field appear after clicking display..
u will see button 'indexes' on right hand top..
click on that and then trying creating a new secondary index..
cheers,
Vishvesh

How can I create a Splash / Welcome Page before the home page

I'm trying to create a splash page to inform our users about some changes to the site before they enter the site. I created a new page in the top menu by clicking the left X of the home / index page, which is the result that wanted. But when I click on site properties of this new splash page it has inherited the "index.html" filename and when I export the HTML my home page is now named "index1.html."
I'm concerned about the effects this will have on our SEO and analytics, so I was wondering if there was a work around for this. Basically I'm looking to have the Splash page with the new information be the first thing visitors see with a button that allows them to enter the main site sfter they've read the information. But I don't want to compromise the page structure by adding another index page or renaming the existing index page.
Is this possible? Or can someone suggest a way to accomplish this in MUSE?

CRESDesigner wrote:
...Is this possible?...
Not quite, if you are concerned about SEO. Introductory or 'splash' pages are terrible for this and can hurt your search results even after you pull the splash page down. In regard to SEO, we already shoot ourselves in the foot by using Muse. Be careful about compounding this with a splash page.
Ideally, your web site would check for the existence of a cookie that identifies if the visitor has seen the alert. If the cookie is not present, a DIV overlay would be presented with your alert. Once that alert is presented, the cookie would be written to prevent further display of the alert. You could achieve this in any other web design program (or text editor) today, or you can submit a feature request and wait for Muse to offer this functionality in months/years.

How to change the index page of tomcat to a specific page in a web app.

hi all
i am trying to figure out a way to change default application to a specific web application deployed in tomcat, so that when you type localhost:8080, it will start with the web app. basically i want to get ride of the context or map the context to the default page. i.e. map this http://localhost:8080/example/ to http://localhost:8080/. thanks.

maybe i didn't explain myself clearly as to what i needed to do.
i have created a web application and deployed into tomcat 5.5 with a context of "example". the path looks something like this: $catalina_home/webapps/example. in order to access the application, i need to type http://localhost:8080/example in the browser. is there any way to change it so that when i type http://localhost:8080, it will take me to my web application without accessing the tomcat index page.
thanks.

IWeb '09 and creating an "Index" page for two separate sides of my website

I'm redesigning my website with iWeb '09 seeing that I've recently switched to Mac from being a life-long PC/Windows user. I'm not too web programming savvy so iWeb fits my needs as a very good program that redesigns my site very nicely (and quite inexpensively, as well).
My current incarnation of my website (http://www.jeffreykern.com) was designed by a professional web designer on Dreamweaver for PC a couple of years ago. Some time ago when I was trying to update my PC with XP SP 3 (bad idea as it turned out), my connection to my web hosting service got completely fouled up and I lost the ability to update the site and haven't updated my site since. Knowing that I was going to be switching to Mac (with my new Mac Pro) I never had the desire, or energy, to patch things up to update my site with my PC. Plus, I was in need of a redesign so I eventually got my site ready to go with iWeb 09. That's where I stand right now...
So, as you can see on my current site I have a main index page that splits up into the two sides of my life: the triathlete side and the writer side. I've already redesigned both sides of my site with iWeb, I'm ready to update it thru my web hosting via FTP and Transmit 3, but I cannot find how to create a main "Index" page on iWeb that will let me branch off into two different directions. By having that "Index" page intact I will be able to keep my domain of jeffreykern.com as it currently stands. I don't mind having to get two different domains for each of my two sides of my site but would like to avoid that extra step -- if, at all, possible.
Thanks in advance for your help,
Jeff

Building three websites on three separate domain files would be my choice.
Its important to realize that you cannot have a page called "index" using iWeb because the associated index.html file will conflict with the one that iWeb creates.
As has been suggested, the first site would be one page. The site name would be jeffreykern.
This site will publish as jeffreykern_files and an index.html file. Inside this folder is another index.html file. This is the one your domain name will be directed at if you don't need an RSS feed.
If your server allows it, create a root folder on it called "jeffreykern" and upload the contents of the local folder to this and ignore the separate index.html file. Note that I said contents and not the folder itself.
A lot of servers require that you upload to a pre existing folder. In this case you will have to upload the index.html file and the jeffreykern _files folder.
The two other sites are named and published as writer and triathlete. The external index files of these two sites are renamed writer.html and triathlete.html.
These two files and their corresponding folders are uploaded to your root folder on the server after adding tags and optimizing.......
http://www.iwebformusicians.com/SearchEngines/SEO.html
Now you have a main (one page) site with two sub sites.
The domain name http://www.jeffreykern.com/ is directed at the index.html file so that when this is entered into the browser, the main page will appear.
The links to the two main sections, whether they be text and/or image, are created and selected as external hyperlinks.
http://www.jeffreykern.com/triathlete/
http://www.jeffreykern.com/writer/
Clicking these links will open the first page of their respective sites.
If you do the sensible thing and trash the iWeb default navigation to replace it with a custom one, you can include external hyperlinks to the landing page and the other site in this.
The website - iWeb for Musicians - is created like this and is built on 9 separate domain files for ease of updating and publishing. The whole site is tied together with a Main navigation to get to each section which has a Sub navigation to jump around that section.
For more on navigation see.....
http://www.iwebformusicians.com/WebMusic/Navigation.html
Also refer to Fonts, Colors and Navigation on this page ......
http://www.iwebformusicians.com/WebMusic/iWebandInternetExplorer.html

Please help me create the indexes for this XML

Hi Mark and others,
What is the way to create the correct index for this kind of XML (I posted earlier)? I created the indexes without using those prefixes without any problems but they do not seem to be used during processing. For 300 statutes, it took about 10 minutes! For the smplier verion, I created indexes and it took no more than 30 seconds to process more than 4000 statutes.
<AllStatuteQueryResponse xmlns="http://crimnet.state.mn.us/mnjustice/statute/service/3.0">
<ns1:Statutes xmlns:ns1="http://crimnet.state.mn.us/mnjustice/statute/messages/3.0">
<ns1:Statutes>
<ns2:StatuteId xmlns:ns2="http://crimnet.state.mn.us/mnjustice/statute/3.0">1</ns2:StatuteId>
<ns3:Chapter xmlns:ns3="http://crimnet.state.mn.us/mnjustice/statute/3.0">84</ns3:Chapter>
<ns4:Section xmlns:ns4="http://crimnet.state.mn.us/mnjustice/statute/3.0">82</ns4:Section>
<ns5:Subdivision xmlns:ns5="http://crimnet.state.mn.us/mnjustice/statute/3.0">1a</ns5:Subdivision>
<ns6:Year xmlns:ns6="http://crimnet.state.mn.us/mnjustice/statute/3.0">0</ns6:Year>
<ns7:LegislativeSessionCode xmlns:ns7="http://crimnet.state.mn.us/mnjustice/statute/3.0">
<ns7:StatuteCode>
<ns7:code>4</ns7:code>
<ns7:description>4</ns7:description>
</ns7:StatuteCode>
</ns7:LegislativeSessionCode>
<ns8:SessionTextIndicator xmlns:ns8="http://crimnet.state.mn.us/mnjustice/statute/3.0">false</ns8:SessionTextIndicator>
<ns9:HeadNoteIndicator xmlns:ns9="http://crimnet.state.mn.us/mnjustice/statute/3.0">false</ns9:HeadNoteIndicator>
<ns10:EffectiveDate xmlns:ns10="http://crimnet.state.mn.us/mnjustice/statute/3.0">1859-01-01</ns10:EffectiveDate>
<ns11:EnactmentDate xmlns:ns11="http://crimnet.state.mn.us/mnjustice/statute/3.0">1859-01-01</ns11:EnactmentDate>
<ns12:RepealedIndicator xmlns:ns12="http://crimnet.state.mn.us/mnjustice/statute/3.0">false</ns12:RepealedIndicator>
<j:DocumentLocationURI xmlns:j="http://www.it.ojp.gov/jxdm/3.0.2">
<j:ID xsi:type="j:TextType" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">http://www.revisor.leg.state.mn.us/stats/84/82.html</j:ID>
</j:DocumentLocationURI>
<ns13:SummaryDescriptionText xmlns:ns13="http://crimnet.state.mn.us/mnjustice/statute/3.0">Snowmobiles-Snowmobile registration</ns13:SummaryDescriptionText>
<ns14:StatuteFunction xmlns:ns14="http://crimnet.state.mn.us/mnjustice/statute/3.0">
<ns14:StatuteIntegrationId>1</ns14:StatuteIntegrationId>
Thanks!
Ben

Hi Mark, here is the schema. I did not register the schema, because when I processed the simpler version, I did not either and I just created the indexes. I did not create an VARRAY in the table. The DDL is simply create table CStatute_XML(id number, xmldoc xmltype).
Schema:
<?xml version="1.0" encoding="UTF-8"?>




<xsd:schema targetNamespace="http://crimnet.state.mn.us/mnjustice/statute/3.0" elementFormDefault="qualified" attributeFormDefault="unqualified" version="3.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://crimnet.state.mn.us/mnjustice/statute/3.0">
     <xsd:element name="StatuteCode">
          <xsd:annotation>
               <xsd:documentation>
                    This complex type is a generic structure representing code value sets defined in the Minnesota Criminal Justice Statute Service.
                    A single element of the value set contains both a code value (e.g. F) and a description (e.g. Felony).
                    The following concepts within the MNCJSS are represented by this complex type:
                         OffenseSummary
                         OffenseSummarySeverityLevel
                         LegislativeSession
                         Function
                         OffenseLevel
                         OffenseSeverityLevel
                         DetailedOffenseCode
                         GeneralOffenseCode
               </xsd:documentation>
          </xsd:annotation>
          <xsd:complexType>
               <xsd:sequence>
                    <xsd:element name="code" type="xsd:string"/>
                    <xsd:element name="description" type="xsd:string"/>
               </xsd:sequence>
          </xsd:complexType>
     </xsd:element>
     <xsd:element name="StatuteId" type="xsd:integer">
          <xsd:annotation>
               <xsd:documentation>Primary Key reference to Minnesota Criminal Justice Statute Service disseminated by CriMNet</xsd:documentation>
               <xsd:appinfo>Statute.statuteId</xsd:appinfo>
          </xsd:annotation>
     </xsd:element>
     <xsd:element name="StatuteIntegrationId" type="xsd:integer">
          <xsd:annotation>
               <xsd:documentation>Primary Key reference to the StatuteFunction object within the Minnesota Criminal Justice Statute Service disseminated by CriMNet</xsd:documentation>
               <xsd:appinfo>StatuteFunction.statuteIntegrationId</xsd:appinfo>
          </xsd:annotation>
     </xsd:element>
     <xsd:element name="FunctionCode">
          <xsd:annotation>
               <xsd:documentation>TBD</xsd:documentation>
               <xsd:appinfo>StatuteFunction.Function</xsd:appinfo>
          </xsd:annotation>
          <xsd:complexType>
               <xsd:sequence>
                    <xsd:element ref="StatuteCode"/>
               </xsd:sequence>
          </xsd:complexType>
     </xsd:element>
     <xsd:element name="OffenseSummaryCode">
          <xsd:annotation>
               <xsd:documentation>TBD</xsd:documentation>
               <xsd:appinfo>StatuteFunction.OffenseSummary</xsd:appinfo>
          </xsd:annotation>
          <xsd:complexType>
               <xsd:sequence>
                    <xsd:element ref="StatuteCode"/>
               </xsd:sequence>
          </xsd:complexType>
     </xsd:element>
     <xsd:element name="OffenseSummarySeverityLevelCode">
          <xsd:annotation>
               <xsd:documentation>TBD</xsd:documentation>
               <xsd:appinfo>StatuteFunction.OffenseSummary.OffenseSummarySeverityLevel</xsd:appinfo>
          </xsd:annotation>
          <xsd:complexType>
               <xsd:sequence>
                    <xsd:element ref="StatuteCode"/>
               </xsd:sequence>
          </xsd:complexType>
     </xsd:element>
     <xsd:element name="OffenseLevelCode">
          <xsd:annotation>
               <xsd:documentation>TBD</xsd:documentation>
               <xsd:appinfo>StatuteFunction.OffenseLevel</xsd:appinfo>
          </xsd:annotation>
          <xsd:complexType>
               <xsd:sequence>
                    <xsd:element ref="StatuteCode"/>
               </xsd:sequence>
          </xsd:complexType>
     </xsd:element>
     <xsd:element name="OffenseSeverityLevelCode">
          <xsd:annotation>
               <xsd:documentation>TBD</xsd:documentation>
               <xsd:appinfo>StatuteFunction.OffenseSeverityLevel</xsd:appinfo>
          </xsd:annotation>
          <xsd:complexType>
               <xsd:sequence>
                    <xsd:element ref="StatuteCode"/>
               </xsd:sequence>
          </xsd:complexType>
     </xsd:element>
     <xsd:element name="LegislativeSessionCode">
          <xsd:annotation>
               <xsd:documentation>TBD</xsd:documentation>
               <xsd:appinfo>StatuteChapterSection.LegislativeSession</xsd:appinfo>
          </xsd:annotation>
          <xsd:complexType>
               <xsd:sequence>
                    <xsd:element ref="StatuteCode"/>
               </xsd:sequence>
          </xsd:complexType>
     </xsd:element>
     <xsd:element name="GeneralOffenseCode" nillable="true">
          <xsd:annotation>
               <xsd:documentation>An integer (1-9) identifier of a general statute category code used for statistical analysis.</xsd:documentation>
               <xsd:appinfo>StatuteFunction.DetailedOffenseCode.GeneralOffenseCode</xsd:appinfo>
          </xsd:annotation>
          <xsd:complexType>
               <xsd:sequence>
                    <xsd:element ref="StatuteCode"/>
               </xsd:sequence>
          </xsd:complexType>
     </xsd:element>
     <xsd:element name="DetailedOffenseCode" nillable="true">
          <xsd:annotation>
               <xsd:documentation>An identification number associated with a statute offense type in the form of nnn.nnn. From a list of 350. Corresponds to the StatuteOffinseTypeText.</xsd:documentation>
               <xsd:appinfo>StatuteFunction.DetailedOffenseCode</xsd:appinfo>
          </xsd:annotation>
          <xsd:complexType>
               <xsd:sequence>
                    <xsd:element ref="StatuteCode"/>
               </xsd:sequence>
          </xsd:complexType>
     </xsd:element>
     <xsd:element name="Chapter" type="xsd:string">
          <xsd:annotation>
               <xsd:documentation>A numeric identifier of a chapter within a statute.</xsd:documentation>
               <xsd:appinfo>Statute.chapter; StatuteChapterSection.chapter</xsd:appinfo>
          </xsd:annotation>
     </xsd:element>
     <xsd:element name="Section" type="xsd:string" nillable="true">
          <xsd:annotation>
               <xsd:documentation>An integer number identifier of a section of a chapter of a statute.</xsd:documentation>
               <xsd:appinfo>Statute.section; StatuteChapterSection.section</xsd:appinfo>
          </xsd:annotation>
     </xsd:element>
     <xsd:element name="Subdivision" type="xsd:string" nillable="true">
          <xsd:annotation>
               <xsd:documentation>An identifier of a subdivision within a code book.</xsd:documentation>
               <xsd:appinfo>Statute.subdivision</xsd:appinfo>
          </xsd:annotation>
     </xsd:element>
     <xsd:element name="HeadNoteIndicator" type="xsd:boolean">
          <xsd:annotation>
               <xsd:documentation></xsd:documentation>
               <xsd:appinfo>StatuteChapterSection.headNote</xsd:appinfo>
          </xsd:annotation>
     </xsd:element>
     <xsd:element name="Year" type="xsd:int">
          <xsd:annotation>
               <xsd:documentation>TBD</xsd:documentation>
               <xsd:appinfo>StatuteChapterSection.year</xsd:appinfo>
          </xsd:annotation>
     </xsd:element>
     <xsd:element name="EffectiveDate" type="xsd:date" nillable="true">
          <xsd:annotation>
               <xsd:documentation>The date a statute came into effect</xsd:documentation>
               <xsd:appinfo>Statute.effectiveDate</xsd:appinfo>
          </xsd:annotation>
     </xsd:element>
     <xsd:element name="ExpirationDate" type="xsd:date" nillable="true">
          <xsd:annotation>
               <xsd:documentation>The date a statute was not longer effective.</xsd:documentation>
               <xsd:appinfo>Statute.effectiveDate</xsd:appinfo>
          </xsd:annotation>
     </xsd:element>
     <xsd:element name="EnactmentDate" type="xsd:date" nillable="true">
          <xsd:annotation>
               <xsd:documentation>A date a statute was signed into law.</xsd:documentation>
               <xsd:appinfo>Statute.enactmentDate</xsd:appinfo>
          </xsd:annotation>
     </xsd:element>
     <xsd:element name="RepealedIndicator" type="xsd:boolean">
          <xsd:annotation>
               <xsd:documentation>A date a statute number was repealed, amended, or renumbered.</xsd:documentation>
               <xsd:appinfo>Statute.repealedFlag</xsd:appinfo>
          </xsd:annotation>
     </xsd:element>
     <xsd:element name="HeadNote" type="xsd:boolean">
          <xsd:annotation>
               <xsd:documentation></xsd:documentation>
               <xsd:appinfo>Statute.headNote</xsd:appinfo>
          </xsd:annotation>
     </xsd:element>
     <xsd:element name="SummaryDescriptionText" type="xsd:string" nillable="true">
          <xsd:annotation>
               <xsd:documentation>A long description of a statute.</xsd:documentation>
               <xsd:appinfo>Statute.summaryText</xsd:appinfo>
          </xsd:annotation>
     </xsd:element>
     <xsd:element name="LegislativeText" type="xsd:string" nillable="true">
          <xsd:annotation>
               <xsd:documentation>The legislative of a statute.</xsd:documentation>
               <xsd:appinfo>StatuteChapterSection.legislativeText</xsd:appinfo>
          </xsd:annotation>
     </xsd:element>
     <xsd:element name="SessionTextIndicator" type="xsd:boolean">
          <xsd:annotation>
               <xsd:documentation></xsd:documentation>
               <xsd:appinfo>StatuteChapterSection.sessionTextFlag</xsd:appinfo>
          </xsd:annotation>
     </xsd:element>
     <xsd:element name="FunctionText" type="xsd:string" nillable="true">
          <xsd:annotation>
               <xsd:documentation></xsd:documentation>
               <xsd:appinfo>StatuteFunction.functionText</xsd:appinfo>
          </xsd:annotation>
     </xsd:element>
     <xsd:element name="JuvenileOnlyIndicator" type="xsd:boolean">
          <xsd:annotation>
               <xsd:documentation>An indicator identifying whether a statute applies to juveniles only.</xsd:documentation>
               <xsd:appinfo>StatuteFunction.juvenileOnlyFlag</xsd:appinfo>
          </xsd:annotation>
     </xsd:element>
     <xsd:element name="CrimeOfViolenceIndicator" type="xsd:boolean">
          <xsd:annotation>
               <xsd:documentation>An indicator identifying whether a statute is a crime of violence under Minnesota statute 624 section 712 subdivision 5.</xsd:documentation>
               <xsd:appinfo>StatuteFunction.crimeOfViolenceFlag</xsd:appinfo>
          </xsd:annotation>
     </xsd:element>
     <xsd:element name="EnhanceableIndicator" type="xsd:boolean">
          <xsd:annotation>
               <xsd:documentation>An indicator identifying whether the charges are enhanceable by specific factors (the definition of enhanceable is pending review).</xsd:documentation>
               <xsd:appinfo>StatuteFunction.enhanceableFlag</xsd:appinfo>
          </xsd:annotation>
     </xsd:element>
     <xsd:element name="TargetedMisdemeanorIndicator" type="xsd:boolean">
          <xsd:annotation>
               <xsd:documentation>An indicator identifying whether a statute is a targeted misdemeanor as defined in Minnnesota Statute 299C.10, subdivision. 1(d).</xsd:documentation>
               <xsd:appinfo>StatuteFunction.targetedMisdemeanorFlag</xsd:appinfo>
          </xsd:annotation>
     </xsd:element>
     <xsd:element name="MandatoryAppearanceIndicator" type="xsd:boolean">
          <xsd:annotation>
               <xsd:documentation></xsd:documentation>
               <xsd:appinfo>StatuteFunction.mandatoryAppearanceFlag</xsd:appinfo>
          </xsd:annotation>
     </xsd:element>
     <xsd:element name="RegisterableOffenseIndicator" type="xsd:boolean">
          <xsd:annotation>
               <xsd:documentation></xsd:documentation>
               <xsd:appinfo>StatuteFunction.registerableOffenseFlag</xsd:appinfo>
          </xsd:annotation>
     </xsd:element>
     <xsd:element name="StatuteFunction">
          <xsd:annotation>
               <xsd:documentation></xsd:documentation>
               <xsd:appinfo>StatuteFunction</xsd:appinfo>
          </xsd:annotation>
          <xsd:complexType>
               <xsd:sequence>
                    <xsd:element ref="StatuteIntegrationId" />
                    <xsd:element ref="FunctionCode"/>
                    <xsd:element ref="FunctionText" minOccurs="0" maxOccurs="1"/>
                    <xsd:element ref="CrimeOfViolenceIndicator"/>
                    <xsd:element ref="EnhanceableIndicator"/>
                    <xsd:element ref="TargetedMisdemeanorIndicator"/>
                    <xsd:element ref="RegisterableOffenseIndicator"/>
                    <xsd:element ref="JuvenileOnlyIndicator"/>
                    <xsd:element ref="MandatoryAppearanceIndicator"/>
                    <xsd:element ref="OffenseLevelCode" minOccurs="0" maxOccurs="1"/>
                    <xsd:element ref="GeneralOffenseCode" minOccurs="0" maxOccurs="1"/>
                    <xsd:element ref="DetailedOffenseCode" minOccurs="0" maxOccurs="1"/>
                    <xsd:element ref="OffenseSummaryCode" minOccurs="0" maxOccurs="1"/>
                    <xsd:element ref="OffenseSummarySeverityLevelCode" minOccurs="0" maxOccurs="1"/>
                    <xsd:element ref="OffenseSeverityLevelCode" minOccurs="0" maxOccurs="1"/>
               </xsd:sequence>
          </xsd:complexType>
     </xsd:element>
</xsd:schema>
Query:
first part to get the statute ID numbers,
insert into CriMNet_Statutes
     select cs.StatuteId, cs.Chapter, cs.Section, cs.Subdivision, cs.Year, cs.LegCode,
          cs.LegDesc, cs.SessionTextIndicator, cs.HeadNoteIndicator,
          to_date(cs.EffectiveDate, 'yyyy/mm/dd') as eDate,
          to_date(cs.EnactmentDate, 'yyyy/mm/dd') as EnDate,
          cs.RepealedIndicator, cs.SummaryDescriptionText
     from Cstatute_xml,
     xmltable
          xmlnamespaces
               default 'http://crimnet.state.mn.us/mnjustice/statute/3.0',
               --- or 'http://crimnet.state.mn.us/mnjustice/statute/3.0' as "cs"
               'http://crimnet.state.mn.us/mnjustice/statute/service/3.0' as "cx",
               'http://crimnet.state.mn.us/mnjustice/statute/messages/3.0' as "ns1"
          '/cx:AllStatuteQueryResponse/ns1:Statutes/ns1:Statutes'
          --- '/AllStatuteQueryResponse//ns:Statutes' --- produces an extra row
          passing SXMLDOC
          columns
          StatuteId     varchar2(10)     path '//StatuteId',
          Chapter          varchar2(10)     path '//Chapter',
          Section          varchar2(20)     path '//Section',
          Subdivision     varchar2(20)     path '//Subdivision',
          Year          number          path '//Year',
          LegCode          varchar2(10)     path '//LegislativeSessionCode/StatuteCode/code',
          LegDesc          varchar2(10)     path '//LegislativeSessionCode/StatuteCode/description',
          SessionTextIndicator varchar2(10) path '//SessionTextIndicator',
          HeadNoteIndicator varchar2(10)     path '//HeadNoteIndicator',
          EffectiveDate     varchar2(15)     path '//EffectiveDate',
          EnactmentDate     varchar2(15)     path '//EnactmentDate',
          RepealedIndicator varchar2(10)     path '//RepealedIndicator',
          SummaryDescriptionText varchar2(150) path '//SummaryDescriptionText'
     ) cs;
Second part to get the function code for each statute ID (one ID to many function codes).
declare
          v_statuteID     number;
          v_statuteIDC     varchar2(10);
          cursor c_cmns is
          select statuteid from CriMNet_Statutes;
     begin
          for v_cmns in c_cmns loop
               v_StatuteID := v_cmns.StatuteID;
               v_statuteIDC := to_char(v_statuteID);
               insert into CriMNet_Statute_Function
               select v_StatuteID, cf.* from Cstatute_xml,
               xmltable
                    xmlnamespaces
                         'http://crimnet.state.mn.us/mnjustice/statute/3.0' as "cs",
                         'http://crimnet.state.mn.us/mnjustice/statute/service/3.0' as "cx",
                         'http://crimnet.state.mn.us/mnjustice/statute/messages/3.0' as "ns1"
                    'for $cxm in /cx:AllStatuteQueryResponse/ns1:Statutes/ns1:Statutes[cs:StatuteId = $val/pStatuteId]/cs:StatuteFunction
                    return
                    <cs:CSFunction>
                         <cs:StatuteIntegrationId>{$cxm//cs:StatuteIntegrationId}</cs:StatuteIntegrationId>
                         <cs:FunctionCode>{$cxm//cs:FunctionCode/cs:StatuteCode/cs:code}</cs:FunctionCode>
                         <cs:FunctionDesc>{$cxm//cs:FunctionCode/cs:StatuteCode/cs:description}</cs:FunctionDesc>
                         <cs:CrimeOfViolenceIndicator>{$cxm//cs:CrimeOfViolenceIndicator}</cs:CrimeOfViolenceIndicator>
                         <cs:EnhanceableIndicator>{$cxm//cs:EnhanceableIndicator}</cs:EnhanceableIndicator>
                         <cs:TargetedMisdIndicator>{$cxm//cs:TargetedMisdemeanorIndicator}</cs:TargetedMisdIndicator>
                         <cs:RegisterableOffIndicator>{$cxm//cs:RegisterableOffenseIndicator}</cs:RegisterableOffIndicator>
                         <cs:JuvenileOnlyIndicator>{$cxm//cs:JuvenileOnlyIndicator}</cs:JuvenileOnlyIndicator>
                         <cs:MandatoryAppIndicator>{$cxm//cs:MandatoryAppearanceIndicator}</cs:MandatoryAppIndicator>
                         <cs:OffenseLevelCode>{$cxm//cs:OffenseLevelCode/cs:StatuteCode/cs:code}</cs:OffenseLevelCode>
                         <cs:OffenseLevelDesc>{$cxm//cs:OffenseLevelCode/cs:StatuteCode/cs:description}</cs:OffenseLevelDesc>
                         <cs:GeneralOffenseCode>{$cxm//cs:GeneralOffenseCode/cs:StatuteCode/cs:code}</cs:GeneralOffenseCode>
                         <cs:GeneralOffenseDesc>{$cxm//cs:GeneralOffenseCode/cs:StatuteCode/cs:description}</cs:GeneralOffenseDesc>
                         <cs:DetailedOffenseCode>{$cxm//cs:DetailedOffenseCode/cs:StatuteCode/cs:code}</cs:DetailedOffenseCode>
                         <cs:DetailedOffenseDesc>{$cxm//cs:DetailedOffenseCode/cs:StatuteCode/cs:description}</cs:DetailedOffenseDesc>
                         <cs:OffenseSummaryCode>{$cxm//cs:OffenseSummaryCode/cs:StatuteCode/cs:code}</cs:OffenseSummaryCode>
                         <cs:OffenseSummaryDesc>{$cxm//cs:OffenseSummaryCode/cs:StatuteCode/cs:description}</cs:OffenseSummaryDesc>
                         <cs:OffenseSumSeverityLevelCode>{$cxm//cs:OffenseSummarySeverityLevelCode/cs:StatuteCode/cs:code}</cs:OffenseSumSeverityLevelCode>
                         <cs:OffenseSumSeverityLevelDesc>{$cxm//cs:OffenseSummarySeverityLevelCode/cs:StatuteCode/cs:description}</cs:OffenseSumSeverityLevelDesc>
                    </cs:CSFunction>'
                    passing SXMLDOC, xmlelement("pStatuteId", v_statuteIDC) as "val"
                    columns
                    StatuteIntegrationId     number     path '/cs:CSFunction/cs:StatuteIntegrationId',
                    FunctionCode          varchar2(10) path '/cs:CSFunction/cs:FunctionCode',
                    FunctionDesc          varchar2(30)     path '/cs:CSFunction/cs:FunctionDesc',
                    CrimeOfViolenceIndicator varchar2(10)     path '/cs:CSFunction/cs:CrimeOfViolenceIndicator',
                    EnhanceableIndicator     varchar2(10)     path '/cs:CSFunction/cs:EnhanceableIndicator',
                    TargetedMisdIndicator     varchar2(10)     path '/cs:CSFunction/cs:TargetedMisdIndicator',
                    RegisterableOffIndicator varchar2(10)     path '/cs:CSFunction/cs:RegisterableOffIndicator',
                    JuvenileOnlyIndicator     varchar2(10)     path '/cs:CSFunction/cs:JuvenileOnlyIndicator',
                    MandatoryAppIndicator     varchar2(10)     path '/cs:CSFunction/cs:MandatoryAppIndicator',
                    OffenseLevelCode     varchar2(10)     path '/cs:CSFunction/cs:OffenseLevelCode',
                    OffenseLevelDesc     varchar2(40)     path '/cs:CSFunction/cs:OffenseLevelDesc',
                    GeneralOffenseCode     varchar2(10)     path '/cs:CSFunction/cs:GeneralOffenseCode',
                    GeneralOffenseDesc     varchar2(60)     path '/cs:CSFunction/cs:GeneralOffenseDesc',
                    DetailedOffenseCode     varchar2(10)     path '/cs:CSFunction/cs:DetailedOffenseCode',
                    DetailedOffenseDesc     varchar2(60)     path '/cs:CSFunction/cs:DetailedOffenseDesc',
                    OffenseSummaryCode     varchar2(10)     path '/cs:CSFunction/cs:OffenseSummaryCode',
                    OffenseSummaryDesc     varchar2(60)     path '/cs:CSFunction/cs:OffenseSummaryDesc',
                    OffenseSumSeverityLevelCode varchar2(10)     path '/cs:CSFunction/cs:OffenseSumSeverityLevelCode',
                    OffenseSumSeverityLevelDesc varchar2(30)     path '/cs:CSFunction/cs:OffenseSumSeverityLevelDesc'
               ) cf;
               ---dbms_output.put_line('Statute ID = ' || v_StatuteID);
          end loop;
     end;
You mentioned that I should include the namespace in the existsnode function but I did not. I am going to try after including it. Thanks.
Ben

Template to create the API index page

Similar Messages

Maybe you are looking for