[JBoss JIRA] (JBIDE-13264) NullPointerException occurs when importing JDF AeroGear HTML5/Mobile
by Denis Golovin (JIRA)
Denis Golovin created JBIDE-13264:
-------------------------------------
Summary: NullPointerException occurs when importing JDF AeroGear HTML5/Mobile
Key: JBIDE-13264
URL: https://issues.jboss.org/browse/JBIDE-13264
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 4.0.0.Final
Reporter: Denis Golovin
Assignee: Fred Bricon
Exceptions related to JPA 2.0 configuration occurs during import:
{code}org.eclipse.wst.common.project.facet.core.FacetedProjectFrameworkException: Failed while installing JPA 2.0.
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1507)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:441)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:324)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339)
at org.jboss.tools.maven.jpa.configurators.JpaProjectConfigurator.configureFacets(JpaProjectConfigurator.java:125)
at org.jboss.tools.maven.jpa.configurators.JpaProjectConfigurator.configure(JpaProjectConfigurator.java:88)
at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:109)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:414)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProject(ProjectConfigurationManager.java:240)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:156)
at org.jboss.tools.maven.project.examples.ImportMavenProjectExampleDelegate.importMavenProjects(ImportMavenProjectExampleDelegate.java:240)
at org.jboss.tools.maven.project.examples.ImportMavenProjectExampleDelegate.importProject(ImportMavenProjectExampleDelegate.java:154)
at org.jboss.tools.maven.project.examples.AbstractImportMavenExample.importProject(AbstractImportMavenExample.java:36)
at org.jboss.tools.project.examples.wizard.NewProjectExamplesJob.runInWorkspace(NewProjectExamplesJob.java:69)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: java.lang.NullPointerException
at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.defaultResourceLocation(JpaFacetInstallDelegate.java:140)
at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.createPersistenceXml(JpaFacetInstallDelegate.java:110)
at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.createProjectXml(JpaFacetInstallDelegate.java:100)
at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.execute_(JpaFacetInstallDelegate.java:61)
at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetActionDelegate.execute(JpaFacetActionDelegate.java:34)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1477)
... 18 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13249) Improve MDB support
by Lucas Ponce (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13249?page=com.atlassian.jira.plugi... ]
Lucas Ponce commented on JBIDE-13249:
-------------------------------------
it would be also interested if as an additional step from top -> down if JBIDE can create the hornetq xml definition of JMS.
Create MDB + JMS definition.
My 2 cents.
> Improve MDB support
> -------------------
>
> Key: JBIDE-13249
> URL: https://issues.jboss.org/browse/JBIDE-13249
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: ejb3
> Reporter: Clebert Suconic
> Assignee: Rob Stryker
>
> I have recently tried creating an MDB and it seems out of date.
> It's not adding any annotations and not asking the user for any parameters.
> You could do something like this:
> - Ask what provider is going to be used...
> Ask what's the queue name to be used
> What Resource Adapter's name. (It would be great if you could inspect the server being used here for the RA's names. Each hornetq pooled connection factory will be a resource adapter name BTW).
> What Queue Name
> you could also provide additional activation properties by either selecting a list of providers. Or even better you could inspect the list of available activation properties, so it would be more generic.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-12156) Apps are not deployed after EAP 6 restart
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12156?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-12156.
---------------------------------
Verified with EAP 6.0.1.ER4.2 with JBDS 6.0.0.CR1e B186
> Apps are not deployed after EAP 6 restart
> -----------------------------------------
>
> Key: JBIDE-12156
> URL: https://issues.jboss.org/browse/JBIDE-12156
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 3.3.0.CR1
> Environment: jbdevstudio-product-universal-5.0.0.v20120605-2229-H183-CR1.jar
> JBoss EAP 6 CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.0.0.Final
>
> Attachments: Screenshot-5.png
>
>
> Found this when verifying JBIDE-11509.
> When you have EAP 6 up and running with an app deployed (any app, e.g. a simple dynamic web project) and then you stop and start the server, the app won't be deployed anymore. This is specific to EAP. In AS 7.1.1 the app gets deployed at the server start.
> With EAP 6 CR1 you will be shown this in the server log:
> {code}
> 15:46:25,828 INFO [org.jboss.as.server.deployment.scanner] JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
> {code}
> I understand this is an issue of EAP, but we need to decide if we can do something to overcome this limitation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13059) test the RichFaces Kitchensink archetype upgrade
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13059?page=com.atlassian.jira.plugi... ]
Brian Leathem commented on JBIDE-13059:
---------------------------------------
[~fbricon] any update on this issue? Is it the RichFaces kitchensink archetype ready to be promoted out of staging by JBIDE standards?
> test the RichFaces Kitchensink archetype upgrade
> ------------------------------------------------
>
> Key: JBIDE-13059
> URL: https://issues.jboss.org/browse/JBIDE-13059
> Project: Tools (JBoss Tools)
> Issue Type: Component Upgrade
> Components: central
> Affects Versions: 4.0.0.Beta1
> Reporter: Brian Leathem
> Assignee: Fred Bricon
> Priority: Critical
> Labels: exampleswarnings
> Fix For: 4.0.0.Final
>
> Attachments: richfaces.png, richfaces1.png
>
>
> RichFaces kitchensink archetype 4.2.3.Final-1 is currently in a JBoss staging repository.
> The archetype will be promoted out of staging when JBoss tools QA is complete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-11602) Provide first class support for client side development
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11602?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-11602:
-----------------------------------------
Regarding JSDT.
In short: it's more dead than alive, but...
Tonight some discussion have taken a continuation at wtp-dev(a)eclipse.org mailing list.
There is an alternate variant have being developed by John Peberdy <john(a)peberdy.ca>. In short, for the Type Resolution he used "NJSDoc as the data source" which "works by executing code in a modified Rhino runtime and analyzing the resulting structure".
He proposes that his JSDT clone is slightly effective and doesn't require to many resources (such as memory and CPU) for the Type Resolution. Also he plans to:
{quote}
Use JSDoc comments to hint types
Add ability to manually hint the type of a local variable (an example of this in Scheme is here [2])
Built in support for AMD spec and maybe CommonJS modules
Improve performance, eliminate more JDT specific code
{quote}
And finally, he hopes to merge its JSDT clone back to WTP.
It seems this project is interresting for the Eclipse Source Editing and JSDT team:
{quote}
John,
We're looking forward to seeing how well it all works. I'm particularly
interested in how/where/if those manual hints are stored between editor
sessions.
Regards,
---
Nitin Dahyabhai
Eclipse WTP Source Editing and JSDT
IBM Rational
{quote}
So, some movement may come with JSDT not so far.
> Provide first class support for client side development
> -------------------------------------------------------
>
> Key: JBIDE-11602
> URL: https://issues.jboss.org/browse/JBIDE-11602
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml source editing
> Reporter: Sebastien Deleuze
> Assignee: Victor Rubezhny
> Fix For: 4.1.x
>
>
> Web application development is currently moving in many projects from end to end server side technologies to HTML5 RIA developed with REST Webservices/ Webscoket on serverside + pure client side technologies GUI (Backbone.js for example).
> Eclipse has been always been quite bad in the field of advanced Javascript development. JSDT was a good start, but its development has been stopped for a few years, and in its current status, it is not really a good tool for real HTML5/JS dev. From what I know, there is no roadmap for strong move on this field in the WTP team. The only real Eclipse initiative for client side development is Orion (http://www.eclipse.org/orion/) outside of the IDE.
> The only other alternative is Aptana Studio 3, acquired last year by AppAccelerator.
> My question is : is there any plan to consider client side development as a first class citizen in JBoss Studio, even if this question apply to the whole Eclipse Ecosystem ? Other IDE like Netbeans or IntelliJ Idea have a strong support for these technologies, and my guess is this lack may be a significant blocking point in the following years.
> Thanks in advance for your feedback.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBDS-2429) NullPointerException when closing JBDS 6.0 beta2
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBDS-2429?page=com.atlassian.jira.plugin.... ]
Snjezana Peco updated JBDS-2429:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/jbosstools/jbosstools-central/pull/44
> NullPointerException when closing JBDS 6.0 beta2
> ------------------------------------------------
>
> Key: JBDS-2429
> URL: https://issues.jboss.org/browse/JBDS-2429
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 6.0.0.Beta2
> Reporter: Itamar Heim
> Assignee: Snjezana Peco
>
> downloaded and installed:
> jbdevstudio-product-universal-6.0.0.Beta2-v20121115-0009-B105.jar
> open jbds.
> agreed to send stats to redhat
> closed jbds
> got:
> SESSION 2012-12-07 14:03:30.380 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.6.0_22
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.jbds.product.product -product com.jboss.jbds.product.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.jbds.product.product -product com.jboss.jbds.product.product
> !ENTRY org.eclipse.osgi 4 0 2012-12-07 14:25:56.679
> !MESSAGE Application error
> !STACK 1
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
> at org.eclipse.swt.SWT.error(SWT.java:4361)
> at org.eclipse.swt.SWT.error(SWT.java:4276)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3529)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3182)
> at org.eclipse.swt.widgets.Display.release(Display.java:3233)
> at org.eclipse.swt.graphics.Device.dispose(Device.java:248)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:140)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
> Caused by: java.lang.NullPointerException
> at org.eclipse.ui.internal.WorkbenchPartReference.subscribe(WorkbenchPartReference.java:209)
> at org.eclipse.ui.internal.WorkbenchPage.createEditorReferenceForPart(WorkbenchPage.java:972)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3078)
> at org.eclipse.ui.internal.WorkbenchPage.access$22(WorkbenchPage.java:3003)
> at org.eclipse.ui.internal.WorkbenchPage$8.run(WorkbenchPage.java:2985)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2981)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2940)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2923)
> at org.jboss.tools.central.JBossCentralActivator.openJBossCentralEditor(JBossCentralActivator.java:377)
> at org.jboss.tools.central.JBossCentralActivator$2$1.run(JBossCentralActivator.java:355)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 18 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-12156) Apps are not deployed after EAP 6 restart
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12156?page=com.atlassian.jira.plugi... ]
Len DiMaggio updated JBIDE-12156:
---------------------------------
Attachment: Screenshot-5.png
Seems OK now
[ldimaggi@ldimaggi bin]$ ./standalone.sh
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/local/EAP6/jboss-eap-6.0
JAVA: /usr/lib/jvm/java-1.6.0-openjdk.x86_64/bin/java
JAVA_OPTS: -server -XX:+UseCompressedOops -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml
=========================================================================
10:34:41,254 INFO [org.jboss.modules] JBoss Modules version 1.1.3.GA-redhat-1
10:34:41,705 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA-redhat-2
10:34:41,790 INFO [org.jboss.as] JBAS015899: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) starting
10:34:43,313 INFO [org.xnio] XNIO Version 3.0.7.GA-redhat-1
10:34:43,315 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
10:34:43,605 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.7.GA-redhat-1
10:34:43,702 INFO [org.jboss.remoting] JBoss Remoting version 3.2.14.GA-redhat-1
10:34:44,006 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
10:34:46,135 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
10:34:44,505 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
10:34:46,251 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011906: Activating OSGi Subsystem
10:34:46,255 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
10:34:46,284 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013171: Activating Security Subsystem
10:34:46,284 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
10:34:46,353 INFO [org.jboss.as.security] (MSC service thread 1-5) JBAS013170: Current PicketBox version=4.0.14.Final-redhat-2
10:34:46,403 INFO [org.jboss.as.connector.logging] (MSC service thread 1-8) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.13.Final-redhat-1)
10:34:46,440 INFO [org.jboss.as.naming] (MSC service thread 1-7) JBAS011802: Starting Naming Service
10:34:46,492 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) JBAS015400: Bound mail session [java:jboss/mail/Default]
10:34:46,718 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
10:34:46,826 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.6.GA-redhat-2
10:34:47,139 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http-/127.0.0.1:8080
10:34:47,639 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
10:34:47,696 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-5) JBAS015012: Started FileSystemDeploymentService for directory /opt/local/EAP6/jboss-eap-6.0/standalone/deployments
10:34:47,700 INFO [org.jboss.as.remoting] (MSC service thread 1-8) JBAS017100: Listening on 127.0.0.1:9999
10:34:47,700 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:4447
10:34:48,781 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
10:34:48,782 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
10:34:48,782 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) started in 10036ms - Started 136 of 217 services (80 services are passive or on-demand)
10:38:17,802 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
10:40:52,975 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "dynproj.war"
10:40:53,545 INFO [org.jboss.as.osgi] (MSC service thread 1-4) JBAS011907: Register module: Module "deployment.dynproj.war:main" from Service Module Loader
10:40:53,706 INFO [org.jboss.web] (MSC service thread 1-3) JBAS018210: Registering web context: /dynproj
10:40:53,903 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "dynproj.war"
^C10:41:36,875 INFO [org.apache.catalina.core.StandardContext] (MSC service thread 1-3) Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started
10:41:36,877 INFO [org.jboss.as.osgi] (MSC service thread 1-5) JBAS011908: Unregister module: Module "deployment.dynproj.war:main" from Service Module Loader
10:41:36,907 INFO [org.jboss.as.logging] JBAS011503: Restored bootstrap log handlers
10:41:36,908 INFO [org.apache.coyote.http11.Http11Protocol] Pausing Coyote HTTP/1.1 on http-/127.0.0.1:8080
10:41:36,914 INFO [org.apache.coyote.http11.Http11Protocol] Stopping Coyote HTTP/1.1 on http-/127.0.0.1:8080
10:41:36,987 INFO [com.arjuna.ats.jbossatx] ARJUNA032018: Destroying TransactionManagerService
10:41:36,989 INFO [com.arjuna.ats.jbossatx] ARJUNA032014: Stopping transaction recovery manager
10:41:37,013 INFO [org.jboss.as.server.deployment] JBAS015877: Stopped deployment dynproj.war in 153ms
10:41:37,026 INFO [org.jboss.as] JBAS015950: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) stopped in 114ms
[ldimaggi@ldimaggi bin]$ ./standalone.sh
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/local/EAP6/jboss-eap-6.0
JAVA: /usr/lib/jvm/java-1.6.0-openjdk.x86_64/bin/java
JAVA_OPTS: -server -XX:+UseCompressedOops -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml
=========================================================================
10:41:46,079 INFO [org.jboss.modules] JBoss Modules version 1.1.3.GA-redhat-1
10:41:46,294 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA-redhat-2
10:41:46,673 INFO [org.jboss.as] JBAS015899: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) starting
10:41:47,731 INFO [org.jboss.as.server.deployment.scanner] JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
10:41:47,749 INFO [org.xnio] XNIO Version 3.0.7.GA-redhat-1
10:41:47,753 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
10:41:47,758 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.7.GA-redhat-1
10:41:47,767 INFO [org.jboss.remoting] JBoss Remoting version 3.2.14.GA-redhat-1
10:41:47,808 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
10:41:47,821 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
10:41:47,831 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
10:41:47,914 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011906: Activating OSGi Subsystem
10:41:47,927 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
10:41:47,947 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013171: Activating Security Subsystem
10:41:47,974 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
10:41:47,981 INFO [org.jboss.as.security] (MSC service thread 1-7) JBAS013170: Current PicketBox version=4.0.14.Final-redhat-2
10:41:48,027 INFO [org.jboss.as.connector.logging] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.13.Final-redhat-1)
10:41:48,076 INFO [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service
10:41:48,081 INFO [org.jboss.as.mail.extension] (MSC service thread 1-8) JBAS015400: Bound mail session [java:jboss/mail/Default]
10:41:48,157 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
10:41:48,229 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-6) JBoss Web Services - Stack CXF Server 4.0.6.GA-redhat-2
10:41:48,310 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http-/127.0.0.1:8080
10:41:48,526 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
10:41:48,750 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory /opt/local/EAP6/jboss-eap-6.0/standalone/deployments
10:41:48,751 INFO [org.jboss.as.remoting] (MSC service thread 1-5) JBAS017100: Listening on 127.0.0.1:4447
10:41:48,757 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 127.0.0.1:9999
10:41:48,763 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "dynproj.war"
10:41:49,076 INFO [org.jboss.as.osgi] (MSC service thread 1-6) JBAS011907: Register module: Module "deployment.dynproj.war:main" from Service Module Loader
10:41:49,193 INFO [org.jboss.web] (MSC service thread 1-3) JBAS018210: Registering web context: /dynproj
10:41:49,210 INFO [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "dynproj.war"
10:41:49,454 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
10:41:49,455 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
10:41:49,455 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) started in 3710ms - Started 176 of 259 services (82 services are passive or on-demand)
^C10:44:15,677 INFO [org.jboss.as.logging] JBAS011503: Restored bootstrap log handlers
> Apps are not deployed after EAP 6 restart
> -----------------------------------------
>
> Key: JBIDE-12156
> URL: https://issues.jboss.org/browse/JBIDE-12156
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 3.3.0.CR1
> Environment: jbdevstudio-product-universal-5.0.0.v20120605-2229-H183-CR1.jar
> JBoss EAP 6 CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.0.0.Final
>
> Attachments: Screenshot-5.png
>
>
> Found this when verifying JBIDE-11509.
> When you have EAP 6 up and running with an app deployed (any app, e.g. a simple dynamic web project) and then you stop and start the server, the app won't be deployed anymore. This is specific to EAP. In AS 7.1.1 the app gets deployed at the server start.
> With EAP 6 CR1 you will be shown this in the server log:
> {code}
> 15:46:25,828 INFO [org.jboss.as.server.deployment.scanner] JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
> {code}
> I understand this is an issue of EAP, but we need to decide if we can do something to overcome this limitation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-11602) Provide first class support for client side development
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11602?page=com.atlassian.jira.plugi... ]
Victor Rubezhny edited comment on JBIDE-11602 at 12/7/12 10:42 AM:
-------------------------------------------------------------------
Regarding the VJET...
In May of 2012 VJET project was proposed as open source project under the Eclipse Web Tools Platform Project (WTP). As the proposal was accepted it moved to http://eclipse.org/vjet/ in late November.
Advantages:
- It works. It needs just to add its compability to a project to be able to use VJET JavaScript editor, Content Assist and so on.
- Provides Content Assistance, Code Search, Syntax and Semantic Checking for JavaScipts.
- Provides Type Declarations using VJETDoc (form of JavaScript comment syntax used to add type information to JavaScript source code.
- Provides Execution/Debugging facilities.
- It's integrated into WTP HTML Editor (this means that it's already integrated into JBoss Tools HTML Editor as well)
- It's an Open Source Project under the Eclipse Web Tools Platform Project (WTP) and it's alive (opposite to JSDT)
- Since it was introduced it became more reliable and stable.
Disadvantages:
- Slowness. It makes Eclipse (and JBT/JBDS) to work significantly slower. The reason is VJET has to compile JavaScripts, build Type info and dependency models as well as to perform Syntax and Semantic checking on the fly.
- Generates too much debug output (but probably it will gone after some tine)
- It still requires to add its capabilities to a project (not a big problem)
- It doesn't solve the Minified jQuery problems as well as some other validation problems even it tries to replace JSDT validation with the own one (I may be mistaken, but I guess it disabled the JSDT Validation when enabled). But I'm sure VJET validation is significantly better that the JSDT one.
- It doesn't solve WTP HTML problems (like that is described in https://issues.jboss.org/browse/JBIDE-3728 Invalid Javascript error - an old Upstream issue (WTP 3.0.3) that still is reproducible today)
Note: It requires a newer Orbit version than we're using in latest JBDS 6.0/JBT 4.0 Target Platforms.
was (Author: vrubezhny):
Regarding the VJET...
In May of 2012 VJET project was proposed as open source project under the Eclipse Web Tools Platform Project (WTP). As the proposal was accepted it moved to http://eclipse.org/vjet/ in late November.
Advantages:
- It works. It needs just to add its compability to a project to be able to use VJET JavaScript editor, Content Assist and so on.
- Provides Content Assistance, Code Search, Syntax and Semantic Checking for JavaScipts.
- Provides TypeDeclarations using VJETDoc (form of JavaScript comment syntax used to add type information to JavaScript source code.
- Provides Execution/Debugging facilities.
- It's integrated into WTP HTML Editor (this means that it's already integrated into JBoss Tools HTML Editor as well)
- It's an Open Source Project under the Eclipse Web Tools Platform Project (WTP) and it's alive (opossite to JSDT)
- Since it was introduced it became more reliable and stable.
Disadvantages:
- Slowness. It makes Eclipse (and JBT/JBDS) to work significantly slower. The reason is VJET has to compile JavaScripts, build Type info and dependency models as well as to perform Syntax and Semantic checking on the fly.
- Generates too much debug output (but probably it will gone after some tine)
- It still requires to add its capabilities to a project (not a big problem)
- It doesn't solve the Minified jQuery problems as well as some other validation problems even it tries to replace JSDT validation with the own one (I may be mistaken, but I guess it disabled the JSDT Validation when enabled). But I'm sure VJET validation is significantly better that the JSDT one.
- It doesn't solve WTP HTML problems (like that is described in https://issues.jboss.org/browse/JBIDE-3728 Invalid Javascript error - an old Upstream issue (WTP 3.0.3) that still is reproducible today)
Note: It requires a newer Orbit version than we're using in latest JBDS 6.0/JBT 4.0 Target Platforms.
> Provide first class support for client side development
> -------------------------------------------------------
>
> Key: JBIDE-11602
> URL: https://issues.jboss.org/browse/JBIDE-11602
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml source editing
> Reporter: Sebastien Deleuze
> Assignee: Victor Rubezhny
> Fix For: 4.1.x
>
>
> Web application development is currently moving in many projects from end to end server side technologies to HTML5 RIA developed with REST Webservices/ Webscoket on serverside + pure client side technologies GUI (Backbone.js for example).
> Eclipse has been always been quite bad in the field of advanced Javascript development. JSDT was a good start, but its development has been stopped for a few years, and in its current status, it is not really a good tool for real HTML5/JS dev. From what I know, there is no roadmap for strong move on this field in the WTP team. The only real Eclipse initiative for client side development is Orion (http://www.eclipse.org/orion/) outside of the IDE.
> The only other alternative is Aptana Studio 3, acquired last year by AppAccelerator.
> My question is : is there any plan to consider client side development as a first class citizen in JBoss Studio, even if this question apply to the whole Eclipse Ecosystem ? Other IDE like Netbeans or IntelliJ Idea have a strong support for these technologies, and my guess is this lack may be a significant blocking point in the following years.
> Thanks in advance for your feedback.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-11602) Provide first class support for client side development
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11602?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-11602:
-----------------------------------------
Regarding the VJET...
In May of 2012 VJET project was proposed as open source project under the Eclipse Web Tools Platform Project (WTP). As the proposal was accepted it moved to http://eclipse.org/vjet/ in late November.
Advantages:
- It works. It needs just to add its compability to a project to be able to use VJET JavaScript editor, Content Assist and so on.
- Provides Content Assistance, Code Search, Syntax and Semantic Checking for JavaScipts.
- Provides TypeDeclarations using VJETDoc (form of JavaScript comment syntax used to add type information to JavaScript source code.
- Provides Execution/Debugging facilities.
- It's integrated into WTP HTML Editor (this means that it's already integrated into JBoss Tools HTML Editor as well)
- It's an Open Source Project under the Eclipse Web Tools Platform Project (WTP) and it's alive (opossite to JSDT)
- Since it was introduced it became more reliable and stable.
Disadvantages:
- Slowness. It makes Eclipse (and JBT/JBDS) to work significantly slower. The reason is VJET has to compile JavaScripts, build Type info and dependency models as well as to perform Syntax and Semantic checking on the fly.
- Generates too much debug output (but probably it will gone after some tine)
- It still requires to add its capabilities to a project (not a big problem)
- It doesn't solve the Minified jQuery problems as well as some other validation problems even it tries to replace JSDT validation with the own one (I may be mistaken, but I guess it disabled the JSDT Validation when enabled). But I'm sure VJET validation is significantly better that the JSDT one.
- It doesn't solve WTP HTML problems (like that is described in https://issues.jboss.org/browse/JBIDE-3728 Invalid Javascript error - an old Upstream issue (WTP 3.0.3) that still is reproducible today)
Note: It requires a newer Orbit version than we're using in latest JBDS 6.0/JBT 4.0 Target Platforms.
> Provide first class support for client side development
> -------------------------------------------------------
>
> Key: JBIDE-11602
> URL: https://issues.jboss.org/browse/JBIDE-11602
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml source editing
> Reporter: Sebastien Deleuze
> Assignee: Victor Rubezhny
> Fix For: 4.1.x
>
>
> Web application development is currently moving in many projects from end to end server side technologies to HTML5 RIA developed with REST Webservices/ Webscoket on serverside + pure client side technologies GUI (Backbone.js for example).
> Eclipse has been always been quite bad in the field of advanced Javascript development. JSDT was a good start, but its development has been stopped for a few years, and in its current status, it is not really a good tool for real HTML5/JS dev. From what I know, there is no roadmap for strong move on this field in the WTP team. The only real Eclipse initiative for client side development is Orion (http://www.eclipse.org/orion/) outside of the IDE.
> The only other alternative is Aptana Studio 3, acquired last year by AppAccelerator.
> My question is : is there any plan to consider client side development as a first class citizen in JBoss Studio, even if this question apply to the whole Eclipse Ecosystem ? Other IDE like Netbeans or IntelliJ Idea have a strong support for these technologies, and my guess is this lack may be a significant blocking point in the following years.
> Thanks in advance for your feedback.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13159) gwt-kitchensink fails to deploy - class not found
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13159?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-13159:
---------------------------------------
I can't still reproduce the issue even after deleting the mentioned directories.
I suppose your maven repository hasn't been updated correctly due to a bad connection and/or some slower maven repo servers.
Could you please specify your environment (OS, JBDS/JBT and JDK)?
> gwt-kitchensink fails to deploy - class not found
> -------------------------------------------------
>
> Key: JBIDE-13159
> URL: https://issues.jboss.org/browse/JBIDE-13159
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: GWT, maven
> Affects Versions: 4.0.0.CR1
> Environment: JBDS 6.0.0.CR1a B133
> JBT 4.0.0.CR1a B97
> OS X 10.8.2
> Oracle Java 1.7
> Reporter: Martin Malina
> Assignee: Fred Bricon
> Fix For: 4.0.0.Final
>
>
> When you try to deploy the gwt project from Central, it fails to deploy with the following error:
> {code}
> 15:27:18,698 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found jboss-gwt-webapp.war in deployment directory. To trigger deployment create a file called jboss-gwt-webapp.war.dodeploy
> 15:27:18,713 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "jboss-gwt-webapp.war"
> 15:27:20,830 INFO [org.jboss.as.jpa] (MSC service thread 1-3) JBAS011401: Read persistence.xml for primary
> 15:27:20,978 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.jboss-gwt-webapp.war" is using a private module ("org.jboss.as.naming:main") which may be changed or removed in future versions without notice.
> 15:27:20,979 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.jboss-gwt-webapp.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
> 15:27:21,021 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment jboss-gwt-webapp.war
> 15:27:21,301 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016005: Starting Services for CDI deployment: jboss-gwt-webapp.war
> 15:27:21,332 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900 1.1.5 (AS71)
> 15:27:21,364 INFO [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011402: Starting Persistence Unit Service 'jboss-gwt-webapp.war#primary'
> 15:27:21,461 INFO [org.hibernate.annotations.common.Version] (MSC service thread 1-1) HCANN000001: Hibernate Commons Annotations {4.0.1.Final}
> 15:27:21,467 INFO [org.hibernate.Version] (MSC service thread 1-1) HHH000412: Hibernate Core {4.0.1.Final}
> 15:27:21,469 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-1) HHH000206: hibernate.properties not found
> 15:27:21,473 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-1) HHH000021: Bytecode provider name : javassist
> 15:27:21,490 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-1) HHH000204: Processing PersistenceUnitInfo [
> name: primary
> ...]
> 15:27:21,499 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.persistenceunit."jboss-gwt-webapp.war#primary": org.jboss.msc.service.StartException in service jboss.persistenceunit."jboss-gwt-webapp.war#primary": Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07]
> Caused by: java.lang.RuntimeException: error trying to scan <jar-file>: vfs:/Users/rasp/jbossqa/runtimes/jboss-as-7.1.1.Final/standalone/deployments/jboss-gwt-webapp.war/WEB-INF/classes/
> at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:854)
> at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:596)
> at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:72)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:162)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:85)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> ... 3 more
> Caused by: java.lang.RuntimeException: JBAS011431: Could not load entity class 'org.jboss.errai.marshalling.server.impl.ServerMarshallingFactoryImpl$30' with PersistenceUnitInfo.getClassLoader()
> at org.jboss.as.jpa.hibernate4.HibernateAnnotationScanner.getPackagesInJar(HibernateAnnotationScanner.java:175)
> at org.hibernate.ejb.Ejb3Configuration.addScannedEntries(Ejb3Configuration.java:489)
> at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:851)
> ... 9 more
> Caused by: java.lang.ClassNotFoundException: org.jboss.errai.marshalling.server.impl.ServerMarshallingFactoryImpl$30 from [Module "deployment.jboss-gwt-webapp.war:main" from Service Module Loader]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
> at org.jboss.as.jpa.hibernate4.HibernateAnnotationScanner.getPackagesInJar(HibernateAnnotationScanner.java:171)
> ... 11 more
> 15:27:21,714 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "jboss-gwt-webapp.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\": Failed to start service"}}
> 15:27:21,742 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment jboss-gwt-webapp.war in 27ms
> 15:27:21,743 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.persistenceunit."jboss-gwt-webapp.war#primary": org.jboss.msc.service.StartException in service jboss.persistenceunit."jboss-gwt-webapp.war#primary": Failed to start service
> 15:27:21,745 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\": Failed to start service"}}}}
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months