[JBoss JIRA] Created: (JBIDE-3749) Strange exceptions while closing JBDS with opened Console view.
by Aliaksey Nis (JIRA)
Strange exceptions while closing JBDS with opened Console view.
---------------------------------------------------------------
Key: JBIDE-3749
URL: https://jira.jboss.org/jira/browse/JBIDE-3749
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.0.0.GA
Environment: WindowsXP SP2
JBoss Developer Studio
Version: 2.0.0.GA
Build id: jbdevstudio-eap-win32-2.0.0.GA-N200902030301-H1413
JRE 1.5_08
Reporter: Aliaksey Nis
Priority: Minor
Attachments: WSclose.txt
EXECUTE: New workspace.
EXECUTE: Open Console view.
EXECUTE: Create any (Seam for example) project. Start server with this project.
ASSERT: Something appears in console view(server startup logs).
EXECUTE: Stop server.
EXECUTE: Close studio.
EXECUTE: Look at .log (in workspace metadata) or start studio again and look at Error log View.
FAILURE: Two exceptions appears.
Each time, when you close workspace with not empty console view - those exceptions appears.
Error log attached.
--
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
17 years, 1 month
[JBoss JIRA] Created: (JBIDE-3841) Use Java generics all over the Hibernate tools code
by Vitali Yemialyanchyk (JIRA)
Use Java generics all over the Hibernate tools code
---------------------------------------------------
Key: JBIDE-3841
URL: https://jira.jboss.org/jira/browse/JBIDE-3841
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.0.0.CR2
Reporter: Vitali Yemialyanchyk
Assignee: Vitali Yemialyanchyk
Priority: Optional
Cause mature of the Hibernate tools code, there are some places where java 1.4 code used;
it will not be a big refactoring of using generics all over the Hibernate tools code;
so we can significantly reduce warnings and make code more secure.
There are 2 possible way to perform this:
1) it could be done as 1 big "refactoring"
or
2) if some source file should be changed - it is possible firstly change it to use generics, commit it and then modify it and then commit it.
--
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
17 years, 1 month
[JBoss JIRA] Created: (JBIDE-3670) Drools Runtime unclear how to correctly define
by Jeff DeLong (JIRA)
Drools Runtime unclear how to correctly define
----------------------------------------------
Key: JBIDE-3670
URL: https://jira.jboss.org/jira/browse/JBIDE-3670
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: drools
Affects Versions: 3.0.0.cr1
Environment: jbdevstudio-linux-gtk-2.0.0.CR2-R200901250322.jar on RHEL 5, jdk 1.5.11
Reporter: Jeff DeLong
I tested out the Drools IDE in JBDS. I used the Drools icon to create a new Drools project, and ran the DroolsTest class the wizard created as a Java Application. I got the following exception:
java.lang.NoClassDefFoundError: org/antlr/runtime/CharStream
The problem is with defining the "Drools Runtime". As part of the setup for creating a Drools Project for the first time, the user is asked to create a "Drools Runtime". This is new (in the past Drools IDE new which set of jars to use), to be consistent with other tools and allow user to select different Drools Runtimes. The challenge for the user is how to define a Drools Runtime. You can either find the jars in JBDS plugins, explode them into a folder, and point to them, or download Drools engine/expert (in this case I had decided to try jboss-brms-engine-5.ea.zip, since this is the .com version). However when this is unzipped, some jars are in the root of the folder and some are in a lib directory. At least four of the ones in the lib directory are required for runtime (antlr-runtime-3.1.1.jar, core-3.4.2.v_883_R34x.jar, mvel2-2.0.5.jar, xstream-1.3.1.jar), and the jars in a subdirectory are not added to the runtime classpath.
It should be easier for the user to define a Drools Runtime. They should not have to know about which jars to move around. They should just be able to download and unzip.
--
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
17 years, 1 month
[JBoss JIRA] Created: (JBIDE-3758) VPE autorefresh is broken in some cases
by Yura Zhishko (JIRA)
VPE autorefresh is broken in some cases
---------------------------------------
Key: JBIDE-3758
URL: https://jira.jboss.org/jira/browse/JBIDE-3758
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.0.0.GA
Reporter: Yura Zhishko
Assignee: Maxim Areshkau
1) Open attached page in VPE
2) Cope source code a shown on a screenshot-1
3) Paste it as shown on screenshot-2
RESULT: Nothing happaned on the Visual Pane. No component is added.
Another test case:
1) Set style="color:red" for <body> tag at the begining of some page with plain text, for example:
<body style="color:red">
Plain Text
</body>
ASSERT: Plain text os red on the visual pane
2) Delete tag <body> with all content
3) Print some text into source code
RESULT: The text is red
--
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
17 years, 1 month