How we can skip project level schema validation in BPEL

How we can skip project level schema validation in BPEL................... Because i have a requirement to send email with attachment. to send attachment i have to skip schema validation from EM console. so it will skip schema validation for all deployed application.it creates problem for other project so i want to do that thing at project level ....

Hi
It can be done by going opening the composite.xml in jdeveloper and than opening the properties window of the composite.There you will see a property Validate schema.Set that to no to overwrite the property set at the sever level.
The following property gets added in the composite.xml
<property name="validateSchema" type="xs:boolean" many="false">false</property>
Redeploy the composite and check.
Hope this helps!!!

Similar Messages

How i can deal with DB schema in SQL developer ?

Hi
Thank you for reading my post , how i can make sql developer just to show one schema ?
Thanks

What the Natalka wanted to say is so that the
hardwired user does not visualize none another user
when clicar in the option 'Other Users'.
For this, you must clicar with the right button of
mouse on the option 'Other Users', 'Apply Filter' and
to move for the panel of the left all the users who
you do not want that they are visualized.
It is not this what you want? If possible, detail
more its request.
Remembering that each user in the Oracle is
corresponding to one schema.by the way, how can I create tables in sql developer if I don't see the one I have already created thanks

How I can open projects of imovie recovered with data rescue?

Hi, I recovered my imovie projects but when I am going to open them , imovie say that it can`t open them . How I can recovered my films of iMovie.? Thanks .
Message was edited by: Dalanina

Nevermind, the Thorough Search option in Data Rescue found the files I thought were gone for good .

How does XML DB handle XML Schema Validation ?

In order to validate an XML document against an XML Schema using Oracle XML DB the XML Schema must first be registered with XML DB using the method registerSchema provided by the package DBMS_XMLSCHEMA.
XDB provides two types of schema validation, 'Lax' Validation and 'Strict' Validation.
'Lax' validation takes place whenever a schema based document is converted from it's textual representation into the XML DB internal object model. Errors caught by this validation will be prefixed with 'ORA'.
'Stict' validation takes place when the XMLType methods schemaValidate() or isSchemaValid() are invoked.
The schemaValidate() method throws an exception with an error message indicating what is wrong it encounteres an invalid document. The error message associated with the exception will be prefixed with LSX.
The isSchemaValid() method returns true or false, depending on whether or not the document is valid. It cannot return any information about why the document is invalid.
The reason for having both the Lax and Strict validation models is that Strict validation is much more expensive in terms of CPU and memory usage than Lax validation.

Here are some examples of what is caught by Lax validation (ORA errors) and what is only caught by Strict validation (LSX errors).
SQL> begin
2     dbms_xmlschema.registerSchema('test',xmltype(
3 '<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.co
eFormDefault="unqualified">
4     <xs:complexType name="RootType">
5             <xs:sequence>
6                     <xs:element name="Mandatory"/>
7                     <xs:element name="Enumeration">
8                             <xs:simpleType>
9                                     <xs:restriction base="xs:string">
10                                             <xs:enumeration value="A"/>
11                                             <xs:enumeration value="B"/>
12                                             <xs:enumeration value="C"/>
13                                     </xs:restriction>
14                             </xs:simpleType>
15                     </xs:element>
16                     <xs:element name="MinLength">
17                             <xs:simpleType>
18                                     <xs:restriction base="xs:string">
19                                             <xs:minLength value="4"/>
20                                             <xs:maxLength value="20"/>
21                                     </xs:restriction>
22                             </xs:simpleType>
23                     </xs:element>
24                     <xs:element name="MaxLength">
25                             <xs:simpleType>
26                                     <xs:restriction base="xs:string">
27                                             <xs:minLength value="1"/>
28                                             <xs:maxLength value="4"/>
29                                     </xs:restriction>
30                             </xs:simpleType>
31                     </xs:element>
32                     <xs:element name="MaxOccurs" type="xs:string" maxOccurs="2"/>
33                     <xs:element name="MinOccurs" minOccurs="2" maxOccurs="2"/>
34                     <xs:element name="Optional" type="xs:string" minOccurs="0"/>
35             </xs:sequence>
36     </xs:complexType>
37     <xs:element name="Root" type="RootType" xdb:defaultTable="ROOT_TABLE"/>
38 </xs:schema>'));
39 end;
40 /
PL/SQL procedure successfully completed.
SQL> --
SQL> -- Valid Document
SQL> --
SQL> insert into ROOT_TABLE values (xmltype(
2 '<Root>
3     <Mandatory>Hello World</Mandatory>
4     <Enumeration>A</Enumeration>
5     <MinLength>ABCD</MinLength>
6     <MaxLength>WXYZ</MaxLength>
7     <MaxOccurs>1</MaxOccurs>
8     <MaxOccurs>2</MaxOccurs>
9     <MinOccurs>1</MinOccurs>
10     <MinOccurs>2</MinOccurs>
11     <Optional>Goodbye</Optional>
12 </Root>'
13 ))
14 /
1 row created.
SQL> --
SQL> -- Undefined element 'Illegal'
SQL> --
SQL> insert into ROOT_TABLE values (xmltype(
2 '<Root>
3     <Mandatory>Hello World</Mandatory>
4     <Illegal>Hello World</Illegal>
5     <Enumeration>A</Enumeration>
6     <MinLength>ABCD</MinLength>
7     <MaxLength>WXYZ</MaxLength>
8     <MaxOccurs>1</MaxOccurs>
9     <MaxOccurs>2</MaxOccurs>
10     <MinOccurs>1</MinOccurs>
11     <MinOccurs>2</MinOccurs>
12     <Optional>Goodbye</Optional>
13 </Root>'
14 ))
15 /
insert into ROOT_TABLE values (xmltype(
ERROR at line 1:
ORA-30937: No schema definition for 'Illegal' (namespace '##local') in parent
'/Root'
SQL> --
SQL> -- Multiple occurences of 'Optional'
SQL> --
SQL> insert into ROOT_TABLE values (xmltype(
2 '<Root>
3     <Mandatory>Hello World</Mandatory>
4     <Enumeration>A</Enumeration>
5     <MinLength>ABCD</MinLength>
6     <MaxLength>WXYZ</MaxLength>
7     <MaxOccurs>1</MaxOccurs>
8     <MaxOccurs>2</MaxOccurs>
9     <MinOccurs>1</MinOccurs>
10     <MinOccurs>2</MinOccurs>
11     <Optional>Goodbye</Optional>
12     <Optional>Goodbye</Optional>
13 </Root>'
14 ))
15 /
insert into ROOT_TABLE values (xmltype(
ERROR at line 1:
ORA-30936: Maximum number (1) of 'Optional' XML node elements exceeded
SQL> --
SQL> -- Missing element 'Manadatory'
SQL> --
SQL> insert into ROOT_TABLE values (xmltype(
2 '<Root>
3     <Enumeration>A</Enumeration>
4     <MinLength>ABCD</MinLength>
5     <MaxLength>WXYZ</MaxLength>
6     <MaxOccurs>1</MaxOccurs>
7     <MaxOccurs>2</MaxOccurs>
8     <MinOccurs>1</MinOccurs>
9     <MinOccurs>2</MinOccurs>
10     <Optional>Goodbye</Optional>
11 </Root>'
12 ))
13 /
1 row created.
SQL> --
SQL> -- Invalid Enumeration Value
SQL> --
SQL> insert into ROOT_TABLE values (xmltype(
2 '<Root>
3     <Mandatory>Hello World</Mandatory>
4     <Enumeration>Z</Enumeration>
5     <MinLength>ABCD</MinLength>
6     <MaxLength>WXYZ</MaxLength>
7     <MaxOccurs>1</MaxOccurs>
8     <MaxOccurs>2</MaxOccurs>
9     <MinOccurs>1</MinOccurs>
10     <MinOccurs>2</MinOccurs>
11     <Optional>Goodbye</Optional>
12 </Root>'
13 ))
14 /
insert into ROOT_TABLE values (xmltype(
ERROR at line 1:
ORA-31038: Invalid enumeration value: "Z"
SQL> --
SQL> -- MinLength Violation
SQL> --
SQL> insert into ROOT_TABLE values (xmltype(
2 '<Root>
3     <Mandatory>Hello World</Mandatory>
4     <Enumeration>A</Enumeration>
5     <MinLength>ABC</MinLength>
6     <MaxLength>WXYZ</MaxLength>
7     <MaxOccurs>1</MaxOccurs>
8     <MaxOccurs>2</MaxOccurs>
9     <MinOccurs>1</MinOccurs>
10     <MinOccurs>2</MinOccurs>
11     <Optional>Goodbye</Optional>
12 </Root>'
13 ))
14 --
15 -- MaxLength Violation
16 --
17 /
1 row created.
SQL> insert into ROOT_TABLE values (xmltype(
2 '<Root>
3     <Mandatory>Hello World</Mandatory>
4     <Enumeration>A</Enumeration>
5     <MinLength>ABCD</MinLength>
6     <MaxLength>VWXYZ</MaxLength>
7     <MaxOccurs>1</MaxOccurs>
8     <MaxOccurs>2</MaxOccurs>
9     <MinOccurs>1</MinOccurs>
10     <MinOccurs>2</MinOccurs>
11     <Optional>Goodbye</Optional>
12 </Root>'
13 ))
14 /
insert into ROOT_TABLE values (xmltype(
ERROR at line 1:
ORA-30951: Element or attribute at Xpath /Root/MaxLength exceeds maximum length
SQL> --
SQL> -- Missing element Optional - Valid Document
SQL> --
SQL> insert into ROOT_TABLE values (xmltype(
2 '<Root>
3     <Mandatory>Hello World</Mandatory>
4     <Enumeration>A</Enumeration>
5     <MinLength>ABCD</MinLength>
6     <MaxLength>WXYZ</MaxLength>
7     <MaxOccurs>1</MaxOccurs>
8     <MaxOccurs>2</MaxOccurs>
9     <MinOccurs>1</MinOccurs>
10     <MinOccurs>2</MinOccurs>
11 </Root>'
12 ))
13 /
1 row created.
SQL> --
SQL> -- Too many instances of 'MaxOccurs'
SQL> --
SQL> insert into ROOT_TABLE values (xmltype(
2 '<Root>
3     <Mandatory>Hello World</Mandatory>
4     <Enumeration>A</Enumeration>
5     <MinLength>ABCD</MinLength>
6     <MaxLength>WXYZ</MaxLength>
7     <MaxOccurs>1</MaxOccurs>
8     <MaxOccurs>2</MaxOccurs>
9     <MaxOccurs>3</MaxOccurs>
10     <MinOccurs>1</MinOccurs>
11     <MinOccurs>2</MinOccurs>
12     <Optional>Goodbye</Optional>
13 </Root>'
14 ))
15 /
insert into ROOT_TABLE values (xmltype(
ERROR at line 1:
ORA-30936: Maximum number (2) of 'MaxOccurs' XML node elements exceeded
SQL> --
SQL> -- Too few instances of 'MinOccurs'
SQL> --
SQL> insert into ROOT_TABLE values (xmltype(
2 '<Root>
3     <Mandatory>Hello World</Mandatory>
4     <Enumeration>A</Enumeration>
5     <MinLength>ABCD</MinLength>
6     <MaxLength>WXYZ</MaxLength>
7     <MaxOccurs>1</MaxOccurs>
8     <MaxOccurs>2</MaxOccurs>
9     <MinOccurs>1</MinOccurs>
10     <Optional>Goodbye</Optional>
11 </Root>'
12 ))
13 /
1 row created.
SQL> create trigger validateSchema
2 before insert on ROOT_TABLE
3 for each row
4 begin
5     :new.object_value.schemaValidate();
6 end;
7 /
Trigger created.
SQL> --
SQL> -- Valid Document
SQL> --
SQL> insert into ROOT_TABLE values (xmltype(
2 '<Root>
3     <Mandatory>Hello World</Mandatory>
4     <Enumeration>A</Enumeration>
5     <MinLength>ABCD</MinLength>
6     <MaxLength>WXYZ</MaxLength>
7     <MaxOccurs>1</MaxOccurs>
8     <MaxOccurs>2</MaxOccurs>
9     <MinOccurs>1</MinOccurs>
10     <MinOccurs>2</MinOccurs>
11     <Optional>Goodbye</Optional>
12 </Root>'
13 ))
14 /
1 row created.
SQL> --
SQL> -- Undefined element 'Illegal'
SQL> --
SQL> insert into ROOT_TABLE values (xmltype(
2 '<Root>
3     <Mandatory>Hello World</Mandatory>
4     <Illegal>Hello World</Illegal>
5     <Enumeration>A</Enumeration>
6     <MinLength>ABCD</MinLength>
7     <MaxLength>WXYZ</MaxLength>
8     <MaxOccurs>1</MaxOccurs>
9     <MaxOccurs>2</MaxOccurs>
10     <MinOccurs>1</MinOccurs>
11     <MinOccurs>2</MinOccurs>
12     <Optional>Goodbye</Optional>
13 </Root>'
14 ))
15 /
insert into ROOT_TABLE values (xmltype(
ERROR at line 1:
ORA-30937: No schema definition for 'Illegal' (namespace '##local') in parent
'/Root'
SQL> --
SQL> -- Multiple occurences of 'Optional'
SQL> --
SQL> insert into ROOT_TABLE values (xmltype(
2 '<Root>
3     <Mandatory>Hello World</Mandatory>
4     <Enumeration>A</Enumeration>
5     <MinLength>ABCD</MinLength>
6     <MaxLength>WXYZ</MaxLength>
7     <MaxOccurs>1</MaxOccurs>
8     <MaxOccurs>2</MaxOccurs>
9     <MinOccurs>1</MinOccurs>
10     <MinOccurs>2</MinOccurs>
11     <Optional>Goodbye</Optional>
12     <Optional>Goodbye</Optional>
13 </Root>'
14 ))
15 /
insert into ROOT_TABLE values (xmltype(
ERROR at line 1:
ORA-30936: Maximum number (1) of 'Optional' XML node elements exceeded
SQL> --
SQL> -- Missing element 'Manadatory'
SQL> --
SQL> insert into ROOT_TABLE values (xmltype(
2 '<Root>
3     <Enumeration>A</Enumeration>
4     <MinLength>ABCD</MinLength>
5     <MaxLength>WXYZ</MaxLength>
6     <MaxOccurs>1</MaxOccurs>
7     <MaxOccurs>2</MaxOccurs>
8     <MinOccurs>1</MinOccurs>
9     <MinOccurs>2</MinOccurs>
10     <Optional>Goodbye</Optional>
11 </Root>'
12 ))
13 /
insert into ROOT_TABLE values (xmltype(
ERROR at line 1:
ORA-31154: invalid XML document
ORA-19202: Error occurred in XML processing
LSX-00213: only 0 occurrences of particle "Mandatory", minimum is 1
ORA-06512: at "SYS.XMLTYPE", line 345
ORA-06512: at "XDBTEST.VALIDATESCHEMA", line 2
ORA-04088: error during execution of trigger 'XDBTEST.VALIDATESCHEMA'
SQL> --
SQL> -- Invalid Enumeration Value
SQL> --
SQL> insert into ROOT_TABLE values (xmltype(
2 '<Root>
3     <Mandatory>Hello World</Mandatory>
4     <Enumeration>Z</Enumeration>
5     <MinLength>ABCD</MinLength>
6     <MaxLength>WXYZ</MaxLength>
7     <MaxOccurs>1</MaxOccurs>
8     <MaxOccurs>2</MaxOccurs>
9     <MinOccurs>1</MinOccurs>
10     <MinOccurs>2</MinOccurs>
11     <Optional>Goodbye</Optional>
12 </Root>'
13 ))
14 /
insert into ROOT_TABLE values (xmltype(
ERROR at line 1:
ORA-31038: Invalid enumeration value: "Z"
SQL> --
SQL> -- MinLength Violation
SQL> --
SQL> insert into ROOT_TABLE values (xmltype(
2 '<Root>
3     <Mandatory>Hello World</Mandatory>
4     <Enumeration>A</Enumeration>
5     <MinLength>ABC</MinLength>
6     <MaxLength>WXYZ</MaxLength>
7     <MaxOccurs>1</MaxOccurs>
8     <MaxOccurs>2</MaxOccurs>
9     <MinOccurs>1</MinOccurs>
10     <MinOccurs>2</MinOccurs>
11     <Optional>Goodbye</Optional>
12 </Root>'
13 ))
14 --
15 -- MaxLength Violation
16 --
17 /
insert into ROOT_TABLE values (xmltype(
ERROR at line 1:
ORA-31154: invalid XML document
ORA-19202: Error occurred in XML processing
LSX-00221: "ABC" is too short (minimum length is 4)
ORA-06512: at "SYS.XMLTYPE", line 345
ORA-06512: at "XDBTEST.VALIDATESCHEMA", line 2
ORA-04088: error during execution of trigger 'XDBTEST.VALIDATESCHEMA'
SQL> insert into ROOT_TABLE values (xmltype(
2 '<Root>
3     <Mandatory>Hello World</Mandatory>
4     <Enumeration>A</Enumeration>
5     <MinLength>ABCD</MinLength>
6     <MaxLength>VWXYZ</MaxLength>
7     <MaxOccurs>1</MaxOccurs>
8     <MaxOccurs>2</MaxOccurs>
9     <MinOccurs>1</MinOccurs>
10     <MinOccurs>2</MinOccurs>
11     <Optional>Goodbye</Optional>
12 </Root>'
13 ))
14 /
insert into ROOT_TABLE values (xmltype(
ERROR at line 1:
ORA-30951: Element or attribute at Xpath /Root/MaxLength exceeds maximum length
SQL> --
SQL> -- Missing element Optional - Valid Document
SQL> --
SQL> insert into ROOT_TABLE values (xmltype(
2 '<Root>
3     <Mandatory>Hello World</Mandatory>
4     <Enumeration>A</Enumeration>
5     <MinLength>ABCD</MinLength>
6     <MaxLength>WXYZ</MaxLength>
7     <MaxOccurs>1</MaxOccurs>
8     <MaxOccurs>2</MaxOccurs>
9     <MinOccurs>1</MinOccurs>
10     <MinOccurs>2</MinOccurs>
11 </Root>'
12 ))
13 /
1 row created.
SQL> --
SQL> -- Too many instances of 'MaxOccurs'
SQL> --
SQL> insert into ROOT_TABLE values (xmltype(
2 '<Root>
3     <Mandatory>Hello World</Mandatory>
4     <Enumeration>A</Enumeration>
5     <MinLength>ABCD</MinLength>
6     <MaxLength>WXYZ</MaxLength>
7     <MaxOccurs>1</MaxOccurs>
8     <MaxOccurs>2</MaxOccurs>
9     <MaxOccurs>3</MaxOccurs>
10     <MinOccurs>1</MinOccurs>
11     <MinOccurs>2</MinOccurs>
12     <Optional>Goodbye</Optional>
13 </Root>'
14 ))
15 /
insert into ROOT_TABLE values (xmltype(
ERROR at line 1:
ORA-30936: Maximum number (2) of 'MaxOccurs' XML node elements exceeded
SQL> --
SQL> -- Too few instances of 'MinOccurs'
SQL> --
SQL> insert into ROOT_TABLE values (xmltype(
2 '<Root>
3     <Mandatory>Hello World</Mandatory>
4     <Enumeration>A</Enumeration>
5     <MinLength>ABCD</MinLength>
6     <MaxLength>WXYZ</MaxLength>
7     <MaxOccurs>1</MaxOccurs>
8     <MaxOccurs>2</MaxOccurs>
9     <MinOccurs>1</MinOccurs>
10     <Optional>Goodbye</Optional>
11 </Root>'
12 ))
13 /
insert into ROOT_TABLE values (xmltype(
ERROR at line 1:
ORA-31154: invalid XML document
ORA-19202: Error occurred in XML processing
LSX-00213: only 1 occurrences of particle "MinOccurs", minimum is 2
ORA-06512: at "SYS.XMLTYPE", line 345
ORA-06512: at "XDBTEST.VALIDATESCHEMA", line 2
ORA-04088: error during execution of trigger 'XDBTEST.VALIDATESCHEMA'
SQL>

Switching ON validate xml(Schema Validation) in BPEL Console for AIAtesting

While we were testing Oracle O2B pip, we have recently switched on schema validation by turning it on to 'Strict' so that we can Validate
XML in BPEL Console. Earlier when we were testing we had turned the schema validation as 'None' on BPEL console, and hence everything was working fine and
no errors we popping out while creating sales order in Siebel CRM. But the moment we put validate xml to ' Strict' it starts throwing validation errors.
So can you please help us to know whether it is right to test the Oracle O2B pip by putting validate xml to 'Strict'? If it is fair to test it by switching
ON Validate XML(putting validate xml to 'Strict') then we are getting below error.
We are creating a new sales order in Siebel CRM and when we check in BPEL console it was faulted at UpdateSalesOrderSiebelCommsProvABCSImpl (v. 1.0) .When we checked the BPEL flow it is throwing error at InvokeUpdateUpsert.
Error is According to the xml schemas, the xml document is invalid. The reason is: Error::cvc-complex-type.2.4.a: Invalid content was found starting with element 'xsdLocal1:Process_spcInstance_spcId'. One of '{"http://siebel.com/asi":Process_spcInstance_spcId}' is expected.
Steps for Switching on Validation ?
1)     Login to BPEL Console
2)     Go To Configuration section
3)     Schema Validation changes
a.     ON: populate validateXML with value strict
b.     OFF: populate validateXML with value none
Really appreciate if you can help..

hi
Indeed, the "Validate XML" menu option only shows "Validate XML: 0 errors, 0 warnings.".
But, if you look at the "Design" tab for your schema, the "invoices" element node contains an "xsd:invoice" sequence shown in red. If you change "xsd:invoice" to "invoice" this becomes white and the node can be expanded.
One other thing, registering an XML Schema in JDeveloper like the one you posted, isn't possible without an "oracle.xml.parser.schema.XSDException" (without further details).
regards
Jan Vervecken

How long can a project be?

I have a 54 min iMovie project. It is starting to crash each time I try to make new edits. Could the crashing be due to the length? What can I do to keep it from closing mid-edit? Please help.

Apple made iDVD go away.
IDVD remains very popular in the Macintosh community.
You can purchase iLife 11 (includes iDVD) on disk.
IDVD is a wonderful piece of software and well worth the low cost of $40.
http://www.amazon.com/Apple-MC623Z-A-iLife-VERSION/dp/B003XKRZES/ref=sr_1_1?ie=U
http://dealmac.com/lw/artclick.html?1,527850,1872219
Yes, there are programs that will put a movie on a DVD. I have tried most of the other substitutes including Toast, Burn, DVD Creator, Wondershare, and others. None of them come anywhere near the ease-of-use and power of iDVD. IDVD is specifically designed to work with iMovie.
With iDVD you can easily and quickly create DVDs with menus and graphics almost on the level of what Hollywood can do.

OLS Label Security: how users can view own level/compartment/group choices?

I have an application using OLS (Oracle Label Security) Virtual Database (VDB) for security; to allow users to only view rows to which they have access.
I'm creating a list of values (LOV) to allow the user to change the level or compartment of a database record to a different value for which they still have access. The views that show these values is DBA_SA_USER_LEVELS (and COMPARTMENTS, GROUPS) but this view is only visible to DBA users, not the regular user. We are considering giving regular users access to this view, or granting SELECT_ALL_TABLES as suggested in an article I read. However, this approach seems to loosen security, not maintain it.
How can I allow a user to get a list of levels, compartments or groups available to them without loosening the security on the DBA_* views?
thanks,
Scott

Bump

Schema Validation Inside BPEL after receive

Hi,
Is there a way i could validate the an XML against a schema inside BPEL.
here is what i want to do, take the input data as a string which is suppose to be an XML and want to validate against different schemas based on some parameters.
thanks,
-Ng.

I created a partner link PartnerLink_1. A wsdl was generated, PartnerLink_1.wsdl:
<definitions
name="DateValidator"
targetNamespace="http://commesse/dates/DateValidator.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://commesse/dates/DateValidator.wsdl"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>
<import namespace="http://commesse/dates/DateValidator.wsdl" location="http://portaldev.zigroup.net:8810/manageDates/DateValidator?WSDL"/>
<plnk:partnerLinkType name="DateValidatorPortType_PL">
<plnk:role name="DateValidatorPortType_Role">
<plnk:portType name="tns:DateValidatorPortType"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>
Is it correct how I changed it?
<definitions
name="DateValidator"
targetNamespace="http://commesse/dates/DateValidator.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://commesse/dates/DateValidator.wsdl"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>
<import namespace="http://commesse/dates/DateValidator.wsdl" location="http://portaldev.zigroup.net:8810/manageDates/DateValidator?WSDL"/>
>>>
<types>
<schema attributeFormDefault="qualified"
elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/diapason"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:tns="http://commesse/dates/DateValidator.wsdl">
<element name="commessaDates">
<complexType>
<sequence>
<element name="fromDate" type="date" />
<element name="toDate" type= "date" />
</sequence>
</complexType>
</element>
</schema>
</types>
<<<
<plnk:partnerLinkType name="DateValidatorPortType_PL">
<plnk:role name="DateValidatorPortType_Role">
<plnk:portType name="tns:DateValidatorPortType"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>

Skip entity level validation programatically - special case

Hi
using jdev 11.1.1.3
Can anyone suggest me a solution as to how I can skip validation programatically.
I have both entity level and deffered entitylevel txn validations on this entity.
I use the VO to populate the data and I modify the date field, and I want to skip validation for this particular usecase as it is against the validation rule(special case)
thanks

Hi,
Check
http://jobinesh.blogspot.com/2009/08/how-to-skip-validation.html
http://andrejusb.blogspot.com/2012/10/transaction-level-adf-bc-entity.html

How i can force sql developer to show just tables of HR schema ?

In sql developer we can filter the tables that it shows under table node ,
how i can force it just to show tables of HR schema ?
Thanks

See my post in your other thread (How i can deal with DB schema in SQL developer ?
In this case, you let only the HR user in the right panel.

Help On schema validation

Hi,
I am a newbie in XML schema territory.
I generates a xml using 'SELECT XMLQuery( ...)' -- This finally works after upgrading to 10.2.0.3!
1) What methods do you recommend to validate the query result agaist the schema? The query result is first returned as 'XMLType' type, and then
I turned it into a CLOB.
At the end, I save the output into a file (via CLOB to String).
2) How do I register the schema in DB? Can I install the schema on the file system, instead? I am not sure which way is simpler and easier. I'd yearn for any simpler method, if any --- a common complaint from any beginner, I guess.
A few pointers will help me a great deal.
Sun

Sun,
You can take a look at an FAQ thread on this topic: How does XML DB handle XML Schema Validation ?
Regards,
Geoff

Project level variables in OSB

Is there any way we can declare project level variables or global variables that are visible to all the projects in OSB?? If yes,the how can they b used??

OSB is stateless and can not remember variables outside a running process instance.
However you can have a solution similar to global/project level variables if they are static.
What you can do is create an XSL or XQuery with your variables defined as elements in the XML and inside Proxy service if you need to refer to these variables just call that XQuery/XSLT for that element.
A use case where this scenario can be used is for defining log levels. You can have a config XQ for each project and define the value of log level element for each project in that XQuery. Inside a Proxy service just call this XQ and fetch the LogLevel and log accordingly. This is also useful in migrating between dev/test/production environments. You can have different values of LogLevel in the XQ in different environments so that you dont need to change the code in proxy service when you move from one environment to other and also you dont need to change in each and every proxy if you need to change the level of logging.

Converting Cost Budget From Plan level Type to Project Level

Hi There ,
I am Working on Project Accounting in Oracle apps .Perviously we used to create projects using oracle forms now we have created the OA pages for the same and using them to create the projects .
Thus Cost budget done by using forms will be at project level and Cost Budget done through OA pages is at PLAN TYPE .
And my problem is , I want to convert PLAN TYPE cost budget to PROJECT LEVEL cost budget. Do any body know how to do it , I know that we can convert project level to plan type by running one request , is there any such request to solve my problem.
Please help me
Thanks

Zafar,
What exactly ur looking for, can u explain in oaf terms, as this is a oaf forum.
--Mukul

How to add XML attribute to an Element using BPEL assign

I have a request xml to a bpel process that does not contain a attribute.
After some process I need to create this missing attribute and set a value.
I tried using the XML fragment in the Assign Activity. But how can I create a attribute?
This XML node to which I am trying to create an attribute is a very huge node with lot of dynamic typing(xsi:type). I can just re-create the complete xml with required nodes.
Does any one know how I can create a xml attribute using the BPEL assign? I do not want to use the Java code in my process.
Thanks.

I'm bit confused about what exact problem you are facing with attributes.
You can check accessing XML attributes in BPEL Assign @ http://download.oracle.com/docs/cd/E12483_01/integrate.1013/b28981/manipdoc.htm#BABIHDHI from the page http://download.oracle.com/docs/cd/E12483_01/integrate.1013/b28981/manipdoc.htm.
I suppose your source input has no attributes and destination has to be an xml with attribute of type xsi:type. You can use the assign activity as mentioned in above document to assign your type structure to type attribute.

How to enable schema validation on Oc4j webservice

I have ejb3 webservice with a separate wsdl file. I would like to enable the schema validation, Someone knows, how can I do that?
I found this, but it´s not so much clear for me:
http://download.oracle.com/docs/cd/B25221_04/web.1013/b25603/wsprovider.htm
Tks

Hi,
This is true for all attributes, not just Display Name. As long as an attribute has a non null value, you will not be able to change the regular expression of that attribute at the schema level.
I don't know if nullifying display attribute for all user objects (assuming you are talking about binding between Display Name and a Person/User object) is an option. If so, its worth considering.
If that is not an option, then assuming your data entry is coming from the FIM Portal and not any other external system like a custom portal, then you are ONLY left with regular expression validation at the RCDC level.
Thanks,
Jameel Syed |
Identity & Security Strategist | [email protected] |
Simplified Identity and Access Management

How we can skip project level schema validation in BPEL

Similar Messages

Maybe you are looking for