[JBoss JIRA] Resolved: (JBIDE-563) JBoss AS X.X Class Path container is never showed in Navigator
by Rob Stryker (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-563?page=all ]
Rob Stryker resolved JBIDE-563.
-------------------------------
Resolution: Done
Fix in SVN
It seems this is an appropriate user interface to add a server runtime's libraries to the classpath of a POJP or some other project.
Sorry for saying you were doing it wrong ;)
> JBoss AS X.X Class Path container is never showed in Navigator
> --------------------------------------------------------------
>
> Key: JBIDE-563
> URL: http://jira.jboss.com/jira/browse/JBIDE-563
> Project: JBoss Tools
> Issue Type: Bug
> Components: JBossAS
> Affects Versions: ExadelStudioPro4
> Reporter: Denis Golovin
> Assigned To: Rob Stryker
> Priority: Blocker
>
> 0. Create JBoss AS server on Servers View
> 1. Create Dynamic Web Project
> 2. Open Project properties dialog by navigator Context menu
> 3. Select Java Build Path Category and press Add Library button on the right of Libraries tab
> 4. Select JBoss-runtime and press Ok.
> 5.Press Ok in preferences dialog.
> 6. Expand the project - there is no JBoss AS X.X Class-path container.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 8 months
[JBoss JIRA] Created: (JBIDE-613) NullPointerException occurs if there are .hbm.xml file with xml errors in it
by Denis Golovin (JIRA)
NullPointerException occurs if there are .hbm.xml file with xml errors in it
-----------------------------------------------------------------------------
Key: JBIDE-613
URL: http://jira.jboss.com/jira/browse/JBIDE-613
Project: JBoss Tools
Issue Type: Bug
Components: Hibernate
Reporter: Denis Golovin
Assigned To: Max Andersen
If there is xml errors in any hbm.xml file that is registered in hibernate.cfg.xml NullPointerExceptions occurs every time when Hibernate configuration with that broken file is selected in Hibernate Configurations View.
java.lang.NullPointerException
at org.hibernate.eclipse.graph.model.PropertyViewAdapter.createSingleEndedEnityAssociations(PropertyViewAdapter.java:98)
at org.hibernate.eclipse.graph.model.PropertyViewAdapter.checkConnections(PropertyViewAdapter.java:71)
at org.hibernate.eclipse.graph.model.PropertyViewAdapter.getSourceConnections(PropertyViewAdapter.java:64)
at org.hibernate.eclipse.graph.parts.PropertyEditPart.getModelSourceConnections(PropertyEditPart.java:76)
at org.eclipse.gef.editparts.AbstractGraphicalEditPart.refreshSourceConnections(AbstractGraphicalEditPart.java:597)
at org.eclipse.gef.editparts.AbstractGraphicalEditPart.refresh(AbstractGraphicalEditPart.java:565)
at org.eclipse.gef.editparts.AbstractEditPart.addNotify(AbstractEditPart.java:235)
at org.eclipse.gef.editparts.AbstractGraphicalEditPart.addNotify(AbstractGraphicalEditPart.java:212)
at org.eclipse.gef.editparts.AbstractEditPart.addChild(AbstractEditPart.java:198)
at org.eclipse.gef.editparts.AbstractEditPart.refreshChildren(AbstractEditPart.java:727)
at org.eclipse.gef.editparts.AbstractEditPart.refresh(AbstractEditPart.java:677)
at org.eclipse.gef.editparts.AbstractGraphicalEditPart.refresh(AbstractGraphicalEditPart.java:564)
at org.eclipse.gef.editparts.AbstractEditPart.addNotify(AbstractEditPart.java:235)
at org.eclipse.gef.editparts.AbstractGraphicalEditPart.addNotify(AbstractGraphicalEditPart.java:212)
at org.eclipse.gef.editparts.AbstractEditPart.addChild(AbstractEditPart.java:198)
at org.eclipse.gef.editparts.AbstractEditPart.refreshChildren(AbstractEditPart.java:727)
at org.eclipse.gef.editparts.AbstractEditPart.refresh(AbstractEditPart.java:677)
at org.eclipse.gef.editparts.AbstractGraphicalEditPart.refresh(AbstractGraphicalEditPart.java:564)
at org.eclipse.gef.editparts.AbstractEditPart.addNotify(AbstractEditPart.java:235)
at org.eclipse.gef.editparts.AbstractGraphicalEditPart.addNotify(AbstractGraphicalEditPart.java:212)
at org.eclipse.gef.editparts.AbstractEditPart.addChild(AbstractEditPart.java:198)
at org.eclipse.gef.editparts.SimpleRootEditPart.setContents(SimpleRootEditPart.java:101)
at org.eclipse.gef.ui.parts.AbstractEditPartViewer.setContents(AbstractEditPartViewer.java:601)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 8 months
[jbosside-issues] [JBoss JIRA] Created: (JBIDE-440) Enable first-class support of Enum types in the Query Parameters view
by Joseph Marques (JIRA)
Enable first-class support of Enum types in the Query Parameters view
---------------------------------------------------------------------
Key: JBIDE-440
URL: http://jira.jboss.com/jira/browse/JBIDE-440
Project: JBoss IDE
Issue Type: Feature Request
Components: Hibernate Tools
Affects Versions: 2.0.0.Beta2
Reporter: Joseph Marques
Assigned To: Max Andersen
Granted, Enums are persisted as either ints or strings, but that doesn't mean that the Query Parameters view can't support Enums as a first-class construct in the Type column. I suppose there are a few different ways to support this, but let me explain the semantics that I think would make the most sense for supreme usability:
Select "enum" for the "Type" column
Then you specify the class in the "Value" column (identical to how it works when "class" is selected for the "Type" column)
Then, the tools should be able to be clever enough to read the mapping strategy for this enum based on the context of where it is being used in the corresponding hql/jpql statement. The tools would then map the Enum class to it's appropriate int or string representation during query translation / execution. This allows the query writer to be more effective because he/she wouldn't have to know the actual enum mapping strategy to be able to mock up and test the query.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 8 months