[Anthony Estelita]

We just upgraded our MyEclipse and a few of the developers are complaining about the “Server” view. When you have an application that contains multiple war files the application status always shows a Status of “OK”. Previous version of MyEclipse the Status would change to “Redeploy” if any of the child war projects needed redeployed. How do we get the “Servers” view to act how it did prior to the 2013 release? It is quite annoying when you believe you are working/testing with the latest deployment when in reality you may not be. 🙁

Greatly appreciate any suggestions,
Anthony

====================================================================
Installation Summary:
====================================================================
*** Date:
Friday, September 13, 2013 3:01:13 PM PDT

*** System properties:
OS=Windows7
OS version=6.1.0
OS arch=amd64
Profile arch=x86_64
Window system=win32
Java version=1.6.0_43
Workspace=file:/C:/Projects/SIA_Projects/SourceCode/DEV/
VM Args=-Xmx512m
-XX:MaxPermSize=256m
-XX:ReservedCodeCacheSize=64m
-Dosgi.nls.warnings=ignore
-jar
C:\Users\AnthonyE\AppData\Local\MYECLI~2\plugins/OR47CC~1.JAR

*** Subscription information
Product Id: E3MP (MyEclipse Professional Subscription)
License version: 3.0
Full Maintenance Included
Subscription expiration date (YYYYMMDD): 20140503
Number of users: 5

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 2013 SR2
Build id: 11.0.2-20130823

Blueprint: N/A

com.genuitec.eclipse.mobile.feature – 11.0.2.201309031939
com.genuitec.myeclipse.database – 11.0.2.me201309021924
com.genuitec.myeclipse.desktop – 11.0.2.me201309021924
com.genuitec.myeclipse.enterprise.workbench – 11.0.2.me201309021924
com.genuitec.myeclipse.geronimo – 11.0.2.me201309021924
com.genuitec.myeclipse.glassfish – 11.0.2.me201309021924
com.genuitec.myeclipse.icefaces.feature – 11.0.2.me201309021924
com.genuitec.myeclipse.imageeditor – 11.0.2.me201309021924
com.genuitec.myeclipse.jboss – 11.0.2.me201309021924
com.genuitec.myeclipse.jetty – 11.0.2.me201309021924
com.genuitec.myeclipse.jonas – 11.0.2.me201309021924
com.genuitec.myeclipse.jrun – 11.0.2.me201309021924
com.genuitec.myeclipse.jsf – 11.0.2.me201309021924
com.genuitec.myeclipse.maven – 11.0.2.me201309021924
com.genuitec.myeclipse.oracle – 11.0.2.me201309021924
com.genuitec.myeclipse.orion – 11.0.2.me201309021924
com.genuitec.myeclipse.persistence – 11.0.2.me201309021924
com.genuitec.myeclipse.reports – 11.0.2.me201309021924
com.genuitec.myeclipse.resin – 11.0.2.me201309021924
com.genuitec.myeclipse.struts – 11.0.2.me201309021924
com.genuitec.myeclipse.sun – 11.0.2.me201309021924
com.genuitec.myeclipse.tomcat – 11.0.2.me201309021924
com.genuitec.myeclipse.uml2 – 11.0.2.me201309021924
com.genuitec.myeclipse.visualvm – 11.0.2.me201309021924
com.genuitec.myeclipse.visualvm.server – 11.0.2.me201309021924
com.genuitec.myeclipse.weblogic – 11.0.2.me201309021924
com.genuitec.myeclipse.websphere – 11.0.2.me201309021924
com.genuitec.myeclipse.ws – 11.0.2.me201309021924
org.eclipse.birt – 4.2.1.me201309021924
org.eclipse.datatools.connectivity.feature – 1.10.1.me201309021924
org.eclipse.datatools.enablement.feature – 1.10.1.me201309021924
org.eclipse.datatools.modelbase.feature – 1.10.1.v201208161415-7707FCcNBHLCgLUEdUb
org.eclipse.datatools.sqldevtools.feature – 1.10.1.me201309021924
org.eclipse.emf – 2.8.1.v20120917-0436
org.eclipse.gef – 3.8.1.201208200205
org.eclipse.graphiti.feature – 0.9.2.v20130211-0913
org.eclipse.jpt.jpa.feature – 3.2.1.me201309021924
org.eclipse.jpt.jpadiagrameditor.feature – 1.1.1.me201309021924
org.eclipse.jst.common.fproj.enablement.jdt – 3.4.0.me201309021924
org.eclipse.jst.enterprise_ui.feature – 3.4.0.me201309021924
org.eclipse.jst.server_adapters.ext.feature – 3.3.101.me201309021924
org.eclipse.jst.server_adapters.feature – 3.2.200.me201309021924
org.eclipse.jst.server_ui.feature – 3.4.0.me201309021924
org.eclipse.jst.ws.axis2tools.feature – 1.1.200.me201309021924
org.eclipse.m2e.feature – 1.2.0.me201309021924
org.eclipse.sapphire.platform – 0.3.0.201106221325
org.eclipse.wst.common.fproj – 3.4.0.me201309021924
org.eclipse.wst.server_adapters.feature – 3.2.201.me201309021924
org.eclipse.xsd – 2.8.0.v20120917-0436
org.springframework.ide.eclipse.feature – 2.9.1.me201309021924

com.microsoft.tfs.client.eclipse.feature – 10.1.0.201101271439
edu.umd.cs.findbugs.plugin.eclipse – 2.0.2.20121210
fr.obeo.acceleo.bridge.feature – 2.6.0.me201309021924
org.eclipse.cvs – 1.3.201.v20130116-085741-7B79FJKAkF7BG7NGE4IAJT
org.eclipse.draw2d – 3.8.1.201208200205
org.eclipse.epp.mpc – 1.1.1.I20110907-0947
org.eclipse.equinox.p2.core.feature – 1.1.0.v20121211-153934-8297FndFWmE7h7Bpz-vcqkxyKz0
org.eclipse.equinox.p2.discovery.feature – 1.0.100.v20120524-0542-4-Bh9oB58B5W8E28KKNEK
org.eclipse.equinox.p2.extras.feature – 1.1.0.v20121211-153934-7A6FEcDiVOTg2RYDuZuFz-L2z00w
org.eclipse.equinox.p2.rcp.feature – 1.1.0.v20121211-153934-785EoBqNKNZz-DW7sUc8hFwz00wd
org.eclipse.equinox.p2.user.ui – 2.2.0.v20121212-204731-62DG9JXTlTj-UXcQ2y3NLn6U4Z3H
org.eclipse.help – 1.4.1.v20120912-145617-8R7xFOXFLWUl7PpMEeZNIGkb4
org.eclipse.jdt – 3.8.2.v20130116-090414-8-8nFu3FNOfwKLRttdWQJ-2z-_83
org.eclipse.jsf.feature – 3.4.1.me201309021924
org.eclipse.ocl – 3.1.0.v20110606-1427
org.eclipse.pde – 3.8.2.v20130116-091538-7c7wFj0FFt6Zr9bc77L7JFNNa
org.eclipse.platform – 3.8.1.v20130118-180812-9jF7oIBFG8eU2pim-VbIlTuQjY0RWWK3x-bv4I
org.eclipse.rcp – 3.8.2.v20130118-180157-96BuGOZFxwOAeG8Ofmqicz0tPK
org.eclipse.wb.core.feature – 1.6.0.r42x201305211944
org.eclipse.wb.core.java.feature – 1.6.0.r42x201305211947
org.eclipse.wb.core.ui.feature – 1.6.0.r42x201305211950
org.eclipse.wb.core.xml.feature – 1.6.0.r42x201305211955
org.eclipse.wb.doc.user.feature – 1.6.0.r42x201305212003
org.eclipse.wb.layout.group.feature – 1.6.0.r42x201305212007
org.eclipse.wb.rcp.SWT_AWT_support – 1.6.0.r42x201305212048
org.eclipse.wb.rcp.doc.user.feature – 1.6.0.r42x201305212036
org.eclipse.wb.rcp.feature – 1.6.0.r42x201305212028
org.eclipse.wb.swing.doc.user.feature – 1.6.0.r42x201305212039
org.eclipse.wb.swing.feature – 1.6.0.r42x201305212042
org.eclipse.wb.swt.feature – 1.6.0.r42x201305212024
org.eclipse.wb.xwt.feature – 1.6.0.r42x201305212050
org.sonatype.m2e.mavenarchiver.feature – 0.15.0.201207090125

Eclipse startup command=-os
win32
-ws
win32
-arch
x86_64
-showsplash
-launcher
C:\Users\AnthonyE\AppData\Local\MyEclipse Professional\myeclipse.exe
-name
Myeclipse
–launcher.library
C:\Users\AnthonyE\AppData\Local\MyEclipse Professional\plugins/org.eclipse.equinox.launcher.i18n.win32.win32.x86_64_3.2.0.v201103301700\eclipse_3215.dll
-startup
C:\Users\AnthonyE\AppData\Local\MyEclipse Professional\plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
-exitdata
1b88_60
-install
C:\Users\AnthonyE\AppData\Local\MyEclipse Professional
-clean
-vm
C:\Users\AnthonyE\AppData\Local\MyEclipse Professional\binary/com.sun.java.jdk.win32.x86_64_1.6.0.u43/bin/javaw.exe

[support-pradeep]

Anthony,

Sorry that you are seeing this issue.

Inorder to help us investigate further, can you please mention the application server name and version in which you are seeing this issue ?

If possible, please attach a sample project which exhibits this issue to help us replicate the issue at our end.

[Anthony Estelita]

* We are using Jboss 7.x Application Server.
* We see this issue on all 7 of our .ear web applications
* Each of our .ear web applications consist of
* multiple .war web modules
* multiple .har hibernate modules
* multiple .jar java libraries

Each .ear application shows a status of “OK” when a child .war web module shows “Redeploy”. Prior to the latest version of myEclipse, the .ear applications would reflect the status of the child .war web modules. Unless you have the .ear web applications expanded you will not know that you need to “Redeploy”.

I am also attaching a set of screen shots that will hopefully help.

Thank you,
Anthony

Attachments:

You must be logged in to view attached files.

[support-pradeep]

Anthony,

Thanks for pointing to this. We could replicate the issue at our end. We have filed a PR for the dev team to investigate this issue.

Sorry for the inconvenience caused.

[Brian Fernandes]

Anthony,

I realize I hadn’t replied to this post. I wanted to let you know that this is actually how we designed it – the OK signifying that the EAR and its own resources were in-synch, you would get a redeploy status when resources like the application.xml for instance are not in synch.

I agree that it does make sense to indicate that the modules are out of synch as part of the EAR’s status – we’ll be fixing this in our next release.

Thanks for pointing this out.

[Author]

Posts