I have an AIR application that is the following:
<h1>Hello World</h1>
It runs on my local machine:
C:\inetpub\wwwroot\AIR\HelloWorldDestination.air
And it runs if I choose "preview in Adobe AIR" in Dreamweaver.
But I can't get it to download and install from my website.
Here is the application.xml that Dreamweaver created:
<?xml version="1.0" encoding="utf-8" ?>
<application xmlns="http://ns.adobe.com/air/application/2.0">
<filename>HelloWorldFileName</filename>
<copyright>Hello World Copyright</copyright>
<description>Hello World Description</description>
<customUpdateUI>false</customUpdateUI>
<name>HelloWorldAppName</name>
<id>com.PhillipSenn.HelloWorldID</id>
<version>1</version>
<initialWindow>
<content>HelloWorld.htm</content>
<height>600</height>
<width>800</width>
<systemChrome>standard</systemChrome>
<transparent>false</transparent>
<visible>true</visible>
</initialWindow>
</application>
It's giving me an error 2032.
I have uploaded these files as well:
AC_RunActiveContent.js
badge.swf
HelloWorldDestination.air
Here's my line of code in Index.htm:
'flashvars','appname=HelloWorldAppName&appurl=http://www.PhillipSenn.com/AIR/HelloWorldDestination.air&airversion=2.0&imageurl=css/Install.gif',
When I create the AIR file, Dreamweaver gives me the following warning:
In order to install this application
on your machine, you need the Adobe
AIR runtime that can be downloaded
from: http://www.adobe.com/go/air
The application to be installed cannot be found at http://www.phillipsenn.com/AIR/HelloWorldDestination.air
Related
Hey im trying to do a mobile testing in JMeter, i've followed every step of this guide, and the recording works fine. The problem is that i have to record in a native app and when i try to log in i get the following error message:
java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.
Im not sure what to do
Why you're asking us and not the author of "this guide"?
These "every steps" are not complete, there is a couple more "every steps" which you need to "follow"
In the application section of your app manifest add the following entry:
android:networkSecurityConfig="#xml/network_security_config
Add network_security_config.xml file to your application resources folder and copy the below code there:
<?xml version="1.0" encoding="utf-8"?>
<network-security-config>
<debug-overrides>
<trust-anchors>
<!-- Trust user added CAs while debuggable only -->
<certificates src="user" />
</trust-anchors>
</debug-overrides>
</network-security-config>
Re-compile your application in the debug mode:
gradlew assembleDebug
Replace the app you're trying to record with the debug .apk from the previous step
You should be able to record now
More information:
Android Network Security Configuration
Configure Android Devices for Proxy Recording
When I run the below command from the command line for the WIx installer after migrated from version 2.0 to 4.0:
E:\Source\TestProgram\builder>ant -v -f Build.xml -Dlabel =.001 install
I am getting the below error:
[exec] light.exe : error LGHT0199 : The WixLocalization element has an
incorrect namespace of 'WixLocalization'. Please make the
WixLocalization element look like the following: .
[ant] Exiting E:\Source\TestProgram1.0.1English_installer.xml.
I want to know the root cause of the error?
I checked "TestProgram1.0.1English_Installer.wxs" file for "WixLocalization" but didn't find any thing.
Pleas help me to resolve the issue.
UPDATE: wixlibs - another feature I have not used.
Localizing Extensions - that wixlib is probably a localization file.
What are .wixlibs and why would you use them?
Create binary .wixlib.
Bob knows everything about this, but let me chip in with a question in case the problem is something else. Just to verify, can you check all *.wxl files (localization files) in the project in question? Just to make sure the schema specified is according to what version 4 expects?:
WiX 4:
English.wxl:
<?xml version="1.0" encoding="utf-8"?>
<WixLocalization Culture="en-us" xmlns="http://wixtoolset.org/schemas/v4/wxl">
<String Id="YOURLOCID">Your localized string</String>
</WixLocalization>
WiX 3:
English.wxl:
<?xml version="1.0" encoding="utf-8"?>
<WixLocalization Culture="en-us" xmlns="http://schemas.microsoft.com/wix/2006/localization">
<String Id="YOURLOCID">Your localized string</String>
</WixLocalization>
Suggestions:
So maybe create a localization file (*.wxl) if it is missing for WiX 4. Either in Visual Studio or slipstream it into your batch build script.
If there is a *.wxl there, maybe update the schema to <WixLocalization Culture="en-us" xmlns="http://wixtoolset.org/schemas/v4/wxl">.
For command lines, please see this: How To: Build a Localized Version of Your Installer.
You're using an Ant task that doesn't support WiX v4. Stick with WiX v3 (the latest supported release).
I have installed domino designer 8.5.2 with extension library and dojo 1.4.3.
I have written coding in source of the Xpage is given by,
<?xml version="1.0" encoding="UTF-8"?>
<xp:view xmlns:xp="http://www.ibm.com/xsp/core"
xmlns:xe="http://www.ibm.com/xsp/coreex">
<xe:mApp id="mApp1" selectedPageId="home">
<xe:mPage id="home" loaded="true" preload="true"
resetContent="false">
<xe:djxmHeading id="djxmHeading1" label="Testing">
</xe:djxmHeading>
</xe:mPage>
</xe:mApp>
</xp:view>
when previewing in the browser, it showing error as,
**"NetworkError: 404 Not Found -"
TabBar.js
failed loading /xsp/.ibmxspres/.extlib/dijit/Mobile.js with error: Error: Could not load 'dojox.mobile.TabBar'; last tried '../dojox/mobile/TabBar.js'
...x=d._toPixelValue;var astr="DXImageTransform.Microsoft.Alpha";var af=function(n,...**
what could be the reason, i have installed dojo in server also...please help me.
Thanks in advance
Dojo 1.4.3 doesn't support mobile controls. These were introduced in Dojo 1.5.1. So if you want to use the mobile controls, you will need to use the mobile controls project on OpenNTF.
Inside is some infrastructure who will detect the server version of Dojo. If it is below 1.5.1 it will use it's version, who is inside the database.
Latest version can be found here, http://mobilecontrols.openntf.org/
It is not well maintained lately.
I have an application which uses fop and xslt to generate the PDF file. The special characters as §£?ÐÅÆ are appearing as ???? in PDF.
The weblogic server is running on solaris machine.
I have already tried with
<charset-params>
<input-charset>
<resource-path>/*</resource-path>
<java-charset-name>UTF-8</java-charset-name>
</input-charset>
<charset-mapping>
<iana-charset-name>UTF-8</iana-charset-name>
<java-charset-name>UTF-8</java-charset-name>
</charset-mapping>
</charset-params>
in weblogic.xml.
I have also tried with
transformer.setOutputProperty( OutputKeys.METHOD, "xml");
transformer.setOutputProperty("{http://xml.apache.org/xslt}indent-amount", "2");
transformer.setOutputProperty( OutputKeys.INDENT, "yes");
transformer.setOutputProperty(OutputKeys.ENCODING, "UTF-8");
Nothing seems to be working over there.
Have you set up fop to find fonts with those characters in? For instance, on Solaris 11
using fop (though not with weblogic) I had to set up paths for fonts in a fop-conf.xml:
<?xml version="1.0"?>
<!-- NOTE: This is the version of the configuration -->
<fop version="1.0">
<renderers>
<renderer mime="application/pdf">
<fonts>
<!-- register all the fonts found in a directory -->
<directory>/usr/share/fonts/TrueType/core/</directory>
<directory>/usr/share/fonts/TrueType/dejavu/</directory>
<directory>/usr/share/fonts/TrueType/liberation/</directory>
<directory>/usr/share/fonts/TrueType/unifont/</directory>
<!-- register all the fonts found in a directory and all of its sub directories (use with care) -->
<!-- directory recursive="true">C:\MyFonts2</directory -->
<!-- automatically detect operating system installed fonts -->
<auto-detect/>
</fonts>
</renderer>
<renderer mime="application/postscript">
<fonts>
<directory>/usr/share/fonts/X11/Type1/</directory>
<directory>/usr/share/ghostscript/fonts/</directory>
<directory>/usr/share/fonts/TrueType/core/</directory>
<directory>/usr/share/fonts/TrueType/dejavu/</directory>
<directory>/usr/share/fonts/TrueType/liberation/</directory>
<directory>/usr/share/fonts/TrueType/unifont/</directory>
</fonts>
</renderer>
</renderers>
</fop>
(Font paths will be different on older versions of Solaris.)
For more details, see:
http://xmlgraphics.apache.org/fop/trunk/fonts.html
http://www.sagehill.net/docbookxsl/AddFont.html#ConfigFontFop
OBJECTIVE :
So here is my problem, I am trying to auto-update an old version software X v1.0.7 AIR Runtime SDK 2.0 to a new version X v1.0.8 AIR Runtime SDK 2.5.
CONFIGURATION =
Old Software X is version 1.0.7 using runtime SDK 2.0. App.xml as follow :
<application xmlns="http://ns.adobe.com/air/application/2.0">
<version>1.0.7</version>
This software X is so, suppose to update to version 1.0.8 which suppose to use the AIR runtime 2.5.
Im using an update.xml file with tags :
<update xmlns="http://ns.adobe.com/air/framework/update/description/1.0">
<version>1.0.8</version>
The computer is MacOS X v10.6.6. running the latest AIR RUNTIME 2.5
The new version of the old software X, version 1.0.8, is using an app.xml as follow :
<application xmlns="http://ns.adobe.com/air/application/2.5">
<versionNumber>1.0.8</versionNumber>
<publisherID>#my hidden publisherID#</publisherID>
The software X v1.0.8 is using the tag publisherID so the software would be recognized as the same software.
WHAT HAPPEN ?
When I launch the old software X v1.0.7, it is trying to update and raise the error 16824. This error is suppose to mean that my version of the new software does not match the version defined in the update.xml file but to me, its not true... so what is wrong ? Anyone can help ?
The solution is here :
http://kb2.adobe.com/cps/873/cpsid_87300.html
If you're trying to follow the instructions in the knowledge base article, you'll find that it tells you what to do but not how to do it. You're told to include the updated applicationupdater.swc and applicationupdater_ui.swc from Air 2.5 / Flex 4.5 but that is the hardest part.
In Flash Builder do this:
Go to "Project Properties", "Build Path"
Unfold the Flex Framework in the list and remove applicationupdater.swc and applcationupdater_ui.swc.
Click "Add SWC" and add those two files from your Flex 4.5 framework location (/Applications/Adobe Flash Builder 4.5/sdks/4.5.0/frameworks/libs/air/applicationupdater.swc on Mac).
If you're using the mxmlc task in an Ant buildfile, this has worked for me:
<target name="compile" depends="css, copy_assets">
<mxmlc file="${MAIN_SOURCE_FILE}" output="${OUTPUT}/${FLEX_APP_NAME}.swf">
<load-config filename="${FLEX_HOME}/frameworks/air-config.xml"/>
<compiler.source-path path-element="${APP_ROOT}/src"/>
<compiler.source-path path-element="${APP_ROOT}/locale/{locale}"/>
<!-- append=false clears your library-path -->
<compiler.library-path dir="${FLEX_HOME}" append="false">
<!-- Now we need to re-add the flex libs -->
<include name="libs"/>
<include name="locale/{locale}"/>
</compiler.library-path>
<compiler.library-path dir="/" append="true">
<!-- Add the updater framework from Flex 4.5 / Air 2.6 -->
<include name="Applications/Adobe Flash Builder 4.5/sdks/4.5.0/frameworks/libs/air/applicationupdater_ui.swc"/>
<include name="Applications/Adobe Flash Builder 4.5/sdks/4.5.0/frameworks/libs/air/applicationupdater.swc"/>
<!-- You may need to adjust these paths -->
</compiler.library-path>
<compiler.library-path dir="${FLEX_HOME}" append="true">
<!-- Re-add the rest of the air libs -->
<include name="libs/air"/>
</compiler.library-path>
<compiler.library-path dir="${APP_ROOT}/libs/" append="true">
<!-- Your custom libraries here -->
</compiler.library-path>
</mxmlc>
</target>
An equivalent set of commandline options should work for the mxmlc command line compiler, but I haven't tested this:
mxmlc -library-path=$(FLEX_HOME)/libs $(FLEX_HOME)/locale/{locale} \
$(FLEX45_HOME)/frameworks/libs/air/applicationupdater.swc \
$(FLEX45_HOME)/frameworks/libs/air/applicationupdater_ui.swc \
$(FLEX_HOME)/frameworks/libs/air \
... your custom libs \
... other compiler options
I have described the entire process with a bit more background information on my blog.
The error occurred for me because versions number in my compiled application was different than the version number in the UpdateDescriptor.xml on the server.
In an AIR application the version number is defined in the application descriptor file under the tag versionNumber:
<versionNumber>2.3.0</versionNumber>
In the UpdateDescriptor.xml file on the server I had a different number:
<?xml version="1.0" encoding="utf-8"?>
<update xmlns="http://ns.adobe.com/air/framework/update/description/2.5">
<versionNumber>2.2.1</versionNumber>
<url>http://www.example.com/project_2.2.1.air</url>
<description><![CDATA[List the changes in this version here]]>
</description>
</update>
It resulted in this error: