Choice element

I have XSD with choice element. How to create javacript which will hide one section and show other?

I'm actually working on an almost identical situation. Supposedly you can use subform sets with the appropriate bindings and only the right data will show. I've been unsuccesful so far. Anyone care to offer a suggestion?
Thanks!
Ryan D. Lunka
Cardinal Solutions Group
[email protected]

Similar Messages

ABAP Proxy generation terminated (WSDl choice element not supported)

Hello
Im trying to generate ABAP proxy from WSDL file (A valid XSD file has imported as External definitions in to XI Integration Repository and created Out bound Interface which gives WSDL file for Proxy generation in SPROXY).
Unfortunately one of the WSDL file element "<choice>" not supported by ABAP Proxy Generation. it gives the following error.
Proxy generation terminated: WSDL error (<choice> not supported)
Message no. SPRX038
Syntax of <choice> element code in WSDL file:
<xsd:choice minOccurs='1' maxOccurs='1'>
<xsd:element name='Employees' minOccurs='1' maxOccurs='1'>
</xsd:element>
</xsd:choice>
Can some one please help if already come across this kind of problem.
Please suggest me if there any alternate element for WSDL <choice>.
Regards
Rajesh

Hi Aamir
Thanks for your help...
I have gone through attached thread.
Does It means should i change <choice> element with any alternate element. If it is the case can u suggest me any alternate to <choice> element.
Can u pls tell what are all changes i need to do in WSDL file to support ABAP proxy generation.
Regards
Rajesh

Xml Schema xs:choice element in dynamic forms

Hi all,
I'm developing an xml schema for creating the data model of a form. I connect LC Designer-8.2ES to this schema.
In the schema I do have mutually exclusive elements implemented with a <xs:choice> element. A very comparable situation was described in this thread : http://www.acrobatusers.com/forums/aucbb/viewtopic.php?id=123 in 2007.
The problem, as related in this thread, is that only the very first element of the choice is displayed in the generated pdf and I don't know how to display all parts as a real choice. So what's the best way to let user fill in one part or the other of the choice?
Does it need to be implemented with scripting (xfa...myform.presence = visible | hidden)?
I want that only the filled element of the choice be exported from the form, the resulting xml being valid according the schema. I seems to work, but as of now, only for the first element...
BTW, what's the best document describing what parts of xml schema are usable in dynamic XFA forms? Is it 100% compatible? I've observed that the constraints in my schema are not validated in the forms. Shouldn't xml schema generate validating script in LCD? Does it apply for a subset of xml schema?
Thanks in advance,
jgrd

Hi all,
finally, I understand that we cannot use "anonymous" sequences neither in LiveCycle (like this following example where person might have many email)
    <xs:element name="person">
        <xs:complexType>
            <xs:sequence maxOccurs="unbounded">
                <xs:element name="email" type="xs:string"/>
            </xs:sequence>
        </xs:complexType>
    </xs:element>
valid instance with 3 emails :
<person xsi:noNamespaceSchemaLocation="Untitled39.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <email>String</email>
    <email>String</email>
    <email>String</email>
</person>
In LC Designer, element with same name (<email>) are not used AFAK. Maybe I'm wrong?
The same hands with <xs:choice> where only first choice appears in pdf although being present in LC Designer.
As for sequences, my idea is to produce <email1>, <email2>, etc. in a static schema, before connecting schema's data to LCD.
Hope someone can show up and tell it's the right way or not.
Regards
jgrd

BPELProcess - Assign Activity - xsd choice element difficulties

Hi,
I am trying to copy values from a pipe ("|") delimited text file that has been picked - up by a file adaptor and converted into xml of form (C1,C2,C3,...,Cn). My problem arises when I need to populate an xsd:choice element with C5 & C6 as the same type. If you need more info just let me know, Please advise...
Kind Regards,
Warren.

well, lets say ur looking at the 'Copy Rules' screen, my converted string delimited file is on the left and the xsd im copying to is the right+ :
body body
spiLine ServiceOrder
C1 ------------------- orderType
C2 ------------------- refrence number
... +choice
+equipment
C5 ------------------ value
C6
if you can make any sense of this, what I need is to create another equipment node to assign C6 too, in the xsd:choice element...

XSL transformations - choice element

Hi all,
Need inputs in doing xslt transformations on a choice element. Please provide helpful urls/inputs.
My xsd(similar one):-
<xs:element name="Root">
                    <xs:complexType>
                         <xs:choice minOccurs="0" maxOccurs="1">
                              <xs:element name="field1" type="xs:string"></xs:element>
                              <xs:element name="field2" type="xs:string"></xs:element>
                              <xs:element name="field3" type="xs:string"></xs:element>
                              <xs:element name="field4" type="xs:string"></xs:element>
                         </xs:choice>
                    </xs:complexType>
Required output:-
<Root>
<field1>message</field1>
</Root>
or
<Root>
<field2>message</field2>
</Root>
or
<Root>
<field3>message</field3>
</Root>
But when i do transformations the output is shown below. How could I get the above input?
<Root>
<field1>message</field1>
<field2/>
<field3/>
<field4/>
</Root>
Please let me know

Hi,
Do you use the "transformation" activity of the BPEL ?
If yes then you can check two things :
- That the option of the XSL map doesn't generate empty node for all unmapped nodes
- That you have an if condition checking if the node exist before mapping it.
regards,
mathieu

Subject: Choice element in JAXB 1.x

Recently i ran into problem of having too many elements in choice tag. JAXB doesn't throw exception, but generated files doesn't comply Java.
While compilation it throws "code too large" exception. On removing few i can manage, but i am looking for long term solution.
Any suggestion appreciated.
-Balaji S

As per my understanding the * at the end SEDOL | SILCHESTER)*> making it to create choice or replace. If you remove star from you DTD it will generate OTD without choice.
Thanks
Sanjeev

Using selectedIndex of UIX choice element?

I'm a bit embarrased that I can't figure this out - it's probably very simple.
I have a messageChoice element on a UIX page, and I'd like to render the page differently based on which option is currently selected. To do this, I figure I can just use an event handler to maintain a value in the page state, tie the event handler to the messageChoice element, and use a switcher referencing that value on the page state to choose between the different sets of elements I want to render.
I added a <primaryClientAction> element to the messageChoice element, a <fireAction> element to that, and tied the event to an event handler. All of this is correct, and I can verify that the event handler runs via a breakpoint and the debugger.
I just can't figure out how to pass the selected index to the event handler! I assume you just add a parameter to the event, but I haven't the slightest clue how to reference the selectedIndex attribute of the messageChoice element from within the UIX page.
I've been searching for hours! Not sure what's wrong with me, but I can't find the solution.
A little help would be hugely appreciated =]
-Matt

Here are some examples that should help you. I have to go fix a high priority bug right now, so I can't mock up a choice example:
<lovChoice name="lovChoiceName" prompt="hello" tip="this is a tip"
                                        destination="lovChoice_DemoDlg.uix" selectedValue="${sessionScope.userDataForLovChoice.favoriteVacation.location}">
<contents   childData="${sessionScope.userDataForLovChoice.vacationSpots}">
<option text="${uix.current.location}" value="${uix.current.location}"/>
</contents>
<primaryClientAction>
<firePartialAction targets="selectedValueTextID selectedValueTextID2 selectedValueTextID3 lovChoiceID"
                                                         event="lovChoiceUpdate"/>
</primaryClientAction>
</lovChoice>and the event handler calls a java method:
    <event name="lovChoiceUpdate">
      <method class="oracle.cabo.servlet.demo.lovchoice.LovChoiceEvents"
              method="handleLovChoiceUpdateEvent"/>
    </event>and this method gets the parameter:
   * handleLovChoiceUpdateEvent
   * @param context the current baja context
   * @param Page the current page
   * @param event the event that got us here
   * @return The event result containing all the parameters
public static EventResult handleLovChoiceUpdateEvent(
    BajaContext bc,
    Page page,
    PageEvent event)
    HttpSession sess = bc.getServletRequest().getSession();
    UserData uData = _getUserData(sess);
    String selectedLocation = (String)event.getParameter("lovChoiceName");
    if (uData != null && selectedLocation != null)
      VacationSpot favVacation = uData.findVacationSpot(selectedLocation);
      uData.setFavoriteVacation(favVacation);
    return null;
} To do it simpler, you can do something like this:
In the following example the page property named "disclosed" is updated to the event source. Notice that data binding is supported.
<set target="${uix.pageProp}"
property="disclosed"
value="${param.source}" />
In the following example the session attribute identified by the event source is updated to the event name.
<set target="${sessionScope}"
property="${param.source}"
value="${param.event}" />
(I got this information from the UIX Element Reference).
Here's an example I found for hide/show:
             <hideShow id="hideShow-2" >
              <boundAttribute name="disclosed" >
               <comparison type="equals" >
                <defaulting>
                 <dataObject select="hideShow-2"
                             source="${uix.pageState}" />
                 <fixed text="hide" />
                </defaulting>
                <fixed text="show" />
               </comparison>
              </boundAttribute>
              <contents>
               <header text="Other Header">
                <contents>
                 <header text="Other SubHeader"/>
                </contents>
               </header>
              </contents>
             </hideShow>
    <event name="hide show">
      <set
             property="${param.source}" target="${uix.pageState}" value="${param.event}"/>
    </event>Jeanne

Error Message ORA-31043: Element 'person' not globally defined in schema

Hello All,
We have registered 2 xsd documents as follows..
DECLARE
   lc_test_xsd   CLOB;
BEGIN
   lc_test_xsd   := '<?xml version="1.0" encoding="UTF-8"?>
<schema
    xmlns="http://www.w3.org/2001/XMLSchema"
    xmlns:tns="http://www.xyz.com/cicat/types/basictypes/2/0"
    targetNamespace="http://www.xyz.com/cicat/types/basictypes/2/0"
    version="2.0">
    <simpleType name="LastNamePrefix">
        <annotation>
            <documentation>
                Additional word to last name (name prefix) corresponding to SAP HR Core
                Table T535N; V.
            </documentation>
        </annotation>
        <restriction base="tns:String255" />
    </simpleType>
    <simpleType name="CountryID">
        <annotation>
            <documentation>
                Codes for the representation of country names according to ISO 3166.
            </documentation>
        </annotation>
        <restriction base="string">
            <maxLength value="2" />
        </restriction>
    </simpleType>
    <simpleType name="LocationCode">
        <annotation>
            <documentation>
                Code of a location, e.g. Fe, Wa2 or Kor.
            </documentation>
        </annotation>
        <restriction base="string">
            <maxLength value="4" />
        </restriction>
    </simpleType>
    <simpleType name="GenderCode">
        <annotation>
            <documentation>
                Code of the gender: male, female, unknown. Unknown is used if the value is
                unknown or must not be stored due to legal restrictions.
            </documentation>
        </annotation>
        <restriction base="string">
            <enumeration value="male" />
            <enumeration value="female" />
            <enumeration value="unknown" />
        </restriction>
    </simpleType>
    <simpleType name="String255">
        <annotation>
            <documentation>
                String with 255 characters max
            </documentation>
        </annotation>
        <restriction base="string">
            <maxLength value="255" />
            <minLength value="1" />
        </restriction>
    </simpleType>
    <simpleType name="RB-CostCenter">
        <annotation>
            <documentation>
                Cost Center
            </documentation>
        </annotation>
        <restriction base="string">
            <minLength value="3" />
            <maxLength value="6" />
        </restriction>
    </simpleType>
    <simpleType name="OrgUnitName">
        <annotation>
            <documentation>
                Name of the Organizational Unit
            </documentation>
        </annotation>
        <restriction base="string">
            <minLength value="1" />
            <maxLength value="18" />
        </restriction>
    </simpleType>
    <complexType name="StringMCA">
        <annotation>
            <documentation>
                Multi Country String. Strings, which must be stored in ASCII code and
                country specific. The subelement ASCIIString contains the string encoded
                with ASCII. The subelement countrySpecificString allows country specific
                encoding.
            </documentation>
        </annotation>
        <sequence>
            <element name="asciiString" type="tns:String255" minOccurs="0" />
            <element name="countrySpecificString" type="tns:String255" />
        </sequence>
    </complexType>
    <simpleType name="OrgUnitID">
        <annotation>
            <documentation>
                ID of the Organizational Unit
            </documentation>
        </annotation>
        <restriction base="unsignedInt">
            <totalDigits value="8" />
        </restriction>
    </simpleType>
    <simpleType name="GlobalID">
        <annotation>
            <documentation>
                Global unique identifier of persons at xyz
            </documentation>
        </annotation>
        <restriction base="unsignedInt">
            <totalDigits value="8" />
        </restriction>
    </simpleType>
    <simpleType name="CiCatPersonID">
        <annotation>
            <documentation>
                CI-CAT Identifier of Persons (CiCat-PID). Unique identifier of a person
                in CI-CAT
            </documentation>
        </annotation>
        <restriction base="unsignedInt">
            <totalDigits value="20" />
        </restriction>
    </simpleType>
    <simpleType name="CiCatAccountID">
        <annotation>
            <documentation>
                CI-CAT Identifier of AD Accounts (CiCat-Ben-Sid). Unique identifier of
                AD Accounts in CI-CAT.
            </documentation>
        </annotation>
        <restriction base="unsignedInt">
            <totalDigits value="20" />
        </restriction>
    </simpleType>
    <simpleType name="PersonnelActionTypeCode">
        <annotation>
            <documentation>
                The operation that was performed on the person: entry, data change,
                re-entry (into company), exit (out of company)
            </documentation>
        </annotation>
        <restriction base="string">
            <enumeration value="entry" />
            <enumeration value="data change" />
            <enumeration value="re-entry" />
            <enumeration value="exit" />
        </restriction>
    </simpleType>
    <simpleType name="ContractStatus">
        <annotation>
            <documentation>
                Contract Status: active, inaktive, resigned, retired
            </documentation>
        </annotation>
        <restriction base="string">
            <enumeration value="retired">
                <annotation>
                    <documentation>
                        End of contract relationship because of retirement
                    </documentation>
                </annotation>
            </enumeration>
            <enumeration value="resigned">
                <annotation>
                    <documentation>
                        End of contract because of quitting
                    </documentation>
                </annotation>
            </enumeration>
            <enumeration value="inactive">
                <annotation>
                    <documentation>
                        Incactive contract relationship, e.g. motherhood, suspension
                    </documentation>
                </annotation>
            </enumeration>
            <enumeration value="active">
                <annotation>
                    <documentation>
                        Normal contract status
                    </documentation>
                </annotation>
            </enumeration>
            <enumeration value="deleted">
                <annotation>
                    <documentation>
                        Contract physically deleted in the source system
                    </documentation>
                </annotation>
            </enumeration>
        </restriction>
    </simpleType>
    <simpleType name="KnownAssociateCode">
        <annotation>
            <documentation>
                Describes status of person to xyz: internal/external/fixed-term
            </documentation>
        </annotation>
        <restriction base="string">
            <enumeration value="External" />
            <enumeration value="Internal" />
            <enumeration value="Fixed Term" />
            <enumeration value="unknown" />
        </restriction>
    </simpleType>
    <simpleType name="AssociateCode">
        <annotation>
            <documentation>
                Describes status of person to xyz: union of known values plus free string
                for not yet known types
            </documentation>
        </annotation>
        <union memberTypes="tns:KnownAssociateCode string" />
    </simpleType>
    <simpleType name="KnownExternalRelationType">
        <annotation>
            <documentation>
                Describes relation (contract relation) of external person to xyz:
                contractor/customer/supplier/subsidiary/selfregistered
            </documentation>
        </annotation>
        <restriction base="string">
            <enumeration value="Contractor" />
            <enumeration value="Customer" />
            <enumeration value="Supplier" />
            <enumeration value="Subsidiary" />
            <enumeration value="Selfregistered" />
            <enumeration value="unknown" />
        </restriction>
    </simpleType>
    <simpleType name="ExternalRelationType">
        <union memberTypes="tns:KnownExternalRelationType string" />
    </simpleType>
    <simpleType name="ValidityState">
        <annotation>
            <documentation>
                If an attribute was taken over by an authoritative source such as HR-MDS or
                WOM. Set to "Valid" to indicate that the value was taken over from the
                source and is therefore valid. Set to "Invalid" if the source indicates the
                value is no longer value, e.g. because it got deleted. Otherwise set to
                "Unknown", e.g. when the value was entered manually.
            </documentation>
        </annotation>
        <restriction base="string">
            <enumeration value="Valid" />
            <enumeration value="Invalid" />
            <enumeration value="Unknown" />
        </restriction>
    </simpleType>
    <complexType name="HrPersonnelId">
        <sequence>
            <element name="hrSourceSystem">
                <annotation>
                    <documentation>
                        Name of HR source system
                    </documentation>
                </annotation>
                <simpleType>
                    <restriction base="string">
                        <minLength value="1" />
                        <maxLength value="20" />
                    </restriction>
                </simpleType>
            </element>
            <element name="hrPersonnelId">
                <annotation>
                    <documentation>
                        ID of person in HR source system
                    </documentation>
                </annotation>
                <simpleType>
                    <restriction base="string">
                        <minLength value="1" />
                        <maxLength value="20" />
                    </restriction>
                </simpleType>
            </element>
        </sequence>
    </complexType>
    <complexType name="AccountType">
        <annotation>
            <documentation>
                Types of Accounts: Three main categories are known: Person, resource or
                service account. A person account represents a single natural person. A
                resource account represents a resource such as a printer, a computer or a
                meeting room. Service Accounts represent everything else. The can be used
                for example for technical users or group accounts. Both resource and service
                accounts have an owner that is responsible for them. Each account type has
                subtypes for further categorization.
            </documentation>
        </annotation>
        <choice>
            <element name="personAccount" type="tns:PersonAccountType" />
            <element name="resourceAccount" type="tns:ResourceAccountType" />
            <element name="serviceAccount" type="tns:ServiceAccountType" />
        </choice>
    </complexType>
    <simpleType name="KnownPersonAccountType">
        <annotation>
            <documentation>
                Pre-defined types of Person Accounts
            </documentation>
        </annotation>
        <restriction base="string">
            <enumeration value="Office" />
            <enumeration value="Admin" />
            <enumeration value="Test" />
            <enumeration value="unknown" />
        </restriction>
    </simpleType>
    <simpleType name="PersonAccountType">
        <union memberTypes="tns:KnownPersonAccountType string" />
    </simpleType>
    <simpleType name="KnownResourceAccountType">
        <annotation>
            <documentation>
                Pre-defined types of Resource Accounts
            </documentation>
        </annotation>
        <restriction base="string">
            <enumeration value="Room" />
            <enumeration value="PC" />
            <enumeration value="Printer" />
            <enumeration value="unknown" />
        </restriction>
    </simpleType>
    <simpleType name="ResourceAccountType">
        <union memberTypes="tns:KnownResourceAccountType string" />
    </simpleType>
    <simpleType name="KnownServiceAccountType">
        <annotation>
            <documentation>
                Pre-defined Types of Service Accounts
            </documentation>
        </annotation>
        <restriction base="string">
            <enumeration value="Group" />
            <enumeration value="Machine" />
            <enumeration value="Support" />
            <enumeration value="System" />
            <enumeration value="unknown" />
        </restriction>
    </simpleType>
    <simpleType name="ServiceAccountType">
        <union memberTypes="tns:KnownServiceAccountType string" />
    </simpleType>
    <simpleType name="ActionType">
        <annotation>
            <documentation>
                Defines the action that was performed on the object.
            </documentation>
        </annotation>
        <restriction base="string">
            <enumeration value="Create" />
            <enumeration value="Update" />
            <enumeration value="Delete" />
        </restriction>
    </simpleType>
    <simpleType name="LegalEntityId">
        <annotation>
            <documentation>
                ID of a legal entity
            </documentation>
        </annotation>
        <restriction base="unsignedInt">
            <totalDigits value="8" />
        </restriction>
    </simpleType>
</schema>
   DBMS_XMLSCHEMA.REGISTERSCHEMA (schemaurl   => 'BasicTypes.xsd',
                                  schemadoc   => lc_test_xsd);
DBMS_OUTPUT.PUT_LINE('BasicTypes.xsd registration successfully completed');
EXCEPTION WHEN OTHERS THEN
DBMS_OUTPUT.PUT_LINE('BasicTypes.xsd registration failed '||SQLERRM);
END;
/

2nd xsd..
-- register PersonTypes.xsd schema
DECLARE
lc_person_xsd   CLOB;
BEGIN
   lc_person_xsd
      := '<?xml version="1.0" encoding="UTF-8"?>


<schema
    xmlns="http://www.w3.org/2001/XMLSchema"
    xmlns:tns="http://www.xyz.com/cicat/types/persontypes/2/0"
    xmlns:basic="http://www.xyz.com/cicat/types/basictypes/2/0"
    targetNamespace="http://www.xyz.com/cicat/types/persontypes/2/0"
    version="2.0">
    <import namespace="http://www.xyz.com/cicat/types/basictypes/2/0" schemaLocation="BasicTypes.xsd"/>
    <complexType name="ADAccount">
        <annotation>
            <documentation>
                Active directory account of a person (also known as NT or Windows account)
            </documentation>
        </annotation>
        <sequence>
            <element name="cicatAccountId" type="basic:CiCatAccountID">
                <annotation>
                    <documentation>
                        CICAT internal ID of account (CI-CAT Ben SID)
                    </documentation>
                </annotation>
            </element>
            <element name="domain" type="basic:String255">
                <annotation>
                    <documentation>
                        NT domain of the userID, e.g. "de", "emea"
                    </documentation>
                </annotation>
            </element>
            <element name="userID" type="basic:String255">
                <annotation>
                    <documentation>
                        NT userID e.g. "xyz5mum" without domain (NT-SID)
                    </documentation>
                </annotation>
            </element>
            <element name="guid" type="basic:String255">
                <annotation>
                    <documentation>
                        Active Directory GUID of account.
                    </documentation>
                </annotation>
            </element>
            <element name="isMasterAccount" type="boolean"
                default="false" minOccurs="0">
                <annotation>
                    <documentation>
                        A person can have several accounts. One of them is marked as the
                        master account. The master account is the account which is mainly
                        used by the user.
                    </documentation>
                </annotation>
            </element>
            <element name="accountType" type="basic:AccountType">
                <annotation>
                    <documentation>
                        Types of Accounts: Three main categories are known: Person, resource
                        or service account. A person account represents a single natural
                        person. A resource account represents a resource such as a printer,
                        a computer or a meeting room. Service Accounts represent everything
                        else. The can be used for example for technical users or group
                        accounts. Both resource and service accounts have an owner that is
                        responsible for them. Each account type has subtypes for further
                        categorization.
                    </documentation>
                </annotation>
            </element>
        </sequence>
    </complexType>
    <complexType name="Person">
        <annotation>
            <documentation>
                All attributes a CI-CAT person record can contain
            </documentation>
        </annotation>
        <sequence>
            <element name="globalID" type="basic:GlobalID" minOccurs="0">
                <annotation>
                    <documentation>
                        Globally unique identifier of a person at xyz. This ID is defined
                        by HR MDS.
                    </documentation>
                </annotation>
            </element>
            <element name="cicatPID" type="basic:CiCatPersonID">
                <annotation>
                    <documentation>
                        Unique identifier of person in CI-CAT.
                    </documentation>
                </annotation>
            </element>
            <element name="hrPersonnelId" type="basic:HrPersonnelId" minOccurs="0">
                <annotation>
                    <documentation>
                        Personnel ID of person in an HR system. The personnel ID is unique
                        throughout one system. But different systems can use the same ID.
                    </documentation>
                </annotation>
            </element>
            <element name="title" type="basic:String255"
                minOccurs="0">
                <annotation>
                    <documentation>
                        Title of the person. In some countries and HR-MDS this field is used
                        for the academic title. In other countries it is used for the job
                        title.
                    </documentation>
                </annotation>
            </element>
            <element name="firstName" type="basic:StringMCA">
                <annotation>
                    <documentation>
                        First name of the person
                    </documentation>
                </annotation>
            </element>
            <element name="middleName" type="basic:StringMCA" minOccurs="0">
                <annotation>
                    <documentation>
                        Middle name(s) of the person
                    </documentation>
                </annotation>
            </element>
            <element name="lastNameAddOn" type="basic:String255"
                minOccurs="0">
                <annotation>
                    <documentation>
                        Additional word to surname (name prefix)
                        corresponding to SAP HR Core Table T535N; V.
                    </documentation>
                </annotation>
            </element>
            <element name="lastName" type="basic:StringMCA">
                <annotation>
                    <documentation>
                        Last names of the person.
                    </documentation>
                </annotation>
            </element>
            <element name="displayName" type="basic:String255" minOccurs="0">
                <annotation>
                    <documentation>
                        Display name of the person. This attribute is calculated from the
                        name, the department. In case of external users it also contains
                        an external flag and the name of the company. This field is
                        calculated by CI-CAT.
                    </documentation>
                </annotation>
            </element>
            <element name="gender" type="basic:GenderCode" minOccurs="0">
                <annotation>
                    <documentation>
                        Gender of the person
                    </documentation>
                </annotation>
            </element>
            <element name="orgUnitID" type="basic:OrgUnitID" minOccurs="0">
                <annotation>
                    <documentation>
                        ID of Organization unit (determined by C/AOO). This ID is taken over
                        from WOM.
                    </documentation>
                </annotation>
            </element>
            <element name="orgUnitIDValidity" type="basic:ValidityState" minOccurs="0">
                <annotation>
                    <documentation>
                        Defines if the attribute orgUnitID was validated by an authoritative
                        source. The default value is "Unknown".
                        VALID:
                        - orgUnitID is linked with WOM reference and orgUnitID is active in WOM
                        - orgUnitID is linked with Exception Organization list maintained in
                          CI-CAT by C/AOO. orgUnitID is active in with Exception Organization list
                        INVALID:
                        - orgUnitID is linked with WOM reference and orgUnitID is inactive in WOM
                        - orgUnitID is linked with Exception Organization list maintained in CI-CAT
                          by C/AOO. orgUnitID is inactive in with Exception Organization list
                        UNKNOWN:
                        - orgUnitID is not linked with WOM reference or Exception Organization
                          list. Active state of the department is not known.
                    </documentation>
                </annotation>
            </element>
            <element name="orgUnitName" type="basic:OrgUnitName">
                <annotation>
                    <documentation>
                        Unit Code (determined by C/AOO) of the organizational office, e.g.
                        Department, group, Project.
                    </documentation>
                </annotation>
            </element>
            <element name="costCenter" type="basic:RB-CostCenter">
                <annotation>
                    <documentation>
                        Cost center the person is assigned to.
                    </documentation>
                </annotation>
            </element>
            <element name="costCenterValidity" type="basic:ValidityState" minOccurs="0">
                <annotation>
                    <documentation>
                        Defines if the attribute costCenter was validated by an authoritative
                        source. The default value is "Unknown".
                    </documentation>
                </annotation>
            </element>
            <element name="email" type="basic:String255"
                minOccurs="0">
                <annotation>
                    <documentation>
                        Primary email of person
                    </documentation>
                </annotation>
            </element>
            <element name="legalEntity" type="basic:LegalEntityId" minOccurs="0">
                <annotation>
                    <documentation>
                        ID of a legalEntity. Legal Entity List will be
                        retrieved from CI-CAT.
                    </documentation>
                </annotation>
            </element>
            <element name="officeLocation" type="basic:LocationCode" minOccurs="0">
                <annotation>
                    <documentation>
                        The office location where the person is currently working,
                        e.g. Fe, Kor, Wa2. Maintained in CI-CAT.
                    </documentation>
                </annotation>
            </element>
            <element name="maintenanceLocation" type="basic:LocationCode" minOccurs="0">
                <annotation>
                    <documentation>
                        The location of the HR department which maintains the person, taken from HR-MDS.
                    </documentation>
                </annotation>
            </element>
            <element name="building" type="basic:String255" minOccurs="0">
                <annotation>
                    <documentation>
                        Building free-from data
                    </documentation>
                </annotation>
            </element>
            <element name="room" type="basic:String255" minOccurs="0">
                <annotation>
                    <documentation>
                        Room (Section, floor and room number)
                    </documentation>
                </annotation>
            </element>
            <element name="externalCompany" type="basic:String255" minOccurs="0">
                <annotation>
                    <documentation>
                        For Externals: Name of the external company.
                    </documentation>
                </annotation>
            </element>
            <element name="externalCompanyLocation" type="basic:LocationCode" minOccurs="0">
                <annotation>
                    <documentation>
                        For Externals: The location of the external company.
                    </documentation>
                </annotation>
            </element>
            <element name="personnelActionType" type="basic:PersonnelActionTypeCode" minOccurs="0">
                <annotation>
                    <documentation>
                        Defines the action type used in SAP HR systems,e.g. Hiring (entry);
                        Organizational reasignment; Transfer; Change in pay;
                        early retirement / retirement; leaving; Re-entry into company
                    </documentation>
                </annotation>
            </element>
            <element name="statusOfContract" type="basic:ContractStatus">
                <annotation>
                    <documentation>
                        Status of current occupation, e.g. active; inactive; resigned; retired
                    </documentation>
                </annotation>
            </element>
            <element name="xyzGroupAssociate" type="basic:AssociateCode">
                <annotation>
                    <documentation>
                        Indicates whether person is xyz Group associate or external
                        according to respective regulations : external; internal
                    </documentation>
                </annotation>
            </element>
            <element name="externalRelationToxyz" type="basic:ExternalRelationType"
                minOccurs="0" maxOccurs="unbounded">
                <annotation>
                    <documentation>
                        Describes for persons of type xyzGroupAssociate = external the
                        relationship to xyz, e.g. customer, subsidiary, ...
                        Persons can be in more than one relation to xyz.
                    </documentation>
                </annotation>
            </element>
            <element name="phone" type="basic:String255" minOccurs="0">
                <annotation>
                    <documentation>
                        Phone Number
                    </documentation>
                </annotation>
            </element>
            <element name="otherPhone" type="basic:String255" minOccurs="0">
                <annotation>
                    <documentation>
                        "Business 2/Other Telephone" ist ein multivalue field which can be
                        filled with additional phone numbers (canonical format).
                    </documentation>
                </annotation>
            </element>
            <element name="mobile" type="basic:String255" minOccurs="0">
                <annotation>
                    <documentation>
                        Mobile Phone Number
                    </documentation>
                </annotation>
            </element>
            <element name="paperFax" type="basic:String255" minOccurs="0" />
            <element name="electronicFax" type="basic:String255" minOccurs="0" />
            <element name="ipPhone" type="basic:String255" minOccurs="0">
                <annotation>
                    <documentation>IP Phone Number</documentation>
                </annotation>
            </element>
            <element name="lastModified" type="dateTime">
                <annotation>
                    <documentation>
                        last Time person was modified in CI-CAT
                    </documentation>
                </annotation>
            </element>
            <element name="lastModifyingUser" type="basic:String255">
                <annotation>
                    <documentation>
                        Last person, who modified person in CI-CAT. Can be a CI-CAT system
                        user, e.g. user to connect CI-CAT to WOM.
                    </documentation>
                </annotation>
            </element>
            <element name="assistant" type="basic:GlobalID" minOccurs="0">
                <annotation>
                    <documentation>
                        Assistant of person. Reference to assistant vie
                        globalId
                    </documentation>
                </annotation>
            </element>
            <element name="activeDirectoryAccount" type="tns:ADAccount"
                maxOccurs="unbounded" minOccurs="0">
                <annotation>
                    <documentation>
                        List of Active Directory accounts of the user.
                        To indicate that a user is deleted, the list of
                        AD accounts is empty.
                    </documentation>
                </annotation>
            </element>
        </sequence>
        <attribute name="action" type="basic:ActionType" use="required"/>
    </complexType>
    <element name="person" type="tns:Person"/>
</schema>
   DBMS_XMLSCHEMA.REGISTERSCHEMA (schemaurl   => 'PersonTypes.xsd',
                                  schemadoc   => lc_person_xsd);
DBMS_OUTPUT.PUT_LINE('PersonTypes.xsd registration successfully completed');
EXCEPTION WHEN OTHERS THEN
DBMS_OUTPUT.PUT_LINE('PersonTypes.xsd registration failed '||SQLERRM);
END;

JAXB generation and XSD choice serious issue

Helo,
Im developing a webservice that uses XSD Choice structure. Unfortunately, this must to done with choice because doesnt make sense using sequences this case.
Ill explain bug using this link:
http://bdoughan.blogspot.com/2011/04/xml-schema-to-java-xsd-choice.html#comment-form
this is exactly same problem as me, JAXB in jdeveloper are generating anotations wrong! I cant map the sequence choice to webservice, that is developed from WSDL...
So, I need some help there, I really need develop this webservice using xsd:choice and cant be done in jdeveloper and dont know why.
I tried put the anotations like this URL but when I call the service, choice element on request was null!
thanks

Hi, i dont know why but when I use JAXB to generate a sample XMl I got this output:
<guiaRequest xmlns="http://www.myservices.gov.br/mensagem/integracaobancaria/guia">
<parametrosConsultaGuia>
<guiaNormalRequest>
<codigoEntidade>B83C15C173633890E0330A67021B3890</codigoEntidade>
<codigoPorte>6</codigoPorte>
<codigoAssunto>148</codigoAssunto>
<numeroTransacaoInternet>267472003</numeroTransacaoInternet>
</guiaNormalRequest>
</parametrosConsultaGuia>
</guiaRequest>
This is correct to my webservice, BUT, when I invoque webservice with xsd:choice I got this request (i see that on enterprise manager) :
<message>
<properties>
<property name="tracking.compositeInstanceId" value="80367" />
<property name="tracking.ecid" value="0000J1pyNtnBDC^5lVg8yZ1DtZWJ002D4z" />
<property name="transport.http.remoteAddress" value="10.106.14.162" />
</properties>
<parts>
<part name="request" >
<ns2:guiaNormalRequest>
<ns2:codigoEntidade>B83C15C173633890E0330A67021B3890</ns2:codigoEntidade>
<ns2:codigoPorte>6</ns2:codigoPorte>
<ns2:codigoAssunto>148</ns2:codigoAssunto>
<ns2:numeroTransacaoInternet>267472003</ns2:numeroTransacaoInternet>
</ns2:guiaNormalRequest>
</part>
</parts>
</message>
This is wrong! see the structure is not correct.

Determine the selected element in a RadioButtonGroupByIndex UI Element??

I am using a RadioButtonGroupByIndex from which the user chooses one entry.
What I need to to know is the entry, the user has chosen, e.g.
element 1
-> element 2 //users choice
element 3
How can access the users choice in coding?
Thanks, Johannes

Hi Johannes Schnatz,
You need to bind the context element to the "text" property of the "RadioButtonGroupByIndex" .
Then after you need to write the code for know which is set to true which is not set to true by the loop or your own logic.
refer
[http://help.sap.com/erp2005_ehp_03/helpdata/EN/1d/99c941c04cc317e10000000a155106/frameset.htm|http://help.sap.com/erp2005_ehp_03/helpdata/EN/1d/99c941c04cc317e10000000a155106/frameset.htm]
points if useful
Thanks
Suresh

Trouble with choices

I'm interfaceing with a web service which has defined its schema with choices. I'm not able to alter the xsd.
I assigned all elements but still get stuck with the empty choice elements:
According to the xml schemas, the xml document is invalid. The reason is: Error::cvc-complex-type.2.4.d: Invalid content was found starting with element 'Subject_niet_natuurlijk'. No child element is expected at this point.
Error::cvc-complex-type.2.4.b: The content of element 'Subject_niet_natuurlijk' is not complete. One of '{"http://www.interaccess.nl/webplus/statuswfm_v2":Bin, "http://www.interaccess.nl/webplus/statuswfm_v2":Unieke_code}' is expected.
I found a solution form Clemens here:
http://clemensblog.blogspot.com/2006/03/bpel-miracle-of-xsdchoice-with-pre.html
And translate it like this in my own bpel code:
<assign name="Assign_WithWorkaround">
<copy>
<from expression="ora:parseEscapedXML('<Subject xmlns="http://xmlns.oracle.com/UsingChoices"><name xmlns="http://xmlns.oracle.com/UsingChoices"/></Subject>') "/>
<to variable="MaakZaak_zaakcreatie_InputVariable" part="payload"
query="/ns1:Zaak/ns1:Subject"/>
</copy>
<copy>
<from expression="number(bpws:getVariableData('VergunningAanvraag','payload','/client:VegunningAanvraag/client:Sofinummer'))"/>
<to variable="MaakZaak_zaakcreatie_InputVariable" part="payload"
query="/ns1:Zaak/ns1:Subject/ns1:Subject_natuurlijk/ns1:Bsn"/>
</copy>
<copy>
<from expression="1111111111"/>
<to variable="MaakZaak_zaakcreatie_InputVariable" part="payload"
query="/ns1:Zaak/ns1:Subject/ns1:Subject_natuurlijk/ns1:Anummer"/>
</copy>
</assign>
And now i get the following error:
<selectionFailure xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"><part name="summary"><summary>XPath query string returns zero node.
According to BPEL4WS spec 1.1 section 14.3, The assign activity <to> part query should not return zero node.
Please check the BPEL source at line number "102" and verify the <to> part xpath query.
</summary>
</part></selectionFailure>
Plz help me out.
By the way the version I'm using is Jdeveloper 10.1.3.3.0
Message was edited by:
Roelofk

Hi Roelof,
Since your interfacing with my webservice, I guess I should give you some pointers :-)
When using choices it is best to initialize the variable first with a literal XML-fragment without values like below (for each element or for the entire variable at once ):
<assign name="initZaak">
<copy>
<from>
<Zaak_verantwoordelijke_mdw xmlns="http://www.interaccess.nl/webplus/statuswfm_v2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Zaak_verw_mdw_id/>
<Zaak_verw_mdw_achternaam/>
<Zaak_verw_mdw_voorvoegsel xsi:nil="true"/>
<Zaak_verw_mdw_roepnaam/>
<Zaak_verw_mdw_voorletters/>
<Zaak_verw_mdw_oeh_id/>
<Zaak_verw_mdw_oeh_naam/>
</Zaak_verantwoordelijke_mdw>
</from>
<to variable="zaakcreatie_Input" part="payload" query="/ns2:Zaak/ns2:Zaak_verantwoordelijke_mdw"/>
</copy>
<copy>
<from>
<Zaak_initiator_mdw xmlns="http://www.interaccess.nl/webplus/statuswfm_v2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Zaak_initiator_mdw_id/>
<Zaak_initiator_mdw_achternaam/>
<Zaak_initiator_mdw_voorvoegsel xsi:nil="true"/>
<Zaak_initiator_mdw_roepnaam/>
<Zaak_initiator_mdw_voorletters/>
<Zaak_initiator_mdw_oeh_id/>
<Zaak_initiator_mdw_oeh_naam/>
</Zaak_initiator_mdw>
</from>
<to variable="zaakcreatie_Input" part="payload" query="/ns2:Zaak/ns2:Zaak_initiator_mdw"/>
</copy>
<copy>
<from>
<Subject xmlns="http://www.interaccess.nl/webplus/statuswfm_v2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Subject_natuurlijk>
<Bsn/>
<Anummer xsi:nil="true"/>
</Subject_natuurlijk>
</Subject>
</from>
<to variable="zaakcreatie_Input" part="payload" query="/ns2:Zaak/ns2:Subject"/>
</copy>
</assign>
After initializing you can for example assign the values as you normaly would
<assign name="maakZaak">
<copy>
<from expression="'123456789'"/>
<to variable="zaakcreatie_Input" part="payload" query="/ns2:Zaak/ns2:Subject/ns2:Subject_natuurlijk/ns2:Anummer"/>
</copy>
</assign>
You'll get something like this:
<Zaak xmlns="http://www.interaccess.nl/webplus/statuswfm_v2">
<Subject xmlns="http://www.interaccess.nl/webplus/statuswfm_v2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Subject_natuurlijk>
<Bsn/>
<Anummer>123456789</Anummer>
</Subject_natuurlijk>
</Subject>
<Zaak_verantwoordelijke_mdw xmlns="http://www.interaccess.nl/webplus/statuswfm_v2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Zaak_verw_mdw_id/>
<Zaak_verw_mdw_achternaam/>
<Zaak_verw_mdw_voorvoegsel xsi:nil="true"/>
<Zaak_verw_mdw_roepnaam/>
<Zaak_verw_mdw_voorletters/>
<Zaak_verw_mdw_oeh_id/>
<Zaak_verw_mdw_oeh_naam/>
</Zaak_verantwoordelijke_mdw>
<Zaak_verantwoordelijke_oeh/>
<Geen_zaak_verantwoordelijke/>
<Zaak_initiator_mdw xmlns="http://www.interaccess.nl/webplus/statuswfm_v2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Zaak_initiator_mdw_id/>
<Zaak_initiator_mdw_achternaam/>
<Zaak_initiator_mdw_voorvoegsel xsi:nil="true"/>
<Zaak_initiator_mdw_roepnaam/>
<Zaak_initiator_mdw_voorletters/>
<Zaak_initiator_mdw_oeh_id/>
<Zaak_initiator_mdw_oeh_naam/>
</Zaak_initiator_mdw>
<Zaak_initiator_oeh/>
<Geen_zaak_initiator/>
<Zaakidentificatie/>
<Startdatum/>
<Zaaktypecode/>
<Zaaktypeomschrijving/>
<Einddatum/>
<Einddatumgepland/>
<Url/>
<Hyperlinkomschrijving/>
<Zaakomschrijving/>
<Kenmerk/>
<Kenmerkbron/>
<Resultaatcode/>
<Resultaatomschrijving/>
<Resultaattoelichting/>
<Zaaktoelichting/>
<Trefwoord/>
<Uiterlijkeeinddatumafdoening/>
<Oge_id/>
</Zaak>
HTH
Mark
ps. you can also ask me directly, ask Harry for my email-adress

Need help in arranging choice group and textfield on screen

Hi friends
i want to display choice element (along with its text) and textfield(small one) in a single row.i want many such rows.
i tried my best to do that.but couldent get as what i wished ,textfields comes down.
Actually i want value inside textfield and name of the choice element when i click on any choice element,I did that functionality but only alignment is problem.
if anyone has tried or any idea about how to get this alignment please let me know.

you can achieve this fairly easily with group policy.
create an OU and put your remote desktop servers in that OU.
configure both user and computer policies in a group policy and link it to that ou.
you need to enable loopback mode - you may want it in merge or replace depending on your other policies you have. Probably replace though I would guess. this is set in the computer configuration > admin templates > system / group policy section.
now remove the policy you have currently setup for your users on the users OU containing the rdp users. If you want you can move these users back to your main users OU.
when your users login to the RDP server the settings in the user section of the GPO linked to the RDP Servers OU will apply.
when the user logs in to their own computer the policies from the user OU and computer OU will apply - but not the more restrictive RDP OU.
hope that makes sense.
Regards,
Denis Cooper
MCITP EA - MCT
Help keep the forums tidy, if this has helped please mark it as an answer
My Blog
LinkedIn:

JAXB: using choice to have a list

I'm going a bit crazy here trying to get JAXB to do what I want. I'm also going crazy trying to get this forum to display my posts, so I'm leaving out the code. The problem I'm having is when I want to have a list with more than one type of element in the list. I'm using a choice element in my schema with maxOccurs="unbounded". The problem is when I marshall the tags of the listed elements are missing. Their children show up, unfortunately now they are the children of the parent of the list! Unmarshalling works fine. Is this a problem with JAXB, or am I misusing the choice element?

anyone can extend a hand to give us a hint?

Shuttle - how can I insert data in database from second part of shuttle ?

I have read it: http://apex.oracle.com/pls/otn/f?p=35253:1:2820687553996558::NO but I don't understand shuttle.
My shuttle name is 'P3_SHUTTLE'. I have created shuttle by clicking (Create Item -> Shuttle -> next -> etc.). In first part of shuttle I have all elements from some table in database. In second part of shuttle I have choiced elements from first part of shuttle (as in each normal simply shuttle). I would like insert elements from second part of shuttle when somebody clicked button (which I have created). I have created process for this button type PL/SQL anonymous block. In field source of this process I have written:
DECLARE
BEGIN
FOR z in 1..htmldb_application.g_f02.count loop
INSERT INTO books(id_book) VALUES(htmldb_application.g_f02(z));
END LOOP;
END;
but it doesn't work (I don't know what is 'htmldb_application.g_f02.count' - it was in yours example).
So I have tried:
DECLARE
BEGIN
FOR z in 1..P3_SHUTTLE.pSQL_2.count loop
INSERT INTO books(id_book) VALUES(P3_AKTORZY.pSQL_2(z));
END LOOP;
END;
P3_SHUTTLE it is name of my shuttle
but this code also doesn't work :( HELP please :(
Edited by: user10728391 on 2008-12-19 01:17
Edited by: user10728391 on 2008-12-19 01:18

I have APEX 3.1.2.
I have tried:
DECLARE
l_selected HTMLDB_APPLICATION_GLOBAL.VC_ARR2;
BEGIN
l_selected := HTMLDB_UTIL.STRING_TO_TABLE(HTMLDB_APPLICATION.G_F02(1));
FOR I IN 1..l_selected.count
LOOP
INSERT INTO BOOKS (ID_BOOK) VALUES (l_selected(I));
END LOOP;
END;
It doesn't work. I have and error: 'No data found'. But you have written about name attribute. In view of code my page with shuttle I have that code about second part of shuttle:
<td class="shuttleSelect2">
<select multiple="multiple" name="p_v03" size="10" id="P3_SHUTTLE_RIGHT" ondblclick="g_Shuttlep_v03.remove()">
<option value="5">Aaa Aaa</option>
<option value="2">Bbb Bbb</option>
<option value="1">Eee Eee</option>
</select>
</td>
So I have tried in above code use: HTMLDB_APPLICATION.G_p_v03 and HTMLDB_APPLICATION.p_v03 but I have an error:
'G_P_V03' must be declared or 'P_V03' must be declared :(
Edited by: user10728391 on 2008-12-19 02:35

Error in xsd.file

Hi,
i imported xsd. file. But there is occuring an error while i activate. The error message is as followed:
Name of '/schema/complexType("GenericTimeStampType")/sequence/choice/element("XMLTimeStamp")' starts with 'xml'
Can you help me please
Thanks in advance
Nurhan

Hello,
You can check if the schema is supported by referring to this link
Enterprise Services Repository&Registry
Hope this helps,
Mark

Choice element

Similar Messages

Maybe you are looking for