July 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-1782) Reorg'd SVN structure for JBDS product / extras / techpreview / soa-tooling sites breaks Hudson jobs

by Nick Boldt (JIRA)

Reorg'd SVN structure for JBDS product / extras / techpreview / soa-tooling sites breaks Hudson jobs ---------------------------------------------------------------------------------------------------- Key: JBDS-1782 URL: https://issues.jboss.org/browse/JBDS-1782 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Build Affects Versions: 5.0.0.M3 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 5.0.0.M3 Old structure had all features in product/features/ folder, but Denis moved these into extras/features/ and so on. Result is "non readable pom (no such file)" errors in Hudson. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBDS-1712) 4.1 Install metadata/display for users refers to the BPEL editor as having "best effort" support.

by Len DiMaggio (JIRA)

4.1 Install metadata/display for users refers to the BPEL editor as having "best effort" support. ------------------------------------------------------------------------------------------------- Key: JBDS-1712 URL: https://issues.jboss.org/browse/JBDS-1712 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: SOA Platform Affects Versions: 4.1.0.CR2 Environment: Version: 4.1.0.CR2 Build id: v20110705-1603-H948-CR2 Build date: 20110705-1603 Reporter: Len DiMaggio Attachments: Screenshot-5.png The text displayed during the install from: http://www.qa.jboss.com/binaries/RHDS/updates/development/4.1.0.CR2_extras/ States: "Contains BPEL Editor features (Certified). Features certified with JBoss Developer Studio have been tested by Red Hat. We will provide best-effort assistance on using these plugins." As of 4.1.1 and SOA-P 5.2 the BPEL editor is full supported - we'll need to update this for 4.1.1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

10
38
0 / 0

[JBoss JIRA] Created: (JBDS-1700) include github connector

by Nick Boldt (JIRA)

include github connector ------------------------ Key: JBDS-1700 URL: https://issues.jboss.org/browse/JBDS-1700 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Components: updatesite Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 5.0.0.M3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
7
0 / 0

[JBoss JIRA] Created: (JBDS-1635) Include JBoss Maven Integration in JBDS Extras site (along with m2eclipse 0.13) ?

by Nick Boldt (JIRA)

Include JBoss Maven Integration in JBDS Extras site (along with m2eclipse 0.13) ? --------------------------------------------------------------------------------- Key: JBDS-1635 URL: https://issues.jboss.org/browse/JBDS-1635 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Components: Build, Requirements Affects Versions: 5.0.0.M1 Reporter: Nick Boldt Assignee: Fred Bricon >From Max: > We're not planning on supporting JBoss Maven Integration (org.jboss.tools.maven.*) before there is stable api from m2e. > But I guess it could be put on the Extras site as a 3rd party "selected" plugin. > The maven stuff can't just be put into JBDS 4.x sites without some work. So its a +1 for JBDS 5 once Snjezana/Fred are ok with it. >From Sneja: +1 Awaiting feedback from Fred. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
12
0 / 0

[JBoss JIRA] Created: (JBDS-1706) Move up to eGit 1.0 in JBDS 5 extras

by Nick Boldt (JIRA)

Move up to eGit 1.0 in JBDS 5 extras ------------------------------------ Key: JBDS-1706 URL: https://issues.jboss.org/browse/JBDS-1706 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Components: 3rdPartyDependencies, Build, updatesite Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 5.0.0.M3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-9365) JPA: @ManyToMany annotation is not supported with Hibernate platform

by Dmitry Geraskov (JIRA)

JPA: @ManyToMany annotation is not supported with Hibernate platform -------------------------------------------------------------------- Key: JBIDE-9365 URL: https://issues.jboss.org/browse/JBIDE-9365 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.3.0.M2 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Priority: Blocker Fix For: 3.3.0.M3 Test Case: 1. Create JPA project with Hibernate Platform 2. Create 2 Entities with @ManyToMany mapping 3. Open Jpa Details view: Failed: It should not be empty 4. create additional fieldin Entity without annotations 5. In Jpa Details view click on "here" link. 6. select ManyToMapping 7. Observe exception: Caused by: java.lang.IllegalArgumentException: invalid mapping key: manyToMany at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentAttribute.getSpecifiedMappingDefinition(AbstractJavaPersistentAttribute.java:325) at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentAttribute.setMappingKey_(AbstractJavaPersistentAttribute.java:216) at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentAttribute.setMappingKey(AbstractJavaPersistentAttribute.java:195) at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentAttribute.setMappingKey(AbstractJavaPersistentAttribute.java:1) at org.eclipse.jpt.jpa.ui.internal.details.PersistentAttributeMapAsComposite$1.morphMapping(PersistentAttributeMapAsComposite.java:82) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBDS-1793) CLONE - Installation of m2e fails and completely breaks JBDS (JBDS 5)

by Brian Fitzpatrick (JIRA)

CLONE - Installation of m2e fails and completely breaks JBDS (JBDS 5) --------------------------------------------------------------------- Key: JBDS-1793 URL: https://issues.jboss.org/browse/JBDS-1793 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: 3rdPartyCertification, updatesite Affects Versions: 4.1.0.CR3, 5.0.0.M2 Reporter: Libor Zoubek Assignee: Nick Boldt Priority: Blocker Fix For: 4.1.0.CR3, 5.0.0.M3 Attachments: .log, 2011-07-18-155018.png, install-2-features-vs.install-jbds-m2e-feature.png, JBDS-1780.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-9372) VPE has a serious performance drawback for rather big pages

by Vitali Yemialyanchyk (JIRA)

VPE has a serious performance drawback for rather big pages ----------------------------------------------------------- Key: JBIDE-9372 URL: https://issues.jboss.org/browse/JBIDE-9372 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Visual Page Editor core, Visual Page Editor Templates Affects Versions: 3.3.0.M3 Reporter: Vitali Yemialyanchyk Assignee: Yahor Radtsevich Priority: Minor rather big pages - in general dev project this is normal page size... My proposition for VPE developers pay attention to performance. This is example place to enhancement: VpeNodeInvocationHandler -> invoke -> for every get attribute call in VPE templates - call this: ElService.getInstance().replaceElAndResources(this.pageContext, toReplace); ElService -> replaceEl -> getAllResources - array creation and then ElService -> replaceEl -> replace - array sort FOR EVERY sourceNode.getAttribute("...") in function VpeAbstractTemplate -> public VpeCreationData create(VpePageContext pageContext, Node sourceNode, nsIDOMDocument visualDocument) {...} array create and sort operations should be performed only one time! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
22
0 / 0

[JBoss JIRA] Created: (JBIDE-9339) VPE has very-very bad exceptions catch/handle logik

by Vitali Yemialyanchyk (JIRA)

VPE has very-very bad exceptions catch/handle logik --------------------------------------------------- Key: JBIDE-9339 URL: https://issues.jboss.org/browse/JBIDE-9339 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core, Visual Page Editor Templates Affects Versions: 3.3.0.M3 Reporter: Vitali Yemialyanchyk Assignee: Yahor Radtsevich Priority: Blocker Attachments: screenshot-1.jpg Guys I can not imagine how you handle/find such real life issues in VPE like I get last time. Now I know this is my issue in my plugable VPE template (it was NPE exception) - but how I find this?! This is a really epic story. No exceptions in Error Log - just Eclipse "graceful" crash with this log in console: >>> Configuration location: file:/C:/_ws/xx_vpe/.metadata/.plugins/org.eclipse.pde.core/New_configuration/ Configuration file: file:/C:/_ws/xx_vpe/.metadata/.plugins/org.eclipse.pde.core/New_configuration/config.ini loaded Install location: file:/C:/Bin/eclipse_3.7/ Framework located: file:/C:/Bin/eclipse_3.7/plugins/org.eclipse.osgi_3.7.0.v20110613.jar Loading extension: reference:file:javax.transaction_1.1.1.v201105210645.jar eclipse.properties not found Framework classpath: file:/C:/Bin/eclipse_3.7/plugins/org.eclipse.osgi_3.7.0.v20110613.jar file:/C:/Bin/eclipse_3.7/plugins/ file:/C:/Bin/eclipse_3.7/plugins/javax.transaction_1.1.1.v201105210645.jar Splash location: C:\Bin\eclipse_3.7\plugins\org.eclipse.platform_3.7.0.v201106131736\splash.bmp Debug options: file:/C:/_ws/xx_vpe/.metadata/.plugins/org.eclipse.pde.core/New_configuration/.options loaded Time to load bundles: 94 Starting application: 6839 !SESSION 2011-07-13 19:56:53.561 ----------------------------------------------- eclipse.buildId=I20110613-1736 java.version=1.6.0_24 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Framework arguments: -product org.eclipse.sdk.ide Command-line arguments: -product org.eclipse.sdk.ide -data C:\_ws\xx_vpe/../runtime-New_configuration -dev file:C:/_ws/xx_vpe/.metadata/.plugins/org.eclipse.pde.core/New_configuration/dev.properties -debug C:\_ws\xx_vpe\.metadata\.plugins\org.eclipse.pde.core\New_configuration/.options -os win32 -ws win32 -arch x86 -consoleLog !ENTRY org.eclipse.mylyn.tasks.ui 2 0 2011-07-13 19:57:06.090 !MESSAGE No search provider was registed. Tasks search is not available. Application Started: 29190 # # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x642c902e, pid=9748, tid=9460 # # JRE version: 6.0_24-b07 # Java VM: Java HotSpot(TM) Client VM (19.1-b02 mixed mode, sharing windows-x86 ) # Problematic frame: # C [js3250.dll+0x4902e] # # An error report file with more information is saved as: # C:\Bin\eclipse_3.7\hs_err_pid9748.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # >>> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

5
32
0 / 0

[JBoss JIRA] Created: (JBIDE-9370) NPE when close VPE during page refresh execution

by Vitali Yemialyanchyk (JIRA)

NPE when close VPE during page refresh execution ------------------------------------------------ Key: JBIDE-9370 URL: https://issues.jboss.org/browse/JBIDE-9370 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.3.0.M3 Reporter: Vitali Yemialyanchyk Assignee: Yahor Radtsevich edit some rather big page with VPE, input some test, during page refresh close VPE - as result get exception: java.lang.NullPointerException at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.getDomDocument(MozillaEditor.java:828) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.getVisualDocument(VpeVisualDomBuilder.java:1556) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:493) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:270) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.updateElement(VpeVisualDomBuilder.java:836) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.updateNode(VpeVisualDomBuilder.java:766) at org.jboss.tools.vpe.editor.VpeController.notifyChangedInUiThread(VpeController.java:748) at org.jboss.tools.vpe.editor.VpeController$1.runInUIThread(VpeController.java:554) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) 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:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2011