May 2009 - jbosstools-issues - Jboss List Archives

[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, 5 months

3
11
0 / 0

[JBoss JIRA] Created: (JBIDE-4261) JBoss jboss-5.1.0.CR1 AS failed to start with JBT 3.0.1

by Anton Klimkovich (JIRA)

JBoss jboss-5.1.0.CR1 AS failed to start with JBT 3.0.1 ------------------------------------------------------- Key: JBIDE-4261 URL: https://jira.jboss.org/jira/browse/JBIDE-4261 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.0.1.GA Reporter: Anton Klimkovich EXECUTE: Add Jboss jboss-5.1.0.CR1 AS EXECUTE: Press Run server button FAILURE: JBoss jboss-5.1.0.CR1 AS failed to start : Failed to boot JBoss: org.jboss.xb.binding.JBossXBException: Failed to parse source: file:/C:/jboss-5.1.0.CR1/server/default/conf/bootstrap/vfs.xml@13,37 at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:177) at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:147) at org.jboss.bootstrap.microcontainer.TempBasicXMLDeployer.deploy(TempBasicXMLDeployer.java:150) at org.jboss.bootstrap.microcontainer.ServerImpl.doStart(ServerImpl.java:138) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:450) at org.jboss.Main.boot(Main.java:216) at org.jboss.Main$1.run(Main.java:546) at java.lang.Thread.run(Thread.java:595) Caused by: org.jboss.xb.binding.JBossXBRuntimeException: {urn:jboss:bean-deployer:2.0}property cannot appear in this position. Expected content of {urn:jboss:bean-deployer:2.0}bean is sequence: {urn:jboss:bean-deployer:2.0}alias* {urn:jboss:bean-deployer:2.0}related-class* {urn:jboss:bean-deployer:2.0}annotation* {urn:jboss:bean-deployer:2.0}classloader? {urn:jboss:bean-deployer:2.0}constructor? {urn:jboss:bean-deployer:2.0}property* {urn:jboss:bean-deployer:2.0}create? {urn:jboss:bean-deployer:2.0}start? {urn:jboss:bean-deployer:2.0}stop? {urn:jboss:bean-deployer:2.0}destroy? {urn:jboss:bean-deployer:2.0}depends* {urn:jboss:bean-deployer:2.0}demand* {urn:jboss:bean-deployer:2.0}supply* {urn:jboss:bean-deployer:2.0}install* {urn:jboss:bean-deployer:2.0}uninstall* {urn:jboss:bean-deployer:2.0}incallback* {urn:jboss:bean-deployer:2.0}uncallback* at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:449) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:173) ... 7 more -- 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, 5 months

3
11
0 / 0

[JBoss JIRA] Created: (JBIDE-4324) Add org.jboss.tools.jst.web.kb and org.jboss.tools.jst.web.kb.test plug-ins to build.

by Alexey Kazakov (JIRA)

Add org.jboss.tools.jst.web.kb and org.jboss.tools.jst.web.kb.test plug-ins to build. ------------------------------------------------------------------------------------- Key: JBIDE-4324 URL: https://jira.jboss.org/jira/browse/JBIDE-4324 Project: Tools (JBoss Tools) Issue Type: Task Components: Build/Releng Reporter: Alexey Kazakov Assignee: Nick Boldt Fix For: 3.1.0.M1 There are two new plug-ins in svn: https://svn.jboss.org/repos/jbosstools/trunk/jst/plugins/org.jboss.tools.... and https://svn.jboss.org/repos/jbosstools/trunk/jst/tests/org.jboss.tools.js... Please add them to build. -- 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, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBDS-722) "Finger touch" button

by Svetlana mukhina (JIRA)

"Finger touch" button --------------------- Key: JBDS-722 URL: https://jira.jboss.org/jira/browse/JBDS-722 Project: Developer Studio Issue Type: Task Components: Doc - JBossAS, Doc - RHDS GSG Affects Versions: 2.0.0.GA Reporter: Svetlana mukhina Assignee: Anastasiya Bogachuk Fix For: 2.1.0 It's necessary to add info on "Finger touch" button to AS and GSG guides, the same as it's done for ESB - http://download.jboss.org/jbosstools/nightly-docs/en/esb_ref_guide/html_s... (Figure 2.10. Finger Touch button) -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-4321) Seam Validator sets wrong error problem when project has @Name annotation and factory tag with the same name

by Daniel Azarov (JIRA)

Seam Validator sets wrong error problem when project has @Name annotation and factory tag with the same name ------------------------------------------------------------------------------------------------------------ Key: JBIDE-4321 URL: https://jira.jboss.org/jira/browse/JBIDE-4321 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.M1 Reporter: Daniel Azarov Assignee: Alexey Kazakov TESTCASE: 1. Create Seam War Project 2. Open components.xml 3. Add <factory name="authenticator" /> string in components.xml 4. Save components.xml file ASSERT: There are no problems for our project FAIL: Two problems appear: 1. Duplicate variable name "authenticator" - Authenticator.java 2. Duplicate variable name "authenticator" - components.xml -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4313) Rename Seam Component does not rename factory tag in components.xml

by Daniel Azarov (JIRA)

Rename Seam Component does not rename factory tag in components.xml ------------------------------------------------------------------- Key: JBIDE-4313 URL: https://jira.jboss.org/jira/browse/JBIDE-4313 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.M1 Reporter: Daniel Azarov Assignee: Viacheslav Kabanovich Testcase: 1. Create seam war project 2. Create seam action with "first" as component name 3. Add next string to components.xml: <factory name="first" /> 4. Open First.java file 5. Select Seam->Rename Seam Component menu 6. Enter "second" as seam component name 7. Press Next button ASSERT: In list of changes must be present next change for components.xml <factory name="first" /> -> <factory name="second" /> FAIL: There is no change for components.xml -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4312) Rename Seam Component does not work correctly with xml declaration of seam components

by Daniel Azarov (JIRA)

Rename Seam Component does not work correctly with xml declaration of seam components ------------------------------------------------------------------------------------- Key: JBIDE-4312 URL: https://jira.jboss.org/jira/browse/JBIDE-4312 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.M1 Reporter: Daniel Azarov Assignee: Viacheslav Kabanovich Testcase: 1. Create seam war project 2. Create seam action with "first" as component name 3. Add next string to components.xml: <component class="org.domain.<projectname>.session.First" name="first" /> 4. Open First.java file 5. Select Seam->Rename Seam Component menu 6. Enter "second" as seam component name 7. Press Next button ASSERT: In list of changes all "first" must be replaced by "second" FAIL: In component.xml Refactoring Dialong offers next replacement: <component class="org.domain.renameseamcomponenttestproject.session.First" name="first" /> to <component class="org.domain.renameseamcomponenttestproject.session.First"second"first" /> -- 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, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-4315) Rename Seam Component wizard sometimes is initialized with a wrong component

by Viacheslav Kabanovich (JIRA)

Rename Seam Component wizard sometimes is initialized with a wrong component ---------------------------------------------------------------------------- Key: JBIDE-4315 URL: https://jira.jboss.org/jira/browse/JBIDE-4315 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.M1 Reporter: Viacheslav Kabanovich Assignee: Daniel Azarov Fix For: 3.1.0.M1 Testcase: 1. Create seam war project 2. Create seam action with "first" as component name 3. Add next string to components.xml: <component class="org.domain.<projectname>.session.First" name="first2" /> 4. Open First.java file 5. Select Seam->Rename Seam Component menu ASSERT: Refactoring wizard appears initialized with component "first". FAIL: Refactoring wizard appears initialized with component "first2". Note: Issue may be not reproduced with names "first" and "first2" because Seam model returns components based on class First in java.util.Set, so that there is indeterminacy which component will be selected. Then other names may be tried, or more components in xml declared. -- 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, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-4281) New Smooks file shows option below Advanced which breaks the flow

by Max Rydahl Andersen (JIRA)

New Smooks file shows option below Advanced which breaks the flow ----------------------------------------------------------------- Key: JBIDE-4281 URL: https://jira.jboss.org/jira/browse/JBIDE-4281 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Reporter: Max Rydahl Andersen Assignee: Feng Qian Fix For: 3.1.0.M1 See attachement. "Advanced" is meant to be at the *bottom* of the wizard. The version info should be above this or on the next page as an optional setting. Also the wizard should use the initial selection to select the output folder and provide a default name. -- 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, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (JBDS-414) invisible tags in VPE

by Svetlana mukhina (JIRA)

invisible tags in VPE --------------------- Key: JBDS-414 URL: https://jira.jboss.org/jira/browse/JBDS-414 Project: Developer Studio Issue Type: Task Components: Doc - VisualWebTools Affects Versions: 1.1.0.GA Reporter: Svetlana mukhina Assignee: Anastasiya Bogachuk Fix For: 2.0.0.alpha update info on VPE in visual web tools according to the changes https://jira.jboss.org/jira/browse/JBIDE-1805 -- 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, 6 months

3
10
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2009