[JBoss JIRA] Created: (JBIDE-9440) NPE in case of nonexistent WebContent folder
by Alexey Kazakov (JIRA)
NPE in case of nonexistent WebContent folder
--------------------------------------------
Key: JBIDE-9440
URL: https://issues.jboss.org/browse/JBIDE-9440
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam2
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 3.3.0.M3
EXECUTE: Create a web seam project
EXECUTE: Open <project>/.settings/org.eclipse.wst.common.component
EXECUTE: Replace <wb-resource deploy-path="/" source-path="/WebContent"/> by <wb-resource deploy-path="/" source-path="/WebContent11"/>
EXECUTE: Save the file. Clean/re-build the project.
FAILURE: See eclipse log:
{code}
!ENTRY org.jboss.tools.seam.core 4 0 2011-08-01 14:04:28.007
!MESSAGE Resource '/java/WebContent11' does not exist.
!STACK 1
org.eclipse.core.internal.resources.ResourceException: Resource '/java/WebContent11' does not exist.
at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:320)
at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:194)
at org.eclipse.core.internal.resources.Container.members(Container.java:266)
at org.eclipse.core.internal.resources.Container.members(Container.java:249)
at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.validateAllPageXMLFiles(SeamCoreValidator.java:389)
at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.validateAll(SeamCoreValidator.java:380)
at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateAll(ValidatorManager.java:242)
at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateInJob(ValidatorManager.java:98)
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.core.resources 4 368 2011-08-01 14:04:28.008
!MESSAGE Resource '/java/WebContent11' does not exist.
!ENTRY org.jboss.tools.jst.web.kb 4 0 2011-08-01 14:04:28.013
!MESSAGE
!STACK 0
org.jboss.tools.jst.web.kb.validation.KBValidationException
at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateInJob(ValidatorManager.java:113)
at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.lang.NullPointerException
at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.validateAllPageXMLFiles(SeamCoreValidator.java:393)
at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.validateAll(SeamCoreValidator.java:380)
at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateAll(ValidatorManager.java:242)
at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateInJob(ValidatorManager.java:98)
... 2 more
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBIDE-9439) Non AS7 launch configurations don't contain JRE classpath entry
by Snjezana Peco (JIRA)
Non AS7 launch configurations don't contain JRE classpath entry
---------------------------------------------------------------
Key: JBIDE-9439
URL: https://issues.jboss.org/browse/JBIDE-9439
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M3
Environment: JBoss Tools trunk
Reporter: Snjezana Peco
Assignee: Rob Stryker
While I was trying to fix JBIDE-9309, I noticed this issue.
Test case:
- create a non AS7 server (JBoss AS 6.0.0.Final, for instance)
- open the server editor and click the Open Launch Configuration link
- click the Classpath (or Source) tab
You will see that the JRE entry doesn't exist either in the Classpath or in the Source tab.
The AS7 launch configuration is created correctly.
Attached is a patch.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBDS-1715) JBossAS Tools has changed EAP default deploy to 'server', JBDS needs to set property for metadata deployment
by Rob Stryker (JIRA)
JBossAS Tools has changed EAP default deploy to 'server', JBDS needs to set property for metadata deployment
-------------------------------------------------------------------------------------------------------------
Key: JBDS-1715
URL: https://issues.jboss.org/browse/JBDS-1715
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: installer
Reporter: Rob Stryker
Assignee: Rob Stryker
Because JBossAS Tools has found most people using EAP are using their own downloaded versions of EAP, these versions are secured. Therefore for out-of-the-box experience, users must switch the deployment location to server-based, or unsecure their EAP, etc.
ASTools has switched to defaulting EAP to server-based, and so a solution needs to be provided to allow JBDS to auto-configure the bundled EAP and created server to default to metadata deployment
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBIDE-9608) When a cdi project is modified, each of projects that depend on it should be updated only once.
by Viacheslav Kabanovich (JIRA)
When a cdi project is modified, each of projects that depend on it should be updated only once.
-----------------------------------------------------------------------------------------------
Key: JBIDE-9608
URL: https://issues.jboss.org/browse/JBIDE-9608
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: cdi
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 3.3.0.M3
Let there be three cdi projects: p1 depends on p2 and p3; p2 depends on p3. All dependencies are explicit. When change in p3 takes place, builder of p3 calls update for dependent projects p1, p2. Now update is implemented recurrently: update of p2 will call update of projects that depend on it, hence update of p1 will be called twice. If there are N projects in similar hierarchy, when the top project is modified, update of the bottom project will be called 2^(N - 2) times. Instead, we should remove recurrence and just collect projects that should be updated.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBIDE-9649) Timeout problem with JBoss 7.0.1.Final
by Tobias Koltsch (JIRA)
Timeout problem with JBoss 7.0.1.Final
--------------------------------------
Key: JBIDE-9649
URL: https://issues.jboss.org/browse/JBIDE-9649
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M2
Environment: Ubuntu 11.04 (x86_64)
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Eclipse 3.7 (Build id: 20110615-0604) with WTP 3.3
JBossAS Tools 2.3.0.v20110624-0505-H8-M2 and 2.3.0.v20110809-1550-H618-M3
Reporter: Tobias Koltsch
Assignee: Rob Stryker
When I start my JBoss with JBossAS tools inside of my eclipse, the server start correctly and prints out the message "JBoss AS 7.0.1.Final "Zap" started in 2073ms - Started 98 of 153 services (55 services are passive or on-demand)". The start timeout is configured with 10 seconds. It seems eclipse didn't notice the server is started, and after 10 seconds I got the error message: „Starting JBoss 7.0.1.Final has encountered a problem. Server JBoss 7.0.1.Final Server failed to start".
With JBoss 7.0.0.Final the timeout work correctly and I got the error only when I use JBoss 7.0.1.Final.
I got this error with the developer milestone 2.3.0.v20110624-0505-H8-M2 as well as with the latest nightly build 2.3.0.v20110829-0855-H677-M3
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBIDE-9316) Missing Java Runtime selector in AS7 runtime definition
by Fred Bricon (JIRA)
Missing Java Runtime selector in AS7 runtime definition
-------------------------------------------------------
Key: JBIDE-9316
URL: https://issues.jboss.org/browse/JBIDE-9316
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M2
Environment: JBT AS plugins from trunk
Reporter: Fred Bricon
Assignee: Rob Stryker
Attachments: java_runtime_selection_as6.jpg, missing_java_runtime_selection_as7.jpg
When creating or modifying an existing AS7 runtime, there is no way you can choose a Java Runtime Environment, like JBoss AS6 or Tomcat server adapters.
It bit me when I wanted to try AS7 with the new JDK7 CR1. It's a severly lacking feature IMHO.
So you need to :
- add the missing UI bits
- make sure AS7 is run using the selected JRE
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months