I am facing issue while upgrading jibx version 1.3.1 from 1.2.1 for java8
Faceing issue Jibx :Java.lang.illegalStateException:internalerror- no direct access to a class.
This will happen while doing jibx compile
Could you please suggest some one.
I was having this same problem, but seem to have found a workaround. If you upgrade BCEL (I went with 6.3.1) instead of JiBX (we're on 1.2.3), compilation will go on even for files containing Java8 syntax.
It'd be better to upgrade JiBX, but I wasn't able to get that to work yet so we might just accept this solution.
Related
I Installed the Nuget Package Installer thing, and it says it installed it.
However I can't find any references to JSON in Visual Studio.
I tried using System.JSON but I can't find it.
How can I use it?
Thanks
I have had been through the same trouble today, when I almost completed my Software Project and just had to use the File to use its contents to change the content of the Project.
For that I wanted to use JsonObject class to get the contents of the .json file. When I tried to write this
using System.Json;
It gave me the exact same error that you might have been going through. It asked for the Assembly files and DLLs.
I kept searching and I stumbled upon to this post, which was totally unhelpfull for me. So I searched and got what I was looking for. After that, I wanted to share that triumph with you people too so that next visitor must have an answer to his trouble on Stack Overflow.
Solution
What I did was, I went to the NuGet website for the System.Json extension package.
http://www.nuget.org/packages/System.Json
There, I capture the command for the installation.
I just click on the Tools --> NuGet package manager --> Package Manager Console and it gave me a new window in the bottom part of Visual Studio 2013.
There I typed (pasted) the link of command I copied. It started and installed the package for me. And now I can use it!
Further answer
I was told that it is a part of .NET v4.5, but I even have the v4.5.1 and still I don't get it why I don't have that package, maybe because on the Web page of the package it is shown deprecated. But still who ever needs it, can have the answer I have posted and it would help him out!
Good luck!
I think you can use the Newtonsoft JSON.NET package.
http://www.nuget.org/packages/newtonsoft.json/
I was also looking for a way to do JSON in C# and saw that they made it easier with .NET 4.5, couldn't do it and found this stack overflow question. I wasn't really satisfied with Afzaal Ahmad Zeeshan's answer so I kept searching and found this which I guess isn't depreciated and worked for me.
Steps in plain English (for .NET 4.5):
1.Add Reference to System.Runtime.Serialization
2.Add "using System.Runtime.Serialization.Json;" to your class
3.call "JsonReaderWriterFactory.CreateJsonReader()" or whatever methods you need to use to read/write json
Install latest VS 2017
Install-Package System.Runtime.Serialization.Json -Version 4.3.0
-- in PM console
I'm working my way through the MMVMCross Tip Calculator tutorial.
Got an Android instance up and running and have now turned my attention to Windows Phone 8.
So far, I can't find the Cirrious.MvvmCross.Plugins.Json assembly in the WindowsPhone bin folder, and I'm also having issues with the CreateApp() method not being able to resolve the Core.App class (there are a bunch of suggestions for chasing down the Core namespace but none of them have an App class inside that I can see).
When I comb through the docs it seems WP7 is supported explicitly, but no mention of 8. Anybody have any luck getting this scenario going? Is there a hack I'm missing?
After installing the Nuget package (The HotTuna Startup) in an Andriod project, I was unable to build and was getting the same problem in the CreateApp() where Core is not resolved. I had missed adding the package MVVMCross.Core and MvvmCross - Hot Tuna Libraries (which added the app.cs) to my core PCL library. Those Nuget packages are a great way to get started!
It's obvious now, but maybe this will help someone else.
Yes, Windows Phone 8 is supported, but there's no specific extensions for WP8 yet (e.g. we still use the Community C# SQLite code)
The Core.App class should be in your Core/application project. e.g. in the tutorial it's in https://github.com/slodge/MvvmCross/tree/vnext/Sample%20-%20Tutorial/Tutorial/Tutorial.Core
I wish to use JSON.Net on a brand spankin new Mono class library (say .. Mono / .NET 4). Of course, this class library will be used by a MonoTouch iPhone/iPad project (also in the same solution).
I'm not sure of the steps I need to do, to use JSON.Net in a Mono Class Library.
The closest I got to this was this SO question .. but it said nothing about how the DLL was made, where it exists, etc.
BTW: I'm also using MonoDevelop for the IDE. This is on a Mac OSX.
If your mono is new enough, you can in fact use NuGet downloaded from here. You also need some trusted certificates to get it working well - they can be imported using:
mozroots --import --ask-remove
And then you can download the package using NuGet
You can also download the library any other way - no need to recompile the sources as Mono and .NET are binary compatible.
Btw, binaries can be directly downloaded from nuget in a way like that:
Json.Net.
I need to define a runtime environment for my development. The first idea is of course not to reinvent the wheel. I downloaded macports, used easy_install, tried fink. I always had problems. Right now, for example, I am not able to compile scipy because the MacPorts installer wants to download and install gcc43, but this does not compile on Snow Leopard. A bug is open for this issue, but I am basically tied to them for my runtime to be usable.
A technique I learned some time ago, was to write a makefile to download and build the runtime/libs with clearly specified versions of libraries and utilities. This predates the MacPorts/fink/apt approach, but you have much more control on it, although you have to do everything by hand. Of course, this can become a nightmare on its own if the runtime grows, but if you find a problem, you can use patch and fix the issue on the downloaded package, then build it.
I have multiple questions:
What is your technique to prepare a well-defined runtime/library collection for your development?
Does MacPorts/fink/whatever allows me the same flexibility of rehacking if something goes wrong ?
Considering my makefile solution, when my software is finally out for download, what are your suggestions about solving the potential troubles between my development environment and the actual platform on my user's machines ?
Edit: What I don't understand in particular is that other projects don't give me hints. For example, I just downloaded scipy, a complex library with lots of dependencies. Developers must have all the deps setup before working on it. Despite this, there's nothing in the svn that creates this environment.
Edit: Added a bounty to the question. I think this is an important issue and it deserves to get more answers. I will consider best those answers with real world examples with particular attention towards any arisen issues and their solution.
Additional questions to inspire for the Bounty:
Do you perform testing on your environment (to check proper installation, e.g. on an integration machine) ?
How do you include your environment at shipping time ? If it's C, do you statically link it, or ship the dynamic library, tinkering the LD_LIBRARY_PATH before running the executable? What about the same issue for python, perl, and other ?
Do you stick to the runtime, or update it as time passes? Do you download "trunk" packages of your dependency libraries or a fixed version?
How do you deal with situations like: library foo needs python 2.5, but you need to develop in python 2.4 because library bar does not work with python 2.5 ?
We use a CMake script that generates Makefiles that download (mainly through SVN)/configure/build all our dependencies. Why CMake? Multiplatform. This works quite well, and we support invocation of scons/autopain/cmake. As we build on several platforms (Windows, MacOSX, a bunch of Linux variants) we also support different compile flags etc based on the operating system. Typically a library has a default configuration, and if we encounter a system that needs special configuration the configuration is replaced with a specialized configuration. This works quite well. We did not really find any ready solution that would fit our purpose.
That being said, it is a PITA to get it up and running - there's a lot of knobs to turn when you need to support several operating systems. I don't think it will become a maintainance-nightmare as the dependencies are quite fixed (libraries are upgraded regularly, but we rarely introduce new one).
virtualenv is good, but it can't do magic - e.g. if you want use a library that just MUST have Python 2.4 and another one that absolutely NEEDS 2.5 instead, you're out of luck. Nor can virtualenv (or any other tool) help when there's a brand new release of an OS and half the tools &c just don't support it yet, as you mentioned for Snow Leopard: some problems are just impossible to solve (two libraries with absolutely conflicting needs within the same build), others just require patience (until all tools you need are ported to the new OS's release, you just need to stick with the previous OS release).
We develop web application and we are going to deploy it on JBoss.
Now we use JSF, Facelets, Webflow, JMX, Spring.
We are going to use JMS(ActiveMQ).
Maybe in the future we will use EJB3. But for near future we will not use it.
What configuration of JBoss would be better to use - web, standard, default?
And why?
Go for the smallest config that does what you need. The "web" configuration seems to have everything you need, including ejb3 support.
Remember, the configurations in the distribution are just examples. It's perfectly acceptable to create custom server configs by copying the deployers and libs around to produce a config that does exactly what you need.
I've never found the need to use anything other than default, sometimes removing some of the config. And that's included JMS, EJB, Spring, Webflow, etc.
I you are using JBoss AS 5.1.X, I recommend this book: http://www.amazon.com/JBoss-AS-Development-Marchioni-Francesco/dp/1847196829
On page 31 there is a detailed explanation about the five provided configurations.