[JBoss JIRA] (JBIDE-10177) web.xml validator should be aware of JSF mappings
by Alexey Kazakov (Created) (JIRA)
web.xml validator should be aware of JSF mappings
-------------------------------------------------
Key: JBIDE-10177
URL: https://issues.jboss.org/browse/JBIDE-10177
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M4
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 3.3.0.Beta1
1. Create JSF2 KickStart project.
2. Create 404.xhtml page in WebContent folder
3. Add the following code to the end of web.xml file:
{code}
<error-page>
<error-code>404</error-code>
<location>/404.jsf</location>
</error-page>
{code}
There should not be any error/warning markers on /404.jsf. This location should be mapped to the 404.xhtml file.
But right now I get: "error: Attribute location references to /404.jsp that does not exist in web content" error message.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (JBIDE-9711) AS7 Adapter : Deployment of OSGI projects fails if the temporary folder doesn't exist
by Libor Zoubek (JIRA)
AS7 Adapter : Deployment of OSGI projects fails if the temporary folder doesn't exist
-------------------------------------------------------------------------------------
Key: JBIDE-9711
URL: https://issues.jboss.org/browse/JBIDE-9711
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M2
Environment: JBossAS Tools 2.3.0.v20110617-0009-H467-M2
Reporter: Libor Zoubek
Assignee: Rob Stryker
Fix For: 3.3.0.M3
I noticed that, in the context of JBIDE-9133, for the existing -broken- AS7 server instances the utility projects were not zipped to the deployment area.
On the other hand, creating a new server instance fixed the issue.
So it seems the temporary folder is only created at the same time as the server instance.
It's an issue in the sense that you can not guarantee the temporary folder will exist at deployment time (could have been deleted by the user ...).
Solution is to call tempdir.mkdirs() right before the actual deployment occurs.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (JBDS-1673) Installer should align with runtime detection
by Max Rydahl Andersen (JIRA)
Installer should align with runtime detection
---------------------------------------------
Key: JBDS-1673
URL: https://issues.jboss.org/browse/JBDS-1673
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: installer
Reporter: Max Rydahl Andersen
Assignee: Denis Golovin
Priority: Blocker
Fix For: 5.0.0.M3, 5.0.0.M2
The installer currently has its own form of server detection which generates a file that runtime detection uses to configure specified servers.
The detection code is not shared and the workflow/power of them are different.
I suggest we either:
A) extract the detection code and uses that in both places
OR
B) change the installer to just ask for directories to scan on every startup which then needs
somehow to be read by the runtime detection and then it takes over all this
WDYT ?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month