[JBoss JIRA] Created: (JBIDE-4149) Hibernate ODA errors on subreport on subsequent calls to Dataset
by Mark Nuttall (JIRA)
Hibernate ODA errors on subreport on subsequent calls to Dataset
----------------------------------------------------------------
Key: JBIDE-4149
URL: https://jira.jboss.org/jira/browse/JBIDE-4149
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: birt
Affects Versions: 3.0.0.GA
Reporter: Mark Nuttall
When using Hibernate ODA in a BIRT report for a subreport, an exception occurs when the dataset is called for a second time. It seems to be expecting the connection to be open and it isn't or it is open and it expects it to be closed. I am pretty sure the exception i saw was that it tried to open the connection.
If i use a single datasource with 2 datasets, then the report errors out after the second call to the subreport. For example:
Customer: Bob Smith
Order 1
Order 2
Customer: Jane Doe
[Exception]
If I use 2 datasources and a single dataset each then the report runs to completion and the exception is shown at the end. Only the first parent will have children though. For example:
Customer: Bob Smith
Order 1
Order 2
Customer: Jane Doe
Customer: Joe Schmo
Customer: Roger Dodger
Customer: Rick James
[Exception]
--
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
16 years, 11 months
[JBoss JIRA] Created: (JBDS-662) centralize requirements folder on in /home/hudson/hudson_workspace/workspace/jbosstools-jbdevstudio-REQUIREMENTS
by Nick Boldt (JIRA)
centralize requirements folder on in /home/hudson/hudson_workspace/workspace/jbosstools-jbdevstudio-REQUIREMENTS
----------------------------------------------------------------------------------------------------------------
Key: JBDS-662
URL: https://jira.jboss.org/jira/browse/JBDS-662
Project: Developer Studio
Issue Type: Task
Affects Versions: LATER
Reporter: Nick Boldt
Priority: Minor
Fix For: 2.0.1, 2.1.0
To avoid meltdowns like we had in JBQA-2144, to reduce disk usage, and to speed up the rollout of new hudson jobs, I propose we create two folders:
/home/hudson/hudson_workspace/workspace/jbosstools-3.0-jbdevstudio-2.0-REQUIREMENTS
/home/hudson/hudson_workspace/workspace/jbosstools-3.1-jbdevstudio-2.1-REQUIREMENTS
In there, we will place a copy of all the requirements used by the paired builds, and instead of burning time and bandwidth fetching the 3G of zips every time we start a new job, we'll simply symlink to that folder so new reqs will be added.
cd /home/hudson/hudson_workspace/workspace/jbosstools-nightly-3.0.x/jbds-build
ln -s /home/hudson/hudson_workspace/workspace/jbosstools-3.0-jbdevstudio-2.0-REQUIREMENTS requirements
Thus, for the 4 parallel jobs for JBDS2.0.0/2.0.1 & JBT3.0.0/3.0.1, we'll use about 3G of disk instead of 12. For the 2 parallel jobs for JBDS2.1.0 & JBT3.1.0, we'd save 3G.
For the case where this is run on a local box (eg., my own Hudson) we just need a catch that says "if /home/hudson/hudson_workspace/workspace/jbosstools-3.1-jbdevstudio-2.1-REQUIREMENTS doesn't exist, create it, symlink to it, and begin downloading" .. of course the path there would be ~/.hudson/jobs/jbosstools-3.1-jbdevstudio-2.1-REQUIREMENTS, but it's the same relative path.
--
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
16 years, 11 months
[JBoss JIRA] Created: (JBIDE-3311) tools try to build jboss project on eclipse start
by arne anka (JIRA)
tools try to build jboss project on eclipse start
-------------------------------------------------
Key: JBIDE-3311
URL: https://jira.jboss.org/jira/browse/JBIDE-3311
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.0.0.cr1
Environment: Version: 3.4.1
Build id: M20080911-1700
tools: JBossTools-3.0.0.CR1-N200811270312-ALL-linux-gtk.zip
Reporter: arne anka
when starting eclipse after a short moment jboss tools try to build my jboss tools project, though it's neither active nor necessary.
i use mylyn and have a context open in no way related to jboss, the jboss project was build successfully last time used (before shutting down eclipse the last time) and not touched since.
in "preferences -> general -> startup and shutdown" everything looking like jboss is disabled.
but still after some seconds of deceptive ease the jboss tools project is build and a db connection is created ...
additionally there seems to be more going on: due to problems i needed to kill eclipse the hard way -- and after restart an error building the jboss project was announced! i did not touch the jbt prjoct and it was not active!
--
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
16 years, 11 months