[
https://issues.jboss.org/browse/JBIDE-7876?page=com.atlassian.jira.plugin...
]
Max Andersen commented on JBIDE-7876:
-------------------------------------
You mentioned this API was javadoc'ed:
public String getConfigDirectory();
is what I see in the interface - no docs.
in DeployServer:
// only used for xpaths and is a complete crap hack ;) misleading, too
public String getConfigDirectory() {
return getDeployFolder();
}
I see public IPath getConfigLocationFullPath(); having javadocs but that is not that API
used.
Also looking at for example EJB3ClasspathContainer which uses getConfigDirectory() it does
not seem it is appending "configname" to the directory name thus
either those are also broken or the API changed.
They do IPath deploy = configPath.append(DEPLOY); where configPath =
jbossServer.getConfigDirectory() and DEPLOY is well "deploy" meaning it will
scan
/jboss-as/config/deploy which is wrong -it should be
/jboss-as/config/<configname>/deploy.
Problem with deploying JDBC driver to JBoss AS 6
------------------------------------------------
Key: JBIDE-7876
URL:
https://issues.jboss.org/browse/JBIDE-7876
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta2
Reporter: Snjezana Peco
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR1
The New Seam Web project wizard copies the JDBC driver to the server/lib directory. JBoss
AS 6 doesn't load libraries from this directory. It loads them from
server/<configuration_name>/lib. This is probably a problem in JBoss AS 6.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira