[JBoss Seam] - Re: Developing with Seam 2 and deploying on WebSphere
by Techieexchange
Hi,
"pete.muir(a)jboss.org" wrote : Yes, Websphere comes with JSF 1.1, not 1.2.
|
| Did you follow the instructions for deploying to websphere discussed in the jpa/hibernate2 examples?
I tried to deploy JPA example (target:Websphere) build and deployed on WAS 6.1 express. I just did exactly how it was guided in read-me file of JPA example.
First i got:
| java.lang.ClassCastException:
| org.jboss.seam.jsf.SeamApplication11 incompatible with com.sun.faces.application.ApplicationImpl at com.ibm.ws.jsf.configuration.FacesConfigParser.createFacesFactories
| (FacesConfigParser.java:1019)
| at com.ibm.ws.jsf.configuration.FacesConfigParser.initializeConfiguration FacesConfigParser.java:354)
| at com.ibm.ws.jsf.util.FacesConfigUtil._parseJSFConfiguration (FacesConfigUtil.java:128)
|
then I installed latest fix pack, as recommended here:
http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg1PK47367
Again i re-deployed the same JPA example and now i'm getting:
| [04.01.08 11:46:46:281 CET] 00000021 ExceptionFilt E org.jboss.seam.log.JDKProvider error exception root cause
| [04.01.08 11:46:46:281 CET] 00000021 WebApp E [Servlet Error]-[Faces Servlet]: java.lang.NoSuchMethodError: org/jboss/seam/ui/component/UISeamCommandBase.getValueExpression(Ljava/lang/String;)Ljavax/el/ValueExpression;
| at org.jboss.seam.ui.component.UISeamCommandBase.getUrl(UISeamCommandBase.java:86)
| at org.jboss.seam.ui.renderkit.LinkRendererBase.doEncodeBegin(LinkRendererBase.java:26)
| at org.jboss.seam.ui.util.cdk.RendererBase.encodeBegin(RendererBase.java:79)
| at javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:717)
| at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:242)
| at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:249)
| at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:249)
| at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:594)
| at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108)
| at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:216)
| at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
| at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:220)
| at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:118)
| at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
| at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:989)
| at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:930)
| at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145)
| at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141)
| at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281)
| at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
| at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
| at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:44)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
| at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
| at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
| at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
| at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:766)
| at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:674)
| at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:498)
| at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:464)
| at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3276)
| at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:267)
| at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:811)
| at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1455)
| at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:113)
| at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:454)
| at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:383)
| at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:263)
| at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
| at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
| at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
| at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
| at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
| at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
| at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195)
| at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743)
| at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
| at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)
|
I know there was some JAR incompatibility but how can i find it?
If you say WAS has only JSF 1.1, then how could JPA example worked for you.
Eventhough i tried all tricks by replacing IBM JSF libs / el-api, impl jars etc., but no success yet.
My customers are very impressed on Seam so i have to run atleast a live Seam example as "Proof of Technology".
Please help me.
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116986#4116986
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116986
18 years, 3 months
[JBoss Seam] - [Beginner] launching a non-predefined workflow. Is my approa
by jbaton
Hi all,
I'm new to Seam+Jbpm.
I have to start a simple workflow (a few nodes long), that contains a task for each user that the workflow initiator has chosen amongst a list of users.
All I have is their username. The number of selected users is variable.
I thought of generating the Jpdl definition through Freemarker.
The N tasks are after a fork.
The general form of my workflow is, (for 3 users)
| Start
| |
| Node1
| |
| fork
| | | |
| user1Task,user2Task,user3Task
| | | |
| join
| |
| node2
| |
| end
|
Then, I register the definition and create an instance.
I noticed that unfortunately, Freemarker's directives, based on the sharp #sign collide with the JSF-EL and then, it's not possible to use JSF beans methods as actions but only ActionHandlers (unless I replace the JSFEL before and after the FM processing).
Is my approach correct ? It seems a bit complicated
What is the simple way to share data between ActionHandlers ?
Thank you
Jerome
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116981#4116981
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116981
18 years, 3 months
[Security & JAAS/JBoss] - Re: Can't get Trace output from JBoss Login Modules
by juhap
I was having the same problem. After doing some changes to jboss-log4j.xml I can now see TRACE messages from login modules:
| 2008-01-04 12:48:48,977 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] initialize, instance=@7662474
| 2008-01-04 12:48:48,977 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] Security domain: my-web
| 2008-01-04 12:48:48,977 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] Saw unauthenticatedIdentity=guest
| 2008-01-04 12:48:48,977 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] DatabaseServerLoginModule, dsJndiName=java:/DefaultDS
|
My jboss-log4j.xml is:
| <?xml version="1.0" encoding="UTF-8"?>
| <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
|
| <!-- ===================================================================== -->
| <!-- -->
| <!-- Log4j Configuration -->
| <!-- -->
| <!-- ===================================================================== -->
|
| <!-- $Id: jboss-log4j.xml 65459 2007-09-19 00:25:51Z dimitris(a)jboss.org $ -->
|
| <!--
| | For more configuration infromation and examples see the Jakarta Log4j
| | owebsite: http://jakarta.apache.org/log4j
| -->
|
| <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/" debug="false">
|
| <!-- ================================= -->
| <!-- Preserve messages in a local file -->
| <!-- ================================= -->
|
| <!-- A time/date based rolling appender -->
| <appender name="FILE" class="org.jboss.logging.appender.DailyRollingFileAppender">
| <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
| <param name="File" value="${jboss.server.log.dir}/server.log"/>
| <param name="Append" value="false"/>
|
| <!-- Rollover at midnight each day -->
| <param name="DatePattern" value="'.'yyyy-MM-dd"/>
|
| <!-- Rollover at the top of each hour
| <param name="DatePattern" value="'.'yyyy-MM-dd-HH"/>
| -->
|
| <layout class="org.apache.log4j.PatternLayout">
| <!-- The default pattern: Date Priority [Category] Message\n -->
| <param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>
|
| <!-- The full pattern: Date MS Priority [Category] (Thread:NDC) Message\n
| <param name="ConversionPattern" value="%d %-5r %-5p [%c] (%t:%x) %m%n"/>
| -->
| </layout>
| </appender>
|
| <!-- A size based file rolling appender
| <appender name="FILE" class="org.jboss.logging.appender.RollingFileAppender">
| <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
| <param name="File" value="${jboss.server.log.dir}/server.log"/>
| <param name="Append" value="false"/>
| <param name="MaxFileSize" value="1000KB"/>
| <param name="MaxBackupIndex" value="1"/>
|
| <layout class="org.apache.log4j.PatternLayout">
| <param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>
| </layout>
| </appender>
| -->
|
| <!-- ============================== -->
| <!-- Append messages to the console -->
| <!-- ============================== -->
|
| <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
| <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
| <param name="Target" value="System.out"/>
| <param name="Threshold" value="DEBUG"/>
|
| <layout class="org.apache.log4j.PatternLayout">
| <!-- The default pattern: Date Priority [Category] Message\n -->
| <param name="ConversionPattern" value="%d{ABSOLUTE} %-5p [%c{1}] %m%n"/>
| </layout>
| </appender>
|
| <!-- ====================== -->
| <!-- More Appender examples -->
| <!-- ====================== -->
|
| <!-- Buffer events and log them asynchronously
| <appender name="ASYNC" class="org.apache.log4j.AsyncAppender">
| <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
| <appender-ref ref="FILE"/>
| <appender-ref ref="CONSOLE"/>
| <appender-ref ref="SMTP"/>
| </appender>
| -->
|
| <!-- EMail events to an administrator
| <appender name="SMTP" class="org.apache.log4j.net.SMTPAppender">
| <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
| <param name="Threshold" value="ERROR"/>
| <param name="To" value="admin(a)myhost.domain.com"/>
| <param name="From" value="nobody(a)myhost.domain.com"/>
| <param name="Subject" value="JBoss Sever Errors"/>
| <param name="SMTPHost" value="localhost"/>
| <param name="BufferSize" value="10"/>
| <layout class="org.apache.log4j.PatternLayout">
| <param name="ConversionPattern" value="[%d{ABSOLUTE},%c{1}] %m%n"/>
| </layout>
| </appender>
| -->
|
| <!-- Syslog events
| <appender name="SYSLOG" class="org.apache.log4j.net.SyslogAppender">
| <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
| <param name="Facility" value="LOCAL7"/>
| <param name="FacilityPrinting" value="true"/>
| <param name="SyslogHost" value="localhost"/>
| <layout class="org.apache.log4j.PatternLayout">
| <param name="ConversionPattern" value="[%d{ABSOLUTE},%c{1}] %m%n"/>
| </layout>
| </appender>
| -->
|
| <!-- Log events to JMS (requires a topic to be created)
| <appender name="JMS" class="org.apache.log4j.net.JMSAppender">
| <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
| <param name="Threshold" value="ERROR"/>
| <param name="TopicConnectionFactoryBindingName" value="java:/ConnectionFactory"/>
| <param name="TopicBindingName" value="topic/MyErrorsTopic"/>
| </appender>
| -->
|
| <!-- Log events through SNMP
| <appender name="TRAP_LOG" class="org.apache.log4j.ext.SNMPTrapAppender">
| <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
| <param name="ImplementationClassName" value="org.apache.log4j.ext.JoeSNMPTrapSender"/>
| <param name="ManagementHost" value="127.0.0.1"/>
| <param name="ManagementHostTrapListenPort" value="162"/>
| <param name="EnterpriseOID" value="1.3.6.1.4.1.24.0"/>
| <param name="LocalIPAddress" value="127.0.0.1"/>
| <param name="LocalTrapSendPort" value="161"/>
| <param name="GenericTrapType" value="6"/>
| <param name="SpecificTrapType" value="12345678"/>
| <param name="CommunityString" value="public"/>
| <param name="ForwardStackTraceWithTrap" value="true"/>
| <param name="Threshold" value="DEBUG"/>
| <param name="ApplicationTrapOID" value="1.3.6.1.4.1.24.12.10.22.64"/>
| <layout class="org.apache.log4j.PatternLayout">
| <param name="ConversionPattern" value="%d,%p,[%t],[%c],%m%n"/>
| </layout>
| </appender>
| -->
|
| <!-- Emit events as JMX notifications
| <appender name="JMX" class="org.jboss.monitor.services.JMXNotificationAppender">
| <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
|
| <param name="Threshold" value="WARN"/>
| <param name="ObjectName" value="jboss.system:service=Logging,type=JMXNotificationAppender"/>
|
| <layout class="org.apache.log4j.PatternLayout">
| <param name="ConversionPattern" value="%d %-5p [%c] %m"/>
| </layout>
| </appender>
| -->
|
| <!-- ================ -->
| <!-- Limit categories -->
| <!-- ================ -->
|
| <category name="org.jboss">
| <priority value="TRACE"/>
| </category>
|
|
| <!-- Limit the org.apache category to INFO as its DEBUG is verbose -->
| <category name="org.apache">
| <priority value="INFO"/>
| </category>
|
| <!-- Limit the jacorb category to WARN as its INFO is verbose -->
| <category name="jacorb">
| <priority value="WARN"/>
| </category>
|
| <!-- Limit the org.jgroups category to WARN as its INFO is verbose -->
| <category name="org.jgroups">
| <priority value="WARN"/>
| </category>
|
| <!-- Limit the org.quartz category to INFO as its DEBUG is verbose -->
| <category name="org.quartz">
| <priority value="INFO"/>
| </category>
|
| <!-- Limit JBoss categories
| <category name="org.jboss">
| <priority value="INFO"/>
| </category>
| -->
|
| <!-- Limit the JSR77 categories -->
| <category name="org.jboss.management">
| <priority value="INFO"/>
| </category>
|
| <!-- Show the evolution of the DataSource pool in the logs [inUse/Available/Max]
| <category name="org.jboss.resource.connectionmanager.JBossManagedConnectionPool">
| <priority value="TRACE"/>
| </category>
| -->
|
| <!-- Limit the org.jboss.serial (jboss-serialization) to INFO as its DEBUG is verbose -->
| <category name="org.jboss.serial">
| <priority value="INFO"/>
| </category>
|
| <!-- Decrease the priority threshold for the org.jboss.varia category
| <category name="org.jboss.varia">
| <priority value="DEBUG"/>
| </category>
| -->
|
| <!-- Enable JBossWS message tracing
| <category name="org.jboss.ws.core.MessageTrace">
| <priority value="TRACE"/>
| </category>
| -->
|
| <!--
| | An example of enabling the custom TRACE level priority that is used
| | by the JBoss internals to diagnose low level details. This example
| | turns on TRACE level msgs for the org.jboss.ejb.plugins package and its
| | subpackages. This will produce A LOT of logging output.
| |
| | Note: since jboss AS 4.2.x, the trace level is supported natively by
| | log4j, so although the custom org.jboss.logging.XLevel priority will
| | still work, there is no need to use it. The two examples that follow
| | will both enable trace logging.
| <category name="org.jboss.system">
| <priority value="TRACE" class="org.jboss.logging.XLevel"/>
| </category>
| <category name="org.jboss.ejb.plugins">
| <priority value="TRACE"/>
| </category>
| -->
|
| <!--
| | Logs these events to SNMP:
| - server starts/stops
| - cluster evolution (node death/startup)
| - When an EJB archive is deployed (and associated verified messages)
| - When an EAR archive is deployed
|
| <category name="org.jboss.system.server.Server">
| <priority value="INFO" />
| <appender-ref ref="TRAP_LOG"/>
| </category>
|
| <category name="org.jboss.ha.framework.interfaces.HAPartition.lifecycle">
| <priority value="INFO" />
| <appender-ref ref="TRAP_LOG"/>
| </category>
|
| <category name="org.jboss.deployment.MainDeployer">
| <priority value="ERROR" />
| <appender-ref ref="TRAP_LOG"/>
| </category>
|
| <category name="org.jboss.ejb.EJBDeployer">
| <priority value="INFO" />
| <appender-ref ref="TRAP_LOG"/>
| </category>
|
| <category name="org.jboss.deployment.EARDeployer">
| <priority value="INFO" />
| <appender-ref ref="TRAP_LOG"/>
| </category>
| -->
|
| <!-- Clustering logging -->
| <!-- Uncomment the following to redirect the org.jgroups and
| org.jboss.ha categories to a cluster.log file.
|
| <appender name="CLUSTER" class="org.jboss.logging.appender.RollingFileAppender">
| <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
| <param name="File" value="${jboss.server.log.dir}/cluster.log"/>
| <param name="Append" value="false"/>
| <param name="MaxFileSize" value="500KB"/>
| <param name="MaxBackupIndex" value="1"/>
|
| <layout class="org.apache.log4j.PatternLayout">
| <param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>
| </layout>
| </appender>
| <category name="org.jgroups">
| <priority value="DEBUG" />
| <appender-ref ref="CLUSTER"/>
| </category>
| <category name="org.jboss.ha">
| <priority value="DEBUG" />
| <appender-ref ref="CLUSTER"/>
| </category>
| -->
|
| <!-- ======================= -->
| <!-- Setup the Root category -->
| <!-- ======================= -->
|
| <root>
| <appender-ref ref="CONSOLE"/>
| <appender-ref ref="FILE"/>
| </root>
|
| </log4j:configuration>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116980#4116980
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116980
18 years, 3 months
[JCA/JBoss] - Re: NestedSQLException: Apparently wrong driver class specif
by lal_praveen
I am getting this same error. My ear does'nt contain any jdbc.jar files.
Configuration is:jdk1.6.0_03, jboss-4.2.2.GA, MySQL version 5.0.45, MySQL driver
C:\jboss-4.2.2.GA\server\default\lib\mysql-connector-java-5.1.5-bin.jar
Though I am seeing C:\jboss-4.2.2.GA\server\default\tmp\deploy\tmp29174jboss-local-jdbc.rar-contents\jboss-local-jdbc.jar
file in tmp folder. Probably it is used by jboss. I am deploying ear in default server config.
04:23:10,942 INFO [InjectedDataSourceConnectionProvider] Using provided datasource
04:23:10,957 WARN [JBossManagedConnectionPool] Throwable while attempting to get a new connection: null
org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (org.jboss.resource.JBossResourceException: Apparently wrong driver class specified for URL: class: com.mysql.jdbc.Driver, url: jdbc:mysql//127.0.0.1:3306/Testworld)
at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:179)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:577)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:262)
at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:500)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:341)
at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:315)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:396)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:842)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116976#4116976
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116976
18 years, 3 months