[JBoss JIRA] Created: (JBIDE-5784) Seam project deployment problem when other JSF implementation (myfaces) is used
by Jiri Peterka (JIRA)
Seam project deployment problem when other JSF implementation (myfaces) is used
-------------------------------------------------------------------------------
Key: JBIDE-5784
URL: https://jira.jboss.org/jira/browse/JBIDE-5784
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS, JSF, Seam
Affects Versions: 3.1.0.CR2
Environment: JBT 3.1.0.v201002012242N-H194-CR2, Linux 64, JDK 6
Reporter: Jiri Peterka
Fix For: 3.1.0.CR2
Steps to reproduce:
1. Create new Seam Project
2. Seam Web Project page, Next
3. Java page, Next
4. Web Module page, Next
5. JSF Capabilities, click download library
6. Download JSF 1.2 Apache Myfaces
7. Finish project creation
8. Deploy project
There is error "Both MyFaces and the RI are on your classpath. Please make sure to use only one of the two JSF-implementations."
ASSUMPTION: Deployment should be working or specific configuration forbidden or at least some warning
12:50:47,001 ERROR [MyfacesConfig] Both MyFaces and the RI are on your classpath. Please make sure to use only one of the two JSF-implementations.
12:51:02,352 INFO [config] Unsanitized stacktrace from failed start...
com.sun.faces.config.ConfigurationException: Factory 'javax.faces.application.ApplicationFactory' was not configured properly.
at com.sun.faces.config.processor.FactoryConfigProcessor.verifyFactoriesExist(FactoryConfigProcessor.java:304)
at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:219)
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:335)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:219)
at org.jboss.web.jsf.integration.config.JBossJSFConfigureListener.contextInitialized(JBossJSFConfigureListener.java:71)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3910)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4389)
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:333)
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:150)
at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:462)
at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118)
at org.jboss.web.deployers.WebModule.start(WebModule.java:97)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:207)
at $Proxy38.start(Unknown Source)
at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37)
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:298)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1633)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:935)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:823)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.system.ServiceController.doChange(ServiceController.java:689)
at org.jboss.system.ServiceController.start(ServiceController.java:461)
at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:163)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:99)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1448)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1166)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1187)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1107)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1633)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:935)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:823)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:783)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:371)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:256)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: javax.faces.FacesException: org.jboss.seam.jsf.SeamApplicationFactory
at javax.faces.FactoryFinder.getImplGivenPreviousImpl(FactoryFinder.java:606)
at javax.faces.FactoryFinder.getImplementationInstance(FactoryFinder.java:472)
at javax.faces.FactoryFinder.access$400(FactoryFinder.java:139)
at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:796)
at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:306)
at com.sun.faces.config.processor.FactoryConfigProcessor.verifyFactoriesExist(FactoryConfigProcessor.java:302)
... 68 more
Caused by: java.lang.InstantiationException: org.jboss.seam.jsf.SeamApplicationFactory
at java.lang.Class.newInstance0(Class.java:340)
at java.lang.Class.newInstance(Class.java:308)
at javax.faces.FactoryFinder.getImplGivenPreviousImpl(FactoryFinder.java:604)
... 73 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years
[JBoss JIRA] Commented: (JBIDE-4706) Maven integration issues: setting facets on maven projects and deploying ear on JBoss
by Snjezana Peco (JIRA)
[ https://jira.jboss.org/jira/browse/JBIDE-4706?page=com.atlassian.jira.plu... ]
Snjezana Peco commented on JBIDE-4706:
--------------------------------------
If you are using Eclipse 3.5.2 or Galileo EPP SR2, you have probably faced https://jira.jboss.org/jira/browse/JBDS-1155
A workaround is to open the .settings/org.eclipse.wst.common.component file and remove all the archiveName arguments.
> Maven integration issues: setting facets on maven projects and deploying ear on JBoss
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-4706
> URL: https://jira.jboss.org/jira/browse/JBIDE-4706
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, UpStream
> Environment: Eclipse 3.5
> m2eclipse (0.9.9.20090720)
> JBoss Tools AS M3 developer version
> Subclipse SVN plugin 1.6.3
> Reporter: Alexander Lengson
> Assignee: Snjezana Peco
> Fix For: 3.1.0.CR1
>
> Attachments: container.zip, libs_issue.zip, screenshot-1.jpg, screenshot-2.jpg, without_vars.zip, without_vars_pure_maven.zip
>
>
> Using Maven command line, I created four projects:
> container - the parent Maven project. It also serves as a container for other projects
> prj-jar - a shared library used by all other EJBs
> prj-ejb - sample EJB
> prj-ear - EE container for jar and ejb
> Apache plugins for Maven (both for ejb and ear) are used.
> I've performed the following steps:
> * imported container into SVN
> * opened Eclipse 3.5 with M3 JBoss AS Tools and dev version of m2eclipse (0.9.9.20090720)
> * right-clicked on container and chosen "Checkout as Maven project"
> * waited for the process to be finished
> And the following likely are bugs and/or open questions:
> * for prj-jar: 0.0.1-SNAPSHOT "JBoss Maven Integration" facet is not checked. After checking further configuration suggests "0.0.1-SNAPSHOT" instead of "1.0-SNAPSHOT" as declared in pom.xml already.
> * for prj-ejb: the same, i.e. 0.0.1-SNAPSHOT "JBoss Maven Integration" facet is not checked. After checking further configuration suggests "0.0.1-SNAPSHOT" instead of "1.0-SNAPSHOT" as declared in pom.xml already.
> * for prj-ear: the same.
> * for container: "JBoss Maven Integration" facet is not set and can not be selected. What another facet should be set to meet requirements?
> * for prj-ejb: there is no Project Facet checked at all.
> * for prj-ejb: when I check EJB 3.0 and then click Further Configuration, it does not propose sensible defaults (instead they are as always: src for sources, build/classes for compiled)
> * for prj-ejb: If I provided values for src and build folder mistakenly, it does not allow to change them (even uncheck/check again shows only form with all fields greyed)
> * for prj-ejb: after checking Java 6.0 and EJB 3.0, there are still errors in Problems View:
> EJB Module 3.0 requires Java 5.0 or newer. prj-ejb line 1 Maven Problem --- disappears after Eclipse restart
> One or more constraints have not been satisfied. prj-ejb line 1 Maven Problem --- disappears after Eclipse restart
> Java compiler level does not match the version of the installed Java project facet. prj-ejb Unknown Faceted Project Problem (Java Version Mismatch) --- survives Eclipse restart
> * for prj-ear: Java EE module dependencies are not checked (they may be suggested from the pom.xml)
> * for prj-ear: Maven plugin maven-ear-plugin has the option to put all referenced libraries into Lib directory:
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-ear-plugin</artifactId>
> <version>2.3.2</version>
> <configuration>
> <includeLibInApplicationXml>true</includeLibInApplicationXml>
> ...
> That builds the EAR which contains lib/ folder inside and all references libs like:
> drools-api-5.0.1.jar
> drools-core-5.0.1.jar
> hsqldb-1.8.0.10.jar
> joda-time-1.6.jar
> mvel2-2.0.10.jar
> prj-jar-1.0-SNAPSHOT.jar
> That can be assured by running command:
> container>mvn install
> Eclipse does not put those libraries into deploy dir while making "Full Publish" which causes server startup errors.
> It's reasonable to copy these libraries onto server when using JBoss Server View and debugging server from Eclipse.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years
[JBoss JIRA] Commented: (JBIDE-4706) Maven integration issues: setting facets on maven projects and deploying ear on JBoss
by Brice Ruth (JIRA)
[ https://jira.jboss.org/jira/browse/JBIDE-4706?page=com.atlassian.jira.plu... ]
Brice Ruth commented on JBIDE-4706:
-----------------------------------
The problem with https://issues.sonatype.org/browse/MNGECLIPSE-1586 and https://issues.sonatype.org/browse/MNGECLIPSE-1585 appears to still be happening with m2e 0.10 and JBossTools 3.1 Final.
Importing a POM with the following configuration puts dependencies into /lib/lib/lib at times ...
<?xml version="1.0"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<parent>
<artifactId>ICSParent</artifactId>
<groupId>com.example.ics</groupId>
<version>1.0-SNAPSHOT</version>
</parent>
<modelVersion>4.0.0</modelVersion>
<groupId>com.example.ics</groupId>
<artifactId>icsebill-listener</artifactId>
<packaging>ear</packaging>
<name>icsebill-listener</name>
<version>1.0-SNAPSHOT</version>
<url>http://maven.apache.org</url>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-ear-plugin</artifactId>
<version>2.3.2</version>
<configuration>
<generateApplicationXml>true</generateApplicationXml>
<version>1.4</version>
<includeLibInApplicationXml>true</includeLibInApplicationXml>
<defaultLibBundleDir>lib</defaultLibBundleDir>
<modules>
<ejbModule>
<groupId>com.example.ics</groupId>
<artifactId>ics-mdb</artifactId>
</ejbModule>
</modules>
</configuration>
</plugin>
</plugins>
</build>
<dependencies>
<dependency>
<groupId>com.example.ics</groupId>
<artifactId>ics-mdb</artifactId>
<type>ejb</type>
<version>1.0-SNAPSHOT</version>
</dependency>
</dependencies>
</project>
> Maven integration issues: setting facets on maven projects and deploying ear on JBoss
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-4706
> URL: https://jira.jboss.org/jira/browse/JBIDE-4706
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, UpStream
> Environment: Eclipse 3.5
> m2eclipse (0.9.9.20090720)
> JBoss Tools AS M3 developer version
> Subclipse SVN plugin 1.6.3
> Reporter: Alexander Lengson
> Assignee: Snjezana Peco
> Fix For: 3.1.0.CR1
>
> Attachments: container.zip, libs_issue.zip, screenshot-1.jpg, screenshot-2.jpg, without_vars.zip, without_vars_pure_maven.zip
>
>
> Using Maven command line, I created four projects:
> container - the parent Maven project. It also serves as a container for other projects
> prj-jar - a shared library used by all other EJBs
> prj-ejb - sample EJB
> prj-ear - EE container for jar and ejb
> Apache plugins for Maven (both for ejb and ear) are used.
> I've performed the following steps:
> * imported container into SVN
> * opened Eclipse 3.5 with M3 JBoss AS Tools and dev version of m2eclipse (0.9.9.20090720)
> * right-clicked on container and chosen "Checkout as Maven project"
> * waited for the process to be finished
> And the following likely are bugs and/or open questions:
> * for prj-jar: 0.0.1-SNAPSHOT "JBoss Maven Integration" facet is not checked. After checking further configuration suggests "0.0.1-SNAPSHOT" instead of "1.0-SNAPSHOT" as declared in pom.xml already.
> * for prj-ejb: the same, i.e. 0.0.1-SNAPSHOT "JBoss Maven Integration" facet is not checked. After checking further configuration suggests "0.0.1-SNAPSHOT" instead of "1.0-SNAPSHOT" as declared in pom.xml already.
> * for prj-ear: the same.
> * for container: "JBoss Maven Integration" facet is not set and can not be selected. What another facet should be set to meet requirements?
> * for prj-ejb: there is no Project Facet checked at all.
> * for prj-ejb: when I check EJB 3.0 and then click Further Configuration, it does not propose sensible defaults (instead they are as always: src for sources, build/classes for compiled)
> * for prj-ejb: If I provided values for src and build folder mistakenly, it does not allow to change them (even uncheck/check again shows only form with all fields greyed)
> * for prj-ejb: after checking Java 6.0 and EJB 3.0, there are still errors in Problems View:
> EJB Module 3.0 requires Java 5.0 or newer. prj-ejb line 1 Maven Problem --- disappears after Eclipse restart
> One or more constraints have not been satisfied. prj-ejb line 1 Maven Problem --- disappears after Eclipse restart
> Java compiler level does not match the version of the installed Java project facet. prj-ejb Unknown Faceted Project Problem (Java Version Mismatch) --- survives Eclipse restart
> * for prj-ear: Java EE module dependencies are not checked (they may be suggested from the pom.xml)
> * for prj-ear: Maven plugin maven-ear-plugin has the option to put all referenced libraries into Lib directory:
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-ear-plugin</artifactId>
> <version>2.3.2</version>
> <configuration>
> <includeLibInApplicationXml>true</includeLibInApplicationXml>
> ...
> That builds the EAR which contains lib/ folder inside and all references libs like:
> drools-api-5.0.1.jar
> drools-core-5.0.1.jar
> hsqldb-1.8.0.10.jar
> joda-time-1.6.jar
> mvel2-2.0.10.jar
> prj-jar-1.0-SNAPSHOT.jar
> That can be assured by running command:
> container>mvn install
> Eclipse does not put those libraries into deploy dir while making "Full Publish" which causes server startup errors.
> It's reasonable to copy these libraries onto server when using JBoss Server View and debugging server from Eclipse.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years
[JBoss JIRA] Created: (JBIDE-1719) Some bugs for <h:selectMany*> components.
by Andrei Scherbovich (JIRA)
Some bugs for <h:selectMany*> components.
-----------------------------------------
Key: JBIDE-1719
URL: http://jira.jboss.com/jira/browse/JBIDE-1719
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor
Affects Versions: 2.0.0.GA
Reporter: Andrei Scherbovich
Assigned To: Maxim Areshkau
Attachments: 1.jpg
<h:selectManyCheckbox>
1) Attributes "dir", "disabled", "disabledClass", "enabledClass" don't work
<h:selectManyListBox> and <h:selectManyMenu>
1) Attributes "dir", "disabled", "disabledClass", "enabledClass", "styleClass", "style" don't work
2) Bad highlighting of selected in VPE elements of these components
<f:selectItem>
1) Attribute "escape" doesn't work
(SEE ATTACHMENT)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years