[JBoss JIRA] Created: (JBDS-535) workflow/usability questions - Step 4: Select Java VM
by Nick Boldt (JIRA)
workflow/usability questions - Step 4: Select Java VM
-----------------------------------------------------
Key: JBDS-535
URL: https://jira.jboss.org/jira/browse/JBDS-535
Project: Developer Studio
Issue Type: Quality Risk
Components: installer
Affects Versions: 2.0.0.cr1
Reporter: Nick Boldt
Assignee: Max Rydahl Andersen
Attachments: Screenshot- JBoss Developer Studio 2.0.0.CR1.png
Actually, it says "gij" but on my monitor the text is cut off and it looks like a q, not a g.
Perhaps we could rework this as follows:
"JBoss Developer Studio requires a Java 5 or later runtime. Gnu Java (gij) is not supported; Open JDK 6 is recommended. Choose the Java VM to use with JBoss Developer Studio.
( ) Default Java VM (defined by PATH)
( ) Alternate Java VM (user-defined)"
Of course that assumes that JDBS *does in fact support JDK6*, and that we'd like to encourage people to use the latest and greatest Open JDK [1] (offered OOTB in Fedora 9 and later [2]), rather than letting them pick Sun, IBM, or BEA's JDKs.
[1] http://openjdk.java.net/
[2] http://fedoraproject.org/wiki/JavaFAQ
Also, does the installer check if the version of java used to run it is a compatible one? For example, will the installer run with 1.4, or with blackdown or gij, but require that JBDS itself use 5.0+?
And, since this selection is a prereq before JBDS will work at all, should this page be step 1, not 4?
--
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, 4 months
[JBoss JIRA] Created: (JBIDE-4369) Issues with BIRT classloader
by Snjezana Peco (JIRA)
Issues with BIRT classloader
----------------------------
Key: JBIDE-4369
URL: https://jira.jboss.org/jira/browse/JBIDE-4369
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: birt, UpStream
Affects Versions: 3.0.0.GA
Reporter: Snjezana Peco
Assignee: Snjezana Peco
Steps to reproduce:
1) create a new Seam Web Project with the "BIRT Reporting Runtime Component" facet
2) call "Generates Seam Entities" and create some entities
3) create a BIRT report
4) restart Eclipse
5) add JBoss Hibernate Data Source and click Test Connection
You will get the "Could not create JPA based Configuration" error (Problem 1). Attached is log1.txt
If you build a session factory using the Hibernate Configuration view in the Hibernate perspective, you will be able to create a data source (5) and data set(6)
6) create Hibernate Data Set
7) call the Previews Result tab in the Edit Data Set dialog
8) call "Generate Seam Entities" and click "Refresh" on the second page of the wizard
You will get the "<Couldn't connect to Database>" error (Problem 2).
9) try to open *.xhtml file using the VPE editor
You will get an error (attached log2.txt). Sometimes Eclipse freezes (Problem 3).
There are two issues related to the BIRT engine:
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=258574
I have created a patch for this issue.
- an issue in DataSetEditor.ItemModelHandler. BIRT sets a context classloader in this class, but doesn't revert the old context classloader. The issue exists in BIRT 2.3.1 and BIRT 2.5.0M7. It is fixed in the current CVS.
BIRT creates a classloader using libraries from all the projects in the workspace including thirdparty-all.jar from the *-test project that contains an incompatible xerces version (which causes problems 2 and 3). The BIRT classloader returns the META-INF/persistence.xml file multiple times because multiple instances of the EJB's source folder are in the classpath (which causes problem 1).
--
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, 4 months