[JBoss jBPM] - Re: dynamic deadlines on tasks ?
by lblaauw
Ronald,
After I did an update from the repository today and redeployed with the jpdl 3.2.3 jar it seems all AoK at this time ;-) So I will try to implement some dynamic deadline in our processes and see how we fare with that.
Greetings,
Leo
"lblaauw" wrote : Well,
|
| One of the things I had a problem with was the fact that now jpb config needs to be set into a system variable for it to work I guess. Is that intended ? It seems to resolve itselves automatically on the classpath in the jars or firstfound in 3.2.2 ?
|
| I had this traced down originally but switched back to 3.2.2 since that worked fine.
|
| I will give 3.2.3 another shot tomorrow since it seems to me that the EL deadline stuff is in the repository currently.
|
| Regards,
| Leo
|
| "kukeltje" wrote : soon... less then a month 1 expect, maybe a lot less
| |
| | anonymous wrote : I tried to upgrade our 3.2.2. with a build from the repository and it was labeled 3.2.3 but ran into some problems...
| | please elaborate, so we can maybe prevent some things
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157243#4157243
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157243
17 years, 10 months
[JBoss Portal] - Re: Supported configurations for Portal2.7 (with PortletCont
by chris.laprun@jboss.com
If you only use official Portal releases, there is no need to worry about Portlet Container. Each Portal release will integrate the appropriate version of Portlet Container, which might or not be different from the one used in a previous Portal release.
Portlet Container is NOT a supported product at this time, only Portal is.
Portlet Container 2.0 will continue to evolve as we see fit. The fact that it has been extracted to a completely separate modules theoretically allows people to replace the version of Portlet Container used by a given version of Portal (post 2.7). However, this does not mean that such a replacement will work with any given version of Portal. For this reason, the only versions that will be supported are the ones that the Portal team will integrate in an official Portal release.
Portal 2.6.4 is NOT compliant with JSR-286 and will never be. Portal will provide support for JSR-286 starting with Portal 2.7. It is NOT possible to replace the portlet container used by Portal 2.6.4 with a JSR-286 compliant portlet container without significant efforts (comparable to implementing Portal 2.7, so you might as well wait for us to do the work ^_^).
RichFaces is a separate project. We plan on providing better integration with it.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157241#4157241
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157241
17 years, 10 months
[JBoss Messaging] - Can JBoss Messaging uses direct method invocation while send
by gary.c.chen
I am now using JBoss Messaging as a JMS server in my application and I don't use any Cluster feature now and this application is deployed on JBoss AS 4.2.2.GA. In my application I use JMS API to send messages and receive messages in a Servlet, that means the JMS client and JMS server are in the same JVM, as shown below :
|-------------------------------------------|
| JVM |
| |
| |---------------| |---------------| |
| | Servlet 1 | | Servlet 2 | |
| | | | | |
| | |-----------| | | |-----------| | |
| | | Sender | | | | Receiver | | |
| | | Client | | | | Client | | |
| | |-----------| | | |-----------| | |
| | | | | /|\ | |
| |------|--------| |-----|---------| |
| | | |
| | | |
| |----- | |---| |
| | | |
| \|/ | |
| |-------------------| |
| | | |
| | | |
| | JMS Server | |
| | | |
| |-------------------| |
| |
|--------------------------------------------
I know we can optimize the Send Cilent (or Receive Cilent) and JMS Server not to use Socket (TCP/IP) while sending (or receiving) messages in this case, for example JBoss MQ uses a JVM connection factory which JNDI name is java:/ConnectionFactory to make client JMS API uses direct method invocation while sending or receiving messages.
Could you please tell me if there is any mechanism to achieve the optimize in this case ?
And I know there is two connection factories which JNDI name are java:/ConnectionFactory and java:/XAConnectionFactory, are them play the same role as in JBoss MQ? We just use (look up) these connection factories and then we can send or receive messages using direct method invocation and we still using the JMS API in the application, is it right ? Or I can use another way ? Or the JBoss Messaging client will achieve the optimize automatic when it determine the JMS client and the JMS server is in the same JVM ? And how it determine ?
I couldn't find my answer from the User Guide.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157239#4157239
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157239
17 years, 10 months
[JNDI/Naming/Network] - java.lang.RuntimeException: mapped-name is required for jdbc
by jerome.droz
Hi,
I'm new to jBoss AS and I'm trying to migrate a web application that almost worked on Tomcat 6.0.16 to jBoss 5 Beta4. The reason is that I realized Tomcat currently doesn't support resource injection and is somehow buggy... The application uses JPA to access one database and a datasource taken out from JNDI to access another database (but no other types of EJBs). The problem occurs when deploying the web archive:
| 09:02:31,896 ERROR [BaseModelMBean] Exception invoking method addChild
| java.lang.RuntimeException: mapped-name is required for jdbc/[my-jndi-name] of deployment [my-war]
| at org.jboss.injection.ResourceHandler.loadXmlResourceRefs(ResourceHandler.java:156)
| at org.jboss.injection.ResourceHandler.loadXml(ResourceHandler.java:270)
| at org.jboss.web.tomcat.service.TomcatInjectionContainer.processMetadata(TomcatInjectionContainer.java:348)
| ...
|
I followed jBoss's guide to configure a data source in an xml file named mysql-ds.xml (in the "deploy" directory) that looks like this:
| <datasources>
| <local-tx-datasource>
| <jndi-name>jdbc/[my-jndi-name]</jndi-name>
| <connection-url>jdbc:mysql://[my-host]:3306/[my-db]</connection-url>
| <driver-class>com.mysql.jdbc.Driver</driver-class>
| <user-name>[my-username]</user-name>
| <password>[my-password]</password>
| <min-pool-size>5</min-pool-size>
| <max-pool-size>20</max-pool-size>
| <idle-timeout-minutes>5</idle-timeout-minutes>
| <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter</exception-sorter-class-name>
| <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker</valid-connection-checker-class-name>
| <new-connection-sql>SELECT 1</new-connection-sql>
| <metadata>
| <type-mapping>mySQL</type-mapping>
| </metadata>
| </local-tx-datasource>
| </datasources>
|
I've also add the following fragment to the web.xml file:
| <resource-ref>
| <description>DB Connection</description>
| <res-ref-name>jdbc/[my-jndi-name]</res-ref-name>
| <res-type>javax.sql.DataSource</res-type>
| <res-auth>Container</res-auth>
| </resource-ref>
|
I found some documentation about mapped-name in the J2EE API docs, in the @Resource annotation class... but I'm confused about its usage. Do I have to use resource injection in order to make it work? Because that's not the case... I'm using plain JNDI coding:
| ...
| Context initialContext = new InitialContext();
| DataSource dataSource = (DataSource)initialContext.lookup(JNDI_CONNECTION_NAME);
| connection = dataSource.getConnection();
| ...
|
Is there something obvious I'm missing? Do I have to configure an ejb-jar.xml and refactor my code to exclusively use stateless Beans and resource injection?
Any help will be appreciated.
Thanks,
Jerome
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157237#4157237
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157237
17 years, 10 months