[JBoss jBPM] - Re: Deployment Problem From Example
by grdzeli_kaci
"colablade" wrote : since IDE 1.6, the deployment is done as the following:
|
| open ur processdefinition.xml in the IDE and u'll find 5 tabs underneath the 3rd is 'deployment', click on it, and there it is.
|
| actually, there're explanations at http://wiki.jboss.org/wiki/Wiki.jsp?page=JbpmGettingStarted
| u need to read on...
hah, sorry, sorry for this stupid question :), it so easy :),
Thank you,
Regards,
Paata.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4060227#4060227
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4060227
18Â years, 9Â months
[JBoss Seam] - Re: Seam is better than Struts..?
by Delphi's Ghost
anonymous wrote : If you are brand new to Java web development, Seam will appear to be confusing and terrible.
I'm new to web development, and found that coming from Client Server to the web was thoroughly depressing Once I understood the problems involved in the bigger picture of web development (multiple tab/windows, back buttons + multiple submits, state management without killing the database or the server, and decent navigation + pageflows). Once you understand these problems, you can really see how Seam was built to address them all. Seam really does find a way to make these problems transparent.
A lot of frameworks are good for Hello World, but beyond that, you are often on your own and stuck on a frustrating path. Traditional problems in other frameworks are often solved with Hacks while Seam addresses them as part of the framework (i.e. LazyInitializationException).
The Seam docs could be better at describing some things, I don't even think they have an example that demonstrates the Update part of CRUD which led to many frustrations for me, but now I've solved those problems, I find Seam wonderful to work with, and to boot it has Ajax , PDF, email and other components built in and a Seam focused IDE coming soon.
The level of integration Seam provides with each of its elements (pageflow, process flow, JSF controls, backing beans, messages, logging, persistence context management) is astounding and how frameworks should be. Not this mix and match your parts and pieces and hope it all plays nicely together.
Also, there is the productivity issue. I think Seam could beat the snot out of Rails, and you end up with an application that is far more robust and scalable out of the box. Seam-Blog in 15 minutes, no problem.
Yep, I'm a new web developer, and I'm really happy with Seam. I stuck with Delphi for 12 years since it came out, and now it looks like I've found a new object of my affection and loyalty.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4060223#4060223
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4060223
18Â years, 9Â months
[Datasource Configuration] - Error when making mysql as the default datasource
by Deep_Edward
Hi,
I am trying to change my the JDBC Persistence in JBoss 4.0.2 from the default hsqldb to mysql.
For this it says that i need to deploy the relevant datasource. So i am tryin to change the datasource from hsql to mysql.
The procedure which I followed for it is as follows:
1. To use JBoss 4.0 with MySQL, we first need to put the MySQL driver classes into the CLASSPATH.
2. Copy the .jar file mysql-connector-java-3.0.9-stable-bin.jar to the /server/default/lib directory.
3. To use the MySQL data source, copy /docs/examples/jca/mysql-ds.xml to the /server/default/deploy directory.
4. Modify the mysql-ds.xml configuration file by setting <driver-class/> to com.mysql.jdbc.Driver and <connection-url/> to jdbc:mysql:///, where is the MySQL host server and is the MySQL database.
5. Next, we need to set the and <type-mapping> elements in the standardjaws.xml or jaws.xml file: (standardjaws.xml or jaws.xml file, i can't find in JBoss 4.0.2)
java:/MySqlDS
<type-mapping>mySQL</type-mapping>
6. We also need to set the and <datasource-mapping> elements in the standardjbosscmp-jdbc.xml or jbosscmp-jdbc.xml file:
<jbosscmp-jdbc>
java:/MySqlDS
<datasource-mapping>mySQL</datasource-mapping>
</jbosscmp-jdbc>
7. Finally, we modify login-config.xml with MySQL database settings. Add the following <application-policy/> element to login-config.xml:
<application-policy name = "MySqlDbRealm">
<login-module code =
"org.jboss.resource.security.ConfiguredIdentityLoginModule"
flag = "required">
<module-option name ="principal">sa</module-option>
<module-option name ="userName">root</module-option>
<module-option name ="password">root</module-option>
<module-option name ="managedConnectionFactoryName">
jboss.jca:service=LocalTxCM,name=MySqlDS
</module-option>
</login-module>
</application-policy>
8.By modifying the mysql-ds.xml, standardjaws.xml(which i never got), standardjbosscmp-jdbc.xml, and login-config.xml files, the JBoss 4.0 server is configured to be used with a MySQL database.
I have removed the hsqldb-jdbc2-service.xml and hsqldb-jdbc-state-service.xml from JBOSS_HOME\server\default\deploy\jmsn and replaced it with mysql-jdbc2-service.xml file.
Now the exceptions I am getting on running the server (dufault configuration) are:
08:59:09,281 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
| 08:59:09,483 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=MySqlDS' to JNDI name 'java:MySqlDS'
| 08:59:17,314 WARN [JBossManagedConnectionPool] Throwable while attempting to get a new connection: null
| org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception:
| ** BEGIN NESTED EXCEPTION **
|
| java.net.UnknownHostException
| MESSAGE: mysql-hostname: mysql-hostname
| STACKTRACE:
|
| java.net.UnknownHostException: mysql-hostname: mysql-hostname
| at java.net.InetAddress.getAllByName0(InetAddress.java:1128)
| at java.net.InetAddress.getAllByName0(InetAddress.java:1098)
| at java.net.InetAddress.getAllByName(InetAddress.java:1061)
| at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:133)
| at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:280)
| at com.mysql.jdbc.Connection.createNewIO(Connection.java:1765)
| at com.mysql.jdbc.Connection.<init>(Connection.java:430)
| at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:268)
| at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:171)
| 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:538)
| 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)
| at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88)
| at org.jboss.mq.pm.jdbc2.PersistenceManager.getConnection(PersistenceManager.java:1689)
| at org.jboss.mq.pm.jdbc2.PersistenceManager.createSchema(PersistenceManager.java:274)
| at org.jboss.mq.pm.jdbc2.PersistenceManager.startService(PersistenceManager.java:1796)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at org.jboss.system.ServiceController.start(ServiceController.java:435)
| at org.jboss.system.ServiceController.start(ServiceController.java:435)
| at org.jboss.system.ServiceController.start(ServiceController.java:435)
| at org.jboss.system.ServiceController.start(ServiceController.java:435)
| at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy4.start(Unknown Source)
| at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
| 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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| 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:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy42.start(Unknown Source)
| at org.jboss.deployment.XSLSubDeployer.start(XSLSubDeployer.java:197)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| 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:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy9.deploy(Unknown Source)
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
| at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy4.start(Unknown Source)
| at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
| 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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| 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:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy5.deploy(Unknown Source)
| at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
| at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
| at org.jboss.Main.boot(Main.java:200)
| at org.jboss.Main$1.run(Main.java:508)
| at java.lang.Thread.run(Thread.java:595)
|
|
| ** END NESTED EXCEPTION **
Thanks in advance
__________________
Deep
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4060222#4060222
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4060222
18Â years, 9Â months
[JBoss Seam] - Re: pages-2.0.xsd schema - undocumented features
by Delphi's Ghost
Obviously, this is an undocumented feature so I could be wrong here but:
The conversation element is for business conversation Ids, so you can define the conversation Id based on a context variable. You can also use the conversation element to define a conversation parameter definition and then refer to it by name. i.e.
| <conversation name="widgetConv" param-name="widgetId" param-value="#{widget.id}"/>
|
|
| <page view-id="widgetEdit.xhtml" conversation="widgetConv">
| ...
| ...
| </page>
|
|
If you navigate to widgetEdit, it will find the value for #{widget} and use the id attribute as the conversation Id.
If you try to open two instances of the same widgetEdit page for the same widget (and hence the widget.id value is the same), rather than try and start a new conversation with the same Id, it will automatically switch to the existing conversation.
I imagine the child conversation element is so you can define the conversation business Id for that page without needing to define it outside of the page and referring to it by name from the page element.
Curious how that works when its a new widget and it has no Id?
For more information look in the docs at the Id parameter in the @Begin annotation. This has now been deprecated in 2.0 Beta 1, but it might still be in the docs, and probably referenced in the java docs. It is very likely to be in the 1.2.1 docs.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4060221#4060221
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4060221
18Â years, 9Â months