- This topic has 12 replies, 4 voices, and was last updated 13 years, 2 months ago by
.
-
Posts
-
JBoss 7 not appearing in Servers for latest MyEclipse.
JBoss 7 is reasonably different to Jboss X..6.
Keen to have it working.
The Manual Deployment may break…
Readme for AS 7:
“By default, auto-deploy of zipped content is enabled, and auto-deploy of
exploded content is disabled. Manual deploy mode is strongly recommended for
exploded content, as exploded content is inherently vulnerable to the scanner
trying to auto-deploy partially copied content. Manual deploy mode also allows
deployment resources (e.g. html and css files) to be replaced without
triggering a redeploy of the application.”I hope you guys can still make your exploded deployment work.
It is extremely productive to change a file in MyEclipse and see the results virtually instantly on the web page.balanceofpower ,
Currently we do not have JBoss 7 support for MyEclipse 9.1 and wei have already filed an enhancement request for JBoss 7. Sorry for the inconvenience caused.
@support-joy wrote:
balanceofpower ,
Currently we do not have JBoss 7 support for MyEclipse 9.1 and wei have already filed an enhancement request for JBoss 7. Sorry for the inconvenience caused.
Any progress on this.
Please also ensure that they have tested exploded deployment as its pretty useless to me unless that works!balanceofpower,
JBoss 7 support would be available on ME 10. This is tentatively scheduled for released in the first week of October.
JBoss 7 support would be available on ME 10. This is tentatively scheduled for released in the first week of October
So looking forward to the new version. It is critical to our time-lines…
I hope, beyond hope, that you got the development and testing team to do the UAT on the project I supplied? This project does not use a build system in any way and provides a hugely productive environment and soon we will be having to move to CDI + Seam 3 and Jboss 6 (or more probably 7).
There will be no competitive advantage to stay with MyEclipse to us if you don’t get this exploded way of working to work… 🙁
I am happy to have a pre-release version of 10 to see if it works…
This was part of an Email to another Architect… you may find the insights useful:
Our IDE (MyEclipse) supports exploded deployment and to the user it LOOKS LIKE you don’t need a build script (SHOCK HORROR).
Set up your code laid out 100% like an EAR (or WAR for J6EE); then you set up your server and point MyEclipse at the server and MyEclipse will handle moving files through to the server without ANY build scripts when you tell it to deploy as an exploded deployment. To the user it appears that you are coding on the server as ANY changes you make are immediately visible on the “site” just be refreshing the page or going to the relevant page. WOW THIS MAKES FOR FAST DEVELOPMENT.There are some exceptions:
Changing a method signature as a message pops up saying its too big a change and asks you to re-start the server… but how often do you do that 😉 and 45 seconds later the server is re-started and you carry on…
Changing the few XML files (this is almost eliminated in JSR299 as nearly everything possible is done via annotations now).PLEASE tell me that the project I supplied will be part of the UAT for the shortly to be released version 10…. you are stopping a number of projects being upgraded as Exploded deployment is too important for us to lose.
JBoss 7 now in list but exploded deployment not working.
This refers:
http://community.jboss.org/message/635179#635179
JBoss7 is radically different from previous versions and hooks have been supplied to allow MyEclipse (IDEs) to handle exploded deployment properly (allegedly).
balanceofpower ,
Please refer – https://www.genuitec.com/forums/topic/please-add-support-for-j6-ee/#post-320895
Since this issue is being addressed in the above post, I am closing this post here.
