Details
-
Bug
-
Resolution: Fixed
-
P4
-
7u40
Description
Testing env: 64bit win7, 7u40 b31
For <fx:param>, no matter using <fx:param> or <param>(as doc http://docs.oracle.com/javafx/2/deployment/javafx_ant_task_reference002.htm#CIACICCF shows) in <fx:application>, the element in generated jnlp is <fx:param> not <param>
Steps to reproduce:
- download http://rehte.cn.oracle.com:8080/wshost/reproduce/fxpackager.zip and unzip it
- cd fxpackager/lib
- execute ant -f FileService.xml
- check ../html/FileService.jnlp file, if <fx:param> rather than <param> is generated under <jfx:javafx-desc> bug is reproduced. In the jnlp file, it doesn't define a "fx" name space.
The lib/ant-javafx.jar file is from 7u40 b31
For <fx:param>, no matter using <fx:param> or <param>(as doc http://docs.oracle.com/javafx/2/deployment/javafx_ant_task_reference002.htm#CIACICCF shows) in <fx:application>, the element in generated jnlp is <fx:param> not <param>
Steps to reproduce:
- download http://rehte.cn.oracle.com:8080/wshost/reproduce/fxpackager.zip and unzip it
- cd fxpackager/lib
- execute ant -f FileService.xml
- check ../html/FileService.jnlp file, if <fx:param> rather than <param> is generated under <jfx:javafx-desc> bug is reproduced. In the jnlp file, it doesn't define a "fx" name space.
The lib/ant-javafx.jar file is from 7u40 b31