I have just gotten Wildfly 8.0 running and integrated with Eclipse (Kepler). I've tried to deploy the following jBPM 5.4 files:
designer
drools-guvnor
jbpm-form-builder
jbpm-gwt-console
jbpm-gwt-console-server
jbpm-human-task-war
but they do not deploy - numerous errors. I just placed them in the .\deployments folder which works under JBoss 7.1. Is this expected behavior? Does this mean that if I want to run Wildfly (which fixes the failure to clean up the 1GB of deployed jBPM files upon shutdown) I have to upgrade everything to the jBPM 6 CR2?
Thank you.
Al
I would recommend you to upgrade to 6.x, we are all working with that version now, so if you have troubles with that let us know and we can looking to fix it.
Related
I'm new in JBoss Developer Studio.
Where I can find example, how I can make fuse integration project and RUN it on server? I cann't run my test project on server, I see a lot of errors, but my project consist only LOG component. And Why I cann't run this project on EAP 7.1 or Fuse 6.3?
i have JBoss EAP 7.1 and JBoss Fuse 6.3.
Thank you in advance, and sorry for my English)
Offtop:
When I use Mule, I can make and run my first project for 10-15 minutes. But in Developer Studio it's very... difficult. I wasted 2 days without result
I am sorry that you are facing problems.
I would suggest you try to read the documentation at https://access.redhat.com/documentation/en-us/red_hat_jboss_fuse/6.3/pdf/tooling_tutorials/Red_Hat_JBoss_Fuse-6.3-Tooling_Tutorials-en-US.pdf . It is a good starting point for writing camel routes with the JBoss Fuse Tooling. I would also recommend you learn more about Apache Camel at http://camel.apache.org as the tooling is for Camel.
Hope that helps,
Lars
After upgrading my Eclipse installation to Luna (from Kepler), my JBoss servers started being overly pedantic with the redeployment of my web projects: even if I change a JavaScript file, a deployment replacement begins and takes significant amount of time. The same happens for JSP files too.
I've set Publishing to Automatically publish when resources change (as it was in Kepler), I've deleted/added JBoss 7.0 several times, tried various combinations of the checkboxes in Deployment Scanners & Application Reload Behavior, the issue persists though.
Configuration:
Eclipse Luna 4.4
JBoss Tools 4.2 beta 2
JBoss server 7.0
After searching further, I found that this was a bug in the beta 2 version of JBoss Tools 4.2 for Luna.
As answered here, beta 3 of JBoss Tools fixes this issue.
I need to migrate from Jboss 5.1.0 GA to any other that supports jdk 1.7.
I'm currently using jboss 5.1 with seam 2, jdk 1.6 and sqlserver 2008 r2.
What community version of Jboss is recommended for jdk 1.7 and why?
Thanks in advance!
You can actually get JBoss AS 5.1.0 GA to run on JDK 7, see JBAS-6981. All of the following options will work with JDK 7:
JBoss AS 5.1.0 (plus the fix for JBAS-6981)
JBoss AS 6.1.0
JBoss AS 7.1.1
JBoss EAP 6.2
WildFly AS 8 CR 1
The right solution depends on your situation:
The simplest solution with the least risk is to stay with JBoss AS 5.1.0 and fix JBAS-6981 yourself. We did that and ran with it for over a year and it worked fine. Note however that JBoss AS 5.1.0 is end of life, eg. there aren't any security patches available.
If you don't want to fix JBAS-6981 yourself you can go with JBoss AS 6.1.0. This should be quite a simple migration because it builds on the same architecture and has the same disk layout. Note however that it is Java EE 6 which means among other things standardized JNDI names. Depending on your application this can have quite a bit impact — or none at all. Note however that JBoss AS 6.1.0 is end of life, eg. there aren't any security patches available.
The next "stable" community version is JBoss AS 7.1.1 with brings a whole new architecture. Depending on your application that can be quite a large migration — or a really simple one. However I would recommend against JBoss AS 7.1.1 as it's buggy as hell. Note there won't be any future releases for JBoss AS 7.1.1 as well.
JBoss EAP 6.2 builds on JBoss AS 7.1.1 (AS 7.3 actually) and contains many bug fixes (and some features). You either need to build it from source or get a license from Red Hat. There will be patches for EAP 6.2.
The current in development community version is WildFly AS 8 CR1. As you can see from the version name there isn't a stable release yet. And it contains a whole new servlet engine, which makes a whole lot of people nervous. I would only use it if you have really good integration tests.
I don't know what the situation regarding Seam is for any of them.
Note that sooner or later you'll have to migrate to a newer version of JBoss AS anyway. To judge how hard the migration will be you first need to know what dependencies on JBoss AS you have in your code.
I have downloaded the Liferay 6.1 with jboss 7.1.1 Bundle and Liferay IDE(Eclipsce Juno).All I have to do is to develop Liferay Project and running it on Jboss server.
I can able to run and open liferay portal in localhost:8080/
I am having issues in developing Liferay portal project.As default server adapter for Liferay in IDE is Tomcat 7.0 and I couldn't able to find Jboss server adapter.I tried by running and deploy it on Tomcat and running the Jboss server by running standalone.bat file.
Please advise and help in develop and running Liferay project on Jboss
There's guide in Liferay Wiki about developing with non-Tomcat Liferay bundles. There you can read about the disadvantages of that kind of development and how to do it if you still want.
But I agree, developing with Tomcat is definetely the better idea.
Liferay IDE is meant for development with Tomcat only since tomcat's start-up time, its simple structure and comparatively easy configuration makes it ideal for a development environment.
If you are development plugin projects like themes, portlets, hook, layouts etc then if it works on tomcat it would work on any other server running with Liferay, so during development you can use tomcat and then when you have completed your development iteration (i.e. when your project is ready to be deployed for testing or for stage environments) you can deploy the WAR to Jboss for testing and can do some testing to see if it works fine.
Since the plugins are made in such a way as to be independent of the underlying Server, there should not be any issues developing them on Tomcat and then running them on Jboss.
Hope this helps.
I achieved it through a work around, steps mentioned # https://www.liferay.com/community/forums/-/message_boards/message/17864836
Benefits of Liferay IDE plugin+ JBoss as runtime configured in IDE.
Only issue is you'll need to use any other eclipse based IDE which supports JBoss AS 7.1.1 as normal server/runtime (like JBoss Developer Studio).
please let me know what are the changes i have to do if i want to deploy the application which was running in jboss 4 and built with ejb 2.0
I am trying to deploy the same ear which was running in jboss 4 and built with ejb 2.0
but i am getting deployment exceptions.
There's a fairly big list, but thankfully it's been documented by some kind people that have done it before. Here's the JBoss community documentation on likely migration issues:
Migration from JBoss 4 to 5