September 2007 - jboss-user - Jboss List Archives

[JBoss jBPM] - Re: Problem using expression language in a process definitio

by kukeltje

Seems about correct. But why is modification of the schema needed? Maybe I miss something (have no access to the code now, will look into that tonight). I saw you made a jira entry thanks http://jira.jboss.com/jira/browse/JBPM-1060 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088535#4088535 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088535

18 years, 7 months

1
0
0 / 0

[JBoss Seam] - Re: Further extending an EntityHome

by mustaghattack

"matt.drees" wrote : right? Right :) It's just a matter of design ... ( To me it would have been better to just remove the reflection stuff and change the no-arg constructor to a parameterized one ) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088533#4088533 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088533

18 years, 7 months

1
0
0 / 0

[JBoss Seam] - s:decorate input control ID change from 1.2 to 2.0

by tynor

I reported a Seam2 bug to Richfaces that turned out to be a Seam bug and apparently already fixed in CVS (http://jira.jboss.org/jira/browse/JBSEAM-1947) (thanks Sergey and Pete!) I have a related question: another change in JSF ID names have broken our selenium test and many of our Javascript functions which refer to input controls by ID. Given something like: <s:decorate id="fooDecoration" template="/WEB-INF/facelets/templates/edit.xhtml"> | <ui:define name="label">Foo</ui:define> | <h:inputText id="foo" value="#{fooHome.instance.foo}"/> | </s:decorate> In Seam1.2.1, the control was addressable as "fooForm:foo". In Seam2, that has changed and we must address it as "fooForm:fooDecoration:foo". Is this intentional? Is it likely to change before 2.0.0GA? Thanks! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088531#4088531 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088531

18 years, 7 months

1
0
0 / 0

[JBoss Seam] - Re: Further extending an EntityHome

by matt.drees

"mustaghattack" wrote : | Of course. But I didn't think it in that way ... You mainly use EntityHome with inheritance so instead of : | | | class PersonHome extends EntityHome< Person > { | | ... | | } | | | | have | | | | class PersonHome extends EntityHome< Person > { | | public PersonHome() { | | super( Person.class ); | | } | | | Ah, ok, gotcha. My bad. However, I don't think you'd need to modify EntityHome to get that kind of behavior. You could do | class PersonHome extends EntityHome< Person > { | public PersonHome() { | setEntityClass(Person.class); | } | right? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088529#4088529 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088529

18 years, 7 months

1
0
0 / 0

[JBoss Seam] - Re: Some of my unscheduled jira issues that I think should b

by pete.muir＠jboss.org

"matt.drees" wrote : 1. | http://jira.jboss.com/jira/browse/JBSEAM-1762 | - Very simple fix; bug breaks session usage in tests +1, I've scheduled it (though Norman might deschedule it ;) ) anonymous wrote : 2. | http://jira.jboss.com/jira/browse/JBSEAM-1257 | - This can be very confusing, especially if a newbie tries to put components in collections. Potentially a two-sentence documentation fix. Or apply my patch. I want Gavin to review this, so I don't think its going to happen in the GA timeframe. Can you add an item to the SeamProblemsFAQ as a start? anonymous wrote : 3. | http://jira.jboss.com/jira/browse/JBSEAM-1647 | - This could be a one-sentence fix. And I think it's a very important thing to document. Otherwise, a newbie might do something like | | | @In String name; | | | | setName(String name){ | | this.name = name; | | } | | | and be very confused why component.setName("joe") is effectively a no-op. +1 anonymous wrote : 4. | http://jira.jboss.com/jira/browse/JBSEAM-1940 | Wrong documentation is very bad. Easy to fix (remove a paragraph). This needs double checking (that the docs are wrong, and its not a bug.) anonymous wrote : If there are ways I can contribute to fixing these, let me know. Documentation patches (especially when it's a concept thats badly documented) are great as then we get a better understanding of whats wrong with the current explanation! Thanks Matt! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088528#4088528 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088528

18 years, 7 months

1
0
0 / 0

[JBoss Seam] - Re: Some of my unscheduled jira issues that I think should b

by matt.drees

Oh, silly forum. The title should read "Some of my unscheduled jira issues that I think should be slated for 2.0" View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088527#4088527 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088527

18 years, 7 months

1
0
0 / 0

[JBoss Seam] - Some of my unscheduled jira issues that I think should be sl

by matt.drees

I just wanted to bring up some of my jira issues that I think are easy to fix and/or relatively important, and I think should be included in 2.0GA (or at least 2.0.1). I'm not making demands, just suggesting things that I think will be beneficial for Seam. 1. http://jira.jboss.com/jira/browse/JBSEAM-1762 - Very simple fix; bug breaks session usage in tests 2. http://jira.jboss.com/jira/browse/JBSEAM-1257 - This can be very confusing, especially if a newbie tries to put components in collections. Potentially a two-sentence documentation fix. Or apply my patch. 3. http://jira.jboss.com/jira/browse/JBSEAM-1647 - This could be a one-sentence fix. And I think it's a very important thing to document. Otherwise, a newbie might do something like | @In String name; | | setName(String name){ | this.name = name; | } | and be very confused why component.setName("joe") is effectively a no-op. 4. http://jira.jboss.com/jira/browse/JBSEAM-1940 Wrong documentation is very bad. Easy to fix (remove a paragraph). If there are ways I can contribute to fixing these, let me know. And many thanks to the Seam dev team for their hard work. Especially Pete. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088526#4088526 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088526

18 years, 7 months

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - Re: Getting java.lang.NoSuchFieldError: TRACE on initial sta

by caspersgrin

The log4j jar was v1.2.7 and I replaced it with 1.2.15. And lo and behold..... it came up successfully. Thanks!!! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088524#4088524 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088524

18 years, 7 months

1
0
0 / 0

[JBoss Seam] - Re: Further extending an EntityHome

by damianharvey

"damianharvey" wrote : ...only updatedMessage(), deletedMessage() and createdMessage() refer to entityClass rather than getEntityClass. ...oh, and createInstance() View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088522#4088522 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088522

18 years, 7 months

1
0
0 / 0

[JBoss Seam] - Re: FYI: Seam 2 CR1 has been released

by pete.muir＠jboss.org

Please create a JIRA issue for this and I'll see if I can do this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088521#4088521 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088521

18 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user September 2007