Highlighted Fields are required Error (a different thread)

I'm working on a component with four pages, some of them custom, and lots of subpages. Getting this error, and of course I can't see any highlighted fields, so I assume the field in question is not visible or required but not in the component - the problem is figuring out which field. I ran a pcode trace and there's nothing in it that I can find that indicates where the problem is. In particular, I looked at the last SaveEdit before trace statements. Can someone suggest how I can use the trace to track down the offending field?
Mike

I had one of these a long time ago.
I found it by turning on the tracing for the panel processor. Of course you are going to ask which settings I used. It was a long time ago and I can't remember. From what I'm seeing in the config file on the app server, I would at least turn on the Dump buffers before save and Log extra debug messages. Not knowing which trace settings I used, I'd be tempted to turn off the obvious ones (Dump after modal panel, etcl) and keep the rest. Once you have the correct settings you'll eventually find an error message associated with a field in the trace file.
One other thought. Try your trace settings on a simple page and don't enter a value for a required field. Find the error for that field in the trace then perform the same routine for your component.
Sorry I couldn't be more help.
Paul

Similar Messages

Highlighted Fields are required Error

Hi,
I am currently working on Manage Applicants Page in TAM. When i try to change an applicant's disposition status and save, i am getting an "Highlighted Fields are required" error though i dont find any fields highlighted on the page.
Regards
Sudha

Nick,
the error message you receive when a required field is not present in the component buffer is silghtly different. It would be something like "*Field Required: <Record Name> - <Field Name> (124,64)*".
When you get an error like "*Highlighted fields are required. (15,30)*" I feel the required field is with in comp buffer. Sudha was receiving this error and thats the reason I thought field must be invisible.
Edited by: user9538086 on Apr 6, 2011 12:04 AM
Edited by: user9538086 on Apr 6, 2011 12:05 AM

LOV selection fails when there are validation errors on the base page

Hi
I have lovs and some other required fields on a page . If there are any validation error on one of those text fields and if I open the LOV (not related to the text fields) and tries to select
an item from the LOV search results, it doesn't do it until unless I go back to the base page and correct all the validation errors on the text fields eventhough those text fields have nothing to do with the LOV.
Any suggestion is appreciated.
Thanks
Anwar

I am on Anwar's team, and I've been dealing with the same problem, although on a different page.
The JSPX for a contrived example is below. I can provide backing bean code, if needed.
The form contains two LOVs. Both fields are required. If you leave both fields blank and click Continue, you get a red box around both fields and error messages are displayed. If you then click the magnifying glass to select from the first LOV, the LOV pop-up is rendered. However, you cannot make a selection, either by double-clicking a line item or by clicking OK (the OK button has no effect). All you can do is cancel.
Interestingly, the act of clicking the magnifying glass on the first LOV gets rid of the red box around that field. So, once you cancel out, the second LOV actually does work. If there were more than two fields on the page, that wouldn't happen. The problem seems to be that the LOV doesn't work unless there are no validation errors on the page other than for the LOV which is being invoked.
As you can see, immediate="true" is set on both LOVs. The behavior is the same whether this is true or not.
I'm left thinking there must be something obvious that we're missing... but none of us can see it.
Thanks,
KEN
<?xml version='1.0' encoding='windows-1252'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
          xmlns:f="http://java.sun.com/jsf/core"
          xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
<jsp:directive.page contentType="text/html;charset=windows-1252"/>
<f:view>
    <af:document title="Add Item">
      <af:form>
        <af:panelGroupLayout>
            <af:panelHeader text="Header">
                <af:panelFormLayout>
                    <af:inputListOfValues label="Id" searchDesc="Search" popupTitle="Supplier Id"
                                          simple="true" required="true" id="supplierId"
                                          model="#{viewScope.AddItemBackingBean.supplierIdListOfValuesModel}"
                                          value="#{viewScope.AddItemValuesBean.supplier.id}"
                                          autoSubmit="true" immediate="true"/>
                    <af:inputListOfValues label="Description" searchDesc="Search" popupTitle="Supplier Id"
                                          simple="true" required="true" id="supplierDescription"
                                          model="#{viewScope.AddItemBackingBean.supplierDescriptionListOfValuesModel}"
                                          value="#{viewScope.AddItemValuesBean.supplier.description}"
                                          autoSubmit="true" immediate="true"/>
                    <f:facet name="footer">
                        <af:panelGroupLayout layout="horizontal" halign="right" >
                          <af:commandButton text="Continue"
                                            actionListener="#{viewScope.AddItemBackingBean.continueAction}"
                                            id="continueButton" />
                        </af:panelGroupLayout>
                    </f:facet>
                </af:panelFormLayout>
            </af:panelHeader>
        </af:panelGroupLayout>
      </af:form>
    </af:document>
</f:view>
</jsp:root>

Highlight Fields as default for PDF Forms

Hello all,
I've recently designed a PDF form with some required fields, which get marked in red as soon as you open the form. However, some Acrobat Reader users have to click first on "highlight fields" in order to see the required fields. Is there a way to set "highlight fields" as a default for this form?
Cheers,
David

The suggested code didn't work for me with Adobe Reader 8.0. However, since I am a novice at this, I may not be adding the code correctly -- can you please tell me if this JavaScript client code for layout:ready is correct or not? I added the code in red. (I am using LiveCycle Designer ES Version 8.2.1.4029.1.523496). It seems to be in the right place because if I alter the code to unconditionally set app.runtimeHighlight to false, then when I open up the form with Reader 9.0, the highlighted fields are off.
form1.#pageSet[0].Page1.CurrentPage::ready:layout - (JavaScript, client)
this.rawValue
=xfa.layout.page(this);
// Turn on highlighted fields
if
(!app.runtimeHighlight){
app.runtimeHighlight
= true;}
form1.#pageSet[0].Page1.PageCount::ready:layout - (JavaScript, client)
this.rawValue
= xfa.layout.pageCount();
// Turn on highlighted fields
if
(!app.runtimeHighlight){
app.runtimeHighlight
= true;}

Sub:ztable fields are used by what are all transactions

Hi Experts,
I am having 2 table fields. These two fields are used in 2 different Ztables. Just i want to modify these two Zfields. But i want to tell our endusers, If i am making changes on these two fields means What are all the Transaction codes will affect? I can take what are all programs used by these 2 different fields through where-used-list option. But user dont need to know the program names know? They are familiar with only transaction codes.
So anyother option is there to find out the transaction codes?
Thanks,
Sankar M

hi
good
your query is bit confusing,if you r going to change anything in the zfields than there must be a requirement for that from your end user,apart from that if you r doing any changes than you must know what r the reports going to affect after that,than you need to change them accordingly,i dont think there is any table which ll give you idea that what r the tcoded going to affect after that,bcz its a table that would have been used in different reports in different scenarios,and you have to chage all those reports accordingly.
thanks
mrutyun^

Email submit button causing required error when all required fields are filled in

It looks like if I have more than 1 instance of subform added, my email submit button triggers "..at least one required " error message when all required fields are filled-in.
I toggle subforms between "visible" and "hidden (from layout)". Any suggestion is appreciated.
ralph

The fields that are hidden should have the validate.nullTest property set to "disabled", something like;
TextField1.validate.nullTest="disabled";

"iTunes can not run because some of the required fields are missing. Please reinstall iTunes." What the ****?!

"iTunes can not run because some of the required fields are missing. Please reinstall iTunes." What the ****? Please help me figure this out. I already removed quicktime (as another thread suggested). I can't get in!

i get same error.
I have uninstalled and reinstalled more times than i care to count. but still i get
itunes cannot run because some of its required files are missing.

Report Generation Toolkit producing error -2147417842, "The application called an interface that was marshalled for a different thread."

Hi everybody,
I've got an application that logs data to an Excel spreadsheet using the Report Generation Toolkit. My VI's have worked fine in the past using Excel XP, but since I've upgraded to Excel 2007, I am getting COM errors like this one:
"Error -2147417842 occurred at The application called an interface that was marshalled for a different thread. in Excel_Insert_Text.vi" That is the exact wording, even with the weird punctuation and capitalization.
The first occurrence of the error is not determinate. Sometimes, up to 10 logging sessions, involving a new .xls file, can occur before this error pops up. Once this error occurs, I must quit LabVIEW to resolve it. If I try to do anything with Excel, I always get this error, although sometimes it comes out of different source VIs. Excel_Open.vi is another.
These logging VIs have worked just fine until upgrading to Excel 2007. I checked, and I was using a really old version of the Report Generation Toolkit, v1.0.1. I read the documentation and had a big sigh of relief when I realized I needed to upgraded to v1.1.2 to get Excel 2007 support. However, even after upgrading, I'm still getting the same errors. I'm using LabVIEW 8.0.1, and I'm also building these VIs into an application. The error occurs both in the LabVIEW IDE and in the built application. Does anybody out there have any idea what I can do to fix this? I googled a little, and discovered this is a COM error, but I can't find any references to the Report Generation Toolkit specifically.
Thanks,
Phil
Solved!
Go to Solution.

Hi Christian,
I do not see that exact option listed, do you mean "user interface"? I recognize the "Run in UI Thread" option, it's on the Call Library Function Node.
I checked, and my top-level VI has "same as caller" set, and I believe all my VIs are set to "same as caller". Are you suggesting I change my top-level VI preferred execution environment to "user interface", or just the logging sub-VIs that use the Report Generation Toolkit?
Thanks,
Phil
Attachments:
VI_properties.png ‏15 KB

To download an App the 3 security questions are required. But at the end, apple is not able to complete the task and gives an error message. No more downloads are possible. What can I do?

to download an App the 3 security questions are required. But at the end, apple is not able to complete the task and gives an error message. No more downloads are possible. What can I do?

Very Important, how much Free Space is on your Hard Drive first of all? Click on the Macintosh HD on the Desktop, then do a Get Info on it.
Could be many things, we should start with this...
"Try Disk Utility
1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu at top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
*Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
3. Click the First Aid tab.
4. Select your Mac OS X volume.
5. Click Repair Disk, (not Repair Permissions). Disk Utility checks and repairs the disk."
http://docs.info.apple.com/article.html?artnum=106214
Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
(Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.)
If perchance you can't find your install Disc, at least try it from the Safe Boot part onward.
Do they launch OK while in Safe Mode?

Radio buttons (from Indesign) get larger and overlap when fields are highlighted in Acrobat X

I have created my first set of interactive forms using Indesign CS6 Buttons and Forms dialog box. As the formatting of the fields does not seem to carry over, I have left the text boxes as Indesign objects and added text fields over the top of them in Acrobat X. I also intended to add drop down menus in Acrobat instead because I didn't like how the Indesign list box behaved in Acrobat (having to click through each item rather than dropping down the entire list). There does not seem to be a way to add a drop down menu item from within Indesign. (Or if there is, can someone please point it out? :-) )
However I used the sample buttons supplied within Indesign to create radio buttons and check boxes (which automatically included the graphics for the different states). On my first test export to Acrobat it appeared that the buttons retained their formatting, but something rather strange is happening when the fields are highlighted, whereby the buttons enlarge and overlap each other. Very frustrating I must say! I have just about gone nuts trying to find a solution. I've tried several different button options from the sample set; I've created them from scratch within Indesign; I've attempted to resize the fields in Acrobat form editing mode, but this screws up the original buttons. I also have found that once selected in Acrobat, I cannot deselect them again. (Don't know if this is significant info but it may point to some kind of stacking problem??)
Anyway, to make it clearer here are some screen captures:
1. Form as it looks when opened in Acrobat X. The two different check box styles are from me experimenting in trying to fix this issue. But they all seem to behave the same way once highlighted.
2. Form when interactive fields are highlighted. The text fields are perfect but note the big ugly overlapping circles... :-(
And some further explanation of how I created the buttons and their issues:
I would very much appreciate some guidance on what I'm doing wrong here, as my poor little head is going to explode very shortly (and my client is getting pretty annoyed at the delay!!)
Thank you in advance :-)

I am having the exact same problem. I can't find a way around it. It seems that they included some states like normal, rollover, and click—but they didn't include a highlighted state. So when highlight fields is on it just shows the generic standard check box, which looks ridiculous if you have customized it at all in inDesign. I read a lot of people saying they can't find a way to change the highlight state—anyone out there have any answers?

Alert user when saving PDF if required fields are empty/null

Greetings,
I've read a fair number of threads on this topic. I am not trying to force the user to stay in a field or otherwise be annoyed. I would just like to alert the user when they save the PDF if there are required fields that have not been filled out. The alert message would simply be a polite reminder to complete the form before sending.
I'm using Acrobat XI Pro.
1) Is the Other Tasks/Set Document Actions/Document Will Save the correct place to use a script in this case?
2) Would the script need to check each required field by name? Or is there a way to reference all required fields in the document?
3) I've seen some examples like this:
f = getField(event.target.name)
if (f.value.length == 0)
    f.setFocus()
    app.alert("This field is required. Please enter a value.")
However it has some issues with respect to closing the alert dialog and so forth. Can anyone provide a sample script to get me started?
Thanks!

Exactly how you check a field for being empty depends on what type of field it is. For text fields, you should get the field's value as a string and compare it to an empty string, something like:
var val = getField("Text1").valueAsString;
if (val) {
    app.alert("Field is not empty");
If there is a default value that needs to be changed, you would compare to the default value:
var f = getField("Text1");
var val = f.valueAsString;
if (val !== f.defaultValue) {
    app.alert("Field value is OK");
For check boxes and radio buttons, you'd compare to the string "Off", which means none in the group is selected.
For dropdowns (combo boxes) and list boxes, there is normally one value selected, so you would have to get the value and check against the default value (or something else) to see if the field is properly filled in.
You could place the script there, but I usually use a separate button that I encourage the user to click in order to check the field. The problem with using the Will Save event is you can't prevent the save from happening.
The script can loop through all of the fields (and test all required ones), or you could set up an array of field names to check.

After upgrade to EMET v4.1 and reboot EMET_Agent didn't self-restarted but now double clicking its icon shows error "Admin privileges are required"

Hello all,
after on my Windows XP SP3 test client I upgraded to EMET v4.1 (from v4.0) and rebooted I noticed the following:
- EMET_Agent didn't self-restarted so I had to run it manually (and I noticed that after it started it also self-added an undocumented --NoRestart command line option),
- now that its icon is already in SysTray (Notification Area) the error "Admin privileges are required" appears whenever I double click on it or select 'Open EMET', so in case of need I can run EMET_GUI.exe only manually.
Is all this normal and expected or there can be any other possibly known way to avoid or definitely fix both effects ?
P.S. If to better show effects also providing any bitmap should be needed, then please just let me know.
Thanks in advance for any helpful reply or suggestion. Regards.
Rob

Hello everyone again,
I'm updating this post to ensure anyone interested may know how to definitely solve this issue.
After verifying that same annoying issue was also found with EMET 4.1 update 1 (valid for its 1st 4/30/2014 release, and verified also with
current and latest 5/29/2014 version) I recently made some little more investigation and after noticing its weird command line (reported by Process Explorer) simply as :
--NoRestart
I simply ensured to manually force same option to be properly set at startup, and that's it. :-D
So here you are quick updated versions of :
- EMET41NotificationFix.reg
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]
"EMET Agent"="\"C:\\Program Files\\EMET 4.1\\EMET_Agent.exe\" --NoRestart"
- EMET41upd1NotificationFix.reg
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]
"EMET 4.1 Update 1 Agent"="\"C:\\Program Files\\EMET 4.1\\EMET_Agent.exe\" --NoRestart"
I hope this helps (and if it does then please be kind and vote this post as useful... ;-) ) while to some forum moderator I'm asking to kindly mark this post as Answer.
P.S. It's just a pity that latest current version of EMET 4.1.1 (aka 4.1 update 1) cannot easily install over its 1st release (its setup suggest to 1st remove existing version), anyway I've found a tricky (hacked) way to overcome this limitation while also
avoiding reboot so in future I'll consider to share it publicly in a different discussion.
Regards
Rob

Adobe forms-checking that required fields are completed-Java Script

I have inserted two Java Scripts into my form--one for checking for required fields are completed, and then one for generating an email pulling a custom subject line, as shown below:
var emptyFields = [];
for (var i=0; i<this.numFields; i++) {
     var f= this.getField(this.getNthFieldName(i));
     if (f.type!="button" && f.required && f.display==display.visible) {
          if ((f.type=="text" && f.value=="") || (f.type=="checkbox" && f.value=="Off")) emptyFields.push(f.name);
if (emptyFields.length>0) {
     app.alert("Error! You must fill in the following fields:\n" + emptyFields.join("\n"));
this.mailDoc({bUI:false,cTo:"[email protected],[email protected],[email protected]",cSubject:"Bugzilla Form for: "+this.getField("Bugzilla Title").value+" - "+this.getField("Bugzilla ID").value})
Issue: After the error window displays fields that have not been completed, when I click OK the email window displays.
QUESTION: How can I stop the email window from displaying until all fields are completed?
THANKS!

Thank you so much for your quick response (and thank you for all the code that I am reusing!) I have another issue now.Can you see why the following is occurring....
I placed else in and now it edits the required fields, but once they are completed, will not initiate the email prompt. Here's what I have now
var emptyFields = [];
for (var i=0; i<this.numFields; i++) {
     var f= this.getField(this.getNthFieldName(i));
     if (f.type!="button" && f.required && f.display==display.visible) {
          if ((f.type=="text" && f.value=="") || (f.type=="checkbox" && f.value=="Off")) emptyFields.push(f.name);
if (emptyFields.length>0) {
     app.alert("Error! You must fill in the following fields:\n" + emptyFields.join("\n"));
elsethis.mailDoc({bUI:false,cTo:"[email protected],[email protected],[email protected]",cSubject:"Bugzilla Form for: "+this.getField("Bugzilla Title").value+" - "+this.getField("Bugzilla ID").value})

Double contacts as "iPhone"...my phone saves the same number twice, once with a 1 before the area code and one without it. It causes two different threads in my texts even of they're saved as the same contact

my phone saves the same number twice, once with a 1 before the area code and one without it. It causes two different threads in my texts even of they're saved as the same contact

My wife is having the same problems as a reciever. She works in a school as a teaching assistant and her teacher sends messages that are mixed with previous texts from ages ago.
Can anyone shed some light on this problem or is it only her and this poster?
2m42s

JDeveloper Error: White spaces are required between publicId and systemId.

I'm using JDeveloper 10.1.3.1.0.
This error is occurring in a BPEL process project.
With one particular web service I have, adding a Partner Link to the BPEL generates the following compile error:
Error: White spaces are required between publicId and systemId.
I can add Partner links from other web services and the BPEL will compile fine. The main difference I can see is that this web service supports WS-Addressing.
I have found one other reference to a similar (but not exactly the same) problem elsewhere in these forums but the fix is not really applicable. All of the wsdl files pass the "Validate WSDL" operation, and I don't see anything wrong with them.
When the error occurs and I select "Go To Source" it points back to the first line of the bpel file.
Can anyone help me out on this?
This is the wsdl for the web service, wsademo.wsdl:
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="wsademo"
targetNamespace="http://localhost:11001/wsademo.wsdl"
xmlns:tns="http://localhost:11001/wsademo.wsdl"
xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope"
xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:ns="http://localhost:11001/wsademo.wsdl"
xmlns:SOAP="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:MIME="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:DIME="http://schemas.xmlsoap.org/ws/2002/04/dime/wsdl/"
xmlns:WSDL="http://schemas.xmlsoap.org/wsdl/"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<types>
<schema targetNamespace="http://localhost:11001/wsademo.wsdl"
xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope"
xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:ns="http://localhost:11001/wsademo.wsdl"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="unqualified"
attributeFormDefault="unqualified">
<import namespace="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
<import namespace="http://www.w3.org/2003/05/soap-encoding"/>

<element name="wsademoResult">
<complexType>
<sequence>
<element name="out" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true"/>
</sequence>
</complexType>
</element>

<element name="wsademo">
<complexType>
<sequence>
<element name="in" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true"/>
</sequence>
</complexType>
</element>

<element name="wsademoResult">
<complexType>
<sequence>
<element name="out" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true"/>
</sequence>
</complexType>
</element>
</schema>
</types>
<message name="wsademoResult">
<part name="parameters" element="ns:wsademoResult"/>
</message>
<message name="wsademo">
<part name="parameters" element="ns:wsademo"/>
</message>
<message name="wsademoResult">
<part name="parameters" element="ns:wsademoResult"/>
</message>
<message name="wsademoHeader">
<part name="MessageID" element="wsa:MessageID"/>
<part name="RelatesTo" element="wsa:RelatesTo"/>
<part name="From" element="wsa:From"/>
<part name="ReplyTo" element="wsa:ReplyTo"/>
<part name="FaultTo" element="wsa:FaultTo"/>
<part name="To" element="wsa:To"/>
<part name="Action" element="wsa:Action"/>
</message>
<portType name="wsademoPort">
<operation name="wsademoResult">
<documentation>accepts a string value from a relayed response</documentation>
<input message="tns:wsademoResult"/>
</operation>
<operation name="wsademo">
<documentation>echos a string value and relays the response to the wsa replyTo address (if present)</documentation>
<input message="tns:wsademo"/>
<output message="tns:wsademoResult"/>
</operation>
</portType>
<binding name="wsademo" type="tns:wsademoPort">
<SOAP:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="wsademoResult">
<SOAP:operation soapAction="urn:wsademo/wsademoPort/wsademoResult"/>
<input>
<SOAP:body parts="parameters" use="literal"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="Action"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="To"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="FaultTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="ReplyTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="From"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="RelatesTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="MessageID"/>
</input>
</operation>
<operation name="wsademo">
<SOAP:operation soapAction="urn:wsademo/wsademoPort/wsademo"/>
<input>
<SOAP:body parts="parameters" use="literal"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="Action"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="To"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="FaultTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="ReplyTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="From"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="RelatesTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="MessageID"/>
</input>
<output>
<SOAP:body parts="parameters" use="literal"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="Action"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="To"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="FaultTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="ReplyTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="From"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="RelatesTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="MessageID"/>
</output>
</operation>
</binding>
<service name="wsademo">
<documentation>demonstrates WS-Addressing capabilities</documentation>
<port name="wsademo" binding="tns:wsademo">
<SOAP:address location="http://localhost:11001"/>
</port>
</service>
</definitions>
This is the wsdl that is generated by JDeveloper that contains the PartnerLinks and refernce back to the original wsdl file, wsademoRef.wsdl:
<definitions
name="wsademo"
targetNamespace="http://localhost:11001/wsademo.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://localhost:11001/wsademo.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://localhost:11001/wsademo.wsdl" location="wsademo.wsdl"/>
<plnk:partnerLinkType name="wsademoPort_PL">
<plnk:role name="wsademoPort_Role">
<plnk:portType name="tns:wsademoPort"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>
And finally the is the BPEL, WSAtest3.bpel:
<?xml version="1.0" encoding="UTF-8"?>

<process name="WsaTest3" targetNamespace="http://xmlns.oracle.com/WsaTest3"
xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:ns1="http://localhost:11001/wsademo.wsdl"
xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:ns2="http://localhost:80/Service.wsdl"
xmlns:client="http://xmlns.oracle.com/WsaTest3"
xmlns:bpelx="http://schemas.oracle.com/bpel/extension/"
xmlns:ora="http://schemas.oracle.com/xpath/extension"
xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc">

<partnerLinks>

<partnerLink name="client" partnerLinkType="client:WsaTest3"
myRole="WsaTest3Provider"/>
<partnerLink name="wsademo" partnerLinkType="ns1:wsademoPort_PL"
myRole="wsademoPort_Role" partnerRole="wsademoPort_Role"/>
</partnerLinks>

<variables>

<variable name="inputVariable" messageType="client:WsaTest3RequestMessage"/>

<variable name="outputVariable"
messageType="client:WsaTest3ResponseMessage"/>
<variable name="Invoke_1_wsademo_InputVariable" messageType="ns1:wsademo"/>
<variable name="Invoke_1_wsademo_OutputVariable"
messageType="ns1:wsademoResult"/>
</variables>

<sequence name="main">

<receive name="receiveInput" partnerLink="client" portType="client:WsaTest3"
operation="process" variable="inputVariable" createInstance="yes"/>

<assign name="Assign_1">
<copy>
<from variable="inputVariable" part="payload"
query="/client:WsaTest3ProcessRequest/client:input"/>
<to variable="Invoke_1_wsademo_InputVariable" part="parameters"/>
</copy>
</assign>
<invoke name="Invoke_1" partnerLink="wsademo" portType="ns1:wsademoPort"
operation="wsademo" inputVariable="Invoke_1_wsademo_InputVariable"
outputVariable="Invoke_1_wsademo_OutputVariable"/>
<assign name="Assign_2">
<copy>
<from variable="Invoke_1_wsademo_OutputVariable" part="parameters"/>
<to variable="outputVariable" part="payload"
query="/client:WsaTest3ProcessResponse/client:result"/>
</copy>
</assign>
<reply name="replyOutput" partnerLink="client" portType="client:WsaTest3"
operation="process" variable="outputVariable"/>
</sequence>
</process>
-Wayne Stielau
Open Text Corporation
Irvine, CA

I have discovered two issues.
1. JDeveloper does not seem to like the SOAP 1.2 envelope and encoding namespaces. Is this a known limitation? Changed them to 1.1.
2. JDeveloper does not like the double definition of wsaDemoResult.
When these two items are changed, the bpel compiles clean. Now I've got to get the message header to populate correctly. There are no values assigned, only namespace definitions. This is the SOAP packet that is received at the web service.
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Header>
<MessageID xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
<From xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
<RelatesTo xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
<Action xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
<ReplyTo xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
<To xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
<FaultTo xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
</env:Header>
<env:Body>
<wsademo xmlns="http://localhost:11001/wsademo.wsdl">
<in xmlns="">hello</in>
</wsademo>
</env:Body>
</env:Envelope>

Highlighted Fields are required Error (a different thread)

Similar Messages

Maybe you are looking for