[edoetsch]

I just inherited a JBoss 4.0.3 / Seam 1.2.1 product and have upgraded to 4.2.3 / 2.1.1 respectively.

Everything is working just fine except one section where we are looping via ui:repeat tags over some data elements.

Now, h:input elements only seem to save data in elements rendered by the last iteration of the loop.

If this is a JFS question, let me know.

Anyone else experienced application behavior changes like this?

[ps]

I have JDK 6 build 1.6.0, Apache Ant version 1.7.0, Apache Maven 2.1.0, seam version 2.1.1.GA

When i try to deploy the booking (or any other) example i get the following exception.

D:\jboss-seam-2.1.1.GA\examples\booking>ant deploy
Buildfile: build.xml

initcopy:

initpoms:
     [echo] Setting up dependencies
     [copy] Copying 1 file to D:\jboss-seam-2.1.1.GA\classes\poms

BUILD FAILED
D:\jboss-seam-2.1.1.GA\build\common.build.xml:96: The following error occurred while executing this line:
D:\jboss-seam-2.1.1.GA\build\utilities.build.xml:80: artifact:install doesn't support the "settingsFile" attribute

Total time: 0 seconds

What could be the problem? Have i missed something?

i had posted this on the Running Seam examples with JBoss Application Server 4.2.X but i guess this is a more appropriate forum, so reposting here.

[dan.j.allen]

That's definitely an incompatibility problem between the Ant tasks for Maven and Maven 2.1. Can you verify it works okay with Maven 2.0?

[aabm.aabm.4intro.jazztel.es]

Hello I’m working with Seam 2.1.1 GA and Jboss 4.2.3. I’m just reproducing the Seam in action book example  and  I can  reverse the Database from MySQL (seam generate) without problems, I get the entities and the ui and it works fine, but when I edit the file seam-gen.reveng.xml to add some customizations for example:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE hibernate-reverse-engineering SYSTEM "http://hibernate.sourceforge.net/hibernate-reverse-engineering-3.0.dtd" >
<hibernate-reverse-engineering>
   <table name="HOLE">
    <column name="M_PAR" property="mensPar" />
    <column name="L_PAR" property="ladiesPar" />
    <column name="M_HANDICAP" property="mensHandicap" />
    <column name="L_HANDICAP" property="ladiesHandicap" />
  </table>

</hibernate-reverse-engineering>

It does the same like if the file seam-gen.reveng.xml   wasn’t edited. It doesn’t change nothing in both entities and ui.

Some idea?

Thanks.

[dan.j.allen]

You should be asking questions specific to the book in the Seam in Action forum. But to give you a quick answer, your problem is that the catalog and schema settings don't carry over from H2. Edit the build.properties file (or seam-gen.properties if running from the project) as follows:

hibernate.default_catalog=open18  <- whatever your MySQL database is called
hibernate.default_schema.null=

You can also select the catalog and schema explicitly in the reverse engineering file:

<schema-selection match-schema="*" match-catalog="open18"/>

You may have to play around with the values, but if it doesn't apply, then likely it isn't matching based on schema and catalog.

[aabm.aabm.4intro.jazztel.es]

Thanks for the response and sorry about to put my question here.

Ok, only to say that I have trying that you said and it didn't work. I have put another thread of this question in the Seam in Action Forum.

Thanks again

[lich]

dependency-report.txt

[liauwsiauwlong]

Hi ,

I'm currently use Seam 2.1.1.GA and JBoss AS 4.2.3.GA .

I'm facing up a problem after i have do deployment to prod with seam gen , by typing :

[dan.j.allen]

Make sure you have the following property in your persistence-prod.xml file.

<property name="jboss.entity.manager.factory.jndi.name" value="java:/superadmEntityManagerFactory"/>

[alartin]

I got the same problem under ant 1.7.1 and maven 2.0.9
Is there any workaround?

[wbrazille]

Hello, I am experiencing an intermittent exception being thrown from Seam 2.1.1 on WebSphere 6.1.13.  This error is occuring 20 - 30 times per day, on a variety of different pages (views), that render successfully for many requests per day.

The response that is generated to the browser is:

Error 500: Filter [Seam Filter]: filter is unavailable.

I do not have a reproducable test case at this time.

Has anyone else seen this issue?  If not, can someone suggest what the issue might be based on the stack trace?  Please note that I do not have any security enabled for this site.

Thanks for the assistance.

Following is the stack trace:

[6/9/09 2:33:10:636 EDT] 00000028 WebApp        E   [Servlet Error]-[Filter [Seam Filter]: filter is unavailable.]: java.lang
.NullPointerException
        at com.ibm.ws.webcontainer.srt.SRTServletRequest$SRTServletRequestHelper.access$200(SRTServletRequest.java:2232)
        at com.ibm.ws.webcontainer.srt.SRTServletRequest.getAttribute(SRTServletRequest.java:196)
        at javax.servlet.ServletRequestWrapper.getAttribute(ServletRequestWrapper.java:127)
        at org.jboss.seam.servlet.ServletRequestMap.get(ServletRequestMap.java:55)
        at org.jboss.seam.contexts.BasicContext.get(BasicContext.java:49)
        at org.jboss.seam.Component.getInstance(Component.java:1966)
        at org.jboss.seam.Component.getInstance(Component.java:1961)
        at org.jboss.seam.Component.getInstance(Component.java:1934)
        at org.jboss.seam.Component.getInstance(Component.java:1929)
        at org.jboss.seam.core.Events.instance(Events.java:157)
        at org.jboss.seam.core.Events.exists(Events.java:152)
        at org.jboss.seam.security.Credentials.getUsername(Credentials.java:43)
        at org.jboss.seam.security.Identity.getUsername(Identity.java:653)
        at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:50)
        at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
        at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
        at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
        at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
        at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
        at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:766)
        at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:674)
        at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:689)
        at com.ibm.ws.wswebcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:101)
        at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.invokeFilters(DefaultExtensionProcessor.java:791)
        at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:741)
        at com.ibm.ws.wswebcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:113)
        at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3276)
        at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:267)
        at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:811)
        at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1455)
        at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:113)
        at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:454)
        at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:383)
        at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:102)
        at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
        at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
        at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
        at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
        at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195)
        at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743)
        at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
        at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)

[wbrazille]

Follow-up on intermittent exception from WebSphere:

Is this possibly the same issue as described in JBSEAM-4102?  If so, are there any issues with backporting the updates made to LoggingFilter in Seam 2.1.2.GA to Seam 2.1.1.GA?

Thanks.

[atamhank]

Anyone used rev eng setting to enable the system to sense the primary key is being generated from associated sequence in database so Seam just needs to take the value from sequence and put in database table's primary key column?

I saw some posts where need to specify the table name, sequence name for each table?
eg.

@Entity
public class Inventory implements Serializable {

        @Id
        @GeneratedValue(generator="InvSeq")
        @SequenceGenerator(name="InvSeq",sequenceName="INV_SEQ", allocationSize=5)
        private long id;
Is there a way for it to sense if the primary key is linked to as sequence (or populated via a sequence) to automatically put the code for that table in place? Very useful especially if there a large number of tables.

I will appreciate any help or sharing of experience around this.
Thanks,
Aaditi