[JBoss jBPM] - Re: tomcat and mysql integration - Cannot login
by vsevel
You are right the problem was due to the port.
Now I have:
anonymous wrote : INFO: building session factory
| 30 oct. 2007 15:13:12 org.hibernate.impl.SessionFactoryObjectFactory addInstance
| INFO: Not binding factory to JNDI, no JNDI name configured
| 30 oct. 2007 15:14:23 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
Previously I imported successfully mysql.identity.script.sql. ( I build the war from jbpm-jpdl-3.2.2)
When I am using the user "ernie" or "bert" (the users that are defined in the database), I got the follwing error:
Error 403 Ressource access has been forbidden
anonymous wrote : L'accès à la ressource demandée (L'accès à la ressource demandée a été interdit) a été interdit.
I did not see any error logged into catalina.2007-10-30.log
What configuration needs to be done?
I have the following in web.xml
anonymous wrote : <!--
| This role list should be changed to include all the relevant roles for your
| environment.
| -->
| <security-role>
| <role-name>admin</role-name>
| </security-role>
|
| <!--
| Security constraints - uncomment and optionally customize the role name to require
| a login before access is allowed to the application.
|
| Also, be sure to edit jboss-web.xml to configure the security domain if you are
| deploying inside JBossAS.
| -->
| <security-constraint>
| <web-resource-collection>
| <web-resource-name>Secure Area</web-resource-name>
| <url-pattern>/sa/*</url-pattern>
| <http-method>GET</http-method>
| <http-method>POST</http-method>
| </web-resource-collection>
| <auth-constraint>
| <role-name>user</role-name>
| </auth-constraint>
| </security-constraint>
| <!-- end security constraints -->
|
| <!-- Example Login page - lists user names -->
| <login-config>
| <auth-method>FORM</auth-method>
| <form-login-config>
| <form-login-page>/ua/login-example.jsf</form-login-page>
| <form-error-page>/ua/login-example.jsf?error=true</form-error-page>
| </form-login-config>
| </login-config>
| <!-- End Example Login page - lists user names -->
|
| <!-- Login configuration option #1 - use the login page ==>
| <login-config>
| <auth-method>FORM</auth-method>
| <form-login-config>
| <form-login-page>/ua/login.jsf</form-login-page>
| <form-error-page>/ua/login.jsf?error=true</form-error-page>
| </form-login-config>
| </login-config>
| <!== End Login configuration option #1 -->
|
| <!-- Login configuration option #2 - use basic auth ==>
| <login-config>
| <auth-method>BASIC</auth-method>
| <realm-name>jBPM Administration Console</realm-name>
| </login-config>
| <!== End Login configuration option #2 -->
|
|
|
| <!-- This servlet serves the purpose of executing pending timer jobs. -->
| <!-- JbpmJobExecutorServlet BEGIN -->
|
| <servlet-name>JobExecutorServlet</servlet-name>
| <servlet-class>org.jbpm.job.executor.JobExecutorServlet</servlet-class>
| <load-on-startup>1</load-on-startup>
|
| <servlet-mapping>
| <servlet-name>JobExecutorServlet</servlet-name>
| <url-pattern>/jobs</url-pattern>
| </servlet-mapping>
| <!-- JbpmJobExecutorServlet END -->
|
| <!-- This section is so that the web console can deploy in the jbpm-enterprise.ear module -->
| <!-- EJB LOCAL REFS BEGIN ===
| <ejb-local-ref>
| <ejb-ref-name>ejb/LocalTimerServiceBean</ejb-ref-name>
| <ejb-ref-type>Session</ejb-ref-type>
| <local-home>org.jbpm.scheduler.ejbtimer.LocalTimerServiceHome</local-home>
| org.jbpm.scheduler.ejbtimer.LocalTimerService
| <ejb-link>TimerServiceBean</ejb-link>
| </ejb-local-ref>
| ==== EJB LOCAL REFS END -->
When I am using the users "user" "admin" "manager", I have the following error Login failed. Invalid user name or password.
This users are described in jbpm-console/WEB-INF/access.properties
Is this file is needed when using mysql?
anonymous wrote : # Security configuration for jBPM Administration Console.
| #
| # Customize the properties in this file to define security permissions
| # for different components within the console.
|
| # Require one of the given roles for identity management functionality.
| # Insert a bogus role name to disable identity management (if you are not
| # using the jBPM identity module, for example).
| role.identities=manager
|
| # Fine-grained controls for different levels of identity management.
| role.identities.user=admin
| role.identities.user.add=
| role.identities.user.delete=
| role.identities.user.modify=
|
| role.identities.group=admin
| role.identities.group.add=
| role.identities.group.delete=
| role.identities.group.modify=
|
| # Process definition operations
| role.process.deploy=manager,admin
| role.process.delete=admin
| role.process.start=manager
|
| # Process instance and token operations
| role.execution.suspend=
| role.execution.edit=
| role.execution.delete=
| role.execution.end=
|
| # Task management operations
| role.tasks=
| role.task.assign=manager
| role.task.assign.any=manager
| role.task.modify=
|
| # Job management operations
| role.jobs=admin
| role.jobs.delete=
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100324#4100324
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100324
18Â years, 5Â months
[JBoss Seam] - Bussines logic : separate service?
by enda
Dear friends,
I have discussion question. I am to build architecture for large web application under Seam 2. We already have good back-end from first application version using Hibernate, Spring, JSF + trinidad (navigation uses pageFlowScope).
In existing version we separated service with service locater pattern(facade), so we have nice layers.
I read two books about Seam and went through JBoss tutorial on web. It seems that general approach in Seam is to put all bussines logic into session beans. So session bean takes care about Authorization, Conversations, Bussines and View. It seems to me that there is too many things in. Isn't it better to separate service into a special session beans that will handle service? this beans will act as service locator.
What do you think? maybe I am missing something important in my consideration.
I will be happy for every opinion.
Tomas
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100320#4100320
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100320
18Â years, 5Â months
[JBoss Seam] - Re: Writing SeamTests with Seam 2.0.0. CR2 - What's Changed?
by bsmithjj
| [DEBUG] Test Classpath :
| [DEBUG] c:\work\BusinessIntelligence\InfoStratGui\app\target\classes
| [DEBUG] c:\work\BusinessIntelligence\InfoStratGui\app\target\test-classes
| [DEBUG] C:\Documents and Settings\a428302\.m2\repository\javax\faces\jsf-impl\1.2_04\jsf-impl-1.2_04.jar
| [DEBUG] C:\Documents and Settings\a428302\.m2\repository\javax\transaction\jta\1.0.1B\jta-1.0.1B.jar
| [DEBUG] C:\Documents and Settings\a428302\.m2\repository\junit\junit\3.8.1\junit-3.8.1.jar
| [DEBUG] C:\Documents and Settings\a428302\.m2\repository\javax\servlet\el-api\2.1wFacelets1.1.4\el-api-2.1wFacelets1.1.4.jar
| [DEBUG] C:\Documents and Settings\a428302\.m2\repository\javax\persistence\ejb3-persistence\1.0\ejb3-persistence-1.0.jar
| [DEBUG] C:\Documents and Settings\a428302\.m2\repository\org\jboss\seam\jboss-embedded-all\2.0.0.CR3\jboss-embedded-all-2.0.0.CR3.jar
| [DEBUG] C:\Documents and Settings\a428302\.m2\repository\commons-logging\commons-logging\1.0.4\commons-logging-1.0.4.jar
| [DEBUG] C:\Documents and Settings\a428302\.m2\repository\org\jboss\jboss-ejb3x\4.0.4.EJB3.RC8\jboss-ejb3x-4.0.4.EJB3.RC8.jar
| [DEBUG] C:\Documents and Settings\a428302\.m2\repository\org\jboss\seam\jboss-embedded-api\2.0.0.CR3\jboss-embedded-api-2.0.0.CR3.jar
| [DEBUG] C:\Documents and Settings\a428302\.m2\repository\jconnect\jconnect\6.0\jconnect-6.0.jar
| [DEBUG] C:\Documents and Settings\a428302\.m2\repository\org\testng\testng\5.5\testng-5.5-jdk15.jar
| [DEBUG] C:\Documents and Settings\a428302\.m2\repository\org\jboss\seam\jboss-el\2.0.0.CR3\jboss-el-2.0.0.CR3.jar
| [DEBUG] C:\Documents and Settings\a428302\.m2\repository\org\jboss\seam\hibernate-all\2.0.0.CR3\hibernate-all-2.0.0.CR3.jar
| [DEBUG] C:\Documents and Settings\a428302\.m2\repository\org\jboss\seam\jboss-seam\2.0.0.CR3\jboss-seam-2.0.0.CR3.jar
| [DEBUG] C:\Documents and Settings\a428302\.m2\repository\org\hibernate\hibernate-annotations\3.3.0.GA\hibernate-annotations-3.3.0.GA.jar
| [DEBUG] C:\Documents and Settings\a428302\.m2\repository\javax\servlet\servlet-api\2.5\servlet-api-2.5.jar
| [DEBUG] C:\Documents and Settings\a428302\.m2\repository\javax\servlet\el-ri\2.1wFacelets1.1.4\el-ri-2.1wFacelets1.1.4.jar
| [DEBUG] C:\Documents and Settings\a428302\.m2\repository\com\evergreen\architecture\evg-jaas-components\1.0\evg-jaas-components-1.0.jar
| [DEBUG] C:\Documents and Settings\a428302\.m2\repository\javax\faces\jsf-api\1.2_04\jsf-api-1.2_04.jar
| [DEBUG] C:\Documents and Settings\a428302\.m2\repository\org\hibernate\hibernate-validator\3.0.0.GA\hibernate-validator-3.0.0.GA.jar
| [DEBUG] C:\Documents and Settings\a428302\.m2\repository\org\jboss\seam\thirdparty-all\2.0.0.CR3\thirdparty-all-2.0.0.CR3.jar
| [DEBUG] C:\Documents and Settings\a428302\.m2\repository\org\jboss\seam\jboss-deployers\2.0.0.CR3\jboss-deployers-2.0.0.CR3.jar
| [DEBUG] Setting system property [localRepository]=[C:\Documents and Settings\a428302\.m2\repository]
| [DEBUG] Setting system property [basedir]=[c:\work\BusinessIntelligence\InfoStratGui\app]
|
classes - my compiled application classes, EJB's, entities, JPA, etc.
test-classes - the test classes and the entire directory tree from the bootstrap directory in the Seam 2.0.0.CR3 and a /META-INF/components.xml. Seam is starting but the embedded container is having trouble here.
It seems like all the "ResourcesToDeploy3" blocks in bootstrap-beans.xml are failing - each one results in a message like this:
| ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Start: name=ResourcesToDeploy3 state=Create
| org.jboss.deployers.spi.DeploymentException: Unable to find deployDir from url: file:/c:/work/BusinessIntelligence/InfoStratGui/app/target/test-clas
| ses/deploy/
| at org.jboss.embedded.DeploymentGroup.getDeployerDirUrls(DeploymentGroup.java:536)
| at org.jboss.embedded.DeploymentGroup.getDeployerDirUrlsFromResource(DeploymentGroup.java:522)
| at org.jboss.embedded.DeploymentGroup.addDirectoryByResource(DeploymentGroup.java:470)
| at org.jboss.embedded.DeploymentScanner.start(DeploymentScanner.java:99)
| 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:585)
| at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:55)
| at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:108)
| at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
| at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:103)
| at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:145)
| at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:197)
| at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.install(KernelControllerContextAction.java:136)
| at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:233)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:724)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:445)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:555)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:489)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:289)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:192)
| at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean(AbstractKernelDeployer.java:302)
| at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:272)
| at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:119)
| at org.jboss.kernel.plugins.deployment.xml.BeanXMLDeployer.deploy(BeanXMLDeployer.java:96)
| at org.jboss.embedded.Bootstrap.deployBaseBootstrapUrl(Bootstrap.java:150)
| at org.jboss.embedded.Bootstrap.bootstrapURL(Bootstrap.java:162)
| at org.jboss.embedded.Bootstrap.bootstrap(Bootstrap.java:201)
| at org.jboss.embedded.Bootstrap.bootstrap(Bootstrap.java:214)
| at org.jboss.seam.mock.EmbeddedBootstrap.startAndDeployResources(EmbeddedBootstrap.java:11)
| at org.jboss.seam.mock.BaseSeamTest.startJbossEmbeddedIfNecessary(BaseSeamTest.java:1006)
| at org.jboss.seam.mock.BaseSeamTest.init(BaseSeamTest.java:931)
| at org.jboss.seam.mock.SeamTest.init(SeamTest.java:42)
| 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:585)
| at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:645)
| at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:385)
| at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:141)
| at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:79)
| at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:158)
| at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:103)
| at org.testng.TestRunner.runWorkers(TestRunner.java:673)
| at org.testng.TestRunner.privateRun(TestRunner.java:620)
| at org.testng.TestRunner.run(TestRunner.java:480)
| at org.testng.SuiteRunner.runTest(SuiteRunner.java:278)
| at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:273)
| at org.testng.SuiteRunner.privateRun(SuiteRunner.java:253)
| at org.testng.SuiteRunner.run(SuiteRunner.java:168)
| at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:987)
| at org.testng.TestNG.runSuitesLocally(TestNG.java:951)
| at org.apache.maven.surefire.testng.TestNGExecutor.executeTestNG(TestNGExecutor.java:161)
| at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:101)
| at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
| 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:585)
| at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:275)
| at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:832)
| Caused by: java.net.MalformedURLException: unknown protocol: vfsfile
| at java.net.URL.<init>(URL.java:574)
| at java.net.URL.<init>(URL.java:464)
| at java.net.URL.<init>(URL.java:413)
| at org.jboss.virtual.plugins.context.file.FileHandler.<init>(FileHandler.java:75)
| at org.jboss.virtual.plugins.context.file.FileHandler.<init>(FileHandler.java:89)
| at org.jboss.virtual.plugins.context.file.FileSystemContext.createVirtualFileHandler(FileSystemContext.java:253)
| at org.jboss.virtual.plugins.context.file.FileSystemContext.createVirtualFileHandler(FileSystemContext.java:186)
| at org.jboss.virtual.plugins.context.file.FileSystemContext.<init>(FileSystemContext.java:150)
| at org.jboss.virtual.plugins.context.file.FileSystemContext.<init>(FileSystemContext.java:124)
| at org.jboss.virtual.plugins.context.file.FileSystemContext.<init>(FileSystemContext.java:113)
| at org.jboss.virtual.plugins.context.file.FileSystemContextFactory.getVFS(FileSystemContextFactory.java:54)
| at org.jboss.virtual.VFS.getVFS(VFS.java:132)
| at org.jboss.virtual.VFS.getRoot(VFS.java:146)
| at org.jboss.embedded.DeploymentGroup.getDeployerDirUrls(DeploymentGroup.java:532)
| ... 62 more
|
Thanks,
Brad
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100317#4100317
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100317
18Â years, 5Â months
[JBoss Seam] - Re: Exception trying to run seam on glassfish.java.lang.NoCl
by deepsix
Thanks!
I included these two jars and changed the seam declaration from jar module to ejb module.
But i get a different exception now.
| SMGT0007: Self Management Rules service is enabled
| Application server startup complete.
| Exception occured in J2EEC Phasejava.lang.IllegalArgumentException: Invalid ejb jar [jboss-seam.jar]: it contains zero ejb.
| Note:
| 1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message driven bean.
| 2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar.
| 3. If the jar file contains valid EJBs which are annotated with EJB component level annotations (@Stateless, @Stateful, @MessageDriven), please check server.log to see whether the annotations were processed properly.
| com.sun.enterprise.deployment.backend.IASDeploymentException: Error loading deployment descriptors for module [seam-facelets] -- Invalid ejb jar [jboss-seam.jar]: it contains zero ejb.
|
|
This is how my application.xml looks like.. nothing major.
| <?xml version="1.0" encoding="UTF-8"?>
| <application xmlns="http://java.sun.com/xml/ns/javaee"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd"
| version="5">
|
| <display-name>seam-facelets</display-name>
|
| <module>
| <web>
| <web-uri>sesam-facelets-war.war</web-uri>
| <context-root>/seam-facelets</context-root>
| </web>
| </module>
| <module>
| <ejb>seam-facelets-ejb.jar</ejb>
| </module>
| <module>
| <ejb>jboss-seam.jar</ejb>
| </module>
| </application>
|
I think i am missing something simple somewhere..
just cant figure out what..
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100314#4100314
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100314
18Â years, 5Â months