I'm developing a project with Equinox execution environment and I'm using the cxf-dosgi-ri-singlebundle-distribution CXF bundle. I'm running my tests within Eclipse RCP (galileo). When I started the program for the first time with the newly added CXF bundle everything worked fine. But at the second try I got a java.lang.LinkageError in cxf-dosgi-ri-singlebundle-distribution bundle. I added some ad hoc "uses" directives, and the problem diappeared. But at the subsequent start the LinkageError was there again! So I modify again (with touch manifest.mf !!!) the manifest and the program started correctly.
The point is that Eclipse is able to correctly start the bundles if and only if I "touch" the manifest file of cxf-dosgi-ri-singlebundle-distribution.
Does anyone have never experienced a similar issue?
Thank you very much,
matteo
To Whom It May Concern: I completely removed and recreated from scratch the eclipse workspace and I upgraded the cxf-dosgi-ri-singlebundle-distribution to a newly available version (I was using v 1.1 and I upgraded to v 1.2). The problem disappeared.
Related
In Production, IBM MobileFirst server running with version 7.1.0.00.20180425-1124 and Project war file with version 7.1.0.00.20180425-1124.
Recent deployment of project war was deployed with 7.1.0.00.20161006-0540, unfortunately.
iOS throws below error:
{"error_description":"Client authentication failed","error":"invalid_client"}
Rolled back the deployment to avoid issues.
While investigating, there was an APAR with similar fix but the version used in the deployment doesn't include this APAR.
Question 1: If same version(7.1.0.00.20180425-1124) of MF Plugin used to build Project .war, will this issue be addressed.
Question 2: Where can I download the Eclipse Plugin of 7.1.0.00.20180425-1124?
Thanks in advance
It is not clear what steps you took to update your server. In your MobileFirst server Operations console , if you see the version as "7.1.0.00.20161006-0540" , then you should definitely update.
If that is the case, merely building a new project runtime war file in latest MobileFirst Eclipse Studio and deploying it will not help. The iFix level in the server will have to be updated too. You can use Server Config Tool or ANT scripts to update your iFix level as well to the latest while you deploy the new runtime war.
You can download the latest versions of the iFix ( Server and Studio plugin) in FixCentral.
Finally achieved by clearing out the keychain items and defaults which work light library has been internally maintaining.
So what's happening behind the scenes is the work light client is creating and maintaining some keychain items and also few user defaults. This is done for storing some information like session id's and stuff. Sometimes the data in the keychain or defaults is getting corrupted during the initial work light handshake with MFP server. In this scenario we get the above error. Once we clear them out and kill the app and launch again. the app will now behave as a new device.
I am an experienced (but retired) Windows software developer, with more years experience than I care to admit, developing in C++, C#, VB and Java. I therefore decided to have a crack at Android development. My development machine is a Windows 7 box. My IDE of choice would be Microsoft Visual Studio but, for now, I am happy doing hand editing and launching tools from the command line.
I started by downloading the Android SDK and various additional items it suggested. I then started working my way through the tutorial at developer.android.com/training/basics/firstapp. Android list targets gave me a couple of choices (Android 4.2.2 and Google APIs:17). I then did Android create project from the command line and that appeared to do its stuff, creating MyFirstApp in my development folder. I then ran Android avd and created an emulator. I also added the android SDK's tools and platform-tools to my path. So far so good.
I fell at the next hurdle. The tutorial told me to change to the root folder of my project and run ant debug. At this point, Windows reports:
'ant' is not recognized as an internal or external command,
operable program or batch file.
I've searched around for ant.exe without success. Did I miss installing something or did I miss a vital step in the set-up? Any advice for this very green newbie would be greatly appreciated.
There is no ant.exe. Only ant.bat. Ant is a Java build tool.
If it comes with the Android SDK, make sure its bin directory is in your PATH environment variable. Otherwise, download it (from [http://ant.apache.org][1]), and follow the installation instructions on the web site.
Normally, simply unzipping it, putting its bin directory in the PATH envieonment variable, and setting a JAVA_HOME environment variable that points to your preferred JDK directory is sufficient.
I have recently upgraded my IntelliJ 10 to the latest 11.0.1 version. I am writing grails app and until I was using the older version of IntelliJ everything was fine, however 11 doesn't allow me to successfully add Grails SDK (2.0.0) - I was trying to add the framework support, this however doesn't seem to be persisted (after adding Groovy and then choosing Grails - nothing happens). I have tried to follow those steps as well: IntelliJ IDEA 9.0 - unable to select project SDK for Grails application
I would be grateful if someone would be able to point me how to configure Grails SDK - or what could be wrong in my configuration.
Thanks,
This is exactly the way that I have my global library defined and still I was having exactly the same issue.
I followed OverZealous advice and created a new Grails project named exactly the same as the original one and boom everything is fine now! Thanks for help.
You don't need both Groovy and Grails for Grails project, just use Grails SDK. When creating a new Grails project there is an option to add new SDK, select the home path of your Grails installation and it will be configured automatically as a Global Library and this library will be added as a dependency to your module.
Grails library configuration contains all the jars from GRAILS_HOME\dist and GRAILS_HOME\lib, plus all the jars from the src directory.
In other words, it's not configured as a framework, it's just a library with all the jars from Grails distribution added to the module dependencies.
Each time I restart IntelliJ, version 13.1.2, it loses the SDK configuration. If I right-click on the project and "Add Framework Support" I can choose the SDK that is already configured and it will begin functioning properly. When it loses this setting, it won't allow me to compile or launch the app with grails. I reject the ideas to recreate the project, (been there/done that) as I have many dependent modules I have to verify and I lose all my run configurations that I've setup manually.
I'm posting the "Add framework support" step here so it might help someone else; hopefully a more permanent solution for you, but its temporary in my situation
I have a simple 3D application programmed in C++ and D3D9 using MSVC++ 2008 Express. Some weeks ago, I had to format my hard disk, so the DirectX SDK is not currently installed.
However, I found that the exe file that I found in my "Debug" folder for the project does not run. The error it gives is:
"This application has failed to start because d3dx9d_38.dll was not found. Re-installing the application may fix this problem."
Of course, it worked after I installed the SDK. Then I compiled a "release build" thinking that that was the solution. Then I uninstalled the SDK and tried to run the .exe file.
Still gave me the error.
So how does one make such .exe files run on machines without the SDK?
I think you cannot run the app without the SDK. See XBMC, which requires the SDK to run.
However, you could try simply placing the required dll file from your SDK in the same directory as the executable.
I followed the solution as stated here.
I copied the d3dx9_38.dll file into my Release folder. It still didn't work. However, I renamed the dll file to "d3dx9d_38.dll. Then it worked.
Wondering why I had to rename to the debug version of the file even though it was a RELEASE build...
When I create a Grails application in IntelliJ 9 on Snow Leopard I am not prompted to create an application. IntelliJ finished the wizard and creates an empty project that is not a Grails application. I have tried two different Apple computers (MacBook Pro and Mac Pro) it does not work on either. The same steps on a Linux system results in a prompt to "create-app" and a Grails application.
I have already tried the steps in Intellij IDEA setup on OS X
Is there a specific place that Grails needs to be installed? Has anyone else seen this behavior?
Thanks
Answer: Make sure that the grails directory is writable.
Just tried this on Snow Leopard running Intellij 94.633 (EAP) + grails 1.2.1 and the create new project wizard has worked just fine.
Started with 'create new project', selected a grails module, was then prompted to 'create-app' or 'create-plugin' and was presented with a completed project.
Might be an idea to try the same EAP build if no joy you will have to file a bug with jetbrains. They are pretty good at responding to issues, you should get some sort of feed back pretty soon.
This is actually the first time I've actually done that in intellji, previously I've always just used the grails command line and then just imported the application to Intellij.
Make sure that the grails directory is writable.
I moved my grails install from /opt/grails-1.2.1 to /Users/dave/grails-1.2.1 and I can now create or import grails applications.