[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
[JBoss JIRA] Created: (JBIDE-9666) JBDS Startup error message: mapass-library-provider
by Libor Zoubek (JIRA)
JBDS Startup error message: mapass-library-provider
---------------------------------------------------
Key: JBIDE-9666
URL: https://issues.jboss.org/browse/JBIDE-9666
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 3.3.0.M3
Environment: jbdevstudio-product-linux-gtk-5.0.0.v201109021637R-H24-M3.jar with all extras and all soa plugins
Reporter: Libor Zoubek
Assignee: Fred Bricon
Fix For: 3.3.0.M4
Right after JBDS starts up I get this message in error log view:
Library provider "mapass-library-provider" is not defined. This id is referenced in plugin org.jboss.tools.maven.ui.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[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
[JBoss JIRA] Created: (JBIDE-9444) Provide mechanism to select default template for VPE for rendering some tag (define tag priority)
by Vitali Yemialyanchyk (JIRA)
Provide mechanism to select default template for VPE for rendering some tag (define tag priority)
-------------------------------------------------------------------------------------------------
Key: JBIDE-9444
URL: https://issues.jboss.org/browse/JBIDE-9444
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Visual Page Editor core, Visual Page Editor Templates
Affects Versions: 3.3.0.M3
Reporter: Vitali Yemialyanchyk
Assignee: Yahor Radtsevich
Priority: Minor
In same cases is necessary to override default template for VPE, but in such cases VPE select default template randomly - it depends on plugin load sequence.
So is necessary to add additional attribute for templates, with fractional value so be possible to modify default template for rendering.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[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