[EJB 3.0] - Re: using GenerationType.TABLE - ERROR [MultipleHiLoPerTable
by fbadt
yup. It is my DB. I can get to it fine with the same ID/pass via a test program to just select from the table, without "for update" and isql also.
* note: using - strategy=GenerationType.TABLE and informix drivers from
http://www14.software.ibm.com/webapp/download/search.jsp?go=y&rs=ifxjdbc
Here is the kicker... This is being run in JBoss 4.04 so I grabbed the hibernate 3.2rc2 source and traced into the code. It dies here as below from the below sql:
"select value from test_tab2 where key_name = 'PK_TABLE' for update"
** the same sql, without "for update", queries fine.
MultipleHiLoPerTableGenerator(line 145)
==> result = rs.getInt(1);
ERROR [MultipleHiLoPerTableGenerator] could not read or init a hi value
java.sql.SQLException: null java.lang.NullPointerException
at com.informix.util.IfxErrMsg.getSQLException(IfxErrMsg.java:448)
at com.informix.jdbc.IfxValue.a(IfxValue.java:424)
at com.informix.jdbc.IfxValue.a(IfxValue.java:350)
at com.informix.jdbc.IfxRowColumn.a(IfxRowColumn.java:279)
at com.informix.jdbc.IfxSqli.a(IfxSqli.java:4340)
at com.informix.jdbc.IfxResultSet.a(IfxResultSet.java:654)
at com.informix.jdbc.IfxResultSet.b(IfxResultSet.java:626)
at com.informix.jdbc.IfxResultSet.getInt(IfxResultSet.java:1075)
at org.jboss.resource.adapter.jdbc.WrappedResultSet.getInt(WrappedResultSet.java:677)
at org.hibernate.id.MultipleHiLoPerTableGenerator.doWorkInCurrentTransaction(MultipleHiLoPerTableGenerator.java:145)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972782#3972782
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972782
19 years, 7 months
[JBoss Seam] - Re: Please help: cannot integrate ICEfaces into Seam applica
by TedGoddard
As has been observed, the current ICEfaces 1.0.1 release does not yet
work with Seam. Internally, however, ICEsoft is actively working on
Seam integration as follows:
- carrying conversationID across Ajax and redirect HTTP requests
- support for the .seam extension with ICEfaces Ajax servlets
- moving Seam Servlet filter implementation to be Ajax-compatible
- transformation of <s:link /> into an Ajax-compatible variant
The end result will be the ability to transparently convert a standard
Seam application into an Ajax application simply by adding icefaces.jar.
We expect to have this publicly available within the next two months.
Alas, just changing the servlet mappings is not enough to get ICEfaces
and Seam running together. The main complication is the fact
the the conversationID must be maintained through both Ajax and
non-Ajax requests (and indeed this is supported by our internal
builds of ICEfaces).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972773#3972773
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972773
19 years, 7 months
[JBoss Seam] - Re: When a component is not found should Seam warn or fail?
by CptnKirk
The thing about this is that null or not found is a valid use case. Many ppl have pages that rely on this functionality to not display something when a variable isn't in context and then to "come alive" once an action puts this variable into context. In this case you wouldn't want a log message every time, and it's impossible for Seam to know if you're doing this on purpose or by mistake.
In practice, with incremental page design and testing, typos are found quickly and are easily fixed. However, given the amount of typo errors we see on the forums, maybe step #1 if you're having a problem would be to double check your spelling. Yea, it's easy to do, but how can Seam really help with that aside from the debug output already provided?
An option to promote this debug output to warn in web.xml or seam.properties?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972770#3972770
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972770
19 years, 7 months