[ https://issues.jboss.org/browse/JBIDE-7876?page=com.atlassian.jira.plugin... ] Max Andersen updated JBIDE-7876: -------------------------------- Fix Version/s: 3.2.0.CR1 Priority: Blocker (was: Major) Rob, I remember you mentioning something about this - do you know if it is a change in AS 6? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7876?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-7876: -------------------------------------- It seems the problem is because the JBossServer.getConfigDirectory() method returns $JBOSS_HOME/server instead of $JBOSS_HOME/server/<configuration_name>. It can also be reproduced with JBoss AS 5.x. JBDS 3.0.1 deploys the JDBC driver correctly. This problem has been introduced in JBDS 4.0.0/JBT 3.2.0. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ 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. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7876?page=com.atlassian.jira.plugin... ] Rob Stryker resolved JBIDE-7876. -------------------------------- Resolution: Done javadoc added, unit test added, fix applied. JBossServer will now call the appropriate method in the IJBossServerRuntime. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira