Jackson in Jboss / Resteasy - jboss

Is there a clean & easy way to enable Jackson implementation in Jboss - AS 7?
Aiming to work only with Jackson and not with Jettison.
I can see that Jboss has support for both:
/usr/share/jboss-as/modules/org/jboss/resteasy/resteasy-jettison-provider/main/resteasy-jettison-provider-2.3.2.Final.jar
/usr/share/jboss-as/modules/org/jboss/resteasy/resteasy-jackson-provider/main/resteasy-jackson-provider-2.3.2.Final.jar

This short tutorial explains how you can configure RESTeasy to use Jackson. You might also want to look at this article on setting up restful applications on JBoss AS 7.

Related

Does Jboss 7.1 AS supports ejb 2.1?

it seems jboss AS 7.1 supports ejb 2.1.Our ejb 2.1 based application is deployed on jboss 5 AS. We are migrating it to jboss7.1. but i want to know what are the additional configurations required to run ejb 2.1 without any errors?
EJB2 is still supported in AS7.x, the issue might be that AS7 is a new implementation and some of the tuning options and configuations are not available for AS7 - especially the EntityBean CMP.
There are some added for EAP6 (based on AS7) you might download the unsupported version.
Wildfly (the successor of JBossAS) will not continue to support EJB2 EntityBeans because EJB3.2 declare it as optional.
Note EJB2 session beans are still supported but I recommend to upgrade it to EJB3 this should faily simple.
You might keep the EJB2 interfaces to provide an interface for EJB2 clients, but I expect effort for the client as well as the lookup Strings changed.
If the appliation should be kept for the future I would recommend to migrate to EJB3

Jboss Wildfly resteasy upgrade

I've googled to find detailed working tutorial for update Jboss Wildfly resteasy to latest version (3.0.17) but seems without solutions.
I'm testing on wildfly 10.0.0.Final release-version: "2.0.10.Final"
with resteasy core version. First question how to list (from shell or from Gui) all core modules version in use?
From official documentation i'm using jboss-jaxrs-api_2.0_spec-1.0.0.Final version but i want use for my project resteasy 3.0.17
I can accept globally upgrade and/or instruction to use resteasy 3.0.17 only in my war project "bypassing" core wildfly resteasy implementation.
I read official Jboss Resteasy upgrade but without success.
Is there some guide or complete tutorial about manage modules on jboss wildfly ?
Or someone has already had these headaches and can share suggestions ?
Have a look at this post from JBoss forum:
https://developer.jboss.org/thread/274219
Basically from Wildfly 11 it will be possible to see the module versions on console and in regards to the upgrade, it's manual work.

migrate from JBOSS AS6 to wild fly

I know its a very high level question, but it will be very much help full if somebody can help me to kick start the migration.
So please provide some links or use full hints to start with it.
Also if somebody knows about delta changes between JBOSS AS 6 to Wild fly.
Major change which i know that our application uses-
JBOSS AOP
JBOSS Interceptors
and binds it in jboss-aop.xml
like below
<bind pointcut="execution(public * *.DBDAO >updateBO(com.test.model.TestClass, com.test.model.TestClass2))">
<interceptor-ref name="TestInterceptor"/>
</bind>
which is not supported by wild fly now.
And so there must be other thing s which might not be supported by wild fly.
Thanks.
According documentation:
Replace JBoss AOP Interceptors
JBoss AOP (Aspect Oriented Programming) is no longer included in JBoss AS 7. In previous releases, JBoss AOP was used by the EJB container. However, in AS 7, the EJB container uses a new mechanism. If your application uses JBoss AOP, you need modify your application code as follows.
Standard EJB3 configurations that were made in the ejb3-interceptors-aop.xml file are now done in the server configuration file. For a standalone server, this is the standalone/configuration/standalone.xml file. If you are running your server in a managed domain, this is the domain/configuration/domain.xml file.
Applications that integrate AOP interceptors into the EJB layer must be redesigned to use EJB3 interceptors and CDI. Server side interceptors can be changed to EJB3 interceptors, but there is no client side interceptor in AS 7.
Like AOP exist other changes you can see in: How do I migrate my application from AS5 or AS6 to WildFly and Experiences with migrating from JBoss AS 7 to WildFly 8.1
The last link refers to some changes that are not in the official documentation.
Here is whole migration guide from Red Hat. JBoss EAP 6.2 has similar architecture to WildFly so you can use it:
https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.2/html-single/Migration_Guide/index.html

reference for ejb jboss and eclipse development

is there a reference or book, maybe a tutorial that can get me started with ejb using the technologies that I have mentioned above?
thank you
You can take a look at the JBoss Tools if you're interested in developing Java EE applications in Eclipse.
If you already know EJB (and if you don't there is quite good Enterprise JavaBeans 3.1 book) you know you can develop your EJB's as plain POJO's just with annotations. No need for fancy plugins here.
You would, however, need a plugin to easily deploy your application to the server. In this case, take a look at these JBoss Tools and this topic.

which server I should go for JBoss or GlassFish

I am project I will be using following tech. JSF 2.0, Hibernate, Spring, jBPM, JAX-WS so I am confused between chosing server and I am locked between JBoss and GlassFish please suggest me why I should use the one. I will be using Netbeans 6.8
From a Development Perspective:
If you are using NetBeans then I think the easiest to integrate with will be GlassFish, simply because they come both from Sun and you will get the best out-of-the-box experience. While not mandatory, the Java EE Tutorial from Sun also emphasizes the use of NetBeans with GlassFish.
Nonetheless if you happen to use JBoss, it won't be difficult to integrate it on NetBeans.
From a Deployment and Long-term Maintenance Perspective:
See my answer to a similar question here.