[JBoss JIRA] Created: (RHDS-270) Split a JBoss AS Server Manager Guide and a Seam Tools Guide
by Michael Yuan (JIRA)
Split a JBoss AS Server Manager Guide and a Seam Tools Guide
------------------------------------------------------------
Key: RHDS-270
URL: http://jira.jboss.com/jira/browse/RHDS-270
Project: Red Hat Developer Studio
Issue Type: Feature Request
Components: Doc - RHDS GettingStartedGuide
Reporter: Michael Yuan
Assigned To: Svetlana mukhina
Fix For: 1.0.0.GA
I think we should keep the GSG really light and concise. Right now, some of chapters reads very long and they discourage the readers to read on. So I propose:
* Split the Server Manager chapter into a separate book called the "JBoss AS Server Manager Reference Guide". The Guide talks about how to setup server runtimes and go through every UI item to cover its features. In the GSG, we will just talk about how to start the JBoss AS 4.2 runtime pre-bundled in RHDS.
* Split all Seam chapters into a "Seam Dev Tools Reference Guide". The Guide talks about how to setup a Seam project from a fresh install of Eclipse+JBoss Tools (i.e, there is no pre-bundled JBoss AS runtime and data source, as they are in RHDS). We will cover all the Seam wizards (new form, new action, generate entity), as well as testing in the separate guide. In GSG, we will just have a chapter on how to setup a Seam project from scratch with tools already in RHDS (i.e., the chapter we already have in the GSG should suffice).
--
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, 6 months
[JBoss JIRA] Created: (JBIDE-1602) Can't generate seam entities / Could not load JPA Configuration
by jneubert (JIRA)
Can't generate seam entities / Could not load JPA Configuration
---------------------------------------------------------------
Key: JBIDE-1602
URL: http://jira.jboss.com/jira/browse/JBIDE-1602
Project: Tools (JBoss Tools)
Issue Type: Bug
Environment: Eclipse 3.3.1
JBoss Tools 2.0.0.GA / Hibernate Tools 3.2.0.GA
Seam 2.0.1.CR
win2k (no whitespace in path)
Reporter: jneubert
When I generate a new Seam 2.0 war or ear project and I call "Seam Generate Entities", I get:
org.eclipse.core.runtime.CoreException: org.hibernate.console.HibernateConsoleRuntimeException: Could not load JPA Configuration
at org.hibernate.eclipse.launch.CodeGenerationLaunchDelegate.launch(CodeGenerationLaunchDelegate.java:151)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:766)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:608)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:601)
at org.jboss.tools.seam.ui.wizard.SeamGenerateEnitiesWizard$1.execute(SeamGenerateEnitiesWizard.java:294)
at org.eclipse.core.commands.operations.DefaultOperationHistory.execute(DefaultOperationHistory.java:511)
at org.jboss.tools.seam.ui.wizard.SeamBaseWizard$1.execute(SeamBaseWizard.java:77)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:101)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1797)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:113)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:934)
at org.jboss.tools.seam.ui.wizard.SeamBaseWizard.performFinish(SeamBaseWizard.java:66)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:742)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:373)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:616)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
at org.eclipse.jface.window.Window.open(Window.java:796)
at org.eclipse.ui.internal.actions.NewWizardShortcutAction.run(NewWizardShortcutAction.java:135)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:546)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
org.eclipse.core.runtime.CoreException[666]: org.hibernate.console.HibernateConsoleRuntimeException: Could not load JPA Configuration
at org.hibernate.console.ConsoleConfiguration.buildConfiguration(ConsoleConfiguration.java:499)
at org.hibernate.console.ConsoleConfiguration.access$0(ConsoleConfiguration.java:484)
at org.hibernate.console.ConsoleConfiguration$2.execute(ConsoleConfiguration.java:203)
at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:65)
at org.hibernate.console.ConsoleConfiguration.buildWith(ConsoleConfiguration.java:185)
at org.hibernate.eclipse.launch.CodeGenerationLaunchDelegate.buildConfiguration(CodeGenerationLaunchDelegate.java:278)
at org.hibernate.eclipse.launch.CodeGenerationLaunchDelegate.runExporters(CodeGenerationLaunchDelegate.java:219)
at org.hibernate.eclipse.launch.CodeGenerationLaunchDelegate.launch(CodeGenerationLaunchDelegate.java:134)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:766)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:608)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:601)
at org.jboss.tools.seam.ui.wizard.SeamGenerateEnitiesWizard$1.execute(SeamGenerateEnitiesWizard.java:294)
at org.eclipse.core.commands.operations.DefaultOperationHistory.execute(DefaultOperationHistory.java:511)
at org.jboss.tools.seam.ui.wizard.SeamBaseWizard$1.execute(SeamBaseWizard.java:77)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:101)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1797)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:113)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:934)
at org.jboss.tools.seam.ui.wizard.SeamBaseWizard.performFinish(SeamBaseWizard.java:66)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:742)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:373)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:616)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
at org.eclipse.jface.window.Window.open(Window.java:796)
at org.eclipse.ui.internal.actions.NewWizardShortcutAction.run(NewWizardShortcutAction.java:135)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:546)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
Caused by: org.hibernate.console.HibernateConsoleRuntimeException: Could not create JPA based Configuration
at org.hibernate.console.ConsoleConfiguration.buildJPAConfiguration(ConsoleConfiguration.java:142)
at org.hibernate.console.ConsoleConfiguration.buildConfiguration(ConsoleConfiguration.java:496)
... 59 more
Caused by: org.hibernate.console.HibernateConsoleRuntimeException: Persistence unit not found: 'null'.
at org.hibernate.console.ConsoleConfiguration.buildJPAConfiguration(ConsoleConfiguration.java:134)
... 60 more
--
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, 7 months
[JBoss JIRA] Commented: (JBDS-178) DocBook Investigation
by Gleb Galkin (JIRA)
[ http://jira.jboss.com/jira/browse/JBDS-178?page=comments#action_12401883 ]
Gleb Galkin commented on JBDS-178:
----------------------------------
Well, I've investigated the problem with line breaking. The conclusion is:
1) If you want to add line-break before or after block element, paragraph for example, you should use element <para> with appropriate role: <para role="space-after"> or <para role="space-before">
2) If you want to add line-break anywhere, you should use processing-instruction <?lb?>
In order to make this features available you should add some code in appropriate files:
1) in *.css:
.space-before{
margin-top:20px;
}
.space-after{
margin-top:20px;
}
.lb{
line-height:20px;
}
2) in *.xsl file for html version:
<xsl:template match="processing-instruction('lb')">
<br class="lb"/>
</xsl:template>
3) in *.xsl file for PDF version:
<!--#### Line breaking ####-->
<xsl:template match="para[@role = 'space-before']">
<fo:block space-before="14.5pt">
<xsl:apply-templates/>
</fo:block>
</xsl:template>
<xsl:template match="para[@role = 'space-after']">
<fo:block space-after="14.5pt">
<xsl:apply-templates/>
</fo:block>
</xsl:template>
<xsl:template match="processing-instruction('lb')">
<fo:block space-before="14.5pt">
<xsl:text />
</fo:block>
</xsl:template>
Note, that the size of line-break is the same in all formats (1pt = 1.38px)
> DocBook Investigation
> ----------------------
>
> Key: JBDS-178
> URL: http://jira.jboss.com/jira/browse/JBDS-178
> Project: Developer Studio
> Issue Type: Task
> Components: documentation
> Affects Versions: 1.0.0.GA
> Reporter: Svetlana mukhina
> Assigned To: Gleb Galkin
> Priority: Optional
> Fix For: 1.1
>
>
> Learn more about DocBook, the tags that we use in our xml, the attributes of the main tags, etc.
--
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, 7 months
[JBoss JIRA] Commented: (JBIDE-675) Large JSF file are too slow to handle, making editor useless for them
by Ronald van Kuijk (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-675?page=comments#action_12401873 ]
Ronald van Kuijk commented on JBIDE-675:
----------------------------------------
>From my experience, the same is true for large xml files? being xml/xsd/... might have a common ground
> Large JSF file are too slow to handle, making editor useless for them
> ---------------------------------------------------------------------
>
> Key: JBIDE-675
> URL: http://jira.jboss.com/jira/browse/JBIDE-675
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JSF, Visual Page Editor
> Affects Versions: ExadelStudioPro4
> Environment: Eclipse 3.2.2
> Exadel Studio 4.0.4
> Kubuntu Feisty Fawn
> 1G RAM
> CPU Intel(R) Pentium(R) 4 CPU 2.80GHz, HyperThreading activated
> Reporter: David Delbecq
> Assigned To: Maxim Areshkau
> Priority: Critical
> Fix For: 2.1
>
> Attachments: .classpath, copy_dump.txt, edit_dump1.txt, edit_dump2.txt, editStructure.txt, JBIDE-675.tar.gz, loading_dump.txt, profiling.tar.gz, stacktraces-rhd2b1.log.gz, tree.txt
>
>
> Post to JIRA, following recommandatiopn here: http://jboss.com/index.html?module=bb&op=viewtopic&t=115447
> When editing JSF files That contains quite a lot of include, it take commonly up to 20 seconds for one character i type to get it's way to the screen. I can even see, after 10 seconds, the cursor goes on step right, and after a new 10 second the character appear in front of the cursor. This make it impossible to use JSF editor from exadel to edit such file, i have to ressort to plain xml editor without completion for facelets tags.
> I will be posting attachement containing description of files involved (sorry, no file content).
--
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, 7 months