[JBoss JIRA] Created: (JBDS-347) JBDevstudio crashes from time to time (in a bleeding edge environment)
by David Tonhofer (JIRA)
JBDevstudio crashes from time to time (in a bleeding edge environment)
----------------------------------------------------------------------
Key: JBDS-347
URL: http://jira.jboss.com/jira/browse/JBDS-347
Project: Developer Studio
Issue Type: Bug
Components: visualeditor
Affects Versions: 1.1.0.CR1
Environment: Fedora 9 + KDE: 2.6.25.3-18.fc9.x86_64
Additional plugins: antlr, sourceforge.metrics, subversive, subversive providers
Reporter: David Tonhofer
Assigned To: Max Rydahl Andersen
JBDevstudio crashes from time to time, leaving only a dialog showing the JVM invocation command line in its wake.
The last message in the .log file is:
!ENTRY org.eclipse.jface 2 0 2008-05-28 21:18:31.564
!MESSAGE Keybinding conflicts occurred. They may interfere with normal accelerator operation.
!SUBENTRY 1 org.eclipse.jface 2 0 2008-05-28 21:18:31.564
!MESSAGE A conflict occurred for CTRL+SHIFT+G:
Binding(CTRL+SHIFT+G,
ParameterizedCommand(Command(org.springframework.ide.eclipse.beans.ui.editor.commands.searchBeanReferences,Spring Beans References Search,
,
Category(org.eclipse.search.ui.category.search,Search,Search command category,true),
,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.wst.sse.ui.structuredTextEditorScope,,,system)
Binding(CTRL+SHIFT+G,
ParameterizedCommand(Command(org.jboss.tools.seam.ui.find.references,Find Seam References,
Find Seam References,
Category(org.eclipse.search.ui.category.search,Search,Search command category,true),
ActionDelegateHandlerProxy(null,org.jboss.tools.seam.ui.actions.FindSeamReferencesAction),
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.wst.sse.ui.structuredTextEditorScope,,,system)
Binding(CTRL+SHIFT+G,
ParameterizedCommand(Command(org.eclipse.jdt.ui.edit.text.java.search.references.in.workspace,References in Workspace,
Search for references to the selected element in the workspace,
Category(org.eclipse.search.ui.category.search,Search,Search command category,true),
,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.window,,,system)
I the log shows more on the next crash, I will append more info here.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 2 months
[JBoss JIRA] Created: (JBIDE-2555) Moving Seam component yields persistent, incorrect validation error
by Tim Otten (JIRA)
Moving Seam component yields persistent, incorrect validation error
-------------------------------------------------------------------
Key: JBIDE-2555
URL: https://jira.jboss.org/jira/browse/JBIDE-2555
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 2.1.0.CR1
Environment: JBoss Developer Studio 1.1.0.CR1
Seam 2.0.2.SP1
Ubuntu Feisty
Reporter: Tim Otten
When moving a Seam component from one Java package to another Java package, the Seam validator erroneously reports the error "Duplicate component name." Cleaning the project does not remove the error. Eclipse must be restarted.
Steps to reproduce:
1. Create a new EAR-based project
2. Generate an entity, entityhome, etc.
3. Move one of the Seam components to a new Java package, e.g.
3.a. In the "Package Explorer" tab, locate the entity's home component.
3.b. Right-click -> Refactor -> Move
3.c. Designate a new package
3.d. Click "OK"
4. Clean/Rebuild project
4.a. In the Eclipse menu bar, choose Project -> Clean
4.b. Choose any/all applicable projects
4.c. Enable "Start a build immediately"
4.d. Click "OK"
5. In the "Problems" tab, an error appears twice: "Duplicate component name"
After repeated attempts to clean/build the project(s), the error message persists.
The error can be removed by:
6. Close Eclipse
7. Open Eclipse
8. Clean/Rebuild project
At this point, the error message goes away. The project will now build and deploy, and the refactored component functions appropriately.
(Note: I'm using the current stable release of JBoss Developer Studio 1.1.0.CR1 with JBoss Tools 2.1.0.CR1. I've checked the list of open tickets and the release notes for JBoss Tools 2.1.1 and 2.1.2 -- I couldn't identify any related issues.)
--
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, 2 months
[JBoss JIRA] Created: (JBIDE-2401) Seam EL inserted w/o closed } usin CA if it was called in specific way.
by Anton Klimkovich (JIRA)
Seam EL inserted w/o closed } usin CA if it was called in specific way.
------------------------------------------------------------------------
Key: JBIDE-2401
URL: http://jira.jboss.com/jira/browse/JBIDE-2401
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing, Visual Page Editor
Affects Versions: 2.1.2
Reporter: Anton Klimkovich
Assigned To: Alexey Kazakov
EXECUTE: Create Seam web Project
EXECUTE: Open any .xhtml page
EXECUTE: Type <h:outputText value="#{" />
EXECUTE: Set cursor after do not closed {
EXECUTE: Call CA
EXECUTE: Select Seam EL
FAILURE: <h:outputText value="#{actor" /> - inserted w/o closed }
EXECUTE: Type <h:outputText value="#{" /> and Set cursor after do not closed {
EXECUTE: Call CA
EXECUTE: Select JSF EL (sessionScope for example)
ASSERT: <h:outputText value="#{sessionScope}" />
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 3 months