Missing element attributes

I have tried to merge two element lists and then process the
result with XSLT.
The problem is that processXSL() never returns. While playing
with my xsl stylesheet it seems that the attributes aren't
visible. (There are some older posts who says the same.)
My workaround is to write the merged data into a string and read
it again.
null

Sebastian Tusk (guest) wrote:
: I have tried to merge two element lists and then process the
: result with XSLT.
: The problem is that processXSL() never returns. While playing
: with my xsl stylesheet it seems that the attributes aren't
: visible. (There are some older posts who says the same.)
: My workaround is to write the merged data into a string and
read
: it again.
Please post a Java code sample, any XML and XSL files that you
may have been using to reproduce this problem. You can attach
files.
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
null

Similar Messages

How to capture element/attribute

We have an export client that converts the Frame file to xml. We are using "LightTitle" element at various places, this element also has an attribute called "LightColor".
When I look at the output xml, I can see all LightTitle elements, but only some of them (2 out of 10) have the LightColor attribute!
How can we capture the attribute associated with a specific element and output it to the final xml?
Thanks.

If your LightColor attributes do not contain ant content - then they will not be written out - you can change the rules to add a 'dummy' if you need them in the XML - OR -(and probably easier) post process your XML and add the missing elements/attribute pairs based on rules in your XSLT or program...
have fun.
David
[signature link removed]

Editable report - Element Attributes

Apex 4.1
The Element Attributes field under Column Attributes is not consistent in whether it expands #COL# substitutions.
1. Based on empirical observations, they are expanded for Select lists but not for the new Simple Checkbox type. I don't think any other editable display type works but I haven't tried all of them.
So if we need a simple checkbox in a report, it leads to awkward constructs like this in a custom report template
       <input type="checkbox" name="f49" class="edit"
              x:attr="foobar"
              x:pk="#PK#"
              value="Y"
              #CHECKED# />and a query like
decode(col,'Y','checked="checked"') checked
...It would be so much easier/declarative if the Element Attributes were to consistently expand #COL# substitutions so we could just put any CSS class and/or custom HTML attributes and use values from the current row.
2. Speaking of Simple Checkbox, it sometimes causes APEX to crash with the following Apache error
/wwv_flow.accept HTTP-404 \nwwv_flow.accept: SIGNATURE (parameter names) MISMATCH\nVARIABLES IN FORM NOT IN PROCEDURE: F03_NOSUBMIT\nNON-DEFAULT VARIABLES IN PROCEDURE NOT IN FORM: I am not able to consistently reproduce this but it is definitely a problem.
Also, it is not very obvious whether the List of Values attribute applies to the Simple Checkbox display type or not. It would appear that it uses a static LOV defined by STATIC2:;Y can someone from Oracle confirm this?
Thanks

Bump. Comments? Am I missing something? Thanks

Column value substitution in tabular form element attributes

We started to discuss this at Re: Tabular form with Ajax
I also mentioned this at Re: how to make only some rows editable in html db.
but thought that this deserves its own thread.
In Doug's sample Sudoku application in that thread, he uses #COLUMN# substitution in the Form Element Attributes and it works fine, but in my example page at http://htmldb.oracle.com/pls/otn/f?p=24317:219 I used the same technique and no matter what I do, the #COLUMN# substitution is not expanded by the Apex engine.
This is driving me nuts, any ideas why it works in one application but not in another?
Thanks

Hm, you might be right.
I copied your row template and modified it at http://htmldb.oracle.com/pls/otn/f?p=24317:219
The styling looks terrible, not sure why, the template is simply
<tr>
<td class="t10data">#EMPNO_DISPLAY#</td>
<td class="t10data">#ENAME#</td>
<td class="t10data">#JOB#</td>
<td class="t10data">#MGR#</td>
<td class="t10data">#HIREDATE#</td>
<td class="t10data">#SAL#</td>
<td class="t10data">#COMM#</td>
<td class="t10data">#DEPTNO#</td>
</tr>I had a lot of trouble getting this to work because the wizard generated tabular form appends 2 hidden fields containing the PK and the row-checksum to the last (editable?) field on each row. If the last editable field has #COL# substitution, it expands the substitution and forgets to close the INPUT tag thus causing malformed HTML (I think this is a bug in the rendering engine).
The readonly condition is sal>1000 which now works. The SAL>1000 fields are now readonly.
But now the update process is broken. If I enter a number in the first blank SAL field (empno=3641) and click Submit, I get no errors but the change is not saved. Wonder why.
Hopefully, Scott (Spadafore) will take mercy on our amateurish experiments and give us some definitive answers soon!
Thanks.

Pop-up LOV, add Element Attributes?

Hello again,
I have a pop-up LOV (named LOV) on a column in the detail section of a master-detail form (imagine the "Employee Num" being a pop-up LOV in the image linked below[1]). This field also allows normal user entry just like any input field (this is, input is not disabled).
However, while viewing the source HTML this field just an ordinary input field, I cannot seem to add an element attribute via the usual means. Just for arguments sake I want an alert box on each keypress, usually I would just add the line: onkeypress="javascript: alert('hello');" in the Element Attributes under the "Column Attributes" section. This is not working for me, however.
How would I go about calling a JavaScript function (on a keypress, say) using this pop-up LOV input method?
Thank you for you time.
I am using APEX version: 4.0.2.00.09
[1] http://imageupload.co.uk/viewer.php?file=yu7i83h5dpk5cy0npsy0.png
Edited by: 986065 on Feb 14, 2013 1:51 PM

Hello Bob,
Sure you can enter a button on the template, but the problem is how to find out which page to call when the Add button is pressed.
You can write your own LOV page(s) and attach those to a field (i.e. by adding a clickable image in the post element text) and then you can have all the control you want.
Greetings,
Roel
http://roelhartman.blogspot.com/
http://www.bloggingaboutoracle.org/
http://www.logica.com/

Caused by: oracle.xml.parser.v2.XMLParseException: '=' missing in attribute

This is a Bursting problem under EBS 5.6.3. In production we have 5.6.2 and since our development system to 5.6.3 has been upgraded, the following error occurs on every single Burst being done using the Concurrent Manager only:
Caused by: oracle.xml.parser.v2.XMLParseException: '=' missing in attribute.
     at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:205)
     at oracle.xml.parser.v2.NonValidatingParser.parseAttrValue(NonValidatingParser.java:1502)
     at oracle.xml.parser.v2.NonValidatingParser.parseAttr(NonValidatingParser.java:1408)
     at oracle.xml.parser.v2.NonValidatingParser.parseAttributes(NonValidatingParser.java:1350)
     at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1180)
     at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:301)
     at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:268)
     at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:201)
     at oracle.apps.xdo.batch.BurstingProcessorEngine.burstingConfigParser(BurstingProcessorEngine.java:1340)
     at oracle.apps.xdo.batch.BurstingProcessorEngine.process(BurstingProcessorEngine.java:1297)
     at oracle.apps.xdo.batch.DocumentProcessor.process(DocumentProcessor.java:213)
     at xxwel.ebs.xmlp.XXWELBurster.processDocuments(XXWELBurster.java:143)
I can run the same file through 5.6.3 ($JAVA_TOP) libraries mounted on my JDev with no problems. Also the same XML file runs fine on Production under 5.6.2 - no problems. I have also checked the XML file using a syntax checker. I know this is not a syntax issue even though it looks like it.
Could someone point me in the right direction - explain what this means. Getting desperate as 5.6.3 will be going into production soon and all Bursting will fail with this error. I can't get the simplest XML File to Burst - NOTE this is only occurring on the EBS system (even running without the CM ie. a standalone java main it fails). I think this has something to do with the XML parser version and the EBS environment.
Please help...

Hi Tim, good thinking - wouldn't have thought to check this file. Anyway can confirm that the problem is happening with multiple burst control files so I haven't checked the files themselves as the problem seems systemic. anyway here is an example.
<?xml version="1.0" encoding="UTF-8"?>
<xapi:requestset xmlns:xapi="http://xmlns.oracle.com/oxp/xapi">
<xapi:request select="/XXWEL_BIP_UNI_INVOICES/LIST_G_CUSTOMER_NUMBER/G_CUSTOMER_NUMBER">
<xapi:delivery>
<xapi:email server="mailwa01" port="25"
from="${ADMIN_EMAIL}" reply-to ="${ADMIN_EMAIL}">
<xapi:message id="111" to="${ADMIN_EMAIL}" attachment="true" subject="Unigas Inv
oice No: ${TRX_NUMBER}">
</xapi:message>
</xapi:email>
</xapi:delivery>
<xapi:document output-type="pdf" delivery="111">
<xapi:template type="rtf" location="/u02/prod/prodappl/wel/11.5.0/interface/bip/templates/uni_invoice_template.rtf">
</xapi:template>
</xapi:document>
</xapi:request>
</xapi:requestset>
I will start stripping the control files to make sure they are not the problem in the meantime.

I recently moved all my logic audio sessions to a back up hard disk. Also updated to Loin OSX. My Stylus RMX is not working. I get a message Missing Element on Part 1...Currently not installed on their computer or has been moved to a different folder. An

I recently moved all my logic audio sessions to a back up hard disk. Also updated to Loin OSX. My Stylus RMX is not working. I get a message Missing Element on Part 1...Currently not installed on their computer or has been moved to a different folder. Any help out there?

Hi
Sounds like you may have moved the RMX library folder?
Is RMX fully updated (for Lion)?
Check your hard drives for a file called SAGE:
It (or an alias of it) is normally found in the <USER>:Library:Application Support:Spectrasonics.
Note that on Lion, the <User> Library is 'hidden'... quickest way to get there is to hold down Option (Alt) whilst using the Finder:Go menu
CCT

Default insertion for missing elements using DBMS_XMLSave.insertXML

Hi,
I am trying to insert default values for some columns, without having those column names as elements in the xml document. Is it possible to do so?? This is the code I am using for now, but it inserts null values for missing elements in the xml document.
insCtx := DBMS_XMLSave.newContext ('TABLENAME'); -- get the context
rows := DBMS_XMLSave.insertXML (insCtx, p_xmlDoc); -- insert the doc
DBMS_XMLSave.closeContext (insCtx); -- close the handle

Only thing I noticed with dbms_xmlstore.insertXML, was when my xml document had "<?xml version = "1.0" ?>" at the start, it gave an error "LPX-00209: PI names starting with XML are reserved"That's probably due to the XML document not starting exactly with "<", like this :
SQL> DECLARE
2
3    xmldoc   clob := '
4 <?xml version="1.0"?>
5        <ROWSET>
6       <ROW>
7        <COL1>1</COL1>
8        <COL2>TEST1</COL2>
9       </ROW>
10       <ROW>
11       <COL1>2</COL1>
12      </ROW>
13     </ROWSET>';
14
15    ctx      dbms_xmlstore.ctxHandle;
16    numrows number;
17
18 BEGIN
19
20    ctx := dbms_xmlstore.newContext('MY_TABLE');
21    numrows := dbms_xmlstore.insertXML(ctx, xmldoc);
22    dbms_xmlstore.closeContext(ctx);
23
24 END;
25 /
DECLARE
ERROR at line 1:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00209: PI names starting with XML are reserved
ORA-06512: at "SYS.DBMS_XMLSTORE", line 78
ORA-06512: at line 21 However, it runs OK if the prolog actually starts the character stream :
SQL> DECLARE
2
3    xmldoc   clob := '<?xml version="1.0"?>
4        <ROWSET>
5       <ROW>
6        <COL1>1</COL1>
7        <COL2>TEST1</COL2>
8       </ROW>
9       <ROW>
10       <COL1>2</COL1>
11      </ROW>
12     </ROWSET>';
13
14    ctx      dbms_xmlstore.ctxHandle;
15    numrows number;
16
17 BEGIN
18
19    ctx := dbms_xmlstore.newContext('MY_TABLE');
20    numrows := dbms_xmlstore.insertXML(ctx, xmldoc);
21    dbms_xmlstore.closeContext(ctx);
22
23 END;
24 /
PL/SQL procedure successfully completed.
With the dbms_xmlsave.inserXML, [...] it wont insert the default column values.Now that's strange...
I understand there could be differences in the parsing implementation, but in the end both processes must issue an INSERT into the target table using plain SQL, so I really wonder why default values are not applied.
I'll try to reproduce when I have access to a Java-enabled db.

Missing Message Attributes: URL/HTTP Destination

Hello,
following scenario:
There is a sync. interface between SAP PI ante the Paypal API within the HTTP adapter calling a dynamic URL.
The dynamic URL is created as mentioned in this blog: http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/7264. [original link is broken]
Also the HTTP adapter is configured as described (Adapter Specific Message Attributes and URL are flagged).
Following error occours when testing the call:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_MISSING_URL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Dynamic Header - Missing Message Attributes: URL/HTTP Destination</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Is there sth. special I have to consider in the HTTP Adapter?
Thanks in advance,
André

Hi Michal,
I´m passing the URL to the attribut "TargetURL" by using a UDF in my mapping.
In the adapter I have flagged "URL".
So the value of TargetURL set in mapping shoul be used as destination in the adapter.
Please have a look onto my UDF used in MM:
http://img408.imageshack.us/i/udf.jpg/
Adapter settings:
http://img691.imageshack.us/i/adaptersetting1.jpg/
http://img339.imageshack.us/i/adaptersetting2.jpg/
How can I check that the TargetURL is successfully set as a dynamic parameter?
Thanks,
André

Custom Tag is missing required attribute property

Hello,
Here is my struts config file source;
<global-forwards>
          <forward name="mainpage" path="/index.jsp">
          </forward>
          <forward name="CustomerDetailsForward" path="/GoToCustomerPage.do">
          </forward>
     </global-forwards>
     
     <action-mappings>
          <action path="/SubmitCustomerForm" type="action.SubmitCustomerForm" name="CustomerForm" scope="request" validate="true" input="/CustomerDetails.jsp">
               <forward name="success" path="/Success.jsp">
               </forward>
               <forward name="failure" path="/Failure.jsp">
               </forward>
          </action>
          <action path="/GoToCustomerPage" type="org.apache.struts.actions.ForwardAction" parameter="/CustomerDetails.jsp">
          </action>
     </action-mappings>
And my index.jsp source;
<html:html>
<head>
<html:base/>
</head>
<body>
<html:button></html:button>
<html:link forward="CustomerDetailsForward">Go To Customer Form </html:link>
</body>
</html:html>
And here is the error;
Error Message:JSPG0227E: Exception caught while translating /index.jsp: /index.jsp(13,1) --> JSPG0006E: Custom Tag is missing required attribute property
Root Cause:com.ibm.ws.jsp.translator.JspTranslationException: JSPG0227E: Exception caught while translating /index.jsp: /index.jsp(13,1) --> JSPG0006E: Custom Tag is missing required attribute property     at com.ibm.ws.jsp.translator.visitor.validator.ValidateVisitor.visitCustomTagStart(ValidateVisitor.java:304)     at com.ibm.ws.jsp.translator.visitor.JspVisitor.processJspElement(JspVisitor.java:267)     at com.ibm.ws.jsp.translator.visitor.JspVisitor.processChildren(JspVisitor.java:309)     at com.ibm.ws.jsp.translator.visitor.JspVisitor.processJspElement(JspVisitor.java:268)     at com.ibm.ws.jsp.translator.visitor.JspVisitor.processChildren(JspVisitor.java:309)     at com.ibm.ws.jsp.translator.visitor.JspVisitor.processJspElement(JspVisitor.java:139)     at com.ibm.ws.jsp.translator.visitor.JspVisitor.visit(JspVisitor.java:121)     at com.ibm.ws.jsp.translator.JspTranslator.processVisitors(JspTranslator.java:121)     at com.ibm.ws.jsp.translator.utils.JspTranslatorUtil.translateJsp(JspTranslatorUtil.java:181)     at com.ibm.ws.jsp.translator.utils.JspTranslatorUtil.translateJspAndCompile(JspTranslatorUtil.java:83)     at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.translateJsp(AbstractJSPExtensionServletWrapper.java:349)     at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper._checkForTranslation(AbstractJSPExtensionServletWrapper.java:317)     at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.checkForTranslation(AbstractJSPExtensionServletWrapper.java:226)     at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.handleRequest(AbstractJSPExtensionServletWrapper.java:131)     at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionProcessor.handleRequest(AbstractJSPExtensionProcessor.java:270)     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:308)     at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:472)     at com.ibm.ws.wswebcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:111)     at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3129)     at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:238)     at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:811)     at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1433)     at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:93)     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:465)     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:394)     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:274)     at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)     at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)     at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:152)     at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:213)     at com.ibm.io.async.AbstractAsyncFuture.fireCompletionActions(AbstractAsyncFuture.java:195)     at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)     at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:194)     at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:741)     at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:863)     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1510)

volkov wrote:
Error Message:JSPG0227E: Exception caught while translating /index.jsp: /index.jsp(13,1) --> JSPG0006E: Custom Tag is missing required attribute propertyWhich is line 13 then? And check the syntax for that tag.

Pixel-Positions in XML-Element attributes

hi,
is there a way, when attaching a xml-tag to e.g. a picture, that the top and left pixel value is saved in a xml-element attribute? the pixel value from top and from the left.
thanks in advance.
regards.

hi,
is there a way, when attaching a xml-tag to e.g. a picture, that the top and left pixel value is saved in a xml-element attribute? the pixel value from top and from the left.
thanks in advance.
regards.

Bulk import error - Missing required attribute fullname

Folks,
I am having trouble trying to bulk import some users.
I have the following file for import (cut down from what I really want to import):
command,user,waveset.resources,password.password,password.confirmpassword,global.firstname,global.lastname,global.fullname
Create,user1,myLDAPresourcename,passwd,passwd,myfirstname1,mysurname1, myfirstname1 mysurname1This works using Accounts->Launch Bulk Actions with Action set to From Action List and everything else on that page left at the default value. The correct data appears in IDM and the LDAP resource.
Now if I try to import the following file, in which the user does not have a first name, I get in to trouble:
command,user,waveset.resources,password.password,password.confirmpassword,global.firstname,global.lastname,global.fullname
Create,user2,myldapresourcename,passwd,passwd,,mysurname2,mysurname2
The error message is:
com.waveset.Util.WaveSetException: An error occurred adding user uid=user2,.. to resource myLDAPresourcename.
com.waveset.util.WavesetException: Missing required attribute fullnameClearly the import file contains a column for fullname (column 8) and a value for fullname in the only row of data mysurname2. As far as I am concerned it is perfectly valid for a user not to have a firstname; but they must have a fullname.
I have tried using an import file without a value for fullname, but with a firstname and lastname like this
command,user,waveset.resources,password.password,password.confirmpassword,global.firstname,global.lastname,global.fullname
Create,user3,myLDAPresourcename,passwd,passwd,myfirstname3,mysurname3,This works. The correct data appears in IDM and the LDAP resource and IDM has generated a fullname value of {Firstname} {Surname}. Trying to leave out the firstname and the fullname gives the same error as above.
The configuration of my resource (in summary) is
objectclasses:
     top
     person
     inetOrgPerson
Account Attributes:
     accounted     -> uid               [required]
     password     -> userPassword
     firstname     -> givenname
     lastname     -> sn               [required]
     objectClass     -> objectClass
     fullname     -> cn               [required]
As an experiment I have tried reconfiguring the resource so that fullname is not marked as required.
Importing user1 and user3 still works and still creates the correct data in IDM and the LDAP resource.
Importing user2 now gives a different error:
com.waveset.Util.WaveSetException: An error occurred adding user uid=user2,.. to resource myLDAPresourcename.
javax.naming.directory.SchemaViolationException: [LDAP: error code 65 Object Class Violation]I dont understand why, during the import of a user without a firstname IDM will not generate a fullname or use the supplied fullname.
Can anyone help?
Regards,
Gavin

After further testing it turned out that I couldn't create a user without a firstname from the IDM GUI and this in turn was because of the way fullname was generated by the user form.
I've got the user form changed and now user creation (from the GUI and via bulk import) is working as hoped.

Java 7u45 gives spurious warning about missing Permissions attribute

The security dialog in 7u45 gives a yellow warning about missing Permissions attribute.   Does anyone know how to get rid of it?
Same as the yellow box in the screenshots (#2 and #3) documented here (although none of them discuss the Permissions attribute) :
What should I do when I see a security prompt from Java?
The MANIFEST.MF file for the app definitely contains this attribute. There's only one jar for the application, and it's signed.
Might this be another security dialog bug? Or am I missing something? The JNLP contains the same "all-permissions" security tag.
I also found the release notes for 7u45 mention a couple of cases where the dialog might still appear
(see last issue: Java™ SE Development Kit 7 Update 45 Release Notes)
I don't use the JNLPDownloadServlet but my own. I didn't model it on the JNLPDownloadServlet, but guess I could have partly the same issue since I use versioning.
My jar doesn't fail to download though, it's just that its displaying this warning.
MANIFEST.MF:
Manifest-Version: 1.0
Implementation-Title: My app
Implementation-Version: 3.0-SNAPSHOT
Built-By: me
Application-Name: Myapp
Created-By: Apache Maven 3.0.5
Ant-Version: Apache Ant 1.8.2
Trusted-Library: true
Implementation-Vendor-Id: org.me
Trusted-Only: true
Build-Jdk: 1.7.0_45
Permissions: all-permissions
Specification-Title: my-client
Specification-Version: 3.0-SNAPSHOT
Archiver-Version: Plexus Archiver
Codebase: *.me.org

I went the Java version detection applet and I don't get a warning about the applet being blocked in the future.
https://java.com/en/download/installed.jsp
https://java.com/en/download/installed.jsp
I dug the jar for the applet out of my Java cache and it contains Manifest.MF with the following contents:
Manifest-Version: 1.0
Codebase: www.java.com java.com
Created-By: 1.7.0_25 (Oracle Corporation)
Permissions: all-permissions
Application-Library-Allowable-Codebase: www.java.com java.com
Application-Name: Java Detection
Name: JNLP-INF/APPLICATION.JNLP
SHA1-Digest: jPquHTBq5R8txQLe5/T20x70Y7w=
Name: JavaDetection.class
SHA1-Digest: kQNVjPC5Yym1DszdpX1D2EH8Ll0=
The jar contains one Java class and a signed JNLP-INF/APPLICATION.JNLP file that looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<jnlp codebase="https://java.com/en/download/" href="JavaDetection_applet.jnlp" spec="1.0+">
    <information>
        <title>Java Detection</title>
        <vendor>Oracle Inc.</vendor>
    </information>
    <resources>
        
<j2se version="1.6+"/>
        <jar href="JavaDetection.jar" />
    </resources>
<security>
<all-permissions />
</security>
    <applet-desc
         name="Java Detection Applet"
         main-class="JavaDetection"
         width="1"
         height="1">
     </applet-desc>
     <update check="background"/>
</jnlp>
They are running applet via JNLP:
<applet code="JavaDetection.class" width="500" height="150"><param name="image" value="/im/download/verify_anim.gif"/><param name="centerimage" value="true"/><param name="boxborder" value="false"/><param name="jnlp_href" value="JavaDetection_applet.jnlp"/></applet>
The JNLP file downloaded from here: https://java.com/en/download/JavaDetection_applet.jnlp matches the signed JNLP file in the jar (except for name).
We are still working on getting our applications to not show the warning message but this appears to be an example of where the "you will be blocked in the future" message is not happening. We don't run our applications as applets so if anyone can find another working example that is a more traditional JNLP app, please post a link.

Cannot open CS5.1, says to reinstall because of missing elements

can not open my CS5.1 , widow pops up telling me to reinstall it because I am missing some elements

If there are missing elements, then reinstalling sound like a good idea.

Error 103: application.initialWindow.autoOrients is an unexpected element/attribute

Hello.
I'm using Flash Builder 4.5 to experiment with building a mobile app for my Android Nexus One. In order to keep the app in landscape mode, regardless of the orientation of the device, I've read that I need to set the following in the "AppName-app.xml" file:
<aspectRatio>landscape</aspectRatio>
<autoOrients>false</autoOrients>
And this does work fine in the debugger, however when I attempt to test it on my connected device it throws this error:
Error occurred while packaging the application:
D:\Projects\FlexMobile\AppName\bin-debug\AppName-app.xml(108): error 103: application.initialWindow.autoOrients is an unexpected element/attribute
I know that I'm able to build and test apps on my device, as I've been through the Flex Test Drive for Mobile tutorial (http://www.adobe.com/devnet/flex/testdrivemobile.html) and was able to build and run that app with no issues and this app I'm currently working on does run on the device if I do not attempt to restrict the auto orientation.
Thank you.
(Note: I'm re-posting this from the Flex SDK > Developers forum.)

User rblaa provided that answer in http://forums.adobe.com/thread/858772.
The <autoOrients> node (along with several others) occours twice in the generated -app.xml file. Do not un-comment the first instance, instead edit the parameters set in the second already un-commented autoOrients node.

Missing element attributes

Similar Messages

Maybe you are looking for