[JBoss JIRA] (JBIDE-13309) New Restful Webservice wizard shouldn't change web.xml by default
by Pete Muir (JIRA)
Pete Muir created JBIDE-13309:
---------------------------------
Summary: New Restful Webservice wizard shouldn't change web.xml by default
Key: JBIDE-13309
URL: https://issues.jboss.org/browse/JBIDE-13309
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Reporter: Pete Muir
Assignee: Brian Fitzpatrick
We recommend the class-style activation of JAX-RS applications
{code}
/**
* A class extending {@link Application} and annotated with @ApplicationPath is the Java EE 6
* "no XML" approach to activating JAX-RS.
*
* <p>
* Resources are served relative to the servlet path specified in the {@link ApplicationPath}
* annotation.
* </p>
*/
@ApplicationPath("/rest")
public class JaxRsActivator extends Application {
/* class body intentionally left blank */
}
{code}
JBDS should offer this as the default approach.
--
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, 6 months
[JBoss JIRA] (JBDS-2436) Create a new HTML5 project from Central - fails to deploy on JBoss AS 7.1.1
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-2436?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-2436:
-------------------------------------
It works for me when I didn't have any existing projects on the server.
Then I tried deploying the java ee web project first, then stopping the server (while leaving the project deployed) and then Start on server on the html5 project. But it still deployed fine and I didn't see any problem.
Len, any other specific way to reproduce this?
> Create a new HTML5 project from Central - fails to deploy on JBoss AS 7.1.1
> ---------------------------------------------------------------------------
>
> Key: JBDS-2436
> URL: https://issues.jboss.org/browse/JBDS-2436
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 6.0.0.GA
> Environment: uname -a
> Linux ldimaggi.csb 2.6.32-279.9.1.el6.x86_64 #1 SMP Fri Aug 31 09:04:24 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux
> Version: 6.0.0.GA
> Build id: GA-v20121206-1855-B186
> Build date: 20121206-1855
> jboss-as-7.1.1.Final (Brontes)
> java -version
> java version "1.7.0_05-icedtea"
> OpenJDK Runtime Environment (rhel-2.2.1.el6_3.3-x86_64)
> OpenJDK 64-Bit Server VM (build 23.0-b21, mixed mode)
> Reporter: Len DiMaggio
> Assignee: Snjezana Peco
> Priority: Blocker
> Fix For: 6.0.1.GA
>
>
> Seeing this exception running the HTML5 new project (created from Central)
> 16:54:09,961 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
> 16:54:11,497 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
> 16:54:11,607 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
> 16:54:16,948 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
> 16:54:17,013 INFO [org.xnio] XNIO Version 3.0.3.GA
> 16:54:17,027 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
> 16:54:17,037 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
> 16:54:17,070 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
> 16:54:17,079 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
> 16:54:17,091 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
> 16:54:17,103 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
> 16:54:17,112 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
> 16:54:17,119 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
> 16:54:17,147 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
> 16:54:17,264 INFO [org.jboss.as.security] (MSC service thread 1-8) JBAS013100: Current PicketBox version=4.0.7.Final
> 16:54:17,394 INFO [org.jboss.as.connector] (MSC service thread 1-1) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
> 16:54:17,602 INFO [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service
> 16:54:17,605 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) JBAS015400: Bound mail session [java:jboss/mail/Default]
> 16:54:18,345 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
> 16:54:19,286 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-5) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
> 16:54:20,538 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
> 16:54:20,754 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-6) JBoss Web Services - Stack CXF Server 4.0.2.GA
> 16:54:21,271 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-7) JBAS015012: Started FileSystemDeploymentService for directory /opt/local/jboss-as-7.1.1/jboss-as-7.1.1.Final/standalone/deployments
> 16:54:21,283 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment jboss-javaee6-webapp.war
> 16:54:21,284 INFO [org.jboss.as.remoting] (MSC service thread 1-6) JBAS017100: Listening on localhost/127.0.0.1:4447
> 16:54:21,284 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on /127.0.0.1:9999
> 16:54:21,580 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment h2console.war
> 16:54:21,581 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found jboss-as-kitchensink-html5-mobile.war in deployment directory. To trigger deployment create a file called jboss-as-kitchensink-html5-mobile.war.dodeploy
> 16:54:21,582 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found jboss-javaee6-webapp.war in deployment directory. To trigger deployment create a file called jboss-javaee6-webapp.war.dodeploy
> 16:54:21,765 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "h2console.war"
> 16:54:21,765 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "jboss-as-kitchensink-html5-mobile.war"
> 16:54:21,765 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "jboss-javaee6-webapp.war"
> 16:54:23,158 INFO [org.jboss.as.jpa] (MSC service thread 1-3) JBAS011401: Read persistence.xml for primary
> 16:54:23,540 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'implClass=org.jboss.shrinkwrap.resolver.impl.maven.MavenBuilderImpl' for service type 'org.jboss.shrinkwrap.resolver.api.maven.MavenDependencyResolver'
> 16:54:23,541 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment jboss-as-kitchensink-html5-mobile.war
> 16:54:23,542 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'implementingClassName=org.jboss.shrinkwrap.impl.base.ConfigurableArchiveImpl' for service type 'org.jboss.shrinkwrap.spi.Configurable'
> 16:54:23,544 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'implementingClassName=org.jboss.shrinkwrap.impl.base.GenericArchiveImpl' for service type 'org.jboss.shrinkwrap.api.GenericArchive'
> 16:54:23,545 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'extension=.jar' for service type 'org.jboss.shrinkwrap.api.GenericArchive'
> 16:54:23,546 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'archiveFormat=UNKNOWN' for service type 'org.jboss.shrinkwrap.api.GenericArchive'
> 16:54:23,553 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named MemberRegistration in deployment unit deployment "jboss-as-kitchensink-html5-mobile.war" are as follows:
> java:global/jboss-as-kitchensink-html5-mobile/MemberRegistration!org.jboss.tools.example.html5.service.MemberRegistration
> java:app/jboss-as-kitchensink-html5-mobile/MemberRegistration!org.jboss.tools.example.html5.service.MemberRegistration
> java:module/MemberRegistration!org.jboss.tools.example.html5.service.MemberRegistration
> java:global/jboss-as-kitchensink-html5-mobile/MemberRegistration
> java:app/jboss-as-kitchensink-html5-mobile/MemberRegistration
> java:module/MemberRegistration
> 16:54:23,548 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'implementingClassName=org.jboss.shrinkwrap.impl.base.serialization.ZipSerializableViewImpl' for service type 'org.jboss.shrinkwrap.api.serialization.SerializableView'
> 16:54:23,557 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named MemberService in deployment unit deployment "jboss-as-kitchensink-html5-mobile.war" are as follows:
> java:global/jboss-as-kitchensink-html5-mobile/MemberService!org.jboss.tools.example.html5.rest.MemberService
> java:app/jboss-as-kitchensink-html5-mobile/MemberService!org.jboss.tools.example.html5.rest.MemberService
> java:module/MemberService!org.jboss.tools.example.html5.rest.MemberService
> java:global/jboss-as-kitchensink-html5-mobile/MemberService
> java:app/jboss-as-kitchensink-html5-mobile/MemberService
> java:module/MemberService
> 16:54:23,559 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'implementingClassName=org.jboss.shrinkwrap.impl.base.spec.JavaArchiveImpl' for service type 'org.jboss.shrinkwrap.api.spec.JavaArchive'
> 16:54:23,561 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'extension=.jar' for service type 'org.jboss.shrinkwrap.api.spec.JavaArchive'
> 16:54:23,562 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'archiveFormat=ZIP' for service type 'org.jboss.shrinkwrap.api.spec.JavaArchive'
> 16:54:23,563 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'implementingClassName=org.jboss.shrinkwrap.impl.base.exporter.tar.TarExporterImpl' for service type 'org.jboss.shrinkwrap.api.exporter.TarExporter'
> 16:54:23,564 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'extension=.tar' for service type 'org.jboss.shrinkwrap.api.exporter.TarExporter'
> 16:54:23,565 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'implementingClassName=org.jboss.shrinkwrap.impl.base.importer.zip.ZipImporterImpl' for service type 'org.jboss.shrinkwrap.api.importer.ZipImporter'
> 16:54:23,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'extension=.jar' for service type 'org.jboss.shrinkwrap.api.importer.ZipImporter'
> 16:54:23,566 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'implementingClassName=org.jboss.shrinkwrap.impl.base.importer.tar.TarImporterImpl' for service type 'org.jboss.shrinkwrap.api.importer.TarImporter'
> 16:54:23,567 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'extension=.tar' for service type 'org.jboss.shrinkwrap.api.importer.TarImporter'
> 16:54:23,568 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'implementingClassName=org.jboss.shrinkwrap.impl.base.spec.WebArchiveImpl' for service type 'org.jboss.shrinkwrap.api.spec.WebArchive'
> 16:54:23,569 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'extension=.war' for service type 'org.jboss.shrinkwrap.api.spec.WebArchive'
> 16:54:23,569 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'archiveFormat=ZIP' for service type 'org.jboss.shrinkwrap.api.spec.WebArchive'
> 16:54:23,571 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'implementingClassName=org.jboss.shrinkwrap.impl.base.exporter.tar.TarGzExporterImpl' for service type 'org.jboss.shrinkwrap.api.exporter.TarGzExporter'
> 16:54:23,572 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'extension=.tar.gz' for service type 'org.jboss.shrinkwrap.api.exporter.TarGzExporter'
> 16:54:23,573 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'implementingClassName=org.jboss.shrinkwrap.impl.base.serialization.ZipSerializableViewImpl' for service type 'org.jboss.shrinkwrap.api.serialization.ZipSerializableView'
> 16:54:23,575 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'implementingClassName=org.jboss.shrinkwrap.impl.base.importer.ExplodedImporterImpl' for service type 'org.jboss.shrinkwrap.api.importer.ExplodedImporter'
> 16:54:23,576 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'implementingClassName=org.jboss.shrinkwrap.impl.base.exporter.ExplodedExporterImpl' for service type 'org.jboss.shrinkwrap.api.exporter.ExplodedExporter'
> 16:54:23,578 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'implementingClassName=org.jboss.shrinkwrap.impl.base.spec.EnterpriseArchiveImpl' for service type 'org.jboss.shrinkwrap.api.spec.EnterpriseArchive'
> 16:54:23,579 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'extension=.ear' for service type 'org.jboss.shrinkwrap.api.spec.EnterpriseArchive'
> 16:54:23,580 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'archiveFormat=ZIP' for service type 'org.jboss.shrinkwrap.api.spec.EnterpriseArchive'
> 16:54:23,581 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'implementingClassName=org.jboss.shrinkwrap.impl.base.spec.ResourceAdapterArchiveImpl' for service type 'org.jboss.shrinkwrap.api.spec.ResourceAdapterArchive'
> 16:54:23,581 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'extension=.rar' for service type 'org.jboss.shrinkwrap.api.spec.ResourceAdapterArchive'
> 16:54:23,582 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'archiveFormat=ZIP' for service type 'org.jboss.shrinkwrap.api.spec.ResourceAdapterArchive'
> 16:54:23,582 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'implementingClassName=org.jboss.shrinkwrap.impl.base.importer.tar.TarGzImporterImpl' for service type 'org.jboss.shrinkwrap.api.importer.TarGzImporter'
> 16:54:23,583 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'extension=.tar.gz' for service type 'org.jboss.shrinkwrap.api.importer.TarGzImporter'
> 16:54:23,584 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'implementingClassName=org.jboss.shrinkwrap.impl.base.exporter.zip.ZipExporterImpl' for service type 'org.jboss.shrinkwrap.api.exporter.ZipExporter'
> 16:54:23,640 INFO [org.jboss.as.jpa] (MSC service thread 1-5) JBAS011401: Read persistence.xml for primary
> 16:54:23,689 INFO [org.jboss.web] (MSC service thread 1-2) JBAS018210: Registering web context: /h2console
> 16:54:23,787 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002: Processing weld deployment jboss-javaee6-webapp.war
> 16:54:23,789 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named MemberRegistration in deployment unit deployment "jboss-javaee6-webapp.war" are as follows:
> java:global/jboss-javaee6-webapp/MemberRegistration!org.jboss.tools.examples.service.MemberRegistration
> java:app/jboss-javaee6-webapp/MemberRegistration!org.jboss.tools.examples.service.MemberRegistration
> java:module/MemberRegistration!org.jboss.tools.examples.service.MemberRegistration
> java:global/jboss-javaee6-webapp/MemberRegistration
> java:app/jboss-javaee6-webapp/MemberRegistration
> java:module/MemberRegistration
> 16:54:24,119 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) JBAS016005: Starting Services for CDI deployment: jboss-as-kitchensink-html5-mobile.war
> 16:54:24,120 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016005: Starting Services for CDI deployment: jboss-javaee6-webapp.war
> 16:54:24,164 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900 1.1.5 (AS71)
> 16:54:24,196 INFO [org.jboss.as.jpa] (MSC service thread 1-6) JBAS011402: Starting Persistence Unit Service 'jboss-as-kitchensink-html5-mobile.war#primary'
> 16:54:24,203 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [jboss/datasources/jboss-javaee6-webappDS]
> 16:54:24,205 INFO [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011402: Starting Persistence Unit Service 'jboss-javaee6-webapp.war#primary'
> 16:54:24,610 INFO [org.hibernate.annotations.common.Version] (MSC service thread 1-6) HCANN000001: Hibernate Commons Annotations {4.0.1.Final}
> 16:54:24,630 INFO [org.hibernate.Version] (MSC service thread 1-6) HHH000412: Hibernate Core {4.0.1.Final}
> 16:54:24,635 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-6) HHH000206: hibernate.properties not found
> 16:54:24,637 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-6) HHH000021: Bytecode provider name : javassist
> 16:54:24,740 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-6) HHH000204: Processing PersistenceUnitInfo [
> name: primary
> ...]
> 16:54:24,740 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-1) HHH000204: Processing PersistenceUnitInfo [
> name: primary
> ...]
> 16:54:25,058 INFO [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (MSC service thread 1-1) HHH000130: Instantiating explicit connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
> 16:54:25,058 INFO [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (MSC service thread 1-6) HHH000130: Instantiating explicit connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
> 16:54:25,321 INFO [org.hibernate.dialect.Dialect] (MSC service thread 1-6) HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> 16:54:25,321 INFO [org.hibernate.dialect.Dialect] (MSC service thread 1-1) HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> 16:54:25,328 WARN [org.hibernate.dialect.H2Dialect] (MSC service thread 1-1) HHH000431: Unable to determine H2 database version, certain features may not work
> 16:54:25,328 WARN [org.hibernate.dialect.H2Dialect] (MSC service thread 1-6) HHH000431: Unable to determine H2 database version, certain features may not work
> 16:54:25,332 INFO [org.hibernate.engine.jdbc.internal.LobCreatorBuilder] (MSC service thread 1-1) HHH000423: Disabling contextual LOB creation as JDBC driver reported JDBC version [3] less than 4
> 16:54:25,332 INFO [org.hibernate.engine.jdbc.internal.LobCreatorBuilder] (MSC service thread 1-6) HHH000423: Disabling contextual LOB creation as JDBC driver reported JDBC version [3] less than 4
> 16:54:25,347 INFO [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (MSC service thread 1-6) HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory
> 16:54:25,347 INFO [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (MSC service thread 1-1) HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory
> 16:54:25,374 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (MSC service thread 1-1) HHH000397: Using ASTQueryTranslatorFactory
> 16:54:25,374 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (MSC service thread 1-6) HHH000397: Using ASTQueryTranslatorFactory
> 16:54:25,451 INFO [org.hibernate.validator.util.Version] (MSC service thread 1-1) Hibernate Validator 4.2.0.Final
> 16:54:25,464 INFO [org.hibernate.validator.xml.ValidationXmlParser] (MSC service thread 1-1) META-INF/validation.xml found. Parsing XML based configuration.
> 16:54:25,769 INFO [org.hibernate.validator.xml.ValidationXmlParser] (MSC service thread 1-1) Using org.hibernate.validator.HibernateValidator as validation provider.
> 16:54:25,770 INFO [org.hibernate.validator.xml.ValidationXmlParser] (MSC service thread 1-1) Using org.hibernate.validator.messageinterpolation.ResourceBundleMessageInterpolator as message interpolator.
> 16:54:25,770 INFO [org.hibernate.validator.xml.ValidationXmlParser] (MSC service thread 1-1) Using org.hibernate.validator.engine.resolver.DefaultTraversableResolver as traversable resolver.
> 16:54:25,771 INFO [org.hibernate.validator.xml.ValidationXmlParser] (MSC service thread 1-1) Using org.hibernate.validator.engine.ConstraintValidatorFactoryImpl as constraint factory.
> 16:54:25,953 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-6) HHH000227: Running hbm2ddl schema export
> 16:54:25,966 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) HHH000227: Running hbm2ddl schema export
> 16:54:25,968 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-6) HHH000389: Unsuccessful: drop sequence hibernate_sequence
> 16:54:25,969 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-6) Sequence "HIBERNATE_SEQUENCE" not found; SQL statement:
> drop sequence hibernate_sequence [90036-161]
> 16:54:25,972 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) HHH000389: Unsuccessful: drop sequence hibernate_sequence
> 16:54:25,972 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) Sequence "HIBERNATE_SEQUENCE" not found; SQL statement:
> drop sequence hibernate_sequence [90036-161]
> 16:54:25,975 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-6) HHH000230: Schema export complete
> 16:54:25,991 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) HHH000230: Schema export complete
> 16:54:26,009 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016008: Starting weld service for deployment jboss-as-kitchensink-html5-mobile.war
> 16:54:26,010 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016008: Starting weld service for deployment jboss-javaee6-webapp.war
> 16:54:26,384 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.deployment.unit."jboss-javaee6-webapp.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."jboss-javaee6-webapp.war".WeldService: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
> Exception 0 :
> java.lang.NullPointerException
> at org.jboss.weld.manager.BeanManagerImpl.getMostSpecializedBean(BeanManagerImpl.java:931)
> at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:605)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:228)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:207)
> at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:75)
> at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:46)
> at org.jboss.weld.bootstrap.events.BeforeBeanDiscoveryImpl.fire(BeforeBeanDiscoveryImpl.java:46)
> at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:322)
> at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:81)
> at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> at org.jboss.as.weld.services.WeldService.start(WeldService.java:83)
> 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]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05-icedtea]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05-icedtea]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05-icedtea]
> Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
> Exception 0 :
> java.lang.NullPointerException
> at org.jboss.weld.manager.BeanManagerImpl.getMostSpecializedBean(BeanManagerImpl.java:931)
> at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:605)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:228)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:207)
> at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:75)
> at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:46)
> at org.jboss.weld.bootstrap.events.BeforeBeanDiscoveryImpl.fire(BeforeBeanDiscoveryImpl.java:46)
> at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:322)
> at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:81)
> at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:48)
> at org.jboss.weld.bootstrap.events.BeforeBeanDiscoveryImpl.fire(BeforeBeanDiscoveryImpl.java:46)
> at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:322)
> at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:81)
> at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
> ... 5 more
> 16:54:26,686 INFO [org.jboss.web] (MSC service thread 1-7) JBAS018210: Registering web context: /jboss-as-kitchensink-html5-mobile
> 16:54:26,689 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015951: Admin console listening on http://127.0.0.1:9990
> 16:54:26,689 ERROR [org.jboss.as] (MSC service thread 1-4) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 17962ms - Started 306 of 409 services (22 services failed or missing dependencies, 80 services are passive or on-demand)
> 16:54:26,891 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "h2console.war" was rolled back with no failure message
> 16:54:26,908 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "jboss-javaee6-webapp.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"jboss-javaee6-webapp.war\".WeldService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jboss-javaee6-webapp.war\".WeldService: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
> Exception 0 :
> java.lang.NullPointerException
> at org.jboss.weld.manager.BeanManagerImpl.getMostSpecializedBean(BeanManagerImpl.java:931)
> at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:605)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:228)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:207)
> at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:75)
> at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:46)
> at org.jboss.weld.bootstrap.events.BeforeBeanDiscoveryImpl.fire(BeforeBeanDiscoveryImpl.java:46)
> at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:322)
> at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:81)
> at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> "}}
> 16:54:26,913 INFO [org.jboss.as.jpa] (MSC service thread 1-7) JBAS011403: Stopping Persistence Unit Service 'jboss-javaee6-webapp.war#primary'
> 16:54:26,916 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "jboss-as-kitchensink-html5-mobile.war" was rolled back with no failure message
> 16:54:26,916 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-7) HHH000227: Running hbm2ddl schema export
> 16:54:26,924 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-7) HHH000230: Schema export complete
> 16:54:26,928 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) JBAS010409: Unbound data source [jboss/datasources/jboss-javaee6-webappDS]
> 16:54:26,984 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment jboss-javaee6-webapp.war in 78ms
> 16:54:27,135 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016009: Stopping weld service for deployment jboss-as-kitchensink-html5-mobile.war
> 16:54:27,141 INFO [org.jboss.as.jpa] (MSC service thread 1-5) JBAS011403: Stopping Persistence Unit Service 'jboss-as-kitchensink-html5-mobile.war#primary'
> 16:54:27,142 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-5) HHH000227: Running hbm2ddl schema export
> 16:54:27,145 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-5) HHH000230: Schema export complete
> 16:54:27,155 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015877: Stopped deployment jboss-as-kitchensink-html5-mobile.war in 238ms
> 16:54:27,156 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment h2console.war in 264ms
> 16:54:27,157 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.deployment.unit."jboss-javaee6-webapp.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."jboss-javaee6-webapp.war".WeldService: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
> Exception 0 :
> java.lang.NullPointerException
> at org.jboss.weld.manager.BeanManagerImpl.getMostSpecializedBean(BeanManagerImpl.java:931)
> at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:605)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:228)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:207)
> at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:75)
> at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:46)
> at org.jboss.weld.bootstrap.events.BeforeBeanDiscoveryImpl.fire(BeforeBeanDiscoveryImpl.java:46)
> at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:322)
> at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:81)
> at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> 16:54:27,161 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS014654: Composite operation was rolled back
> 16:54:27,166 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.deployment.unit.\"jboss-javaee6-webapp.war\".WeldService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jboss-javaee6-webapp.war\".WeldService: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
> Exception 0 :
> java.lang.NullPointerException
> at org.jboss.weld.manager.BeanManagerImpl.getMostSpecializedBean(BeanManagerImpl.java:931)
> at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:605)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:228)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:207)
> at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:75)
> at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:46)
> at org.jboss.weld.bootstrap.events.BeforeBeanDiscoveryImpl.fire(BeforeBeanDiscoveryImpl.java:46)
> at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:322)
> at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:81)
> at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> "}}}}
> 16:54:27,170 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS014654: Composite operation was rolled back
--
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, 6 months
[JBoss JIRA] (JBIDE-13308) Remove cascading
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-13308:
--------------------------------------
Summary: Remove cascading
Key: JBIDE-13308
URL: https://issues.jboss.org/browse/JBIDE-13308
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Build/Releng
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.1.0.Alpha1
Unlink job by disabling cascading/blocked by upstream. That will make us able to het faster feedback and consume/depend on less Jenkins resources.
--
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, 6 months
[JBoss JIRA] (JBIDE-13272) When using JBDS 6, authentication to a Load Balanced broker fails
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13272?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-13272:
------------------------------------------
Scott gave me the credentials and I could successfully connect to the following:
host: broker.osop.cloud.lab.eng.bos.redhat.com
user: scollier
pw: XXXX
{code}
!ha-broker.png!
{code}
I'll have to find out (I just mailed) about any changes to the broker and make sure that there's no workaround to a possible issue on our side.
> When using JBDS 6, authentication to a Load Balanced broker fails
> -----------------------------------------------------------------
>
> Key: JBIDE-13272
> URL: https://issues.jboss.org/browse/JBIDE-13272
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: LATER
> Environment: 2 Red Hat Linux 6.3 Load balancer (piranha) add-on systems set up in direct routing mode with a virtual server sending traffic to two brokers (real servers). Brokers are running OpenShift Enterprise 1.0. The brokers are set up to do authentication via LDAP (Windows 2008 R2 Active Directory).
> Reporter: Scott Collier
> Assignee: Andre Dietisheim
> Attachments: ha-broker.png
>
>
> When using jbds 6, Authenticating to a load balanced broker (VIP) does not work. It worked in JBDS 5.
--
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, 6 months
[JBoss JIRA] (JBIDE-13272) When using JBDS 6, authentication to a Load Balanced broker fails
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13272?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13272:
-------------------------------------
Attachment: ha-broker.png
> When using JBDS 6, authentication to a Load Balanced broker fails
> -----------------------------------------------------------------
>
> Key: JBIDE-13272
> URL: https://issues.jboss.org/browse/JBIDE-13272
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: LATER
> Environment: 2 Red Hat Linux 6.3 Load balancer (piranha) add-on systems set up in direct routing mode with a virtual server sending traffic to two brokers (real servers). Brokers are running OpenShift Enterprise 1.0. The brokers are set up to do authentication via LDAP (Windows 2008 R2 Active Directory).
> Reporter: Scott Collier
> Assignee: Andre Dietisheim
> Attachments: ha-broker.png
>
>
> When using jbds 6, Authenticating to a load balanced broker (VIP) does not work. It worked in JBDS 5.
--
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, 6 months
[JBoss JIRA] (JBIDE-13272) When using JBDS 6, authentication to a Load Balanced broker fails
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13272?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-13272 at 12/16/12 3:26 PM:
--------------------------------------------------------------------
Scott gave me the credentials and I could successfully connect to the following:
host: broker.osop.cloud.lab.eng.bos.redhat.com
user: scollier
pw: XXXX
!ha-broker.png!
I'll have to find out (I just mailed) about any changes to the broker and make sure that there's no workaround to a possible issue on our side.
was (Author: adietish):
Scott gave me the credentials and I could successfully connect to the following:
host: broker.osop.cloud.lab.eng.bos.redhat.com
user: scollier
pw: XXXX
{code}
!ha-broker.png!
{code}
I'll have to find out (I just mailed) about any changes to the broker and make sure that there's no workaround to a possible issue on our side.
> When using JBDS 6, authentication to a Load Balanced broker fails
> -----------------------------------------------------------------
>
> Key: JBIDE-13272
> URL: https://issues.jboss.org/browse/JBIDE-13272
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: LATER
> Environment: 2 Red Hat Linux 6.3 Load balancer (piranha) add-on systems set up in direct routing mode with a virtual server sending traffic to two brokers (real servers). Brokers are running OpenShift Enterprise 1.0. The brokers are set up to do authentication via LDAP (Windows 2008 R2 Active Directory).
> Reporter: Scott Collier
> Assignee: Andre Dietisheim
> Attachments: ha-broker.png
>
>
> When using jbds 6, Authenticating to a load balanced broker (VIP) does not work. It worked in JBDS 5.
--
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, 6 months