[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
13 years, 10 months
[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
13 years, 10 months
[JBoss JIRA] Created: (JBIDE-8938) Renaming a seam project makes the ds.xml undeployable
by Martin Malina (JIRA)
Renaming a seam project makes the ds.xml undeployable
-----------------------------------------------------
Key: JBIDE-8938
URL: https://issues.jboss.org/browse/JBIDE-8938
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.2.1.M1
Environment: jbdevstudio-product-eap-macosx-cocoa-4.1.0.v201105091943R-H400-M1.jar
Mac OS X 10.6 Snow Leopard
Reporter: Martin Malina
Assignee: Alexey Kazakov
If you rename a seam project it fails to deploy again because of failed dependencies:
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "persistence.unit:unitName=#SeamWar" is missing the following dependencies:
Dependency "jboss.jca:name=SeamWarDatasource,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=SeamWarDatasource,service=DataSourceBinding' **")
DEPLOYMENTS IN ERROR:
Deployment "jboss.jca:name=SeamWarDatasource,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=SeamWarDatasource,service=DataSourceBinding' **
This happens because after the renaming, the ds file becomes undeployable. If you mark it as deployable again, you can then deploy it and also the renamed seam project deploys correctly.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] Created: (JBDS-1815) Context menu misnomer when right clicking on struts-config.xml action-mappings in diagram, tree view or outline
by Tony Samlal (JIRA)
Context menu misnomer when right clicking on struts-config.xml action-mappings in diagram, tree view or outline
---------------------------------------------------------------------------------------------------------------
Key: JBDS-1815
URL: https://issues.jboss.org/browse/JBDS-1815
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: runtime
Affects Versions: 4.0.0.GA, 3.0.1.GA, 4.1.0.GA
Environment: Windows 7 64 bit w/ Java 1.6.24, Mac OSX 10.6.8
Reporter: Tony Samlal
Priority: Minor
When right clicking on an existing action mapping to create a local forward or local exception, the only options are global forward and global exception. Using these context menus does indeed create the respective local forward/exception but it is confusing as right clicking on global-exceptions and global-forwards also gives the same options. The local forwards/exceptions should say either "create forward/create exception" as it does in the original Exadel Studio Pro product which Jboss Developer Tools is based on or perhaps just Local Forward/Local Exception.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months