[JBoss JIRA] Created: (JBIDE-6407) Unable to resolve property: _com
by Krasimir Goutcev (JIRA)
Unable to resolve property: _com
--------------------------------
Key: JBIDE-6407
URL: https://jira.jboss.org/browse/JBIDE-6407
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.1.1
Environment: Hibernate Tools 3.3.1.v201006011046R-H111-GA
Boss Archives Tools 3.1.1.v201006011046R-H111-GA
JBoss Tools RichFaces 3.1.1.v201006011046R-H111-GA
JBossAS Tools 2.1.1.v201006011046R-H111-GA org.jboss.ide.eclipse.as.feature.feature.group
GalileoSR2
java.version=1.6.0_16
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=bg_BG
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product -clean
Reporter: Krasimir Goutcev
Assignee: Max Rydahl Andersen
Attachments: AdmProcEtapIzp.hbm.xml, AdmProcEtapIzp.java
I have veeery simple mapping and pojo (just for this test)
So when i run in HQL this:
from com.indexbg.delo.db.AdmProcEtapIzp
all is OK.
But when I click on some result row in HQResult View =>
org.hibernate.HibernateException: Unable to resolve property: _com
at org.hibernate.tuple.entity.EntityMetamodel.getPropertyIndex(EntityMetamodel.java:487)
at org.hibernate.tuple.entity.AbstractEntityTuplizer.getPropertyValue(AbstractEntityTuplizer.java:302)
at org.hibernate.persister.entity.AbstractEntityPersister.getPropertyValue(AbstractEntityPersister.java:3600)
at org.hibernate.eclipse.console.views.properties.EntityPropertySource.getPropertyValue(EntityPropertySource.java:127)
at org.eclipse.ui.views.properties.PropertySheetEntry.refreshValues(PropertySheetEntry.java:611)
at org.eclipse.ui.views.properties.PropertySheetEntry.refreshChildEntries(PropertySheetEntry.java:568)
at org.eclipse.ui.views.properties.PropertySheetEntry.setValues(PropertySheetEntry.java:760)
at org.eclipse.ui.views.properties.PropertySheetViewer.setInput(PropertySheetViewer.java:973)
at org.eclipse.ui.views.properties.PropertySheetPage.selectionChanged(PropertySheetPage.java:510)
at org.eclipse.ui.views.properties.PropertySheet.selectionChanged(PropertySheet.java:344)
at org.eclipse.ui.internal.AbstractSelectionService.fireSelection(AbstractSelectionService.java:156)
at org.eclipse.ui.internal.AbstractSelectionService$1.selectionChanged(AbstractSelectionService.java:62)
at org.hibernate.eclipse.console.views.QueryPageTabView.fireSelectionChangedEvent(QueryPageTabView.java:178)
at org.hibernate.eclipse.console.views.QueryPageViewer.tableDoubleClicked(QueryPageViewer.java:246)
at org.hibernate.eclipse.console.views.QueryPageViewer.access$2(QueryPageViewer.java:241)
at org.hibernate.eclipse.console.views.QueryPageViewer$4.selectionChanged(QueryPageViewer.java:235)
at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:162)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.runtime.Platform.run(Platform.java:888)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:160)
at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2132)
at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1160)
at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1190)
at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:228)
at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:222)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:389)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3910)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3503)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
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:194)
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:368)
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:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 10 months
[JBoss JIRA] Created: (JBIDE-6176) Seam validator doesn't recognize Databinder associated with Factory.
by Alexey Kazakov (JIRA)
Seam validator doesn't recognize Databinder associated with Factory.
--------------------------------------------------------------------
Key: JBIDE-6176
URL: https://jira.jboss.org/jira/browse/JBIDE-6176
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.1.0.GA
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 3.1.1
The following piece of code causes the error 'Factory Method "somethings" with a void return type must have an associated @Out/Databinder' to be displayed'. But it should not.
@Name("somethingManager")
@Scope(ScopeType.CONVERSATION)
public class SomethingManager implements Serializable {
@DataModel("somethings")
@Out
private List<Something> somethingList;
@DataModelSelection
@Out(value = "something", required = false, scope = ScopeType.SESSION)
private Hardware selectedSomething;
@Factory(value = "somethings") // !Error is displayed right here!
public void findSomething() { //...
}
}
--
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
15 years, 10 months
[JBoss JIRA] Created: (JBIDE-5950) Need additional runtime checks for ESB & BPEL project examples
by Brian Fitzpatrick (JIRA)
Need additional runtime checks for ESB & BPEL project examples
--------------------------------------------------------------
Key: JBIDE-5950
URL: https://jira.jboss.org/jira/browse/JBIDE-5950
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: project-examples
Affects Versions: 3.1.0.CR2
Reporter: Brian Fitzpatrick
Assignee: Snjezana Peco
Fix For: 3.2.next, 3.1.1
While taking a look at adding runtime requirements to some of the other project examples for BPEL, ESB, and so on, it became apparent tha for now, you can only add requirements for a WTP Runtime, Seam Runtime, and plugin. For the ESB examples, I'd need to specify SOA-P 5.0 or EAP 5.0 + ESB 4.7. For the BPEL examples, I'd need to specify EAP 5.0 + ESB 4.7 + Riftsaw 2.0 or SOA-P 5.0 + Riftsaw 2.0.
How would I do either using the "fix type="wtpruntime"" fix properties? Seems we'd need to implement additional runtime checks.
(Snjeza, this is based on our e-mail conversation yesterday. Thanks in advance!)
--
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
15 years, 10 months
[JBoss JIRA] Created: (JBIDE-5867) Move GlobalElVariablesComposite to org.jboss.tools.vpe or another appropriate vpe plugin
by Maxim Areshkau (JIRA)
Move GlobalElVariablesComposite to org.jboss.tools.vpe or another appropriate vpe plugin
----------------------------------------------------------------------------------------
Key: JBIDE-5867
URL: https://jira.jboss.org/jira/browse/JBIDE-5867
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Visual Page Editor core
Affects Versions: 3.1.0.CR2
Reporter: Maxim Areshkau
Assignee: Maxim Areshkau
Priority: Critical
Fix For: 3.2.next
Currently, plugin org.jboss.tools.common.el.ui depends on org.jboss.tools.vpe.resref through entry
Import-Package: org.jboss.tools.vpe.resref.core
in manifest. That package is only used by class GlobalElVariablesComposite and that class is only used in plugin org.jboss.tools.vpe. So, one vpe plugin is dependent on the other vpe plugin, which is ok, but by some reason a common plugin is inserted into the dependency. That makes our code balancing on the edge of cyclic dependency, though GlobalElVariablesComposite is not needed in common at all. Let's move it to org.jboss.tools.vpe or another appropriate vpe plugin as soon as possible.
--
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
15 years, 10 months