[JBoss Tools (users)] - visual HQL constructor tool?
by asookazian
Does JBoss Tools 3.x have a tool that will allow you to do this:
see a view with all of your entity classes
select multiple entity classes in this diagram/view to form the basis of a HQL select statement
automatically create the HQL and dump it in the HQL editor (assuming Hibernate console is setup).
And you go from there. For example, I have this native query I'm trying to "reverse engineer" to HQL. It would be nice to have the above tool:
select er.equipmentRepairId,
| e.serialNumber,
| ddv.description,
| sum(erc.cost) as Cost
| from Equipment as e
| inner join EquipmentRepair as er on er.equipmentId = e.equipmentId
| left outer join EquipmentRepairCost as erc on er.equipmentRepairId = erc.equipmentRepairId
| left outer join DropDownValue as ddv on er.equipmentRepairTypeCode = ddv.code
| left outer join DropDown as dd on dd.listId = ddv.listId
| where e.serialNumber = :serialNumber and
| dd.listName = :repairTypeDropDown
| group by er.equipmentRepairId,
| e.serialNumber,
| ddv.description
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217661#4217661
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217661
17 years, 3 months
[Installation, Configuration & DEPLOYMENT] - Re: Jboss 5.x deploy problem
by PeterJ
The "unable to find orb" message is expected when running a nonclustered instance of JBoss AS - you can ignore that message. Note that it is a DEBUG message.
I dont like the looks of this part of the error text:
Dependency "jboss.jca:name=
| java:/app/jdbc/jdbc/cbadmDS
| ,service=DataSourceBinding
Did you by any chance define the data source name in persistence.xml as follows:
<jta-data-source>
| java:/app/jdbc/jdbc/cbadmDS
| </jta-data-source>
Are you aware that white space is not trimmed for the data source name that you provide? Thus the newlines and spaces are assumed to be part of the name? Instead, use:
<jta-data-source>java:/app/jdbc/jdbc/cbadmDS</jta-data-source>
folesen, I don't see how you ran into the exact same problem unless you are deploying the exact same application that zlatkop is deploying. I recommend that you open a new topic and post your exception stack trace there - hijacking someone else's post to get help on your problem is not good manners.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217659#4217659
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217659
17 years, 3 months