[JBoss JIRA] Created: (JBIDE-1788) Extend XML Catalog to support jboss.dtd, jboss-app.dtd, and jboss-web.xml
by Juergen Zimmermann (JIRA)
Extend XML Catalog to support jboss.dtd, jboss-app.dtd, and jboss-web.xml
-------------------------------------------------------------------------
Key: JBIDE-1788
URL: http://jira.jboss.com/jira/browse/JBIDE-1788
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: jsp/jsf/xml source editing
Affects Versions: 2.0.1
Environment: Eclipse 3.3.2RC2, WTP 2.0.2RC2, JBossTools nightly 20080201
Reporter: Juergen Zimmermann
When a project has jboss.xml, jboss-app.xml, or jboss-web.xml, then the XML validator of WTP shows warnings regarding a missing dtd, e.g. when the internet connection is broken.
Workaround is to extend the XML catalog (Preferences -> Web and XML -> XML catalog) so that there are entries like
* -//JBoss//DTD JBOSS 4.2//EN
* -//JBoss//DTD J2EE Application 4.2//EN
* -//JBoss//DTD Web Application 4.2//EN
These entries are mapped to a local DTD just like Hibernate Tools are already doing it with
* -//Hibernate/Hibernate Configuration DTD 3.0//EN
* -//Hibernate/Hibernate Mapping DTD 3.0//EN
* -//Hibernate/Hibernate Reverse Engineering DTD 3.0//EN
I'd appreciate to also have mappings for JBoss' XML files.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 8 months
[JBoss JIRA] Created: (JBDS-369) Installer build fails on unziping Dpring IDE
by Denis Golovin (JIRA)
Installer build fails on unziping Dpring IDE
--------------------------------------------
Key: JBDS-369
URL: http://jira.jboss.com/jira/browse/JBDS-369
Project: Developer Studio
Issue Type: Bug
Components: Build
Affects Versions: 2.0.0.alpha
Reporter: Denis Golovin
Assigned To: Denis Golovin
Fix For: 2.0.0.alpha
prepare-springide:
[unzip] Expanding: /qa/services/hudson/hudson_workspace/workspace/devstudio-nightly/org.jboss.ide.eclipse.releng/builders/product/${springide.archive} into /home/hudson/hudson_workspace/workspace/devstudio-nightly/jbds-build/200806211337-nightly/installer/build/distribution/studio/eclipse
BUILD FAILED
/qa/services/hudson/hudson_workspace/workspace/devstudio-nightly/org.jboss.ide.eclipse.releng/builders/build.xml:64: The following error occurred while executing this line:
/qa/services/hudson/hudson_workspace/workspace/devstudio-nightly/org.jboss.ide.eclipse.releng/builders/build.xml:27: The following error occurred while executing this line:
/qa/services/hudson/hudson_workspace/workspace/devstudio-nightly/org.jboss.ide.eclipse.releng/builders/build.xml:45: The following error occurred while executing this line:
/qa/services/hudson/hudson_workspace/workspace/devstudio-nightly/org.jboss.ide.eclipse.releng/builders/product/productBuild.xml:69: The following error occurred while executing this line:
/qa/services/hudson/hudson_workspace/workspace/devstudio-nightly/org.jboss.ide.eclipse.releng/builders/product/productBuild.xml:410: The following error occurred while executing this line:
/qa/services/hudson/hudson_workspace/workspace/devstudio-nightly/org.jboss.ide.eclipse.releng/builders/product/buildInstaller.xml:35: The following error occurred while executing this line:
/qa/services/hudson/hudson_workspace/workspace/devstudio-nightly/org.jboss.ide.eclipse.releng/builders/product/buildInstaller.xml:37: The following error occurred while executing this line:
/qa/services/hudson/hudson_workspace/workspace/devstudio-nightly/org.jboss.ide.eclipse.releng/builders/product/buildInstaller.xml:58: The following error occurred while executing this line:
/home/hudson/hudson_workspace/workspace/devstudio-nightly/jbds-build/200806211337-nightly/installer/build.xml:270: Error while expanding /qa/services/hudson/hudson_workspace/workspace/devstudio-nightly/org.jboss.ide.eclipse.releng/builders/product/${springide.archive}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 8 months
[JBoss JIRA] Commented: (JBIDE-719) Hibernate Tools should be able to use a named Eclipse provided connection
by Dima Geraskov (JIRA)
[ https://jira.jboss.org/jira/browse/JBIDE-719?page=com.atlassian.jira.plug... ]
Dima Geraskov commented on JBIDE-719:
-------------------------------------
1. Create new java project as usual, console configuration hibernate launch with dao exporter
2. Make sure that exporter works
3. Open hibernate.cfg.xml file, remove dialect property, rebuild your console configuration
4. Run exporter again
5. See errors:
org.hibernate.HibernateException: Hibernate Dialect must be explicitly set
at org.hibernate.dialect.DialectFactory.determineDialect(DialectFactory.java:57)
at org.hibernate.dialect.DialectFactory.buildDialect(DialectFactory.java:39)
at org.hibernate.cfg.SettingsFactory.determineDialect(SettingsFactory.java:426)
at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:128)
at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2005)
at org.hibernate.cfg.JDBCMetaDataConfiguration.readFromJDBC(JDBCMetaDataConfiguration.java:40)
at org.hibernate.eclipse.launch.CodeGenerationLaunchDelegate$2.execute(CodeGenerationLaunchDelegate.java:316)
at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:64)
at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:91)
at org.hibernate.eclipse.launch.CodeGenerationLaunchDelegate.buildConfiguration(CodeGenerationLaunchDelegate.java:283)
at org.hibernate.eclipse.launch.CodeGenerationLaunchDelegate.runExporters(CodeGenerationLaunchDelegate.java:216)
at org.hibernate.eclipse.launch.CodeGenerationLaunchDelegate.launch(CodeGenerationLaunchDelegate.java:136)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:764)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:614)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:880)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1083)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Hibernate Tools should be able to use a named Eclipse provided connection
> -------------------------------------------------------------------------
>
> Key: JBIDE-719
> URL: https://jira.jboss.org/jira/browse/JBIDE-719
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Hibernate
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Fix For: 3.0.0.beta1
>
> Attachments: EditConsolleConfig.JPG, EditConsolleConfig_Res1.jpg, EditConsolleConfig_Res2.jpg, EditConsolleConfigNew2.JPG, JBIDE-719.zip, NewSeamProj.JPG
>
> Original Estimate: 4 days
> Remaining Estimate: 4 days
>
> currently we use the settings specified in hibernate.properties/cfg.xml/persistence.xml
> Users should be able to say to use a named WTP provided database connection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 8 months