[JBoss JIRA] Created: (JBIDE-3475) New deployment mechanism not working correclty on clustered or multi-server envs.
by Galder Zamarreno (JIRA)
New deployment mechanism not working correclty on clustered or multi-server envs.
---------------------------------------------------------------------------------
Key: JBIDE-3475
URL: https://jira.jboss.org/jira/browse/JBIDE-3475
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.CR2
Reporter: Galder Zamarreno
Priority: Critical
Fix For: 3.0.0.GA
There's something not working correctly with the new deployment mechanism:
I have a cluster of 2 nodes with an clustered EJB3 application deployed (SLSBs, SFSBs, Entities...etc).
When I start the 1st node, it works perfectly and after startup being completed, ear is deployed without
any issues.
After deployment is complete, I start the 2nd node and the EJB3 application is deployed again in the 1st
node and the 2nd node has no deployment whatsoever.
See attached logs + ear app.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 2 months
[JBoss JIRA] Created: (JBIDE-3586) java.lang.NumberFormatException then calling rich:editor
by Yura Zhishko (JIRA)
java.lang.NumberFormatException then calling rich:editor
--------------------------------------------------------
Key: JBIDE-3586
URL: https://jira.jboss.org/jira/browse/JBIDE-3586
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor Templates
Affects Versions: 3.0.0.CR2
Environment: RichFaces 3.3.0 GA
Reporter: Yura Zhishko
Assignee: Yahor Radtsevich
Priority: Critical
1) Open any page and add RichFaces 3.3.0 GA libraries
2) Add rich:editor component into source code
Next exception appears:
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NumberFormatException: multiple points)
at org.eclipse.swt.SWT.error(SWT.java:3777)
at org.eclipse.swt.SWT.error(SWT.java:3695)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3800)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
Caused by: java.lang.NumberFormatException: multiple points
at sun.misc.FloatingDecimal.readJavaFormatString(Unknown Source)
at java.lang.Double.parseDouble(Unknown Source)
at org.jboss.tools.vpe.editor.template.expression.VpeFunctionTldVersionCheck.exec(VpeFunctionTldVersionCheck.java:98)
at org.jboss.tools.vpe.editor.template.VpeTemplateConditionSet.test(VpeTemplateConditionSet.java:59)
at org.jboss.tools.vpe.editor.template.VpeTemplateConditionSet.getTemplate(VpeTemplateConditionSet.java:48)
at org.jboss.tools.vpe.editor.template.VpeTemplateSet.getTemplate(VpeTemplateSet.java:41)
at org.jboss.tools.vpe.editor.template.VpeTemplateManager.getTemplateImpl(VpeTemplateManager.java:320)
at org.jboss.tools.vpe.editor.template.VpeTemplateManager.getTemplate(VpeTemplateManager.java:305)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:442)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:264)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:624)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:559)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:264)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.updateElement(VpeVisualDomBuilder.java:1025)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.updateNode(VpeVisualDomBuilder.java:955)
at org.jboss.tools.vpe.editor.VpeController.notifyChangedInUiThread(VpeController.java:608)
at org.jboss.tools.vpe.editor.VpeController$1.runInUIThread(VpeController.java:477)
at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:94)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133)
Marked as critical because VPE refresh crashes
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 2 months
[JBoss JIRA] Created: (JBIDE-2805) Update JBossTools Features names to ease uninstall/update operations through Eclipse update framework
by Denis Golovin (JIRA)
Update JBossTools Features names to ease uninstall/update operations through Eclipse update framework
-----------------------------------------------------------------------------------------------------
Key: JBIDE-2805
URL: https://jira.jboss.org/jira/browse/JBIDE-2805
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Build/Releng
Affects Versions: 3.0.0.alpha
Reporter: Denis Golovin
Assignee: Denis Golovin
Fix For: 3.0.0.beta1
Now we have several features (see attached pictures). There is no common prefix for them and that doesn't help to ease update/uninstall. Now they are
scattered between installed items and it is difficult to find them in Installed Software list.
So my proposition is to have prefix JBT or JBoss Tools for all features to keep them together in Installed Software list. Another solution is to have pattern for feature names, for instance, JBoss <component name> Tools, so list would look like:
JBoss ESB Tools
JBoss Seam Tools
JBoss Protlet Tools
JBoss Struts Tools
JBoss ReachFaces Tools
JBoss WS Tools
JBoss Hibernate Console
JBoss AS Tools
e.t.c.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 2 months