[EJB 3.0] - Re: Persistence in EJB3
by masoodah@mdsit.com
Yes
I have mysql-ds.xml in my default/deploy folder. HAve I configures it right. Pl. let me know. - Thanks
<?xml version="1.0" encoding="UTF-8"?>
<!-- $Id: mysql-ds.xml 41016 2006-02-07 14:23:00Z acoliver $ -->
<!-- Datasource config for MySQL using 3.0.9 available from:
http://www.mysql.com/downloads/api-jdbc-stable.html
-->
<local-tx-datasource>
<jndi-name>DPDS</jndi-name>
<!--
<connection-url>jdbc:mysql://mysql-hostname:3306/jbossdb</connection-url>
-->
<connection-url>jdbc:mysql://localhost:3306/dreamPlay</connection-url>
<driver-class>com.mysql.jdbc.Driver</driver-class>
<user-name>dreamplay</user-name>
dreamplay
<min-pool-size>2</min-pool-size>
<max-pool-size>10</max-pool-size>
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter</exception-sorter-class-name>
<!-- should only be used on drivers after 3.22.1 with "ping" support
<valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker</valid-connection-checker-class-name>
-->
<!-- sql to call when connection is created
<new-connection-sql>some arbitrary sql</new-connection-sql>
-->
<!-- sql to call on an existing pooled connection when it is obtained from pool - MySQLValidConnectionChecker is preferred for newer drivers
<check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
-->
<!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
<type-mapping>mySQL</type-mapping>
</local-tx-datasource>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4124060#4124060
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4124060
18 years, 3 months
[JBoss Portal] - Sticky Validation Errors
by jannie
Hi,
I am working on a Richfaces-Portlet using RF 3.1.0 with the 3.1.0 SNAPHSHOT implementation on Portal 2.6.3.
As soon as a validation error is reported, the message sticks with the session and prevents the form from being completed. Not even an immediate action overcomes this. Here a log:
14:39:04,640 INFO [STDOUT] before - RESTORE_VIEW 1
14:39:04,640 INFO [STDOUT] after - RESTORE_VIEW 1
14:39:04,656 INFO [STDOUT]
>>>>>> PortletAjaxContext CONSTRUCTOR called!
14:39:04,656 INFO [STDOUT] before - APPLY_REQUEST_VALUES 2
14:39:04,859 INFO [STDOUT] after - APPLY_REQUEST_VALUES 2
14:39:04,937 INFO [STDOUT] AJAXFacesPortlet viewId=/jsf/index.xhtml view Root=o
rg.ajax4jsf.component.AjaxViewRoot@960b08
facesContext.application=com.sun.faces.application.ApplicationImpl@14d583a
14:39:04,937 INFO [STDOUT]
>>>>>> PortletAjaxContext CONSTRUCTOR called!
14:39:04,937 INFO [STDOUT] before - RENDER_RESPONSE 6
14:39:05,187 INFO [lifecycle] WARNING: FacesMessage(s) have been enqueued, but
may not have been displayed.
I expected the messages to disappear with the next request. But obviously they remain! resulting in 1 error message after the first request, 2 after the 2nd, 4 after the 3rd,... even when data gets corrected or the validation phase - as shown above - is jumped totally!?!
Does anyone have an idea what might cause this behaviour?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4124054#4124054
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4124054
18 years, 3 months
[JBoss Seam] - Re: NPE in Param.validateConvertedValue
by pgmjsd
Okay, I think I've figured out why this NPE only happens sometimes. The .page.xml file in this case binds a simple expression to the parameter value. For example:
| <param name="windowType" value="#{windowType}"/>
|
This value is intended to be passed down through the Facelets templates and turn off nav bars, etc. With this kind of expression, ValidatingResolver.getInvalidValues() returns null because of the condition in the if statement:
| @Override
| public void setValue(ELContext context, Object base, Object property, Object value)
| throws NullPointerException, PropertyNotFoundException, PropertyNotWritableException, ELException
| {
| if (base!=null && property!=null ) // <== This is false, so invalidValues is never set.
| {
| context.setPropertyResolved(true);
| invalidValues = getValidator(base).getPotentialInvalidValues( property.toString(), value );
|
| }
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4124041#4124041
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4124041
18 years, 3 months