[JBoss JIRA] Created: (AS7-1628) Custom JSF deployment does not work altogether with CDI
by George Gastaldi (JIRA)
Custom JSF deployment does not work altogether with CDI
-------------------------------------------------------
Key: AS7-1628
URL: https://issues.jboss.org/browse/AS7-1628
Project: Application Server 7
Issue Type: Bug
Reporter: George Gastaldi
When using another JSF impl (with flag org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL set to true) and a beans.xml is on WEB-INF, the following error occurs:
{code:java}
12:33:07,066 INFO [org.jboss.modules] JBoss Modules version 1.0.1.GA
12:33:07,341 INFO [org.jboss.msc] JBoss MSC version 1.0.0.GA
12:33:07,394 INFO [org.jboss.as] JBoss AS 7.0.1.Final "Zap" starting
12:33:08,212 WARN [org.jboss.as] No security realm defined for native management service, all access will be unrestricted.
12:33:08,220 INFO [org.jboss.as] creating http management service using network interface (management) port (9990)
12:33:08,267 WARN [org.jboss.as] No security realm defined for http management service, all access will be unrestricted.
12:33:08,276 INFO [org.jboss.as.logging] Removing bootstrap log handlers
12:33:08,293 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)
12:33:08,306 INFO [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem.
12:33:08,418 INFO [org.jboss.as.naming] (Controller Boot Thread) Activating Naming Subsystem
12:33:08,426 INFO [org.jboss.as.naming] (MSC service thread 1-5) Starting Naming Service
12:33:08,429 INFO [org.jboss.as.osgi] (Controller Boot Thread) Activating OSGi Subsystem
12:33:08,449 INFO [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem
12:33:08,453 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 3.2.0.Beta2
12:33:08,469 INFO [org.xnio] (MSC service thread 1-4) XNIO Version 3.0.0.Beta3
12:33:08,482 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.0.0.Beta3
12:33:08,724 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-1) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: D:\jdk6\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;D:/powerlogic/jcompany55/java/bin/../jre/bin/server;D:/powerlogic/jcompany55/java/bin/../jre/bin;D:/powerlogic/jcompany55/java/bin/../jre/lib/amd64;D:\powerlogic\jcompany55\java\bin;c:\Program Files\Microsoft IntelliType Pro\;D:\jdk6\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;D:\maven\bin;C:\Program Files (x86)\apache-ant-1.8.2\bin;C:\Program Files\TortoiseSVN\bin;C:\Program Files (x86)\GnuWin32\bin;C:\Program Files (x86)\GNU\GnuPG\pub;C:\Program Files (x86)\Git\bin;D:\powerlogic\jcompany55\eclipse;
12:33:08,731 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
12:33:08,753 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-7) Starting remote JMX connector
12:33:08,757 INFO [org.jboss.as.remoting] (MSC service thread 1-5) Listening on /127.0.0.1:9999
12:33:08,803 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-8) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
12:33:09,018 INFO [org.jboss.as.connector] (MSC service thread 1-3) Starting JCA Subsystem (JBoss IronJacamar 1.0.3.Final)
12:33:09,088 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) Bound data source [java:jboss/datasources/ExampleDS]
12:33:09,394 INFO [org.jboss.as.deployment] (MSC service thread 1-1) Started FileSystemDeploymentService for directory D:\jboss-as-web-7.0.1.Final\standalone\deployments
12:33:09,402 INFO [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Found exemplo.war in deployment directory. To trigger deployment create a file called exemplo.war.dodeploy
12:33:09,403 INFO [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Found hellomyfaces.war in deployment directory. To trigger deployment create a file called hellomyfaces.war.dodeploy
12:33:09,427 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.1.Final "Zap" started in 2588ms - Started 93 of 148 services (55 services are passive or on-demand)
12:33:09,444 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) Starting deployment of "hellomyfaces.war"
12:33:10,229 INFO [org.jboss.as.jpa] (MSC service thread 1-8) added javax.persistence.api dependency to hellomyfaces.war
12:33:10,274 INFO [org.jboss.weld] (MSC service thread 1-5) Processing CDI deployment: hellomyfaces.war
12:33:10,628 INFO [org.jboss.weld] (MSC service thread 1-1) Starting Services for CDI deployment: hellomyfaces.war
12:33:10,652 INFO [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900 1.1.2 (Final)
12:33:10,679 INFO [org.jboss.weld] (MSC service thread 1-4) Starting weld service
12:33:11,055 INFO [org.apache.myfaces.ee6.MyFacesContainerInitializer] (MSC service thread 1-6) Added FacesServlet with mappings=[/faces/*, *.jsf, *.faces]
12:33:11,096 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.PRETTY_HTML' found, using default value true
12:33:11,096 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.ALLOW_JAVASCRIPT' found, using default value true
12:33:11,096 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.RENDER_CLEAR_JAVASCRIPT_FOR_BUTTON' found, using default value false
12:33:11,097 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.RENDER_HIDDEN_FIELDS_FOR_LINK_PARAMS' found, using default value false
12:33:11,097 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.SAVE_FORM_SUBMIT_LINK_IE' found, using default value false
12:33:11,097 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.READONLY_AS_DISABLED_FOR_SELECTS' found, using default value true
12:33:11,097 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.RENDER_VIEWSTATE_ID' found, using default value true
12:33:11,097 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.STRICT_XHTML_LINKS' found, using default value true
12:33:11,097 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.RENDER_FORM_SUBMIT_SCRIPT_INLINE' found, using default value false
12:33:11,098 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.CONFIG_REFRESH_PERIOD' found, using default value 2
12:33:11,098 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.VIEWSTATE_JAVASCRIPT' found, using default value false
12:33:11,098 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.REFRESH_TRANSIENT_BUILD_ON_PSS' found, using default value auto
12:33:11,098 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.REFRESH_TRANSIENT_BUILD_ON_PSS_PRESERVE_STATE' found, using default value false
12:33:11,098 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.VALIDATE_XML' found, using default value false
12:33:11,098 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.WRAP_SCRIPT_CONTENT_WITH_XML_COMMENT_TAG' found, using default value true
12:33:11,099 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) Tomahawk jar not available. Autoscrolling, DetectJavascript, AddResourceClass and CheckExtensionsFilter are disabled now.
12:33:11,122 INFO [org.apache.myfaces.config.DefaultFacesConfigurationProvider] (MSC service thread 1-6) Reading standard config META-INF/standard-faces-config.xml
12:33:11,425 AVISO [org.apache.myfaces.config.annotation.DefaultAnnotationProvider] (MSC service thread 1-6) AnnotationConfigurator does not found classes for annotations in /WEB-INF/classes/org/jboss/test/jsf/hellomyfaces/ . This could happen because maven jetty plugin is used (goal jetty:run). Try configure org.apache.myfaces.annotation.SCAN_PACKAGES init parameter or use jetty:run-exploded instead.
12:33:11,681 INFO [org.apache.myfaces.config.DefaultFacesConfigurationProvider] (MSC service thread 1-6) Reading config : jar:file:D:%5Cjboss-as-web-7.0.1.Final%5Cmodules%5Corg%5Cjboss%5Cas%5Cweld%5Cmain%5Cjboss-as-weld-7.0.1.Final.jar!/META-INF/faces-config.xml
12:33:11,714 GRAVE [org.apache.myfaces.webapp.AbstractFacesInitializer] (MSC service thread 1-6) An error occured while initializing MyFaces: Class org.jboss.as.weld.webtier.jsf.WeldApplicationFactory is no javax.faces.application.ApplicationFactory: java.lang.IllegalArgumentException: Class org.jboss.as.weld.webtier.jsf.WeldApplicationFactory is no javax.faces.application.ApplicationFactory
at javax.faces.FactoryFinder.newFactoryInstance(FactoryFinder.java:311) [myfaces-api-2.1.1.jar:]
at javax.faces.FactoryFinder._getFactory(FactoryFinder.java:277) [myfaces-api-2.1.1.jar:]
at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:200) [myfaces-api-2.1.1.jar:]
at org.apache.myfaces.config.FacesConfigurator.configureApplication(FacesConfigurator.java:489) [myfaces-impl-2.1.1.jar:]
at org.apache.myfaces.config.FacesConfigurator.configure(FacesConfigurator.java:401) [myfaces-impl-2.1.1.jar:]
at org.apache.myfaces.webapp.AbstractFacesInitializer.buildConfiguration(AbstractFacesInitializer.java:309) [myfaces-impl-2.1.1.jar:]
at org.apache.myfaces.webapp.Jsp21FacesInitializer.initContainerIntegration(Jsp21FacesInitializer.java:73) [myfaces-impl-2.1.1.jar:]
at org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces(AbstractFacesInitializer.java:125) [myfaces-impl-2.1.1.jar:]
at org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:111) [myfaces-impl-2.1.1.jar:]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3368) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3821) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:70) [jboss-as-web-7.0.1.Final.jar:7.0.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
12:33:11,725 INFO [org.jboss.web] (MSC service thread 1-6) registering web context: /hellomyfaces
12:33:11,770 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "hellomyfaces.war"
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (AS7-3199) RESTEasy: Can't deploy WebApp if more than one subclass of javax.ws.rs.Application is present
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/AS7-3199?page=com.atlassian.jira.plugin.s... ]
Stuart Douglas reassigned AS7-3199:
-----------------------------------
Assignee: (was: Stuart Douglas)
> RESTEasy: Can't deploy WebApp if more than one subclass of javax.ws.rs.Application is present
> ---------------------------------------------------------------------------------------------
>
> Key: AS7-3199
> URL: https://issues.jboss.org/browse/AS7-3199
> Project: Application Server 7
> Issue Type: Bug
> Components: REST
> Affects Versions: 7.1.0.CR1b
> Reporter: Pavel Janousek
> Attachments: ExampleJAXRS.war
>
>
> If I packed WAR WebApp with more that one subclass of javax.ws.rs.Application, deployment fails with "JBAS011232: Only one JAX-RS Application Class allowed."
> This is not correct because it is against JAX-RS 1.1. specs where invalid situation (in section 2.3.2) is only when "It is a n error for
> more than one application to be deployed +at the same effective servlet mapping+".
> If you have any objections, please compare to reference JEE6 and JAX-RS implementation represented by the GlassFish Prelude 3.1.1 application server with already +fully JEE6 platform support+.
--
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] (JASSIST-177) javassist.bytecode.BadBytecode on weblogic.jdbc.jts.Driver:
by ami tabak (JIRA)
ami tabak created JASSIST-177:
---------------------------------
Summary: javassist.bytecode.BadBytecode on weblogic.jdbc.jts.Driver:
Key: JASSIST-177
URL: https://issues.jboss.org/browse/JASSIST-177
Project: Javassist
Issue Type: Bug
Affects Versions: 3.17.0-GA
Reporter: ami tabak
Assignee: Shigeru Chiba
Attachments: javassist-3-17-GA-weblogicBugSample.zip
Once upgraded from 3.13 to 3.17 GA started receiving the following error:
Might be reappearance of JASSIST-125.
I tried to run the test with JDK 1.5 / 6/ 7 Same result.
java version:1.6.0_16
test: loading class data from pool:weblogic.jdbc.jts.Driver
(2)javassist.CtMethod@3b9ab065[public connect (Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;]
Found method:(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;
Fetching method attribute:
Exception in thread "main" javassist.CannotCompileException: by javassist.bytecode.BadBytecode: connect (Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection; in weblogic.jdbc.jts.Driver: dead code detected at 664. No stackmap table generated.
at javassist.CtBehavior.insertBefore(CtBehavior.java:773)
at javassist.CtBehavior.insertBefore(CtBehavior.java:730)
at com.optier.bug.report.Test.main(Test.java:76)
Caused by: javassist.bytecode.BadBytecode: connect (Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection; in weblogic.jdbc.jts.Driver: dead code detected at 664. No stackmap table generated.
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:103)
at javassist.bytecode.MethodInfo.rebuildStackMap(MethodInfo.java:423)
at javassist.bytecode.MethodInfo.rebuildStackMapIf6(MethodInfo.java:405)
at javassist.CtBehavior.insertBefore(CtBehavior.java:764)
... 2 more
Caused by: javassist.bytecode.BadBytecode: dead code detected at 664. No stackmap table generated.
at javassist.bytecode.stackmap.MapMaker.fixDeadcode(MapMaker.java:314)
at javassist.bytecode.stackmap.MapMaker.fixTypes(MapMaker.java:297)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:151)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:100)
... 5 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, 7 months
[JBoss JIRA] (AS7-4637) Get core resources and operations out of the controller module
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-4637:
-------------------------------------
Summary: Get core resources and operations out of the controller module
Key: AS7-4637
URL: https://issues.jboss.org/browse/AS7-4637
Project: Application Server 7
Issue Type: Task
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 7.2.0.Alpha1
The controller module has a lot of classes related to core resources (resource defs, op handlers, description providers for things like interfaces) that are only in there so they can be commonly accessible to both server and host-controller. This is unnecessary, since host-controller depends on server.
Either move these to server or create a separate module for this stuff; restrict the controller module to the true core ModelController stuff.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-5418) Resource description for platform mbean properties that throw UnsupportedOperationException should say nillable="true"
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-5418:
-------------------------------------
Summary: Resource description for platform mbean properties that throw UnsupportedOperationException should say nillable="true"
Key: AS7-5418
URL: https://issues.jboss.org/browse/AS7-5418
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.2.Final (EAP)
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Minor
Some platform mbean getters are documented to throw a UOE on some VMs. The read-resource handler will catch the UOE and leave the attribute undefined, but the description says it's not nillable.
Specifically, PlatformMBeanDescriptions.getThreadingResource()'s THREAD_CPU_TIME_ENABLED attribute, although there may well be others.
This leads to this unit test failure on jvms where the UOE is thrown:
failure message="thread-cpu-time-enabled is undefined"
type="junit.framework.AssertionFailedError">junit.fra mework.AssertionFailedError: thread-cpu-time-enabled is undefined
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.assertTrue(Assert.java:20)
at
org.jboss.as.platform.mbean.PlatformMBeanResourceUnitTestCase.validateResource(PlatformMBeanResourceUn
itTestCase.java:595)
at org.jboss.as.platform.mbean.PlatformMBeanResourceUnitTestCase.basicResourceTest(PlatformMBeanResourceUnitTestCase.java:563)
at
org.jboss.as.platform.mbean.PlatformMBeanResourceUnitTestCase.testThreadingMXBean(PlatformMBeanResourceUnitTestCase.java:340)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-5879) Eliminate imports of jboss-as-controller classes from arquillian modules
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-5879:
-------------------------------------
Summary: Eliminate imports of jboss-as-controller classes from arquillian modules
Key: AS7-5879
URL: https://issues.jboss.org/browse/AS7-5879
Project: Application Server 7
Issue Type: Task
Affects Versions: 7.1.3.Final (EAP)
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 7.2.0.CR1
The arquillian modules have some imports of classes in the jboss-as-controller module in client-side classes. I've seen them in the ManagementClient classes; there may be others. Basically imports of string constants and some static utility methods.
The controller module is a server side module and its classes should not leak out to client-side 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, 7 months