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:
Related
I have a Web Api application targeting NET Core 2.1. When I upgrade the Microsoft.AspNetCore.All nuget package to v2.1.1, the application stops running.
My dotnet:
$ dotnet --version
2.1.300
In my Windows Application event viewer, I first see this warning:
The directory specified for caching compressed content C:\inetpub\temp\IIS Temporary Compressed Files\myproj.Logs.HostedApi AppPool is invalid. Static compression is being disabled.
And then I have two of this error:
Log Name: Application
Source: IIS Express AspNetCore Module
Date: 6/21/2018 4:15:11 PM
Event ID: 1000
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: CarbonVic
Description:
Application 'MACHINE/WEBROOT/APPHOST/MYPROJ.LOGS.HOSTEDAPI' with physical root 'C:\myproj\Code\myproj-moonshot\apps\myproj.Logs\myproj.Logs.HostedApi\' failed to start process with commandline 'C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\Microsoft\Web Tools\ProjectSystem\VSIISExeLauncher.exe -argFile "C:\Users\me\AppData\Local\Temp\tmp27D2.tmp"', ErrorCode = '0x80004005 : 0.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="IIS Express AspNetCore Module" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2018-06-21T20:15:11.470607900Z" />
<EventRecordID>9844</EventRecordID>
<Channel>Application</Channel>
<Computer>machinename</Computer>
<Security />
</System>
<EventData>
<Data>Application 'MACHINE/WEBROOT/APPHOST/myproj.LOGS.HOSTEDAPI' with physical root 'C:\myproj\Code\myproj-moonshot\apps\myproj.Logs\myproj.Logs.HostedApi\' failed to start process with commandline 'C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\Microsoft\Web Tools\ProjectSystem\VSIISExeLauncher.exe -argFile "C:\Users\me\AppData\Local\Temp\tmp27D2.tmp"', ErrorCode = '0x80004005 : 0.</Data>
</EventData>
</Event>
Every machine in my shop has this issue. We had to revert back to Microsoft.AspNetCore.All v2.0.8 to make it work again.
Funny thing is: there is no c:\inetpub on any of our machines and there never has been.
Also, I tried to run it on both IISExpress and self-hosted; it will not start with either profile.
Am I missing something here? Anyone know if there's a fix for this?
Help is appreciated always.
V
Well, the good news is that .NET Core 2.1.1 is released now, so you can go and install the new SDK version (2.1.301) from https://dot.net. :)
Now about the issue you had: The meta packages work by referencing the shared framework, which gets installed by the SDK. Since the SDK for 2.1.1 was not installed (2.1.301) your application blew up.
You also mentioned that in the NuGet window the updated packages where already visible. That's true. The individual packages were already released. They just couldn't be resolved because the Microsoft.AspNetCore.All metapackage version 2.1.1 wasn't installed.
On a sidenote: It's recommended to target Microsoft.AspNetCore.App instead of .All . Also the version number can be inferred from the SDK, so you can remove that too.
See: https://learn.microsoft.com/en-us/aspnet/core/fundamentals/metapackage?view=aspnetcore-2.1#migrate
The 2.1.1 release is still in progress. You should use the 2.1.0 packages until it's complete: https://twitter.com/DamianEdwards/status/1009873842662043648.
After installing the newly released IJ14 Community Edition - the quasiquotes (which had been working on IJ13) popped up on the radar.
Is there an IJ setting to enable this?
BTW this is a maven build (and works in 13.1 just fine!). Here is the section of the build related to the quasiquotes. I have not seen any mention of the plugin not working properly in 14, but input here would be appreciated.
<!-- The following plugin is required to use quasiquotes in Scala 2.10 and is used
by Spark SQL for code generation. -->
<compilerPlugins>
<compilerPlugin>
<groupId>org.scalamacros</groupId>
<artifactId>paradise_${scala.version}</artifactId>
<version>${scala.macros.version}</version>
</compilerPlugin>
</compilerPlugins>
UPDATE I just installed the 14.0.1 update from 11/11/14. This time I tried Intellij Ultimate : but Quasiquotes are still not working.
UPDATE I have opened a JIRA with JetBrains. https://youtrack.jetbrains.com/issue/IDEA-133993
I think there is a workaround to get it running:
You have to go to the IntelliJ settings, to the "Scala Compiler" and add a plugin: "/home/YOURUSERNAME/.m2/repository/org/scalamacros/paradise_2.10.4/paradise_2.10.4-2.0.1.jar"
The problem involves the paradise plugin that provides support for quasiquotes with scala 2.10. It is not working in IJ14 presently.
UPDATE The following is new info on the building with Spark page
https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark#ContributingtoSpark-IntelliJ
"Rebuild Project" can fail the first time the project is compiled, because generate source files are not automatically generated. Try clicking the "Generate Sources and Update Folders For All Projects" button in the "Maven Projects" tool window to manually generate these sources.
Compilation may fail with an error like "scalac: bad option: -P:/home/jakub/.m2/repository/org/scalamacros/paradise_2.10.4/2.0.1/paradise_2.10.4-2.0.1.jar". If so, go to Preferences > Build, Execution, Deployment > Scala Compiler and clear the "Additional compiler options" field. It will work then although the option will come back when the project reimports. If you try to build any of the projects using quasiquotes (eg., sql) then you will need to make that jar a compiler plugin (just below "Additional compiler options"). Otherwise you will see errors like:
/Users/irashid/github/spark/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/codegen/CodeGenerator.scala
Error:(147, 9) value q is not a member of StringContext
Note: implicit class Evaluate2 is not applicable here because it comes after the application point and it lacks an explicit result type
q"""
^
It's s not q:
val x = 5.0
println(s"$x.toInt")
I loaded spark up in Intellij 13 and the macro paradise backport of quaisquotes still shows an error, I don't see how intellij would be able to support this syntax as it's a compiler plugin:
For my JNLP file , there is some nativelib info like below:
<resources os="Windows">
<nativelib href="lib/x264-win.jar" />
</resources>
<resources os="SunOS" arch="sparc">
<nativelib href="lib/x264-SunOS-sparc.jar" />
</resources>
<resources os="SunOS" arch="x86">
<nativelib href="lib/x264-SunOS-x86.jar" />
</resources>
When I Update To JRE7, can not load nativelib jar, but JRE6 works fine.
The load nativelib code like below:
String source = "x264.jar";
ClassLoader cl = Thread.currentThread().getContextClassLoader();
URL url= cl.getResource(source);
"x264.jar" is one jar in x264-win.jar,lib/x264-SunOS-sparc.jar or lib/x264-SunOS-x86.jar.
When I used JRE6 to load x264.jar, it worked fine.
But when I updated to JRE7, it can not load x264.jar.
When use JRE6, url would be"x264.jar" info, like jar:http://test.local:8080/JNLP.jar!/x264.jar,
but use JRE7, url would be null, and I found code not load nativelib "x264.jar"
Does any one have find JRE7 can not load nativelib.jar?
Is the problem of using Thread.currentThread().getContextClassLoader() to load "x264.jar"?
Ensure that you have the correct bitwise native binary to match your JRE. If you are testing on a 64-bit JRE, you need a 64-bit native binary. If you're testing on a 32-bit JRE, you need a 32-bit native binary. You might need to include resources for each of these three:
<resources os="Windows" arch="amd64">
<resources os="Windows" arch="x86_64">
<resources os="Windows" arch="x86">
I had similar trouble ; however even in JRE 6 this didn't get this to work.
Found a bug that could be related to that :
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6758884
Apparently JRE can have trouble downloading nativelib resources.
The bug is still opened, and targeted towards version 8 of java ...
The following "dll relying" applet is working fine (besides the security problems when using 1.7.0_51 (you need to decrease the security settings to medium since it is self signed)).
So if the native lib loading mechanism of the jnlp file is broken then you can distribute your .dll files alongside a normal jar file like in the upper example.
Put the dlls/sos in your jar file like in the example: jssc.jar
Load the libraries with System.load(libFolderPath + fileSeparator + libName); like used here.
As mentioned by Joseph please note the fine grained version differentiation between win, solaris, linux, arm and i86 and amd64 bit systems. So if you e.g. don't supply a 64Bit dll and run it with 64Bit Java it won't work...
I had forgot I solved this a while ago. I found that I had to handle this in Java code with System.loadLibrary( "jarNameNoExtension" );
Hopefully that helps others.
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