MyEclipse :: View topic - Please add support for J6 EE

MyEclipse: Please add support for J6 EE

balanceofpower - Sep 08, 2011 - 11:36 PM
Post subject: Please add support for J6 EE

I open java files and a lot of annotations don't have attached documentation.
As an example the CDI type annotations @Inject does not have any "doco" when you hover or use ctrl-space for completion.

Quote:

Note: This element neither has attached source nor attached Javadoc and hence no Javadoc could be found.

I am using JBoss's Weld for CDI.

Secondly; its been quite a few years and I was wondering if more of the JBoss Tools can be added to MyEclipse. I believe they were incompatible for a long while.

support-joy - Sep 09, 2011 - 09:12 AM
Post subject:

balanceofpower,

We are looking into the issue of documentation related to annotations in Java EE 6.

We are doing a JBoss Tools upgrade in ME 10.1, but I am afraid it is not possible to add JBoss Tools upgrade right now. Could you elaborate what features of JBoss Tools you are looking for, so that we can ensure these get included in 10.1 version?

Sorry for the inconvenience.

balanceofpower - Sep 09, 2011 - 01:27 PM
Post subject:

CDI
Weld,
Seam 3
Drools

balanceofpower - Sep 14, 2011 - 05:21 AM
Post subject: Addition of a "MyEclipse project"

Here is a MyEclipse project.

I reverse engineered from a war file created through the Seam3 drop.

It does run up (well since jBoss 6 does not work I had to run up through a cmd window on Windows)...

Please use this as part of your UAT testing for your next drop as a number of things, in MyEclipse, don't seem to validate properly.

I can supply the project file (cant be attached!)

support-joy - Sep 14, 2011 - 10:46 AM
Post subject:

balanceofpower,

Could you send your project as an attachment to support@myeclipseide.com . Please include the weblink of this post and steps to reproduce. This project would not be visible and would be treated as strictly confidential for our internal testing. Please add ATTN:Joy in the subject for quick tracing.

Thank you for your help.

balanceofpower - Sep 23, 2011 - 01:02 AM
Post subject:

Please can you advise when there may be a version (patch or new) of MyEclipse that I can actually use?

Looking forward to JBoss 6 and 7 being supported.

Have you managed to debug all the errors in the supplied project I kindly supplied.

support-joy - Sep 26, 2011 - 08:31 AM
Post subject:

balanceofpower,

Apologies for the late reply. MyEclipse 10 is going to support JBoss 7. It is tentatively due on second week of October. Thank you for sending in your project. Our dev teams have included this in the UAT testing of your issues.

balanceofpower - Sep 26, 2011 - 08:51 AM
Post subject:

support-joy wrote:

Happy to let you release the Project as an example (download) of CDI (+Seam 3 extensions)... it shows Exploded deployment.

It also should be used as part of ME10 UAT.

balanceofpower - Oct 23, 2011 - 07:48 AM
Post subject:

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).

balanceofpower - Nov 01, 2011 - 07:17 AM
Post subject:

Please can you advise when a version will be available (even one for me to test).

Support-Brian - Nov 01, 2011 - 09:31 AM
Post subject:

Tony,

We are planning to MyEclipse 10 today on Pulse, installers may take an additional day or two to appear.

1) We have fixed the JEE 6 annotation issue.
2) We also have JBoss 7 support.
3) In our internal testing, we were able to deploy your project without issue to JBoss 7, however, there were some Seam related errors at runtime which I'm afraid we did not have the time to look into for 10.0; unfortunately we had too many other moving parts and an already delayed release.
4) There are also some flexible deployment enhancements (which I will talk to here: http://www.myeclipseide.com/PNphpBB2-viewtopic-t-24072.html)

A JBoss tools refresh is planned for the next major release, but we will most likely not be integrating the tools you requested. However, the refresh should allow you to add these to MyEclipse without issue - the aim is to try and make MyEclipse as compatible as possible with additional tools and I realize the current state makes it impossible.

If you try 10.0 and you still experience issues with deployment, I will work with you personally on making sure your needs are met as long as they are viable. Most of the flexible deployment support you see in 10.0 has been a result of rather intense customer interaction.

balanceofpower - Nov 01, 2011 - 10:14 AM
Post subject:

I tried pulse but it just crashed (W7 x64).
I will try again tomorrow (bedtime in this timeline).
A full installer for 64 base version would be what I normally download.

balanceofpower - Nov 02, 2011 - 09:11 AM
Post subject:

No all inclusive installers yet.
I tried Pulse but got that attached response.

Thx for your support.

Can't want to try it out...

support-tony - Nov 02, 2011 - 10:46 AM
Post subject:

Tony,

That error may happen if you downloaded the 32 bit version of Pulse but only have a 64 bit Java installed (or vice versa). If this is the case, please download the correct version of Pulse.

Hopefully, the offline installers won't be too much longer in coming.

balanceofpower - Nov 02, 2011 - 06:37 PM
Post subject:

Humm...

Looking forward to installer...

support-tony - Nov 03, 2011 - 04:53 AM
Post subject:

OK, Tony. In that case, I'm stumped, especially as I just tried it on Win 7 64 bit with only JDK 7 installed, and had no problem. This would be one for the pulse team.

However, the release 10 installer is there now, so go for it!

balanceofpower - Nov 05, 2011 - 04:51 AM
Post subject:

Hi Tony....
http://community.jboss.org/thread/174488
:(

support-tony - Nov 07, 2011 - 07:49 AM
Post subject:

Tony,

That's unfortunate. Thanks for posting on the JBoss forum; I see that one of the respondents intends to contribute here, which would be useful. I tried adding a .skipdeploy marker file manually (as mentioned here), but JBoss didn't seem to honor it (I just added an index.jsp.skipdeploy file to a default Web Application); JBoss undeployed and redeployed the application when I changed the JSP.

However, I think you need more than just html page changes not triggering a redeploy. For example changes to Java code (apart from method signature changes) shouldn't trigger a redeploy, only a re-load of the class file. I don't think marker files can help there.

I'll pass this on to development to see if they can help.

balanceofpower - Nov 07, 2011 - 08:16 AM
Post subject:

support-tony wrote:

I'll pass this on to development to see if they can help.

This is great;
The JBoss guys are willing to help; we need the developers there and the JBoss guys to talk.

Should not take long and may give MyEclipse a competitive edge as a by-product!

balanceofpower - Nov 10, 2011 - 05:56 AM
Post subject:

Be great to hear that JBoss and MyEclipse have talked and sorted this out.
Any updates?

Support-Brian - Nov 10, 2011 - 04:18 PM
Post subject:

Tony,

I just checked with my team and we have the manual deployment mode working. The preference page where you configure JBoss 7 will now allow you to choose whether you would like to keep the existing auto deployment behavior too.

Do you have any other problems with JBoss 7 that need attention?

I'm planning to release this as as an update to MyEclipse 10 near the end of next week on our milestone stream. There will be online installers for this stream and if you already have a base MyEclipse 10 install, running this installer will result in a minimal additional download which will download only the changed plugins.

balanceofpower - Nov 10, 2011 - 07:11 PM
Post subject:

Hi Joy,

Quote:

I just checked with my team and we have the manual deployment mode working. The preference page where you configure JBoss 7 will now allow you to choose whether you would like to keep the existing auto deployment behavior too.

A little confused as to your terminology... hopefully we are on the same page...

Quote:

manual deployment mode

I had no problem with what I believe was manual deployment working before ! I will take your work for the fact a bug has been cleared.

Quote:

whether you would like to keep the existing auto deployment behavior too

The discussions in forums with JBoss indicated they had put in specific capability for "exploded deployment" for JBoss 7 over and above what has ever been available before.

Please can you confirm that the process as described here:
http://community.jboss.org/thread/174488
will work and your developers have tested changing code (xhtml and java source) and seen that the application is not re-deployed etc.
I did provide an example project for them to play with.

I still expect that changing a method signature willl cause JBoss to die and require a re-start but, as JBoss developers have said, they have added a LOT of hooks in so it may not... I am sure they have learnt a lot from doing support for JRebel etc.

I look forward to having a chance to see how well the integration works.

X Cross posted to JBoss AS 7 Forums

Support-Brian - Nov 10, 2011 - 09:25 PM
Post subject:

Tony,

To clarify, the deployment was working, but each change would cause your app to restart because of the forced auto-deploy setting in the configuration file. With the modifications we have made now, you can:

a) Continue to keep this behavior

b) Turn the auto-deploy setting off on our preference page (it will be off by default) and here JBoss will not restart the app for changes to resources and class files. This has been tested & I believe we are using additional metadata (that has been referenced in the JBoss thread) to achieve the right behavior here.

I will let you know when a build with this fix is publicly available; appreciate your support.

balanceofpower - Nov 10, 2011 - 09:46 PM
Post subject:

Hi Brian,

Great support.

I am keen to get it to test.

Thx.

balanceofpower - Nov 19, 2011 - 01:57 AM
Post subject:

Support-Brian wrote:

Tony,

b) Turn the auto-deploy setting off on our preference page (it will be off by default) and here JBoss will not restart the app for changes to resources and class files. This has been tested

Great; I am looking forward to doing that...

Support-Brian wrote:

I believe we are using additional metadata (that has been referenced in the JBoss thread) to achieve the right behavior here.

It is quite sad that developers really DON'T talk to each other.
The JBoss guys have said they have added numerous things into JBoss7 to support the IDE writers... and from that comment your development team has figured out what they are.... Why not TALK to them and give MyEclipse an edge?

Support-Brian wrote:

I will let you know when a build with this fix is publicly available; appreciate your support.

Is there a date for this...
I keep checking and no updates appear and you are silent on the matter.

Support-Brian - Nov 20, 2011 - 08:09 PM
Post subject:

Tony,

10.0.1 is now available for you to test; please see this link for further details on fixes and how to get it. I hope this addresses your issues. If not, let us know and we'll continue to work on it with you. If it does work but you have a "but I wish you could do xyz too" request, let us know and we can try to implement it, if viable.

Quote:

It is quite sad that developers really DON'T talk to each other.

I agree; all I can say is that we are moving in this direction now and attempting to provide superlative support, especially when driven by specific customer need.

Quote:

Is there a date for this...
I keep checking and no updates appear and you are silent on the matter.

It is hard to set dates with a milestone release as the target changes given issues we see with MyEclipse in everyday use. The aim, however, is to provide an update as soon as is possible, irrespective of the number of fixes. This is why I mentioned earlier that I would let you know when a build was available - if you are subscribed to this thread you should be automatically notified when an update is posted without having to come back here and check repeatedly. Do you have any alternative or additional suggestions on how communication could be improved?

balanceofpower - Dec 06, 2011 - 08:50 PM
Post subject:

It seems to work well apart from when I have to restart the JBoss7 server.

Things like updates to messages.properties need a server restart to be picked when they have changed; but when the server is simply restarted using MyEclipse then it does not tell JBoss7 to do a "proper deploy".

I suspect that the .dodeploy is not being added on the server deploy area on re/start so JBoss is not forced to do a full re-deploy.

If the guys can hack this in then it would be super great as it's not that often you want NOT to do a full deploy when the server starts from within MyEclipse.

balanceofpower - Dec 07, 2011 - 04:41 AM
Post subject:

Another problem (probably mine!) is that I am getting reports of missing Jars when they are no-where to be found in my project.
Yes I did add them; but have removed them since.. but MyEclipse is claiming I have not :O
Screeny attached...

balanceofpower - Dec 07, 2011 - 07:35 AM
Post subject:

Found no refs in the .files (project, classpath) etc.
I deleted all libraries and re-added.
Closed all other projects.
Now the problem has gone away... including a few other strange problems that seems to come from non-existent libraries hanging about (possibly from other projects).

balanceofpower - Dec 07, 2011 - 07:35 AM
Post subject:

This however is still a problem (minor niggle)

balanceofpower wrote:

support-tony - Dec 07, 2011 - 08:55 AM
Post subject:

Tony,

Thanks for your observations; we have someone looking at them now.

I'm glad you've managed to pare the problems down to a "minor niggle". It looks like we're getting there!

Support-Brian - Dec 08, 2011 - 06:57 AM
Post subject:

Tony,

Glad we are moving along. Not quite sure I understand your request regarding deployment.

When you make a change in the properties file, MyEclipse will push the changed file to the server. Since your application will not react to this as expected, you will be forced to restart the server. At this point the server should re-load your application from the deployed location - which now does contain the updated properties file and you should be all set. Redeploying the application should not be necessary.

Can you please elaborate?

balanceofpower - Feb 20, 2012 - 12:58 AM
Post subject:

Ok, I have exploded deployment working great (even in a maven setup on another project which pleasantly surprised me!) and as requested I was asked to report back and problems I found.

Here goes:

1. Debug of files that I update is FUBAR.. It is like the code debugger seems to still keep the old line numbers... the only way to clear this is to stop the server and restart; which sort of defeats the point of exploded deployment... I should be coding for hours before doing a sever restart. Works fine with XHTML and EL line reporting it seems.

2. In another project on Tomcat I use exploded deployment and quite often have to go into webapps and remove files that have "leaked out" of my project into the webapps directory.

Java development projects in Both Spring and CDI.
Build id: 10.0-20111028
+SVN, Git

balanceofpower - Feb 20, 2012 - 01:00 AM
Post subject:

Quote:

1. Debug of files that I update is FUBAR.. It is like the code debugger seems to still keep the old line numbers... the only way to clear this is to stop the server and restart; which sort of defeats the point of exploded deployment... I should be coding for hours before doing a sever restart. Works fine with XHTML and EL line reporting it seems.

This might be JUST the Maven laid out project.. I will try to find out.

balanceofpower - Feb 20, 2012 - 01:05 AM
Post subject:

Quote:

Glad we are moving along. Not quite sure I understand your request regarding deployment.

When you make a change in the properties file, MyEclipse will push the changed file to the server. Since your application will not react to this as expected, you will be forced to restart the server. At this point the server should re-load your application from the deployed location - which now does contain the updated properties file and you should be all set. Redeploying the application should not be necessary.

Can you please elaborate?

It was promised some time back that you could do a hot deploy but pick a "template" (i.e. which packages/jars to omit/include or whatever when you exploded deploy).. making testing easy without a need for a build/deploy script as you just pick a template at exploded deployment time and either are in test config or not...

What you say about properties files is what I find; I can live with that; Its not like you change them THAT often and seeing ???some_lable??? on the screen for inl8 is not a big issue as you wait till the next server restart.

Support-Brian - Feb 20, 2012 - 07:05 PM
Post subject:

Tony,

I assume you are still deploying to JBoss 7 and using MyEclipse 10.0.1?

1) Debug issue
Can you please confirm exactly what files you are updating? Java classes or JSP files, for instance? Also, you do need to start the server in Debug mode for hot synch with classes to work, but I'm sure you are doing that already. Can you confirm that your changes are actually getting to the server (i.e. your application behaves differently, according to the changes you made) but it's just debugging that is messed up? Please let us know if you figure out if the problem only exists for Maven project or is independent of Maven.

2) Deployment Filters
If you go to Project Properties > MyEclipse > Deployment Assembly, you can specify what folders in your source map to destinations in your deployed locations. However, this feature is still under development and libraries and containers are not fully supported yet. Would this be sufficient for your present needs?

balanceofpower - Feb 20, 2012 - 07:57 PM
Post subject:

Support-Brian wrote:

Updating Java Classes. Both projects are JSF projects and not that complicated yet.
I always run in debug mode as its so quick its not a problem.
The changes do go to the server; as I can see the code stepping over the wrong lines!
Still working on maven question... had a horse problem last night!

I will wait for the full version of the deployment system as I cant easily switch in/out stubs etc. by selecting a template of groups... Nice to see progress though.

i4073 - Feb 21, 2012 - 06:57 PM
Post subject:

I am having the same issue. Actually posted my question before I realize there is already a topic on this. See http://www.myeclipseide.com/index.php?name=PNphpBB2&file=viewtopic&p=129449#129449

Will be following this topic closely.

Support-Brian - Feb 23, 2012 - 12:05 PM
Post subject:

Tony,

Thanks for the info, we'll test with JSF projects and JBoss 7; if you find any additional information, do pass it along.

i4073, we responded to your other thread.