[JBoss JIRA] Created: (JBIDE-7219) Finish button should be enabled on the first page of New Seam Project wizard.
by Alexey Kazakov (JIRA)
Finish button should be enabled on the first page of New Seam Project wizard.
-----------------------------------------------------------------------------
Key: JBIDE-7219
URL: https://jira.jboss.org/browse/JBIDE-7219
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Seam
Affects Versions: 3.2.0.Beta2
Reporter: Alexey Kazakov
Assignee: Daniel Azarov
Fix For: 3.2.0.Beta2
EXECUTE: Start Seam Web Project Wizard (fill in all the required fields and press finish)
ASSERT: Project is created
EXECUTE: Start Seam Web Project Wizard again (fill in project name)
ASSERT: Finish should be possible now since we have set all required stuff (runtimes, drivers, etc.) and all of them set by default.
Currently we have to click next through all pages without changing anything and then we can press finish.
It causes testJiraJbide1111 failure:
testJiraJbide1111(org.jboss.tools.seam.ui.test.wizard.SeamProjectNewWizardTest) Time elapsed: 3.443 sec <<< FAILURE!
junit.framework.AssertionFailedError: Finish button is disabled at first wizard page in spite of created JBoss AS Runtime, Server, DB Connection and Seam Runtime and valid project name.
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at org.jboss.tools.seam.ui.test.wizard.SeamProjectNewWizardTest.testJiraJbide1111(SeamProjectNewWizardTest.java:103)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Created: (JBIDE-7622) SeamCoreValidator may validate a wrong Seam project in case of there is more than one project in workspace
by Victor Rubezhny (JIRA)
SeamCoreValidator may validate a wrong Seam project in case of there is more than one project in workspace
----------------------------------------------------------------------------------------------------------
Key: JBIDE-7622
URL: https://jira.jboss.org/browse/JBIDE-7622
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.2.0.Beta1
Reporter: Victor Rubezhny
Assignee: Victor Rubezhny
Fix For: 3.2.0.Beta2
If there are 2 or more projects exist in workspace and at least one of them is a Seam project then SeamCoreValidator may validate previously validated Seam project instead the project which is really requested to be validated. If this happens then it may try to validate the projects which have been closed and even removed from the workspace.
The following log says that SeamCoreValidator tries to validate numberguess project which actually was removed a few seconds ago. (Additional print out is made due to see what project is actually validated in SeamCoreValidator.init() method):
init() => WAR project not found: project (P/test_seam12_ear_t-ejb) ==>> seamProject (org.jboss.tools.seam.internal.core.SeamProject@27d0820, numberguess) ==>> projectName (numberguess)
!ENTRY org.jboss.tools.seam.core 4 0 2010-11-17 01:48:39.878
!MESSAGE NumberGuess [in NumberGuess.java [in org.jboss.seam.example.numberguess [in src [in numberguess]]]] does not exist
!STACK 1
Java Model Exception: Java Model Status [NumberGuess [in NumberGuess.java [in org.jboss.seam.example.numberguess [in src [in numberguess]]]] does not exist]
at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:784)
at org.eclipse.jdt.internal.core.SourceType.newSupertypeHierarchy(SourceType.java:726)
at org.eclipse.jdt.internal.core.SourceType.newSupertypeHierarchy(SourceType.java:678)
at org.jboss.tools.common.el.core.resolver.TypeInfoCollector$SuperTypeInfo.<init>(TypeInfoCollector.java:800)
at org.jboss.tools.common.el.core.resolver.TypeInfoCollector.getSuperTypes(TypeInfoCollector.java:822)
at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.validateComponent(SeamCoreValidator.java:575)
at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.validateAll(SeamCoreValidator.java:349)
at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateAll(ValidatorManager.java:116)
at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateInJob(ValidatorManager.java:81)
at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
!SUBENTRY 1 org.eclipse.jdt.core 4 969 2010-11-17 01:48:39.879
!MESSAGE NumberGuess [in NumberGuess.java [in org.jboss.seam.example.numberguess [in src [in numberguess]]]] does not exist
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Created: (JBIDE-7377) Exception in error log after several files deletion -> ResourceException: Resource 'xxx' does not exist.
by Vitali Yemialyanchyk (JIRA)
Exception in error log after several files deletion -> ResourceException: Resource 'xxx' does not exist.
--------------------------------------------------------------------------------------------------------
Key: JBIDE-7377
URL: https://jira.jboss.org/browse/JBIDE-7377
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: jsp/jsf/xml source editing
Affects Versions: 3.2.0.Beta2
Reporter: Vitali Yemialyanchyk
Assignee: Alexey Kazakov
Priority: Minor
after several files deletion - I get this in Error Log:
org.eclipse.core.internal.resources.ResourceException: Resource '/booking22/src/111/hibernate.cfg.xml' does not exist.
at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:326)
at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:200)
at org.eclipse.core.internal.resources.Resource.deleteMarkers(Resource.java:826)
at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.removeMarkers(ValidatorManager.java:104)
at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validate(ValidatorManager.java:94)
at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateInJob(ValidatorManager.java:78)
at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
all is working correct, but this exception - may be there is no sense to log it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months