From jira-events at lists.jboss.org Thu Jan 1 19:50:54 2009 From: jira-events at lists.jboss.org (Stephen Friedrich (JIRA)) Date: Thu, 1 Jan 2009 19:50:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1855) Provide a FacesMessages.instance().addToControlById() or equivalent In-Reply-To: <29923147.1187959818110.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <5920727.1230857454334.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444363#action_12444363 ] Stephen Friedrich commented on JBSEAM-1855: ------------------------------------------- Any news on this? IMHO this is a bug, not a feature request: You currently just cannot add a FacesMessage to a specific component and have it survive a redirect. After the redirect it will be a global message instead. (Because FacesMessages.getClientId(String) tries to walk the component tree to determine the client id for the component id, but that tree is still _empty_ so null is returned.) We need the client id to correctly add the faces message when rendering the response, but I don't see how the client id can be computed from the component id when the tree does not yet exist. So my conclusion would be that we really need a way to add a message for a _client_ id. > Provide a FacesMessages.instance().addToControlById() or equivalent > ------------------------------------------------------------------- > > Key: JBSEAM-1855 > URL: https://jira.jboss.org/jira/browse/JBSEAM-1855 > Project: Seam > Issue Type: Feature Request > Components: JSF Integration > Affects Versions: 1.2.0.GA > Reporter: Andy Bosch > Priority: Minor > Fix For: The future > > Attachments: FacesMessages patch.txt > > > It is possible do add FacesMessages via the Seam functionality with FacesMessages.instance().addToControl. In the parameters you have to pass the component id. In the plain JSF way, you can add FacesMessages via FacesContext ... addMessage. In the JSF-way you have to pass the client-id. > With normal input components you can use both ways. But when you work with datatables, you MUST work with the client-id, the Seam-way with using only the component-id does NOT work. > Explanation: When using a datatable-tag, you only have one component. The renderer generates the various rows. In the component-tree there is yet only one component! If you want to add a FacesMessage to one row, you can only work with client-ids (because you have to include the row-index). > My wish: Please change FacesMessages.instance().addToControl. for using with client-ids. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 2 16:55:04 2009 From: jira-events at lists.jboss.org (Reind D (JIRA)) Date: Fri, 2 Jan 2009 16:55:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2523) Identity component should be scoped to the WAR module In-Reply-To: <7025756.1201032321074.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <11732907.1230933304802.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reind D updated JBSEAM-2523: ---------------------------- Attachment: seam2523.ear.tar.gz 1. Deploy the ear. 2. Go to http://localhost:8080/a/ 3. Enter any user & pass, and hit the login button. Note that the text "**** in B.login() ****" is output to the server log. Instead, this should say "in A.login()". It's calling B.login() instead of A.login() as configured in a.war/WEB-INF/components.xml 4. Repeat steps 2-3 on http://localhost:8080/b/ and note that the message indicates that B.login() is invoked (as expected, this time). This example is intended to be deployed to JBoss 5.0.0.GA Note: It's included here as a tar.gz file b/c jboss5 has issues deploying it as a zipped ear. Please unzip and deploy the exploded ear. > Identity component should be scoped to the WAR module > ----------------------------------------------------- > > Key: JBSEAM-2523 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2523 > Project: Seam > Issue Type: Bug > Components: Security > Affects Versions: 2.1.1.GA > Environment: JBoss 4.2.2.GA (also tested on 4.2.0.GA) > Reporter: Reind D > Attachments: seam2523.ear.tar.gz > > > I have an EAR with two web modules. I have configured the 'Identity authenticateMethod' in components.xml to use a different a method for each WAR (authA.authenticate, authB.authenticate). When attempting to login to the 'b' webapp it invokes the authenticateMethod defined in a.war. Attempting to login to the 'a' webapp works as expected. It appears as though the Identity component is not scoped to the WAR. > The EAR is packaged as follows: > my-application.ear/ > a.war/ > WEB-INF/ > components.xml > ... > b.war/ > WEB-INF/ > components.xml > ... > web.jar > Congure authentication as follows in both components.xml files: > a.war/WEB-INF/components.xml > > b.war/WEB-INF/components.xml > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 2 17:00:54 2009 From: jira-events at lists.jboss.org (Reind D (JIRA)) Date: Fri, 2 Jan 2009 17:00:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2523) Identity component should be scoped to the WAR module In-Reply-To: <7025756.1201032321074.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <417728.1230933654205.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444395#action_12444395 ] Reind D commented on JBSEAM-2523: --------------------------------- I noticed that this issues does not occur if I comment out the "Seam Filter" from both WARs. This can be reproduced in the attached project. > Identity component should be scoped to the WAR module > ----------------------------------------------------- > > Key: JBSEAM-2523 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2523 > Project: Seam > Issue Type: Bug > Components: Security > Affects Versions: 2.1.1.GA > Environment: JBoss 4.2.2.GA (also tested on 4.2.0.GA) > Reporter: Reind D > Attachments: seam2523.ear.tar.gz > > > I have an EAR with two web modules. I have configured the 'Identity authenticateMethod' in components.xml to use a different a method for each WAR (authA.authenticate, authB.authenticate). When attempting to login to the 'b' webapp it invokes the authenticateMethod defined in a.war. Attempting to login to the 'a' webapp works as expected. It appears as though the Identity component is not scoped to the WAR. > The EAR is packaged as follows: > my-application.ear/ > a.war/ > WEB-INF/ > components.xml > ... > b.war/ > WEB-INF/ > components.xml > ... > web.jar > Congure authentication as follows in both components.xml files: > a.war/WEB-INF/components.xml > > b.war/WEB-INF/components.xml > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 2 17:57:54 2009 From: jira-events at lists.jboss.org (Daniel Roth (JIRA)) Date: Fri, 2 Jan 2009 17:57:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1350) Provide download component (e.g.) In-Reply-To: <27185821.1180049308709.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <848551.1230937074271.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444396#action_12444396 ] Daniel Roth commented on JBSEAM-1350: ------------------------------------- Committed. Docs to go! > Provide download component (e.g.) > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBSEAM-1350 > URL: https://jira.jboss.org/jira/browse/JBSEAM-1350 > Project: Seam > Issue Type: Feature Request > Components: JSF Controls > Reporter: jarkko Lietolahti > Assignee: Daniel Roth > Fix For: The future > > Attachments: download.patch > > > > We're going to create new (more general component) which allows the user to download a file (any resource, Excel file, Document whatever). > The plan is to create a new UI component named UIDownload which has attributes like value, contentType (some more?). > 1) UIDownload a backing bean (value) (is this still valid word in the seam world?) to generate the data ( allow byte[], OutputStreams ?). > 2) UIDownload creates DownloadResource which is stored in DownloadStore. > 3) UIDownload generates HTML which redirects the browser to ResourceServlet > 4) ResourceServlet then uses DownloadResource to get hold of the data and the pushes it to browser > The reason for this is that we're building portlets with Seam and it's impossible to "download" files from a portal environment without additional servlet and we think it's good idea to reuse existing stuff. > Patch coming soon (if we can make it work ;) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 2 18:09:54 2009 From: jira-events at lists.jboss.org (Reind D (JIRA)) Date: Fri, 2 Jan 2009 18:09:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2523) Identity component should be scoped to the WAR module In-Reply-To: <7025756.1201032321074.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <14934385.1230937794477.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reind D updated JBSEAM-2523: ---------------------------- Attachment: seam2523.ear.tar.gz I've attached another EAR. This one works with both JBoss 4 & 5 (the only difference is that slf4j is now packaged). > Identity component should be scoped to the WAR module > ----------------------------------------------------- > > Key: JBSEAM-2523 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2523 > Project: Seam > Issue Type: Bug > Components: Security > Affects Versions: 2.1.1.GA > Environment: JBoss 4.2.2.GA (also tested on 4.2.0.GA) > Reporter: Reind D > Attachments: seam2523.ear.tar.gz, seam2523.ear.tar.gz > > > I have an EAR with two web modules. I have configured the 'Identity authenticateMethod' in components.xml to use a different a method for each WAR (authA.authenticate, authB.authenticate). When attempting to login to the 'b' webapp it invokes the authenticateMethod defined in a.war. Attempting to login to the 'a' webapp works as expected. It appears as though the Identity component is not scoped to the WAR. > The EAR is packaged as follows: > my-application.ear/ > a.war/ > WEB-INF/ > components.xml > ... > b.war/ > WEB-INF/ > components.xml > ... > web.jar > Congure authentication as follows in both components.xml files: > a.war/WEB-INF/components.xml > > b.war/WEB-INF/components.xml > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 2 19:00:54 2009 From: jira-events at lists.jboss.org (Daniel Roth (JIRA)) Date: Fri, 2 Jan 2009 19:00:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3684) baseNameForViewId is present in (at least) four classes In-Reply-To: <19524168.1226246316450.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <17920829.1230940854238.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roth closed JBSEAM-3684. ------------------------------- Fix Version/s: 2.1.2.CR1 Resolution: Done Relocated to Pages.java > baseNameForViewId is present in (at least) four classes > -------------------------------------------------------- > > Key: JBSEAM-3684 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3684 > Project: Seam > Issue Type: Bug > Components: Excel, JSF Controls, PDF, RSS JSF Controls > Affects Versions: 2.1.0.SP1 > Reporter: Daniel Roth > Assignee: Daniel Roth > Fix For: 2.1.2.CR1 > > > I think this could be removed to the Pages class -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sat Jan 3 19:16:54 2009 From: jira-events at lists.jboss.org (Daniel Roth (JIRA)) Date: Sat, 3 Jan 2009 19:16:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-1350) Provide download component (e.g.) In-Reply-To: <27185821.1180049308709.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <15792770.1231028214441.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roth closed JBSEAM-1350. ------------------------------- Fix Version/s: 2.1.2.CR1 (was: The future) Resolution: Done Docs committed! There will be some blog about it too. > Provide download component (e.g.) > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBSEAM-1350 > URL: https://jira.jboss.org/jira/browse/JBSEAM-1350 > Project: Seam > Issue Type: Feature Request > Components: JSF Controls > Reporter: jarkko Lietolahti > Assignee: Daniel Roth > Fix For: 2.1.2.CR1 > > Attachments: download.patch > > > > We're going to create new (more general component) which allows the user to download a file (any resource, Excel file, Document whatever). > The plan is to create a new UI component named UIDownload which has attributes like value, contentType (some more?). > 1) UIDownload a backing bean (value) (is this still valid word in the seam world?) to generate the data ( allow byte[], OutputStreams ?). > 2) UIDownload creates DownloadResource which is stored in DownloadStore. > 3) UIDownload generates HTML which redirects the browser to ResourceServlet > 4) ResourceServlet then uses DownloadResource to get hold of the data and the pushes it to browser > The reason for this is that we're building portlets with Seam and it's impossible to "download" files from a portal environment without additional servlet and we think it's good idea to reuse existing stuff. > Patch coming soon (if we can make it work ;) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Jan 4 07:36:04 2009 From: jira-events at lists.jboss.org (=?UTF-8?Q?kabil_akp=C3=84=C2=B1nar_=28JIRA=29?=) Date: Sun, 4 Jan 2009 07:36:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-994) seam-gen and mutiple foreign keys In-Reply-To: <29543710.1173200903914.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <14418265.1231072564865.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444423#action_12444423 ] kabil akp??nar commented on JBSEAM-994: --------------------------------------- This problem exist in 2.1.1 GA release also. Can these supplied patches be applied against version 2.1.1 GA ? > seam-gen and mutiple foreign keys > --------------------------------- > > Key: JBSEAM-994 > URL: https://jira.jboss.org/jira/browse/JBSEAM-994 > Project: Seam > Issue Type: Bug > Components: Tools > Affects Versions: 1.2.0.GA > Environment: JBoss-4.0.5 > Reporter: Niels Hoogeveen > Assignee: Dan Allen > Attachments: doublon.patch, doublon.zip, doublon2.patch, EntityHome.java.ftl.patch, seam-gen.diff, seam-gen.zip > > > I have generated a project with seam-gen based on generate-entities. All works fine, except for the generation of the home interfaces. In one of my tables I have two foreign keys to the same table. In the home interface two references are created to the appropriate object, but with the same name (which of course doesn't compile). > Here is a simplified example: > Table 1 > Code: > CREATE TABLE test > ( > id int4 NOT NULL DEFAULT nextval('test_id_seq'::regclass), > name varchar, > id_test2_1 int4, > id_test2_2 int4, > CONSTRAINT test_pkey PRIMARY KEY (id), > CONSTRAINT test_id_test2_1_fkey FOREIGN KEY (id_test2_1) > REFERENCES test2 (id) MATCH SIMPLE > ON UPDATE NO ACTION ON DELETE NO ACTION, > CONSTRAINT test_id_test2_2_fkey FOREIGN KEY (id_test2_2) > REFERENCES test2 (id) MATCH SIMPLE > ON UPDATE NO ACTION ON DELETE NO ACTION > ) > > Table2 > Code: > CREATE TABLE test2 > ( > id int4 NOT NULL DEFAULT nextval('test2_id_seq'::regclass), > name varchar, > CONSTRAINT test2_pkey PRIMARY KEY (id) > ) > > First Entity > Code: > @Entity > @Table(name = "test", schema = "public") > public class Test implements java.io.Serializable { > private int id; > private Test2 test2ByIdTest22; > private Test2 test2ByIdTest21; > private String name; > public Test() { > } > public Test(int id) { > this.id = id; > } > public Test(int id, Test2 test2ByIdTest22, Test2 test2ByIdTest21, > String name) { > this.id = id; > this.test2ByIdTest22 = test2ByIdTest22; > this.test2ByIdTest21 = test2ByIdTest21; > this.name = name; > } > @Id > @Column(name = "id", unique = true, nullable = false) > @NotNull > public int getId() { > return this.id; > } > public void setId(int id) { > this.id = id; > } > @ManyToOne(fetch = FetchType.LAZY) > @JoinColumn(name = "id_test2_2") > public Test2 getTest2ByIdTest22() { > return this.test2ByIdTest22; > } > public void setTest2ByIdTest22(Test2 test2ByIdTest22) { > this.test2ByIdTest22 = test2ByIdTest22; > } > @ManyToOne(fetch = FetchType.LAZY) > @JoinColumn(name = "id_test2_1") > public Test2 getTest2ByIdTest21() { > return this.test2ByIdTest21; > } > public void setTest2ByIdTest21(Test2 test2ByIdTest21) { > this.test2ByIdTest21 = test2ByIdTest21; > } > @Column(name = "name", length = 0) > @Length(max = 0) > public String getName() { > return this.name; > } > public void setName(String name) { > this.name = name; > } > } > > second entity > Code: > @Entity > @Table(name = "test2", schema = "public") > public class Test2 implements java.io.Serializable { > private int id; > private String name; > private Set testsForIdTest21 = new HashSet(0); > private Set testsForIdTest22 = new HashSet(0); > public Test2() { > } > public Test2(int id) { > this.id = id; > } > public Test2(int id, String name, Set testsForIdTest21, > Set testsForIdTest22) { > this.id = id; > this.name = name; > this.testsForIdTest21 = testsForIdTest21; > this.testsForIdTest22 = testsForIdTest22; > } > @Id > @Column(name = "id", unique = true, nullable = false) > @NotNull > public int getId() { > return this.id; > } > public void setId(int id) { > this.id = id; > } > @Column(name = "name", length = 0) > @Length(max = 0) > public String getName() { > return this.name; > } > public void setName(String name) { > this.name = name; > } > @OneToMany(cascade = CascadeType.ALL, fetch = FetchType.LAZY, mappedBy = "test2ByIdTest21") > public Set getTestsForIdTest21() { > return this.testsForIdTest21; > } > public void setTestsForIdTest21(Set testsForIdTest21) { > this.testsForIdTest21 = testsForIdTest21; > } > @OneToMany(cascade = CascadeType.ALL, fetch = FetchType.LAZY, mappedBy = "test2ByIdTest22") > public Set getTestsForIdTest22() { > return this.testsForIdTest22; > } > public void setTestsForIdTest22(Set testsForIdTest22) { > this.testsForIdTest22 = testsForIdTest22; > } > } > > Home interface of first entity. Here we have two Test2Home references, both with the name test2Home. > Code: > @Name("testHome") > public class TestHome extends EntityHome { > @In(create = true) > Test2Home test2Home; > @In(create = true) > Test2Home test2Home; > public void setTestId(Integer id) { > setId(id); > } > public Integer getTestId() { > return (Integer) getId(); > } > @Override > protected Test createInstance() { > Test test = new Test(); > return test; > } > public void wire() { > Test2 test2ByIdTest22 = test2Home.getDefinedInstance(); > if (test2ByIdTest22 != null) { > getInstance().setTest2ByIdTest22(test2ByIdTest22); > } > Test2 test2ByIdTest21 = test2Home.getDefinedInstance(); > if (test2ByIdTest21 != null) { > getInstance().setTest2ByIdTest21(test2ByIdTest21); > } > } > public boolean isWired() { > return true; > } > public Test getDefinedInstance() { > return isIdDefined() ? getInstance() : null; > } > } > > BTW. I used the latest seam version from CVS. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Jan 4 10:54:54 2009 From: jira-events at lists.jboss.org (Geoffrey De Smet (JIRA)) Date: Sun, 4 Jan 2009 10:54:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2371) Integration testing Seam components with Maven In-Reply-To: <15535346.1197495953674.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <6497190.1231084494735.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444433#action_12444433 ] Geoffrey De Smet commented on JBSEAM-2371: ------------------------------------------ The seam download zip doesn't contain the embedded bootstrap jar. Here's the maven error when running "mvn test": Embedded error: Unable to download the artifact from any repository ... org.jboss.embedded:jboss-embedded-bootstrap:zip:beta3 Where can I find this mystical jar (preferable with pom) and any chance it can be deployed to the jboss repo to make our live a bit easier? :) > Integration testing Seam components with Maven > ---------------------------------------------- > > Key: JBSEAM-2371 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2371 > Project: Seam > Issue Type: Task > Components: Build, Test Harness > Affects Versions: 2.0.0.GA > Environment: Maven 2.0.7 > Reporter: Siarhei Dudzin > Priority: Critical > Fix For: The future > > Attachments: jg-seamtest-1.0.tgz, maven-seam-microcontainer-testng-template.zip, tech-stack-1.0.1.pom, testproject-master-JBSEAM-2371.zip > > > Various users have reported integration testing with Seam is not working in 'Mavenized' projects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Jan 4 12:27:54 2009 From: jira-events at lists.jboss.org (Daniel Roth (JIRA)) Date: Sun, 4 Jan 2009 12:27:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2109) Mail should throw an exception if multiple reply to's are entered In-Reply-To: <22988671.1192457343317.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <16307700.1231090074208.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444434#action_12444434 ] Daniel Roth commented on JBSEAM-2109: ------------------------------------- Why? The RFC (822, section 4.4.3) specifies that many Reply-To's is perfectly valid. > Mail should throw an exception if multiple reply to's are entered > ----------------------------------------------------------------- > > Key: JBSEAM-2109 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2109 > Project: Seam > Issue Type: Bug > Components: Mail > Affects Versions: 2.0.0.CR2 > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Optional > Fix For: The future > > > See org.jboss.seam.example.mail.test.MailTest.testReplyToErrors -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Jan 4 16:03:54 2009 From: jira-events at lists.jboss.org (Pete Muir (JIRA)) Date: Sun, 4 Jan 2009 16:03:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-2109) Mail should throw an exception if multiple reply to's are entered In-Reply-To: <22988671.1192457343317.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <8411835.1231103034207.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir closed JBSEAM-2109. ----------------------------- Resolution: Rejected As Dan says :-) > Mail should throw an exception if multiple reply to's are entered > ----------------------------------------------------------------- > > Key: JBSEAM-2109 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2109 > Project: Seam > Issue Type: Bug > Components: Mail > Affects Versions: 2.0.0.CR2 > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Optional > Fix For: The future > > > See org.jboss.seam.example.mail.test.MailTest.testReplyToErrors -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Jan 4 16:19:54 2009 From: jira-events at lists.jboss.org (Pete Muir (JIRA)) Date: Sun, 4 Jan 2009 16:19:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3873) Memory leak using EJB transactions and jBpm contexts In-Reply-To: <7336851.1230648414356.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <19107726.1231103994743.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated JBSEAM-3873: ------------------------------ Fix Version/s: 2.1.2.CR1 > Memory leak using EJB transactions and jBpm contexts > ---------------------------------------------------- > > Key: JBSEAM-3873 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3873 > Project: Seam > Issue Type: Bug > Components: BPM, Core, EJB3 > Affects Versions: 2.1.1.GA > Environment: JBoss 4.2.x, Mac OSX and Linux environments, Java 1.5 > Reporter: Torsten Fink > Fix For: 2.1.2.CR1 > > Attachments: MemoryLeakEventKontext.tgz > > > Our application had to survive a night with full load. On the next morning the heap was full of JbpmContext's. > After looking at the source code of Seam and at the debug messages we came up with this hypothesis: > * The SFSB EjbSynchronizations is placed in the event context, the Seam-JbpmContext-Component also lives in the event context. > * Using EJB transactions, EjbSynchronizations is responsible for cleaning up the JbpmContext after the end of the transaction. > * Unfortunately the event context ends BEFORE EjbSynchronizations has the chance to clean up the JbpmContext. > Using BMT the transaction ends before the event context ends. Thus, the JbpmContext is cleaned up. > We switch all our MDBs, EJB-timers, and Web-services from CMT to BMT and (after fixing some other leaks, e.g. a class loader issue in jBpm), we survived the night. > I wrote a small test application that shows the memory leak and I will try to attach it to this issue. > It is a Maven application that consists of > - a Web-GUI to start the test and displays the results (http://localhost:8080/leak/) > - a SFSB that sends 10 messages each to two queues (the standard queues A and B), waits a little bit, and does a gc > - two MDBs, one with CMT, one with BMT, which uses Seam injection to access a jBpm-Context > - an application scoped POJO that saves the contexts in a Set using a weak reference > After executing the tests and the GC, the surviving references are displayed. You can see that the CMT references are not gs'ed whereas the BMT references are cleaned up. You can execute the test several times. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Jan 4 16:53:54 2009 From: jira-events at lists.jboss.org (Daniel Roth (JIRA)) Date: Sun, 4 Jan 2009 16:53:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3676) s:validateEquality doesn't work in s:decorate In-Reply-To: <27866474.1225911153400.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <21610195.1231106034245.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roth closed JBSEAM-3676. ------------------------------- Fix Version/s: 2.1.2.CR1 Resolution: Done I think I fixed this now. The NamingContainer of the Decorate was unable to find the correct component, so the validator itself searches for the component to validate top-down from the Decorators NamingContainer. This seems to works as long as you don't have nested Decorator's. Thanks Ingo for the pre-work :-) > s:validateEquality doesn't work in s:decorate > --------------------------------------------- > > Key: JBSEAM-3676 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3676 > Project: Seam > Issue Type: Bug > Components: JSF Controls > Affects Versions: 2.1.0.SP1 > Environment: JBoss 4.2.2 with Java 1.5 (Mac Os X) > Reporter: Frederic Nauleau > Assignee: Daniel Roth > Priority: Minor > Fix For: 2.1.2.CR1 > > > Hello, > I have dicovered the s:validateEquality control. It's perfect for email and password double check. > I have a problem, if the tags are in a s:decorate template... The validation failed with this exception: > Caused by: java.lang.IllegalStateException: forId must reference an EditableValueHolder ("input") component > at org.jboss.seam.ui.validator.EqualityValidator$OtherComponent.(EqualityValidator.java:168) > at org.jboss.seam.ui.validator.EqualityValidator.validate(EqualityValidator.java:74) > at org.richfaces.component.html.HtmlInputText.validateValue(HtmlInputText.java:35) > at javax.faces.component.UIInput.validate(UIInput.java:867) > This code is working: > > > > > > > This code is not working > > > > > > > > > > > Regards -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Jan 4 17:27:54 2009 From: jira-events at lists.jboss.org (Stephen Friedrich (JIRA)) Date: Sun, 4 Jan 2009 17:27:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3771) URL Rewriting Not Occurring In-Reply-To: <10072980.1228147776458.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <14475741.1231108074234.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444442#action_12444442 ] Stephen Friedrich commented on JBSEAM-3771: ------------------------------------------- Found the culprit: The session id _should_ be added when a JSF renderer calls context.getExternalContext().encodeResourceURL(urlText); However as soon as you have Seam's rewrite filter enabled in components.xml then the encoding is done by org.jboss.seam.web.RewritingResponse.encode(String) and that method returns the (possibily rewritten) URL without ever adding the session id. > URL Rewriting Not Occurring > --------------------------- > > Key: JBSEAM-3771 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3771 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.1.CR1 > Environment: Windows Vista, JBoss 4.2.0, JRockit 1.5 > Reporter: Dave Everson > Assignee: Norman Richards > > We have just updated Seam to 2.1.1CR1 > We started to use the rewrite functionality within pages.xml. > We have the following pages defined: > > > > > > > > > > > > > > > > > > We are able to access /newFamilyAccount without issue and a conversation is started > After entering data that already exists in the database, we should be taken to the /existingAccounts (/pages/account/existing.xhtml) view. We are taken to the view, however the URL shows: https://localhost/a/pages/account/existing.seam?cid=9. > We have tried several things and can't see to ever have the rewritten URL appear. Does anyone have any suggestions on what we are doing incorrectly. Thanks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Jan 4 17:41:54 2009 From: jira-events at lists.jboss.org (Stephen Friedrich (JIRA)) Date: Sun, 4 Jan 2009 17:41:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3771) URL Rewriting Not Occurring In-Reply-To: <10072980.1228147776458.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <4477401.1231108914239.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444445#action_12444445 ] Stephen Friedrich commented on JBSEAM-3771: ------------------------------------------- Sorry - the comment is not really applying to this issue, but to the fact that Seam fails to add the session id parameter. > URL Rewriting Not Occurring > --------------------------- > > Key: JBSEAM-3771 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3771 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.1.CR1 > Environment: Windows Vista, JBoss 4.2.0, JRockit 1.5 > Reporter: Dave Everson > Assignee: Norman Richards > > We have just updated Seam to 2.1.1CR1 > We started to use the rewrite functionality within pages.xml. > We have the following pages defined: > > > > > > > > > > > > > > > > > > We are able to access /newFamilyAccount without issue and a conversation is started > After entering data that already exists in the database, we should be taken to the /existingAccounts (/pages/account/existing.xhtml) view. We are taken to the view, however the URL shows: https://localhost/a/pages/account/existing.seam?cid=9. > We have tried several things and can't see to ever have the rewritten URL appear. Does anyone have any suggestions on what we are doing incorrectly. Thanks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Jan 4 18:04:54 2009 From: jira-events at lists.jboss.org (Stephen Friedrich (JIRA)) Date: Sun, 4 Jan 2009 18:04:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3875) Seam's Rewrite filter breaks URL-session-id-rewriting Message-ID: <2782549.1231110294248.JavaMail.jira@cloud.prod.atl2.jboss.com> Seam's Rewrite filter breaks URL-session-id-rewriting ----------------------------------------------------- Key: JBSEAM-3875 URL: https://jira.jboss.org/jira/browse/JBSEAM-3875 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA Reporter: Stephen Friedrich If Seam's rewrite filter is enabled, the session id is never added as a parameter to URLs. That should happen when one of the HttpServletResponse.encode...() methods is called and no session cookie is found. However the rewrite filter adds a response wrapper that delegates all encode methods to a method that only (possibly) rewrites the URL according to defined rewrite-rules, but never actually let's the servlet container encode the url. Fix: In org.jboss.seam.web.RewritingResponse.encodeURL(String) add this line: result = ((HttpServletResponse) getResponse()).encodeURL(result); before returning the result. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Jan 4 18:36:54 2009 From: jira-events at lists.jboss.org (Ingo Jobling (JIRA)) Date: Sun, 4 Jan 2009 18:36:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3875) Seam's Rewrite filter breaks URL-session-id-rewriting In-Reply-To: <2782549.1231110294248.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <8022225.1231112214279.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444449#action_12444449 ] Ingo Jobling commented on JBSEAM-3875: -------------------------------------- Would this work if running on JBoss portal server? I think getResponse() would return a PortletResponse rather than HttpServletResponse, thereby causing a ClassCastException. Perhaps add instanceOf to discover what the return from getResponse() is? > Seam's Rewrite filter breaks URL-session-id-rewriting > ----------------------------------------------------- > > Key: JBSEAM-3875 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3875 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.1.1.GA > Reporter: Stephen Friedrich > > If Seam's rewrite filter is enabled, the session id is never added as a parameter to URLs. > That should happen when one of the HttpServletResponse.encode...() methods is called and no session cookie is found. > However the rewrite filter adds a response wrapper that delegates all encode methods to a method that only (possibly) rewrites the URL according to defined rewrite-rules, but never actually let's the servlet container encode the url. > Fix: In org.jboss.seam.web.RewritingResponse.encodeURL(String) add this line: > result = ((HttpServletResponse) getResponse()).encodeURL(result); > before returning the result. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Jan 4 18:59:54 2009 From: jira-events at lists.jboss.org (Stephen Friedrich (JIRA)) Date: Sun, 4 Jan 2009 18:59:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3875) Seam's Rewrite filter breaks URL-session-id-rewriting In-Reply-To: <2782549.1231110294248.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <12442213.1231113594215.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444450#action_12444450 ] Stephen Friedrich commented on JBSEAM-3875: ------------------------------------------- Hm, the RewritingResponse extends HttpServletResponseWrapper. I don't know how (or even if) url rewriting is working in a portlet context. RewritingResponse gets passed HttpServletRequest and HttpServletResponse in its constructor and is already storing the request in a field anyway, so the same should probably be done for the response (avoiding the cast and call to super). > Seam's Rewrite filter breaks URL-session-id-rewriting > ----------------------------------------------------- > > Key: JBSEAM-3875 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3875 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.1.1.GA > Reporter: Stephen Friedrich > > If Seam's rewrite filter is enabled, the session id is never added as a parameter to URLs. > That should happen when one of the HttpServletResponse.encode...() methods is called and no session cookie is found. > However the rewrite filter adds a response wrapper that delegates all encode methods to a method that only (possibly) rewrites the URL according to defined rewrite-rules, but never actually let's the servlet container encode the url. > Fix: In org.jboss.seam.web.RewritingResponse.encodeURL(String) add this line: > result = ((HttpServletResponse) getResponse()).encodeURL(result); > before returning the result. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 5 03:16:54 2009 From: jira-events at lists.jboss.org (Jozef Hartinger (JIRA)) Date: Mon, 5 Jan 2009 03:16:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3702) NotBoundException when undeploying Seam examples on AS5 In-Reply-To: <20618941.1226666437087.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <27134662.1231143414736.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jozef Hartinger updated JBSEAM-3702: ------------------------------------ Fix Version/s: 2.1.2.CR1 > NotBoundException when undeploying Seam examples on AS5 > ------------------------------------------------------- > > Key: JBSEAM-3702 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3702 > Project: Seam > Issue Type: Bug > Components: EJB3, Examples > Affects Versions: 2.1.0.SP1 > Environment: JDK 6 > AS 5 trunk > Seam trunk r9564 > Reporter: Jozef Hartinger > Fix For: 2.1.2.CR1 > > Attachments: booking-undeploy.txt, dvdstore-undeploy.txt, wicket_undeploy_.txt > > > I am getting NotBoundException when undeploying Seam example when @Remove method is being called on statefull session bean. Affected examples are booking, dvdstore, nestedbooking, icefaces. Basic interaction with the example is needed before undeployment to reproduce the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 5 09:58:54 2009 From: jira-events at lists.jboss.org (Ga?l Beaudoin (JIRA)) Date: Mon, 5 Jan 2009 09:58:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3555) SeamMailAgain In-Reply-To: <3978595.1223977760796.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <1467360.1231167534565.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444532#action_12444532 ] Ga?l Beaudoin commented on JBSEAM-3555: --------------------------------------- Using jboss 4.2.3, seam 2.1.1, same issue with asynchronous email rendering with quartz dispatcher. It wometimes workds sometimes don't. What is sure is that it never works at application startup. > SeamMailAgain > ------------- > > Key: JBSEAM-3555 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3555 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.0.CR1 > Environment: JBoss AS 4.2.1.GA > JBoss Seam 2.1.0-SNAPSHOT (10.10. HudsonNo330) > Reporter: Markus Heidt > Assignee: Pete Muir > Fix For: 2.1.2.CR1 > > Attachments: server.log > > > Simple Mailing via Renderer doesn't work. > 'Seam-gen'erated a new project and added a new action 'sendMail' > Added the line to the action code: > Renderer.instance().render("/simple.xhtml"); > simple.xhtml is a modified version of the seam example (without #{person}) > Error after executing the action: > 2008-10-14 11:40:21,847 FATAL [javax.enterprise.resource.webcontainer.jsf.application] org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > javax.faces.el.EvaluationException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:91) > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:91) > ... > Caused by: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory > at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:256) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 5 11:31:54 2009 From: jira-events at lists.jboss.org (Susanne Jarl (JIRA)) Date: Mon, 5 Jan 2009 11:31:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3876) Seam text img alt and title encoding issue Message-ID: <1311525.1231173114262.JavaMail.jira@cloud.prod.atl2.jboss.com> Seam text img alt and title encoding issue ------------------------------------------ Key: JBSEAM-3876 URL: https://jira.jboss.org/jira/browse/JBSEAM-3876 Project: Seam Issue Type: Bug Components: Seam Text Affects Versions: 2.1.1.GA Environment: JBoss 4.2.3 GA, Java SDK6 Reporter: Susanne Jarl Priority: Minor If you use the img tag in seam text it now supports attributes alt and title. But there seems to be an encoding problem because you get a validation error if you put for instance some of the swedish letters ??? in the strings for alt or title attributes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 5 12:07:54 2009 From: jira-events at lists.jboss.org (Stefano Travelli (JIRA)) Date: Mon, 5 Jan 2009 12:07:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3838) Permission check fails on collections that contain lazily initialized entities In-Reply-To: <28195480.1229109456431.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <15612579.1231175274562.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444560#action_12444560 ] Stefano Travelli commented on JBSEAM-3838: ------------------------------------------ An analogue issue (equals used with instance.getClass(), where instance is potentially an instrumented proxy) is in JBSEAM-3672. > Permission check fails on collections that contain lazily initialized entities > ------------------------------------------------------------------------------ > > Key: JBSEAM-3838 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3838 > Project: Seam > Issue Type: Bug > Components: Security > Affects Versions: 2.1.0.SP1 > Reporter: Georges Berscheid > Assignee: Shane Bryzak > Fix For: 2.1.2.CR1 > > > org.jboss.seam.security.permission.PermissionMapper.filterByPermission:94 > The permission filter checks if the target of the check is of the same class as the target of the permission. If the collection-parameter is the result of a javax.persistence.Query.getResultList() (using Hibernate), and one of the entities returned in that List had previously been lazily fetched (e.g. as part of an entity relationship) this check will fail. > Hibernate probably does some optimization and knows that it had fetched this entity before, and hence puts the lazy proxy into the result list. The proxy's class name is something like Entity_$$_javassist_12 which won't match the class name of the permission target (Entity). > The only work-around I could find for this is to eagerly fetch all entity relationships that are affected by this behavior, which kills the performance of the application. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 5 13:35:54 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Mon, 5 Jan 2009 13:35:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3791) EjbEntityDescriptor setIdentifierAttribute and setVersionAttribute wrong string comparision In-Reply-To: <7921531.1228440216605.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <5970548.1231180554241.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3791. ----------------------------------- Resolution: Done thanks > EjbEntityDescriptor setIdentifierAttribute and setVersionAttribute wrong string comparision > ------------------------------------------------------------------------------------------- > > Key: JBSEAM-3791 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3791 > Project: Seam > Issue Type: Bug > Reporter: Francisco Jose Peredo Noguez > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > Attachments: patch.txt > > > In the methods setIdentifierAttribute and setVersionAttribute strings are being compared using ==, but .equals is what should be used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 5 15:43:54 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Mon, 5 Jan 2009 15:43:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2791) Support CJK in a chart. In-Reply-To: <10110540.1206721960161.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <16716168.1231188234258.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444594#action_12444594 ] Norman Richards commented on JBSEAM-2791: ----------------------------------------- Eek. iText is really ugly here. I had to spend some time convincing myself that iText was really that messed up. Can you attach an xhtml example of your usage so I can make sure what I check in works for you. I don't want to add a local flag until it's clear we have some interesting behavior for it. > Support CJK in a chart. > ----------------------- > > Key: JBSEAM-2791 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2791 > Project: Seam > Issue Type: Feature Request > Components: PDF > Affects Versions: 2.1.0.A1 > Environment: ubuntu linux 7.10 > jdk1.5.0_14 > jboss seam 2.1.0A > Reporter: Nobuyuki Inaba > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > Attachments: chart.patch > > > Hi, > Seam 2.1.0A does not support CJK character in a chart( in a PDF file). > because, UIChart class use DefaultFontMapper class. > I think UIChart class should use settings. > I attached the patch against this issue to this ticket.Please check the patch. > When apply the patch to Seam, Seam can support CJK chacter in a chart. > and In a chart, developer have to appoint the following to use CJK. > 1. Appoint the 'locale' in . e.g. . Now, 'ja' has not mean. but I think that this is necessary when Seam supports other multi-byte languages. > 2. Setting of . already fixed in JBSEAM-1039. > best regards, > Nobuyuki Inaba -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 5 16:42:54 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Mon, 5 Jan 2009 16:42:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-3875) Seam's Rewrite filter breaks URL-session-id-rewriting In-Reply-To: <2782549.1231110294248.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <27068081.1231191774585.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards reassigned JBSEAM-3875: --------------------------------------- Assignee: Norman Richards > Seam's Rewrite filter breaks URL-session-id-rewriting > ----------------------------------------------------- > > Key: JBSEAM-3875 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3875 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.1.1.GA > Reporter: Stephen Friedrich > Assignee: Norman Richards > > If Seam's rewrite filter is enabled, the session id is never added as a parameter to URLs. > That should happen when one of the HttpServletResponse.encode...() methods is called and no session cookie is found. > However the rewrite filter adds a response wrapper that delegates all encode methods to a method that only (possibly) rewrites the URL according to defined rewrite-rules, but never actually let's the servlet container encode the url. > Fix: In org.jboss.seam.web.RewritingResponse.encodeURL(String) add this line: > result = ((HttpServletResponse) getResponse()).encodeURL(result); > before returning the result. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 5 16:44:54 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Mon, 5 Jan 2009 16:44:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3875) Seam's Rewrite filter breaks URL-session-id-rewriting In-Reply-To: <2782549.1231110294248.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <28643725.1231191894262.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards updated JBSEAM-3875: ------------------------------------ Affects Version/s: 2.1.1.CR2 (was: 2.1.1.GA) > Seam's Rewrite filter breaks URL-session-id-rewriting > ----------------------------------------------------- > > Key: JBSEAM-3875 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3875 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.1.1.CR2 > Reporter: Stephen Friedrich > Assignee: Norman Richards > > If Seam's rewrite filter is enabled, the session id is never added as a parameter to URLs. > That should happen when one of the HttpServletResponse.encode...() methods is called and no session cookie is found. > However the rewrite filter adds a response wrapper that delegates all encode methods to a method that only (possibly) rewrites the URL according to defined rewrite-rules, but never actually let's the servlet container encode the url. > Fix: In org.jboss.seam.web.RewritingResponse.encodeURL(String) add this line: > result = ((HttpServletResponse) getResponse()).encodeURL(result); > before returning the result. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 5 17:03:54 2009 From: jira-events at lists.jboss.org (Stephen Friedrich (JIRA)) Date: Mon, 5 Jan 2009 17:03:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3875) Seam's Rewrite filter breaks URL-session-id-rewriting In-Reply-To: <2782549.1231110294248.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <18027234.1231193034213.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444599#action_12444599 ] Stephen Friedrich commented on JBSEAM-3875: ------------------------------------------- Why 2.1.1.CR2? I had this issue with 2.1.1.GA. > Seam's Rewrite filter breaks URL-session-id-rewriting > ----------------------------------------------------- > > Key: JBSEAM-3875 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3875 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.1.1.CR2 > Reporter: Stephen Friedrich > Assignee: Norman Richards > > If Seam's rewrite filter is enabled, the session id is never added as a parameter to URLs. > That should happen when one of the HttpServletResponse.encode...() methods is called and no session cookie is found. > However the rewrite filter adds a response wrapper that delegates all encode methods to a method that only (possibly) rewrites the URL according to defined rewrite-rules, but never actually let's the servlet container encode the url. > Fix: In org.jboss.seam.web.RewritingResponse.encodeURL(String) add this line: > result = ((HttpServletResponse) getResponse()).encodeURL(result); > before returning the result. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 5 18:09:04 2009 From: jira-events at lists.jboss.org (Nicola Benaglia (JIRA)) Date: Mon, 5 Jan 2009 18:09:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3767) Italian translation of Seam manual In-Reply-To: <4858384.1227892716499.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <24843167.1231196944086.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444611#action_12444611 ] Nicola Benaglia commented on JBSEAM-3767: ----------------------------------------- Hi Stefano, again my thanks for your help. Here new tasks: Framework.po Persistence.po Mail.po Webservices.po Getting_started_with_JBoss_Tools.po Bye, Nicola > Italian translation of Seam manual > ---------------------------------- > > Key: JBSEAM-3767 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3767 > Project: Seam > Issue Type: Release > Components: Documentation Translation > Reporter: Nicola Benaglia > Priority: Optional > > This Jira Issue is for coordinating the activity of translation of Seam manual in italian. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 5 18:21:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Mon, 5 Jan 2009 18:21:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3875) Seam's Rewrite filter breaks URL-session-id-rewriting In-Reply-To: <2782549.1231110294248.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <32306111.1231197664234.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards updated JBSEAM-3875: ------------------------------------ Fix Version/s: 2.1.2.CR1 Affects Version/s: (was: 2.1.1.CR2) woops > Seam's Rewrite filter breaks URL-session-id-rewriting > ----------------------------------------------------- > > Key: JBSEAM-3875 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3875 > Project: Seam > Issue Type: Bug > Components: Core > Reporter: Stephen Friedrich > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > > If Seam's rewrite filter is enabled, the session id is never added as a parameter to URLs. > That should happen when one of the HttpServletResponse.encode...() methods is called and no session cookie is found. > However the rewrite filter adds a response wrapper that delegates all encode methods to a method that only (possibly) rewrites the URL according to defined rewrite-rules, but never actually let's the servlet container encode the url. > Fix: In org.jboss.seam.web.RewritingResponse.encodeURL(String) add this line: > result = ((HttpServletResponse) getResponse()).encodeURL(result); > before returning the result. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 00:03:04 2009 From: jira-events at lists.jboss.org (Shane Bryzak (JIRA)) Date: Tue, 6 Jan 2009 00:03:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3225) Seam Remoting JS memory leak in IE In-Reply-To: <3019211.1218026234255.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <13541219.1231218184192.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444641#action_12444641 ] Shane Bryzak commented on JBSEAM-3225: -------------------------------------- I've made some changes to remote.js, hopefully fixing the garbage collection issues. Could you please try the latest SVN version and let me know if it works. > Seam Remoting JS memory leak in IE > ---------------------------------- > > Key: JBSEAM-3225 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3225 > Project: Seam > Issue Type: Bug > Components: Remoting > Affects Versions: 2.0.1.GA, 2.0.2.GA > Environment: IE 6 > Reporter: Joshua Davis > Assignee: Shane Bryzak > Attachments: fix_IE_memory_leak.patch, ie6leak-example.zip > > > Issuing many Seam Remoting calls can cause IE6 to fail with an 'out of memory' error. The problem seems to be related to the fact that the AJAX request object is a COM object in IE, so it doesn't get garbage collected in the same way. On a P3 machine with 512M of RAM, IE6 can handle about 30k calls before failing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 02:30:03 2009 From: jira-events at lists.jboss.org (Jarek Gilewski (JIRA)) Date: Tue, 6 Jan 2009 02:30:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3877) Use SeamGlobalResolver in the RuleBasedPermissionResolver as it is in ManagedWorkingMemory Message-ID: <15193852.1231227003980.JavaMail.jira@cloud.prod.atl2.jboss.com> Use SeamGlobalResolver in the RuleBasedPermissionResolver as it is in ManagedWorkingMemory ------------------------------------------------------------------------------------------ Key: JBSEAM-3877 URL: https://jira.jboss.org/jira/browse/JBSEAM-3877 Project: Seam Issue Type: Feature Request Components: Security Affects Versions: 2.1.1.GA Reporter: Jarek Gilewski SeamGlobalResolver is not used by RuleBasedPermissionResolver, so the global variable is not resolved. (Details on the forum) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 04:22:03 2009 From: jira-events at lists.jboss.org (Alexander Schwartz (JIRA)) Date: Tue, 6 Jan 2009 04:22:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3878) Excel null Values get hardcoded, non-localized "#not a number#" or "#not a date#" Message-ID: <837003.1231233724002.JavaMail.jira@cloud.prod.atl2.jboss.com> Excel null Values get hardcoded, non-localized "#not a number#" or "#not a date#" ---------------------------------------------------------------------------------- Key: JBSEAM-3878 URL: https://jira.jboss.org/jira/browse/JBSEAM-3878 Project: Seam Issue Type: Sub-task Components: Excel Affects Versions: 2.1.1.GA Environment: Seam 2.1.1 GA, Windows, Jetty Reporter: Alexander Schwartz When there is a null date or a null number, the helper outputs a fixed, non-localized string "#not a number#" or "#not a date#" . I think it should work like h:outputText and the string should be empty. Another alternative would be to look up the string in the messages resources to be able to change it and to localize it. >From JXLHelper.java: case number: try { return new jxl.write.Number(column, row, Double.parseDouble(data.toString()), cellFormat); } catch (NumberFormatException e) { return new Label(column, row, "#not a number#", cellFormat); } case date: try { return new DateTime(column, row, (Date) data, cellFormat); } catch (ClassCastException e) { return new Label(column, row, "#not a date#", cellFormat); } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 04:24:04 2009 From: jira-events at lists.jboss.org (Alexander Schwartz (JIRA)) Date: Tue, 6 Jan 2009 04:24:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3878) Excel e:cell null Values get hardcoded, non-localized "#not a number#" or "#not a date#" In-Reply-To: <837003.1231233724002.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <17579564.1231233844207.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Schwartz updated JBSEAM-3878: --------------------------------------- Summary: Excel e:cell null Values get hardcoded, non-localized "#not a number#" or "#not a date#" (was: Excel null Values get hardcoded, non-localized "#not a number#" or "#not a date#" ) > Excel e:cell null Values get hardcoded, non-localized "#not a number#" or "#not a date#" > ----------------------------------------------------------------------------------------- > > Key: JBSEAM-3878 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3878 > Project: Seam > Issue Type: Sub-task > Components: Excel > Affects Versions: 2.1.1.GA > Environment: Seam 2.1.1 GA, Windows, Jetty > Reporter: Alexander Schwartz > > When there is a null date or a null number, the helper outputs a fixed, non-localized string "#not a number#" or "#not a date#" . > I think it should work like h:outputText and the string should be empty. Another alternative would be to look up the string in the messages resources to be able to change it and to localize it. > From JXLHelper.java: > case number: > try { > return new jxl.write.Number(column, row, Double.parseDouble(data.toString()), cellFormat); > } catch (NumberFormatException e) { > return new Label(column, row, "#not a number#", cellFormat); > } > case date: > try { > return new DateTime(column, row, (Date) data, cellFormat); > } catch (ClassCastException e) { > return new Label(column, row, "#not a date#", cellFormat); > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 04:35:04 2009 From: jira-events at lists.jboss.org (Alexander Schwartz (JIRA)) Date: Tue, 6 Jan 2009 04:35:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3879) e:cell formatting of date or number colum fails, if first value is a null value Message-ID: <30253649.1231234504857.JavaMail.jira@cloud.prod.atl2.jboss.com> e:cell formatting of date or number colum fails, if first value is a null value ------------------------------------------------------------------------------- Key: JBSEAM-3879 URL: https://jira.jboss.org/jira/browse/JBSEAM-3879 Project: Seam Issue Type: Sub-task Components: Excel Affects Versions: 2.1.1.GA Environment: Seam 2.1.1.GA, Windows, Jetty Reporter: Alexander Schwartz The cell style of a e:cell is cached (for the specific id) when it is accessed for the first time. When the first value is a null value, uiCell.getDataType() is unable to automatically detect the data type of the column and returns 'general'. This is then cached. All other columns are then treated as 'general' in createCell(), and all data is converted using data.toString() leading to ugly results. Our solution is to add "xls-force-type: date" to all e:cell of type number or date. We added this to the evaluation (see below). Another idea would have been to defer caching until the first non-null value has been met. But this might cause troubles in createCell() when there is a handing depending on the type. from JXLHelper.java: /** * Gets the cell type for a cell. Tries to look it up in a cache based on the * component id of the cell. If it's not found, it's created and cached. * * @param uiCell The cell to look up * @return The data type of a cell */ private CellType getCellDataType(UICell uiCell) { if (log.isTraceEnabled()) { log.trace("Getting cell data type from cache for #0", uiCell.getId()); } CellType cellDataType = cellInfoCache.getCachedCellType(uiCell.getId()); if (cellDataType == null) { /* old code: cellDataType = uiCell.getDataType(); */ /* new code start */ CellStyle cellStyle = new CellStyle(parser.getCascadedStyleMap(uiCell)); cellDataType = cellStyle.forceType != null ? CellType .valueOf(cellStyle.forceType) : uiCell.getDataType(); /* new code end */ cellInfoCache.setCachedCellType(uiCell.getId(), cellDataType); } return cellDataType; } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 04:37:03 2009 From: jira-events at lists.jboss.org (Alexander Schwartz (JIRA)) Date: Tue, 6 Jan 2009 04:37:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3879) e:cell formatting of date or number colum fails, if first value is a null value In-Reply-To: <30253649.1231234504857.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <3193498.1231234624049.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Schwartz updated JBSEAM-3879: --------------------------------------- Attachment: jxlhelper.java.patch code change as patch > e:cell formatting of date or number colum fails, if first value is a null value > ------------------------------------------------------------------------------- > > Key: JBSEAM-3879 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3879 > Project: Seam > Issue Type: Sub-task > Components: Excel > Affects Versions: 2.1.1.GA > Environment: Seam 2.1.1.GA, Windows, Jetty > Reporter: Alexander Schwartz > Attachments: jxlhelper.java.patch > > > The cell style of a e:cell is cached (for the specific id) when it is accessed for the first time. When the first value is a null value, uiCell.getDataType() is unable to automatically detect the data type of the column and returns 'general'. This is then cached. > All other columns are then treated as 'general' in createCell(), and all data is converted using data.toString() leading to ugly results. > Our solution is to add "xls-force-type: date" to all e:cell of type number or date. We added this to the evaluation (see below). > Another idea would have been to defer caching until the first non-null value has been met. But this might cause troubles in createCell() when there is a handing depending on the type. > from JXLHelper.java: > /** > * Gets the cell type for a cell. Tries to look it up in a cache based on the > * component id of the cell. If it's not found, it's created and cached. > * > * @param uiCell The cell to look up > * @return The data type of a cell > */ > private CellType getCellDataType(UICell uiCell) > { > if (log.isTraceEnabled()) > { > log.trace("Getting cell data type from cache for #0", uiCell.getId()); > } > CellType cellDataType = cellInfoCache.getCachedCellType(uiCell.getId()); > if (cellDataType == null) > { > /* old code: > cellDataType = uiCell.getDataType(); > */ > /* new code start */ > CellStyle cellStyle = new CellStyle(parser.getCascadedStyleMap(uiCell)); > cellDataType = cellStyle.forceType != null ? CellType > .valueOf(cellStyle.forceType) : uiCell.getDataType(); > /* new code end */ > cellInfoCache.setCachedCellType(uiCell.getId(), cellDataType); > } > return cellDataType; > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 05:54:05 2009 From: jira-events at lists.jboss.org (Jozef Hartinger (JIRA)) Date: Tue, 6 Jan 2009 05:54:05 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3449) Upgrade to latest RestEasy beta In-Reply-To: <21376851.1222121060720.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <14015924.1231239245985.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jozef Hartinger updated JBSEAM-3449: ------------------------------------ Fix Version/s: 2.1.2.GA > Upgrade to latest RestEasy beta > ------------------------------- > > Key: JBSEAM-3449 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3449 > Project: Seam > Issue Type: Feature Request > Components: WS > Affects Versions: 2.1.0.BETA1 > Reporter: Scott Olcott > Assignee: Jozef Hartinger > Fix For: 2.1.2.GA > > Attachments: resteasyBeta-8.txt > > > The latest beta is beta-8 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 09:51:04 2009 From: jira-events at lists.jboss.org (Nobuyuki Inaba (JIRA)) Date: Tue, 6 Jan 2009 09:51:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2791) Support CJK in a chart. In-Reply-To: <10110540.1206721960161.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <25719962.1231253464110.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444709#action_12444709 ] Nobuyuki Inaba commented on JBSEAM-2791: ---------------------------------------- Hi, Norman. I attach a xhtml sample and working screen snapshot( apply patch version, not apply patch version). Japanese is not displayed if you watch snap shots unless I apply a patch. About a "locale" flag, I think that Seam is used in the country except Japan and U.S.A. For the countries that had to change kind of the FontMapper, I thought that "locale" flag was necessary. but I don't know whether there is a country having to change FontMapper. sorry... P.S. The AsianFontMapper class is included in iTextAsian.jar. I downloaded it from here(http://itextpdf.sourceforge.net/). > Support CJK in a chart. > ----------------------- > > Key: JBSEAM-2791 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2791 > Project: Seam > Issue Type: Feature Request > Components: PDF > Affects Versions: 2.1.0.A1 > Environment: ubuntu linux 7.10 > jdk1.5.0_14 > jboss seam 2.1.0A > Reporter: Nobuyuki Inaba > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > Attachments: chart.patch > > > Hi, > Seam 2.1.0A does not support CJK character in a chart( in a PDF file). > because, UIChart class use DefaultFontMapper class. > I think UIChart class should use settings. > I attached the patch against this issue to this ticket.Please check the patch. > When apply the patch to Seam, Seam can support CJK chacter in a chart. > and In a chart, developer have to appoint the following to use CJK. > 1. Appoint the 'locale' in . e.g. . Now, 'ja' has not mean. but I think that this is necessary when Seam supports other multi-byte languages. > 2. Setting of . already fixed in JBSEAM-1039. > best regards, > Nobuyuki Inaba -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 09:53:04 2009 From: jira-events at lists.jboss.org (Nobuyuki Inaba (JIRA)) Date: Tue, 6 Jan 2009 09:53:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2791) Support CJK in a chart. In-Reply-To: <10110540.1206721960161.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <22051645.1231253584908.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nobuyuki Inaba updated JBSEAM-2791: ----------------------------------- Attachment: cjkChart.xhtml > Support CJK in a chart. > ----------------------- > > Key: JBSEAM-2791 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2791 > Project: Seam > Issue Type: Feature Request > Components: PDF > Affects Versions: 2.1.0.A1 > Environment: ubuntu linux 7.10 > jdk1.5.0_14 > jboss seam 2.1.0A > Reporter: Nobuyuki Inaba > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > Attachments: chart.patch, cjkChart.xhtml > > > Hi, > Seam 2.1.0A does not support CJK character in a chart( in a PDF file). > because, UIChart class use DefaultFontMapper class. > I think UIChart class should use settings. > I attached the patch against this issue to this ticket.Please check the patch. > When apply the patch to Seam, Seam can support CJK chacter in a chart. > and In a chart, developer have to appoint the following to use CJK. > 1. Appoint the 'locale' in . e.g. . Now, 'ja' has not mean. but I think that this is necessary when Seam supports other multi-byte languages. > 2. Setting of . already fixed in JBSEAM-1039. > best regards, > Nobuyuki Inaba -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 09:55:04 2009 From: jira-events at lists.jboss.org (Nobuyuki Inaba (JIRA)) Date: Tue, 6 Jan 2009 09:55:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2791) Support CJK in a chart. In-Reply-To: <10110540.1206721960161.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <22960436.1231253704771.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nobuyuki Inaba updated JBSEAM-2791: ----------------------------------- Attachment: screenshot(apply patch version).jpg > Support CJK in a chart. > ----------------------- > > Key: JBSEAM-2791 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2791 > Project: Seam > Issue Type: Feature Request > Components: PDF > Affects Versions: 2.1.0.A1 > Environment: ubuntu linux 7.10 > jdk1.5.0_14 > jboss seam 2.1.0A > Reporter: Nobuyuki Inaba > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > Attachments: chart.patch, cjkChart.xhtml, screenshot(apply patch version).jpg > > > Hi, > Seam 2.1.0A does not support CJK character in a chart( in a PDF file). > because, UIChart class use DefaultFontMapper class. > I think UIChart class should use settings. > I attached the patch against this issue to this ticket.Please check the patch. > When apply the patch to Seam, Seam can support CJK chacter in a chart. > and In a chart, developer have to appoint the following to use CJK. > 1. Appoint the 'locale' in . e.g. . Now, 'ja' has not mean. but I think that this is necessary when Seam supports other multi-byte languages. > 2. Setting of . already fixed in JBSEAM-1039. > best regards, > Nobuyuki Inaba -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 09:57:03 2009 From: jira-events at lists.jboss.org (Nobuyuki Inaba (JIRA)) Date: Tue, 6 Jan 2009 09:57:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2791) Support CJK in a chart. In-Reply-To: <10110540.1206721960161.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <16913424.1231253823982.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nobuyuki Inaba updated JBSEAM-2791: ----------------------------------- Attachment: screenshot( not apply patch version).jpg Japanese not displayed in the chart. > Support CJK in a chart. > ----------------------- > > Key: JBSEAM-2791 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2791 > Project: Seam > Issue Type: Feature Request > Components: PDF > Affects Versions: 2.1.0.A1 > Environment: ubuntu linux 7.10 > jdk1.5.0_14 > jboss seam 2.1.0A > Reporter: Nobuyuki Inaba > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > Attachments: chart.patch, cjkChart.xhtml, screenshot( not apply patch version).jpg, screenshot(apply patch version).jpg > > > Hi, > Seam 2.1.0A does not support CJK character in a chart( in a PDF file). > because, UIChart class use DefaultFontMapper class. > I think UIChart class should use settings. > I attached the patch against this issue to this ticket.Please check the patch. > When apply the patch to Seam, Seam can support CJK chacter in a chart. > and In a chart, developer have to appoint the following to use CJK. > 1. Appoint the 'locale' in . e.g. . Now, 'ja' has not mean. but I think that this is necessary when Seam supports other multi-byte languages. > 2. Setting of . already fixed in JBSEAM-1039. > best regards, > Nobuyuki Inaba -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 10:18:04 2009 From: jira-events at lists.jboss.org (Clint Popetz (JIRA)) Date: Tue, 6 Jan 2009 10:18:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3880) Wicket interception doesn't throw error on missing required injections Message-ID: <12660077.1231255084052.JavaMail.jira@cloud.prod.atl2.jboss.com> Wicket interception doesn't throw error on missing required injections ----------------------------------------------------------------------- Key: JBSEAM-3880 URL: https://jira.jboss.org/jira/browse/JBSEAM-3880 Project: Seam Issue Type: Bug Reporter: Clint Popetz Assignee: Clint Popetz -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 10:48:04 2009 From: jira-events at lists.jboss.org (Denis Forveille (JIRA)) Date: Tue, 6 Jan 2009 10:48:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3726) Methods with an "InvocationContext" parameter annotated with "javax.ejb.PostActivate" cause a validation exception in WebSphere v7.0 In-Reply-To: <21537061.1227043896577.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <7846295.1231256884452.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444718#action_12444718 ] Denis Forveille commented on JBSEAM-3726: ----------------------------------------- To summarize, the methods with a bad signature are annotated with - javax.ejb.PostActivate - javax.annotation.PostConstruct In - EntityManagerProxyInterceptor - HibernateSessionProxyInterceptor > Methods with an "InvocationContext" parameter annotated with "javax.ejb.PostActivate" cause a validation exception in WebSphere v7.0 > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBSEAM-3726 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3726 > Project: Seam > Issue Type: Bug > Components: Platform interoperability > Affects Versions: 2.1.1.CR2 > Environment: WebSphere v7.0 > Reporter: Denis Forveille > Assignee: Dan Allen > Priority: Critical > Fix For: 2.1.2.CR1 > > Attachments: traceback.txt > > > When starting our app in WebSphere v7.0 with seam v2.1.0.SP1, we receive the exception below > Is it possible that annotation "javax.ejb.PostActivate" is used instead of "org.jboss.seam.annotations.intercept.PostActivate" annotation and that the former does not accept any parameter for the annotated method (At least in WebSphere v7.0) and the latter does... > The method in question is declared as > @PostActivate > public void postActivate(InvocationContext invocation) throws Exception > This method signature is present in classes SessionBeanInterceptor, EntityManagerProxyInterceptor and HibernateSessionProxyInterceptor > Exception: > [18/11/08 16:17:51:537 EST] 0000001a annotations E AnnotativeMetadataManagerImpl merge Caught exception while merging > com.ibm.wsspi.amm.validate.ValidationException: For method, org.jboss.seam.persistence.EntityManagerProxyInterceptor.postActivate(Lorg/jboss/seam/intercept/InvocationContext;)V\[com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 1b8e1b8e\], parameters were specified, but null was the expected comparison -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 13:36:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Tue, 6 Jan 2009 13:36:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2791) Support CJK in a chart. In-Reply-To: <10110540.1206721960161.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <30547699.1231266964335.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444750#action_12444750 ] Norman Richards commented on JBSEAM-2791: ----------------------------------------- Thanks. I've committed something based on your idea and tested it against your chart. I am not happy that we need to specify a character encoding for iText as I feel character encoding ought to come from the XML encoding. But, I'm just not sure how this should work with iText. Can I include your chart in the iText example for others to use? > Support CJK in a chart. > ----------------------- > > Key: JBSEAM-2791 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2791 > Project: Seam > Issue Type: Feature Request > Components: PDF > Affects Versions: 2.1.0.A1 > Environment: ubuntu linux 7.10 > jdk1.5.0_14 > jboss seam 2.1.0A > Reporter: Nobuyuki Inaba > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > Attachments: chart.patch, cjkChart.xhtml, screenshot( not apply patch version).jpg, screenshot(apply patch version).jpg > > > Hi, > Seam 2.1.0A does not support CJK character in a chart( in a PDF file). > because, UIChart class use DefaultFontMapper class. > I think UIChart class should use settings. > I attached the patch against this issue to this ticket.Please check the patch. > When apply the patch to Seam, Seam can support CJK chacter in a chart. > and In a chart, developer have to appoint the following to use CJK. > 1. Appoint the 'locale' in . e.g. . Now, 'ja' has not mean. but I think that this is necessary when Seam supports other multi-byte languages. > 2. Setting of . already fixed in JBSEAM-1039. > best regards, > Nobuyuki Inaba -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 13:56:03 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Tue, 6 Jan 2009 13:56:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3797) ConversationInterceptor.aroundInvoke broken stacktrace In-Reply-To: <15882360.1228444246897.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <11000934.1231268163995.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3797. ----------------------------------- Resolution: Won't Fix I don't see any value in wrapping the exception here, and in an interceptor it could possibly confuse the callers. I'm going to close these. Feel free to re-open if you still think this is an issue. > ConversationInterceptor.aroundInvoke broken stacktrace > ------------------------------------------------------ > > Key: JBSEAM-3797 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3797 > Project: Seam > Issue Type: Bug > Reporter: Francisco Jose Peredo Noguez > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > Attachments: patch.txt > > > catch (Exception e) > { > if ( isEndConversationRequired(e) ) > { > endConversation(false, false); > } > throw e; //<---HERE! > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 13:58:03 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Tue, 6 Jan 2009 13:58:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3796) SeamNamespaceHandler.decorate broken stacktrace In-Reply-To: <11787333.1228443996959.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <19916388.1231268284002.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3796. ----------------------------------- Resolution: Done Thanks. > SeamNamespaceHandler.decorate broken stacktrace > ----------------------------------------------- > > Key: JBSEAM-3796 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3796 > Project: Seam > Issue Type: Bug > Reporter: Francisco Jose Peredo Noguez > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > Attachments: patch.txt > > > try > { > cls = ClassUtils.forName(SEAM_COMPONENT_POST_PROCESSOR); > } > catch (ClassNotFoundException e) > { > throw new IllegalStateException("Unable to load class '" > + SEAM_COMPONENT_POST_PROCESSOR > + "' make sure you have the jboss-seam-spring.jar in your classpath."); //<-- HERE > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 14:03:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Tue, 6 Jan 2009 14:03:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3795) ControllerNotificationComponent.create broken stacktrace In-Reply-To: <23190846.1228443760264.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <20766336.1231268584828.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3795. ----------------------------------- Resolution: Done Thanks. > ControllerNotificationComponent.create broken stacktrace > -------------------------------------------------------- > > Key: JBSEAM-3795 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3795 > Project: Seam > Issue Type: Bug > Reporter: Francisco Jose Peredo Noguez > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > Attachments: patch.txt > > > catch (Throwable t) > { > throw new IllegalArgumentException("Exception installing ControllerNotificationComponent: " + t); > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 15:05:04 2009 From: jira-events at lists.jboss.org (Nicklas Karlsson (JIRA)) Date: Tue, 6 Jan 2009 15:05:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3878) Excel e:cell null Values get hardcoded, non-localized "#not a number#" or "#not a date#" In-Reply-To: <837003.1231233724002.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <30423030.1231272304080.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444764#action_12444764 ] Nicklas Karlsson commented on JBSEAM-3878: ------------------------------------------ I think it would be a little sneaky to just silently insert a blank and drive the user nuts as to why the value doesn't appear. I'll have a look if I could drag something out of the seam resource bundle. > Excel e:cell null Values get hardcoded, non-localized "#not a number#" or "#not a date#" > ----------------------------------------------------------------------------------------- > > Key: JBSEAM-3878 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3878 > Project: Seam > Issue Type: Sub-task > Components: Excel > Affects Versions: 2.1.1.GA > Environment: Seam 2.1.1 GA, Windows, Jetty > Reporter: Alexander Schwartz > > When there is a null date or a null number, the helper outputs a fixed, non-localized string "#not a number#" or "#not a date#" . > I think it should work like h:outputText and the string should be empty. Another alternative would be to look up the string in the messages resources to be able to change it and to localize it. > From JXLHelper.java: > case number: > try { > return new jxl.write.Number(column, row, Double.parseDouble(data.toString()), cellFormat); > } catch (NumberFormatException e) { > return new Label(column, row, "#not a number#", cellFormat); > } > case date: > try { > return new DateTime(column, row, (Date) data, cellFormat); > } catch (ClassCastException e) { > return new Label(column, row, "#not a date#", cellFormat); > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 15:09:05 2009 From: jira-events at lists.jboss.org (Nicklas Karlsson (JIRA)) Date: Tue, 6 Jan 2009 15:09:05 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3879) e:cell formatting of date or number colum fails, if first value is a null value In-Reply-To: <30253649.1231234504857.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <15002872.1231272545712.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444767#action_12444767 ] Nicklas Karlsson commented on JBSEAM-3879: ------------------------------------------ "All other columns are then treated as 'general' in createCell()" All other columns or all other rows on that column? I think we need some sort of non-null data to make assumptions on it (surprise). The performance is generally OK and I would think that there aren't that many null values in real scenarios so perhaps the cacheing could be delayed. I'll have a look... > e:cell formatting of date or number colum fails, if first value is a null value > ------------------------------------------------------------------------------- > > Key: JBSEAM-3879 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3879 > Project: Seam > Issue Type: Sub-task > Components: Excel > Affects Versions: 2.1.1.GA > Environment: Seam 2.1.1.GA, Windows, Jetty > Reporter: Alexander Schwartz > Attachments: jxlhelper.java.patch > > > The cell style of a e:cell is cached (for the specific id) when it is accessed for the first time. When the first value is a null value, uiCell.getDataType() is unable to automatically detect the data type of the column and returns 'general'. This is then cached. > All other columns are then treated as 'general' in createCell(), and all data is converted using data.toString() leading to ugly results. > Our solution is to add "xls-force-type: date" to all e:cell of type number or date. We added this to the evaluation (see below). > Another idea would have been to defer caching until the first non-null value has been met. But this might cause troubles in createCell() when there is a handing depending on the type. > from JXLHelper.java: > /** > * Gets the cell type for a cell. Tries to look it up in a cache based on the > * component id of the cell. If it's not found, it's created and cached. > * > * @param uiCell The cell to look up > * @return The data type of a cell > */ > private CellType getCellDataType(UICell uiCell) > { > if (log.isTraceEnabled()) > { > log.trace("Getting cell data type from cache for #0", uiCell.getId()); > } > CellType cellDataType = cellInfoCache.getCachedCellType(uiCell.getId()); > if (cellDataType == null) > { > /* old code: > cellDataType = uiCell.getDataType(); > */ > /* new code start */ > CellStyle cellStyle = new CellStyle(parser.getCascadedStyleMap(uiCell)); > cellDataType = cellStyle.forceType != null ? CellType > .valueOf(cellStyle.forceType) : uiCell.getDataType(); > /* new code end */ > cellInfoCache.setCachedCellType(uiCell.getId(), cellDataType); > } > return cellDataType; > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 16:01:04 2009 From: jira-events at lists.jboss.org (Alexander Schwartz (JIRA)) Date: Tue, 6 Jan 2009 16:01:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3879) e:cell formatting of date or number colum fails, if first value is a null value In-Reply-To: <30253649.1231234504857.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <25549749.1231275664500.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12445075#action_12445075 ] Alexander Schwartz commented on JBSEAM-3879: -------------------------------------------- It's only the cells in that column that get the wrong format. Deferring could solve most common problems, but might conflict with JBSEAM-3878, when for the first null values in a column a different message is pulled from the resources... that depends on the implementation there. Even if there is a deferred resolving of the type that will work in most cases, I'd like to see "xls-force-type" in the code to cover all corner cases. Thanks, Alex. > e:cell formatting of date or number colum fails, if first value is a null value > ------------------------------------------------------------------------------- > > Key: JBSEAM-3879 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3879 > Project: Seam > Issue Type: Sub-task > Components: Excel > Affects Versions: 2.1.1.GA > Environment: Seam 2.1.1.GA, Windows, Jetty > Reporter: Alexander Schwartz > Attachments: jxlhelper.java.patch > > > The cell style of a e:cell is cached (for the specific id) when it is accessed for the first time. When the first value is a null value, uiCell.getDataType() is unable to automatically detect the data type of the column and returns 'general'. This is then cached. > All other columns are then treated as 'general' in createCell(), and all data is converted using data.toString() leading to ugly results. > Our solution is to add "xls-force-type: date" to all e:cell of type number or date. We added this to the evaluation (see below). > Another idea would have been to defer caching until the first non-null value has been met. But this might cause troubles in createCell() when there is a handing depending on the type. > from JXLHelper.java: > /** > * Gets the cell type for a cell. Tries to look it up in a cache based on the > * component id of the cell. If it's not found, it's created and cached. > * > * @param uiCell The cell to look up > * @return The data type of a cell > */ > private CellType getCellDataType(UICell uiCell) > { > if (log.isTraceEnabled()) > { > log.trace("Getting cell data type from cache for #0", uiCell.getId()); > } > CellType cellDataType = cellInfoCache.getCachedCellType(uiCell.getId()); > if (cellDataType == null) > { > /* old code: > cellDataType = uiCell.getDataType(); > */ > /* new code start */ > CellStyle cellStyle = new CellStyle(parser.getCascadedStyleMap(uiCell)); > cellDataType = cellStyle.forceType != null ? CellType > .valueOf(cellStyle.forceType) : uiCell.getDataType(); > /* new code end */ > cellInfoCache.setCachedCellType(uiCell.getId(), cellDataType); > } > return cellDataType; > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 18:43:03 2009 From: jira-events at lists.jboss.org (Joshua Davis (JIRA)) Date: Tue, 6 Jan 2009 18:43:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3225) Seam Remoting JS memory leak in IE In-Reply-To: <3019211.1218026234255.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <26935095.1231285384000.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12445100#action_12445100 ] Joshua Davis commented on JBSEAM-3225: -------------------------------------- Hm... rev 9869 trunk doesn't seem to work at all because 'req' is undefined in a few places. I fixed that and I'm running the simple test now, after about 2000 calls it is using up more and more memory. So, it's not looking good right now. > Seam Remoting JS memory leak in IE > ---------------------------------- > > Key: JBSEAM-3225 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3225 > Project: Seam > Issue Type: Bug > Components: Remoting > Affects Versions: 2.0.1.GA, 2.0.2.GA > Environment: IE 6 > Reporter: Joshua Davis > Assignee: Shane Bryzak > Attachments: fix_IE_memory_leak.patch, ie6leak-example.zip > > > Issuing many Seam Remoting calls can cause IE6 to fail with an 'out of memory' error. The problem seems to be related to the fact that the AJAX request object is a COM object in IE, so it doesn't get garbage collected in the same way. On a P3 machine with 512M of RAM, IE6 can handle about 30k calls before failing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 18:47:14 2009 From: jira-events at lists.jboss.org (Joshua Davis (JIRA)) Date: Tue, 6 Jan 2009 18:47:14 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3225) Seam Remoting JS memory leak in IE In-Reply-To: <3019211.1218026234255.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <28297044.1231285634389.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12445101#action_12445101 ] Joshua Davis commented on JBSEAM-3225: -------------------------------------- After 5000 iterations IE6 is using over 165K of memory. It started with about 30K. > Seam Remoting JS memory leak in IE > ---------------------------------- > > Key: JBSEAM-3225 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3225 > Project: Seam > Issue Type: Bug > Components: Remoting > Affects Versions: 2.0.1.GA, 2.0.2.GA > Environment: IE 6 > Reporter: Joshua Davis > Assignee: Shane Bryzak > Attachments: fix_IE_memory_leak.patch, ie6leak-example.zip > > > Issuing many Seam Remoting calls can cause IE6 to fail with an 'out of memory' error. The problem seems to be related to the fact that the AJAX request object is a COM object in IE, so it doesn't get garbage collected in the same way. On a P3 machine with 512M of RAM, IE6 can handle about 30k calls before failing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 19:01:03 2009 From: jira-events at lists.jboss.org (Ian Darwin (JIRA)) Date: Tue, 6 Jan 2009 19:01:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3881) Typo in XML in Getting_Started_With_JBoss_Tools.xml Message-ID: <16912616.1231286463963.JavaMail.jira@cloud.prod.atl2.jboss.com> Typo in XML in Getting_Started_With_JBoss_Tools.xml --------------------------------------------------- Key: JBSEAM-3881 URL: https://jira.jboss.org/jira/browse/JBSEAM-3881 Project: Seam Issue Type: Patch Components: Documentation Issues Affects Versions: 2.1.1.GA Environment: N/A Reporter: Ian Darwin Typo in XML element. Patch attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 19:03:04 2009 From: jira-events at lists.jboss.org (Ian Darwin (JIRA)) Date: Tue, 6 Jan 2009 19:03:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3881) Typo in XML in Getting_Started_With_JBoss_Tools.xml In-Reply-To: <16912616.1231286463963.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <20901204.1231286584095.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Darwin updated JBSEAM-3881: ------------------------------- Attachment: seamref.diff Fixes XML typo. > Typo in XML in Getting_Started_With_JBoss_Tools.xml > --------------------------------------------------- > > Key: JBSEAM-3881 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3881 > Project: Seam > Issue Type: Patch > Components: Documentation Issues > Affects Versions: 2.1.1.GA > Environment: N/A > Reporter: Ian Darwin > Attachments: seamref.diff > > > Typo in XML element. Patch attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 19:03:04 2009 From: jira-events at lists.jboss.org (Shane Bryzak (JIRA)) Date: Tue, 6 Jan 2009 19:03:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3225) Seam Remoting JS memory leak in IE In-Reply-To: <3019211.1218026234255.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <24192868.1231286584306.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12445104#action_12445104 ] Shane Bryzak commented on JBSEAM-3225: -------------------------------------- I've fixed the incorrect variable names (you found only 2 instances right?). Which version of JScript.dll do you have? > Seam Remoting JS memory leak in IE > ---------------------------------- > > Key: JBSEAM-3225 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3225 > Project: Seam > Issue Type: Bug > Components: Remoting > Affects Versions: 2.0.1.GA, 2.0.2.GA > Environment: IE 6 > Reporter: Joshua Davis > Assignee: Shane Bryzak > Attachments: fix_IE_memory_leak.patch, ie6leak-example.zip > > > Issuing many Seam Remoting calls can cause IE6 to fail with an 'out of memory' error. The problem seems to be related to the fact that the AJAX request object is a COM object in IE, so it doesn't get garbage collected in the same way. On a P3 machine with 512M of RAM, IE6 can handle about 30k calls before failing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 21:11:03 2009 From: jira-events at lists.jboss.org (Clint Popetz (JIRA)) Date: Tue, 6 Jan 2009 21:11:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3882) PermissionResolvers can't use injections Message-ID: <29532787.1231294264040.JavaMail.jira@cloud.prod.atl2.jboss.com> PermissionResolvers can't use injections ---------------------------------------- Key: JBSEAM-3882 URL: https://jira.jboss.org/jira/browse/JBSEAM-3882 Project: Seam Issue Type: Bug Components: Security Reporter: Clint Popetz PermissionResolvers are seam components, and the documentation doesn't mention any restrictions on them. However, because PermissionMapper caches the resolver chain in the application, and doesn't serialize access to the resolvers themselves, PermissionResolvers must not only be stateless but also must not use injections, even of stateless components, as bijection on each resolver might be interlaced from multiple threads. This should probably be documented, as it just exposed itself as on our production server as nasty errors under load :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 6 22:49:14 2009 From: jira-events at lists.jboss.org (Shane Bryzak (JIRA)) Date: Tue, 6 Jan 2009 22:49:14 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-3882) PermissionResolvers can't use injections In-Reply-To: <29532787.1231294264040.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <14208782.1231300154143.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Bryzak reassigned JBSEAM-3882: ------------------------------------ Assignee: Shane Bryzak > PermissionResolvers can't use injections > ---------------------------------------- > > Key: JBSEAM-3882 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3882 > Project: Seam > Issue Type: Bug > Components: Security > Reporter: Clint Popetz > Assignee: Shane Bryzak > > PermissionResolvers are seam components, and the documentation doesn't mention any restrictions on them. However, because PermissionMapper caches the resolver chain in the application, and doesn't serialize access to the resolvers themselves, PermissionResolvers must not only be stateless but also must not use injections, even of stateless components, as bijection on each resolver might be interlaced from multiple threads. > This should probably be documented, as it just exposed itself as on our production server as nasty errors under load :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 7 02:31:04 2009 From: jira-events at lists.jboss.org (Stephen Friedrich (JIRA)) Date: Wed, 7 Jan 2009 02:31:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3883) URL rewriting broken for view-id of redirects in exceptions Message-ID: <31240748.1231313464202.JavaMail.jira@cloud.prod.atl2.jboss.com> URL rewriting broken for view-id of redirects in exceptions ----------------------------------------------------------- Key: JBSEAM-3883 URL: https://jira.jboss.org/jira/browse/JBSEAM-3883 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA Reporter: Stephen Friedrich When a configured exception handler redirects to a view-id, then the URL for that view-id is not processed by Seam's URL rewriting filter. As a result you cannot re-write the URL for your login page if you want to redirect to the login page when a ViewExpiredSException occurs. The problem is that the RewriteFilter is deeper in the filter chain than the ExceptionFilter, so at the time when the exception filter is handling an exception no RewritingResponse is on the chain of wrapped responses. Norman RIchards suggested to split incoming and outgoing rewriting and place it at opposite ends of the filter chain. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 7 02:36:03 2009 From: jira-events at lists.jboss.org (Takayoshi Kimura (JIRA)) Date: Wed, 7 Jan 2009 02:36:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3884) Seam file upload 100% CPU in MultipartRequest Message-ID: <31626436.1231313763963.JavaMail.jira@cloud.prod.atl2.jboss.com> Seam file upload 100% CPU in MultipartRequest --------------------------------------------- Key: JBSEAM-3884 URL: https://jira.jboss.org/jira/browse/JBSEAM-3884 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Environment: JBoss EAP 4.3.0.GA (no CP) Java VM: Java HotSpot(TM) Server VM 1.5.0_13-b05,Sun Microsystems Inc. OS-System: Linux 2.6.9-67.EL,i386 and JBoss EAP 4.2.0.GA (no CP) Java VM: Java HotSpot(TM) 64-Bit Server VM 1.5.0_12-b04,Sun Microsystems Inc. OS-System: Linux 2.6.9-34.ELsmp,amd64 Reporter: Takayoshi Kimura Sometimes org.jboss.seam.web.MultipartRequest#parseRequest() goes into an endless loop and takes 100% CPU when uploading a large file. The root cause is most likely due to the HttpServletRequest#getInputStream()#read() always returns 0. The API docs for InputStream state: "If the first byte cannot be read for any reason other than end of file, then an |IOException| is thrown. In particular, an |IOException| is thrown if the input stream has been closed." It's similar problem to RF-3746: https://jira.jboss.org/jira/browse/RF-3746 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 7 02:39:03 2009 From: jira-events at lists.jboss.org (Takayoshi Kimura (JIRA)) Date: Wed, 7 Jan 2009 02:39:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3884) Seam file upload 100% CPU in MultipartRequest In-Reply-To: <31626436.1231313763963.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <17897912.1231313943988.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takayoshi Kimura closed JBSEAM-3884. ------------------------------------ Fix Version/s: 2.1.2.CR1 Resolution: Done Assignee: Takayoshi Kimura Committed fix revision 9807: http://fisheye.jboss.org/changelog/Seam/?cs=9807 > Seam file upload 100% CPU in MultipartRequest > --------------------------------------------- > > Key: JBSEAM-3884 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3884 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.1.GA > Environment: JBoss EAP 4.3.0.GA (no CP) > Java VM: Java HotSpot(TM) Server VM 1.5.0_13-b05,Sun Microsystems Inc. > OS-System: Linux 2.6.9-67.EL,i386 > and > JBoss EAP 4.2.0.GA (no CP) > Java VM: Java HotSpot(TM) 64-Bit Server VM 1.5.0_12-b04,Sun Microsystems Inc. > OS-System: Linux 2.6.9-34.ELsmp,amd64 > Reporter: Takayoshi Kimura > Assignee: Takayoshi Kimura > Fix For: 2.1.2.CR1 > > > Sometimes org.jboss.seam.web.MultipartRequest#parseRequest() goes into an endless loop and takes 100% CPU when uploading a large file. The root cause is most likely due to the HttpServletRequest#getInputStream()#read() always returns 0. > The API docs for InputStream state: > "If the first byte cannot be read for any reason other than end of file, > then an |IOException| is thrown. In particular, an |IOException| is > thrown if the input stream has been closed." > It's similar problem to RF-3746: https://jira.jboss.org/jira/browse/RF-3746 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 7 06:26:03 2009 From: jira-events at lists.jboss.org (Pete Muir (JIRA)) Date: Wed, 7 Jan 2009 06:26:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3881) Typo in XML in Getting_Started_With_JBoss_Tools.xml In-Reply-To: <16912616.1231286463963.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <6903834.1231327563985.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated JBSEAM-3881: ------------------------------ Fix Version/s: 2.1.2.CR1 > Typo in XML in Getting_Started_With_JBoss_Tools.xml > --------------------------------------------------- > > Key: JBSEAM-3881 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3881 > Project: Seam > Issue Type: Patch > Components: Documentation Issues > Affects Versions: 2.1.1.GA > Environment: N/A > Reporter: Ian Darwin > Fix For: 2.1.2.CR1 > > Attachments: seamref.diff > > > Typo in XML element. Patch attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 7 08:06:04 2009 From: jira-events at lists.jboss.org (Nobuyuki Inaba (JIRA)) Date: Wed, 7 Jan 2009 08:06:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2791) Support CJK in a chart. In-Reply-To: <10110540.1206721960161.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <6998689.1231333564060.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12445193#action_12445193 ] Nobuyuki Inaba commented on JBSEAM-2791: ---------------------------------------- > Can I include your chart in the iText example for others to use? My example is very little and cheap, so I don't hope things that my example included iText example. sorry. > Support CJK in a chart. > ----------------------- > > Key: JBSEAM-2791 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2791 > Project: Seam > Issue Type: Feature Request > Components: PDF > Affects Versions: 2.1.0.A1 > Environment: ubuntu linux 7.10 > jdk1.5.0_14 > jboss seam 2.1.0A > Reporter: Nobuyuki Inaba > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > Attachments: chart.patch, cjkChart.xhtml, screenshot( not apply patch version).jpg, screenshot(apply patch version).jpg > > > Hi, > Seam 2.1.0A does not support CJK character in a chart( in a PDF file). > because, UIChart class use DefaultFontMapper class. > I think UIChart class should use settings. > I attached the patch against this issue to this ticket.Please check the patch. > When apply the patch to Seam, Seam can support CJK chacter in a chart. > and In a chart, developer have to appoint the following to use CJK. > 1. Appoint the 'locale' in . e.g. . Now, 'ja' has not mean. but I think that this is necessary when Seam supports other multi-byte languages. > 2. Setting of . already fixed in JBSEAM-1039. > best regards, > Nobuyuki Inaba -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 7 09:18:05 2009 From: jira-events at lists.jboss.org (Joshua Davis (JIRA)) Date: Wed, 7 Jan 2009 09:18:05 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3225) Seam Remoting JS memory leak in IE In-Reply-To: <3019211.1218026234255.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <16820525.1231337886025.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12445228#action_12445228 ] Joshua Davis commented on JBSEAM-3225: -------------------------------------- jscript.dll File Version: 5.7.0.18066 > Seam Remoting JS memory leak in IE > ---------------------------------- > > Key: JBSEAM-3225 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3225 > Project: Seam > Issue Type: Bug > Components: Remoting > Affects Versions: 2.0.1.GA, 2.0.2.GA > Environment: IE 6 > Reporter: Joshua Davis > Assignee: Shane Bryzak > Attachments: fix_IE_memory_leak.patch, ie6leak-example.zip > > > Issuing many Seam Remoting calls can cause IE6 to fail with an 'out of memory' error. The problem seems to be related to the fact that the AJAX request object is a COM object in IE, so it doesn't get garbage collected in the same way. On a P3 machine with 512M of RAM, IE6 can handle about 30k calls before failing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 7 10:06:05 2009 From: jira-events at lists.jboss.org (Ian Darwin (JIRA)) Date: Wed, 7 Jan 2009 10:06:05 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1896) Documentation for pages.xml In-Reply-To: <2924519.1188839003974.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <675144.1231340765235.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12445239#action_12445239 ] Ian Darwin commented on JBSEAM-1896: ------------------------------------ Dan: Could you please document the interactions of having multiple elements where one is a wildcard and the other(s) not, for things like login-required? E.g., I'd LIKE to be able to do: That is, I'd like to provide an "industry-standard" :-) secure-by-default security stance with clearly defined exceptions... If this is NOT possible at present please document that fact (and I'll open a Feature Request). If it IS possible please give an example. Thanks!! > Documentation for pages.xml > --------------------------- > > Key: JBSEAM-1896 > URL: https://jira.jboss.org/jira/browse/JBSEAM-1896 > Project: Seam > Issue Type: Task > Components: Documentation Issues > Reporter: Pete Muir > Assignee: Dan Allen > Priority: Blocker > Fix For: 2.1.2.CR1 > > > Documentation for pages.xml is missing in places (e.g no mention of begin-conversation element). > Also, it's still (including navigation!) under the heading Events -> Page Actions which is odd. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 7 10:25:03 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Wed, 7 Jan 2009 10:25:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2791) Support CJK in a chart. In-Reply-To: <10110540.1206721960161.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <31265820.1231341905814.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12445242#action_12445242 ] Norman Richards commented on JBSEAM-2791: ----------------------------------------- Ok. Thanks. I can create a chinese example, but I don't know enough japanese to create an interesting example with japanese text. It would be really nice if we could have a japanese example too. > Support CJK in a chart. > ----------------------- > > Key: JBSEAM-2791 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2791 > Project: Seam > Issue Type: Feature Request > Components: PDF > Affects Versions: 2.1.0.A1 > Environment: ubuntu linux 7.10 > jdk1.5.0_14 > jboss seam 2.1.0A > Reporter: Nobuyuki Inaba > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > Attachments: chart.patch, cjkChart.xhtml, screenshot( not apply patch version).jpg, screenshot(apply patch version).jpg > > > Hi, > Seam 2.1.0A does not support CJK character in a chart( in a PDF file). > because, UIChart class use DefaultFontMapper class. > I think UIChart class should use settings. > I attached the patch against this issue to this ticket.Please check the patch. > When apply the patch to Seam, Seam can support CJK chacter in a chart. > and In a chart, developer have to appoint the following to use CJK. > 1. Appoint the 'locale' in . e.g. . Now, 'ja' has not mean. but I think that this is necessary when Seam supports other multi-byte languages. > 2. Setting of . already fixed in JBSEAM-1039. > best regards, > Nobuyuki Inaba -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 7 12:04:04 2009 From: jira-events at lists.jboss.org (Jason Long (JIRA)) Date: Wed, 7 Jan 2009 12:04:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3555) SeamMailAgain In-Reply-To: <3978595.1223977760796.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <32572230.1231347844269.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12445565#action_12445565 ] Jason Long commented on JBSEAM-3555: ------------------------------------ I have seen this bumped and reopened a few times. Is this firmly scheduled 2.1.2 or is there a chance of further slippage? > SeamMailAgain > ------------- > > Key: JBSEAM-3555 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3555 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.0.CR1 > Environment: JBoss AS 4.2.1.GA > JBoss Seam 2.1.0-SNAPSHOT (10.10. HudsonNo330) > Reporter: Markus Heidt > Assignee: Pete Muir > Fix For: 2.1.2.CR1 > > Attachments: server.log > > > Simple Mailing via Renderer doesn't work. > 'Seam-gen'erated a new project and added a new action 'sendMail' > Added the line to the action code: > Renderer.instance().render("/simple.xhtml"); > simple.xhtml is a modified version of the seam example (without #{person}) > Error after executing the action: > 2008-10-14 11:40:21,847 FATAL [javax.enterprise.resource.webcontainer.jsf.application] org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > javax.faces.el.EvaluationException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:91) > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:91) > ... > Caused by: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory > at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:256) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 7 12:12:14 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Wed, 7 Jan 2009 12:12:14 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3786) Nullcheck too late in SpringTaskExecutorDispatcher.scheduleDispatcher In-Reply-To: <14561818.1228439737054.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <32072412.1231348334313.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3786. ----------------------------------- Resolution: Done Thanks. > Nullcheck too late in SpringTaskExecutorDispatcher.scheduleDispatcher > ---------------------------------------------------------------------- > > Key: JBSEAM-3786 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3786 > Project: Seam > Issue Type: Bug > Reporter: Francisco Jose Peredo Noguez > Assignee: Norman Richards > Priority: Trivial > Fix For: 2.1.2.CR1 > > Attachments: patch.txt > > > Nullcheck of SpringTaskExecutorDispatcher.scheduleDispatcher at line 64 of value previously dereferenced in org.jboss.seam.ioc.spring.SpringTaskExecutorDispatcher.getScheduleDispatcher() -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 7 12:42:03 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Wed, 7 Jan 2009 12:42:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3785) Nullcheck too late in UIChartSeries.encodeEnd In-Reply-To: <12692257.1228439631560.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <21099743.1231350124048.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3785. ----------------------------------- Resolution: Done Done. Thanks! > Nullcheck too late in UIChartSeries.encodeEnd > --------------------------------------------- > > Key: JBSEAM-3785 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3785 > Project: Seam > Issue Type: Bug > Reporter: Francisco Jose Peredo Noguez > Assignee: Norman Richards > Priority: Minor > Fix For: 2.1.2.CR1 > > Attachments: patch.txt > > > Nullcheck of chart at line 144 of value previously dereferenced in org.jboss.seam.pdf.ui.UIChartSeries.encodeEnd(FacesContext) jboss-seam/src -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 7 12:56:14 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Wed, 7 Jan 2009 12:56:14 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3000) Conversation leak with UIChart In-Reply-To: <6073065.1210846042995.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <11151301.1231350974400.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3000. ----------------------------------- Resolution: Done Thanks. I think you are right. That is a holdover from from when we were using the documentstore in the conversation and needed to force the conversation to stay valid until the next request. > Conversation leak with UIChart > ------------------------------ > > Key: JBSEAM-3000 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3000 > Project: Seam > Issue Type: Bug > Components: JSF Controls > Affects Versions: 2.0.1.CR2 > Environment: NA > Reporter: Tom Goring > Assignee: Norman Richards > Priority: Minor > Fix For: 2.1.2.CR1 > > > Added a chart on a page generates a long running conversation due to a bug in UIChart: > UIChart > public void encodeEnd(FacesContext context) > .. > Manager.instance().beforeRedirect(); > beforeRedirect is creating a redirect conversation.. however I don't see why it needs todo this. The chart is rendered to the graphic store and then is pulled out when requiested from the browser. > I think Manager.instance().beforeRedirect(); should be deleted ... but I'm not sure. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 7 13:35:03 2009 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ond=3Fej_=C5=BDi=C5=BEka_=28JIRA=29?=) Date: Wed, 7 Jan 2009 13:35:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3845) NullPointerException in org.jboss.seam.exception.Exceptions.parse In-Reply-To: <19616339.1229350549866.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <1524239.1231353304161.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12445579#action_12445579 ] Ond?ej ?i?ka commented on JBSEAM-3845: -------------------------------------- Unfortunatelly not, the test changed a lot since Dec 23rd... Probably, it was really some mis-configured input, but generally, undocumented NPEs souldn't be thrown through the public API, and IIRC, this NPE was not not documented in the method of origin. > NullPointerException in org.jboss.seam.exception.Exceptions.parse > ----------------------------------------------------------------- > > Key: JBSEAM-3845 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3845 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.0.SP1 > Environment: JBoss EAP 4.3.0 default, JSFUnit, run using Cactus ServletTestRunner > Reporter: Ond?ej ?i?ka > Fix For: 2.1.2.CR1 > > Attachments: SeamNPE.txt > > > Seam throws a NPE when I run a JSFUnit test case. The test may be fault, but at least the NPE should be handled. > Full stack trace: > ------------------------------------------------------- > 15:11:11,933 ERROR [BaseXMLFilter] Exception in the filter chain > javax.servlet.ServletException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions > at org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:126) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) > at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) > at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) > at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) > at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:595) > Caused by: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions > at org.jboss.seam.Component.newInstance(Component.java:2096) > at org.jboss.seam.Component.getInstance(Component.java:1978) > at org.jboss.seam.Component.getInstance(Component.java:1957) > at org.jboss.seam.Component.getInstance(Component.java:1951) > at org.jboss.seam.Component.getInstance(Component.java:1924) > at org.jboss.seam.Component.getInstance(Component.java:1919) > at org.jboss.seam.exception.Exceptions.instance(Exceptions.java:256) > at org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114) > ... 31 more > Caused by: java.lang.NullPointerException > at org.jboss.seam.exception.Exceptions.parse(Exceptions.java:195) > at org.jboss.seam.exception.Exceptions.initialize(Exceptions.java:119) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) > at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:138) > at org.jboss.seam.Component.callComponentMethod(Component.java:2201) > at org.jboss.seam.Component.callCreateMethod(Component.java:2124) > at org.jboss.seam.Component.newInstance(Component.java:2084) > ... 38 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 7 13:45:04 2009 From: jira-events at lists.jboss.org (Cristian Fabiano (JIRA)) Date: Wed, 7 Jan 2009 13:45:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3673) horizontalAlignment="right" broken in PDF cells (regression) In-Reply-To: <29246884.1225868480972.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <31825203.1231353904285.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12445580#action_12445580 ] Cristian Fabiano commented on JBSEAM-3673: ------------------------------------------ but when cell is inside a ui:repeat, it broken anyway: cell
> horizontalAlignment="right" broken in PDF cells (regression) > ------------------------------------------------------------ > > Key: JBSEAM-3673 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3673 > Project: Seam > Issue Type: Bug > Components: PDF > Affects Versions: 2.1.0.SP1 > Reporter: Dan Allen > Assignee: Norman Richards > Fix For: 2.1.1.CR1 > > > All of a sudden the horizontal alignment on PDF cells stopped working in Seam 2.1. You can see the discrepancy by deploying the iText example in Seam 2.0 and Seam 2.1 and observing the servlet path /seam-itext/format.seam. You'll notice that the Order Summary table is formatted differently in the two cases, with the right-hand alignment not taking affect under Seam 2.1. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 7 14:03:04 2009 From: jira-events at lists.jboss.org (Klaasjan te Voortwis (JIRA)) Date: Wed, 7 Jan 2009 14:03:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3885) Make CookiePath for RememberMe cookies optionally fixed Message-ID: <8637402.1231354984046.JavaMail.jira@cloud.prod.atl2.jboss.com> Make CookiePath for RememberMe cookies optionally fixed ------------------------------------------------------- Key: JBSEAM-3885 URL: https://jira.jboss.org/jira/browse/JBSEAM-3885 Project: Seam Issue Type: Feature Request Components: Security Affects Versions: 2.1.1.GA Reporter: Klaasjan te Voortwis The RememberMe cookies are stored on the same path as where the page was served from. When providing a user/pass field in the top of all pages, a user can for example - log in on http://domain.name/issuesystem/issue/create.seam, and mark RememberMe true - come back to the site http://domain.name/someotherpath, and now the user is not logged in (optionally) fixing the CookiePath for the RememberMe cookies to "/" instead of ctx.getExternalContext().getRequestContextPath() will solve this issue. Setting the cookiePath is done in RememberMe.java on lines 221 and 238. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 7 14:37:04 2009 From: jira-events at lists.jboss.org (Tony Herstell (JIRA)) Date: Wed, 7 Jan 2009 14:37:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3555) SeamMailAgain In-Reply-To: <3978595.1223977760796.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <23318793.1231357024065.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12445587#action_12445587 ] Tony Herstell commented on JBSEAM-3555: --------------------------------------- Please add to sema mail bucket problems: http://www.seamframework.org/Community/SeamMailProblemNPE#comment58020 > SeamMailAgain > ------------- > > Key: JBSEAM-3555 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3555 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.0.CR1 > Environment: JBoss AS 4.2.1.GA > JBoss Seam 2.1.0-SNAPSHOT (10.10. HudsonNo330) > Reporter: Markus Heidt > Assignee: Pete Muir > Fix For: 2.1.2.CR1 > > Attachments: server.log > > > Simple Mailing via Renderer doesn't work. > 'Seam-gen'erated a new project and added a new action 'sendMail' > Added the line to the action code: > Renderer.instance().render("/simple.xhtml"); > simple.xhtml is a modified version of the seam example (without #{person}) > Error after executing the action: > 2008-10-14 11:40:21,847 FATAL [javax.enterprise.resource.webcontainer.jsf.application] org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > javax.faces.el.EvaluationException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:91) > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:91) > ... > Caused by: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory > at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:256) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 7 15:12:03 2009 From: jira-events at lists.jboss.org (Denis Forveille (JIRA)) Date: Wed, 7 Jan 2009 15:12:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3886) Document the usage of to disable identity managment Message-ID: <4633773.1231359124040.JavaMail.jira@cloud.prod.atl2.jboss.com> Document the usage of to disable identity managment ----------------------------------------------------------------------------------------- Key: JBSEAM-3886 URL: https://jira.jboss.org/jira/browse/JBSEAM-3886 Project: Seam Issue Type: Bug Components: Documentation Issues Affects Versions: 2.1.1.GA Reporter: Denis Forveille Priority: Minor Document the usage of to disable identity managment in seam v2.1 as stated in jira JBSEAM-3629 Maybe this should be included in section 15.2 (Security/Disabling security) ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 7 17:08:05 2009 From: jira-events at lists.jboss.org (Clint Popetz (JIRA)) Date: Wed, 7 Jan 2009 17:08:05 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3887) Allow configuration of seam components from System properties Message-ID: <10608378.1231366085885.JavaMail.jira@cloud.prod.atl2.jboss.com> Allow configuration of seam components from System properties ------------------------------------------------------------- Key: JBSEAM-3887 URL: https://jira.jboss.org/jira/browse/JBSEAM-3887 Project: Seam Issue Type: Patch Components: Core Reporter: Clint Popetz Assignee: Clint Popetz Priority: Minor Attachments: Initialization.java.patch It is often required to push a single deployment to multiple types of servers (different testing servers, mirrors, backups, etc.), and so it would be nice to be able to configure seam components with -D on startup of the container. The attached patch looks for system properties with names like "org.jboss.seam.properties.NAME" for component NAME and treats them just like NAME=value in seam.properties. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 7 17:08:06 2009 From: jira-events at lists.jboss.org (Clint Popetz (JIRA)) Date: Wed, 7 Jan 2009 17:08:06 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3887) Allow configuration of seam components from System properties In-Reply-To: <10608378.1231366085885.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <1796020.1231366086046.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clint Popetz updated JBSEAM-3887: --------------------------------- Attachment: Initialization.java.patch > Allow configuration of seam components from System properties > ------------------------------------------------------------- > > Key: JBSEAM-3887 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3887 > Project: Seam > Issue Type: Patch > Components: Core > Reporter: Clint Popetz > Assignee: Clint Popetz > Priority: Minor > Attachments: Initialization.java.patch > > > It is often required to push a single deployment to multiple types of servers (different testing servers, mirrors, backups, etc.), and so it would be nice to be able to configure seam components with -D on startup of the container. The attached patch looks for system properties with names like "org.jboss.seam.properties.NAME" for component NAME and treats them just like NAME=value in seam.properties. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 8 06:19:04 2009 From: jira-events at lists.jboss.org (Pete Muir (JIRA)) Date: Thu, 8 Jan 2009 06:19:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3887) Allow configuration of seam components from System properties In-Reply-To: <10608378.1231366085885.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <23460264.1231413544065.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12445824#action_12445824 ] Pete Muir commented on JBSEAM-3887: ----------------------------------- Nice one, please apply, though perhaps initPropertiesFromProperties should be initPropertiesFromFile? > Allow configuration of seam components from System properties > ------------------------------------------------------------- > > Key: JBSEAM-3887 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3887 > Project: Seam > Issue Type: Patch > Components: Core > Reporter: Clint Popetz > Assignee: Clint Popetz > Priority: Minor > Attachments: Initialization.java.patch > > > It is often required to push a single deployment to multiple types of servers (different testing servers, mirrors, backups, etc.), and so it would be nice to be able to configure seam components with -D on startup of the container. The attached patch looks for system properties with names like "org.jboss.seam.properties.NAME" for component NAME and treats them just like NAME=value in seam.properties. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 8 09:12:04 2009 From: jira-events at lists.jboss.org (Clint Popetz (JIRA)) Date: Thu, 8 Jan 2009 09:12:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3887) Allow configuration of seam components from System properties In-Reply-To: <10608378.1231366085885.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <17606012.1231423924895.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clint Popetz closed JBSEAM-3887. -------------------------------- Fix Version/s: 2.1.2.CR1 Resolution: Done I changed it to initPropertiesFromMap(), and committed r9893. Thanks Pete. > Allow configuration of seam components from System properties > ------------------------------------------------------------- > > Key: JBSEAM-3887 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3887 > Project: Seam > Issue Type: Patch > Components: Core > Reporter: Clint Popetz > Assignee: Clint Popetz > Priority: Minor > Fix For: 2.1.2.CR1 > > Attachments: Initialization.java.patch > > > It is often required to push a single deployment to multiple types of servers (different testing servers, mirrors, backups, etc.), and so it would be nice to be able to configure seam components with -D on startup of the container. The attached patch looks for system properties with names like "org.jboss.seam.properties.NAME" for component NAME and treats them just like NAME=value in seam.properties. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 8 10:11:04 2009 From: jira-events at lists.jboss.org (Julien Kronegg (JIRA)) Date: Thu, 8 Jan 2009 10:11:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3821) seam-gen - entity is not mapped in war project on AS5 In-Reply-To: <9544242.1228754556504.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <7212145.1231427464054.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12445876#action_12445876 ] Julien Kronegg commented on JBSEAM-3821: ---------------------------------------- I had the same issue. The server startup sequence is the following: 15:33:23,440 INFO [ServerImpl] Starting JBoss (Microcontainer)... 15:33:23,440 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.GA (build: SVNTag=JBoss_5_0_0_GA date=200812042120) ... 15:35:07,612 INFO [PersistenceUnitDeployment] Starting persistence unit persistence.unit:unitName=#testSeamProject2 15:35:07,706 INFO [Version] Hibernate Annotations 3.4.0.GA 15:35:07,721 INFO [Environment] Hibernate 3.3.1.GA 15:35:08,034 INFO [Environment] hibernate.properties not found 15:35:08,050 INFO [Environment] Bytecode provider name : javassist 15:35:08,050 INFO [Environment] using JDK 1.4 java.sql.Timestamp handling 15:35:08,206 INFO [Version] Hibernate Commons Annotations 3.1.0.GA 15:35:08,206 INFO [Version] Hibernate EntityManager 3.4.0.GA 15:35:08,378 WARN [Ejb3Configuration] Persistence provider caller does not implement the EJB3 spec correctly. PersistenceUnitInfo.getNewTempClassLoader() is null. 15:35:09,487 INFO [AnnotationBinder] Binding entity from annotated class: org.domain.testseamproject2.entity.SqlColumn 15:35:09,581 INFO [EntityBinder] Bind entity org.domain.testseamproject2.entity.SqlColumn on table SQL_COLUMN ... (other entities are discovered or the like) 15:35:15,487 INFO [Version] Hibernate Validator 3.1.0.GA 15:35:15,628 INFO [HibernateSearchEventListenerRegister] Unable to find org.hibernate.search.event.FullTextIndexEventListener on the classpath. Hibernate Search is not enabled. 15:35:16,018 INFO [ConnectionProviderFactory] Initializing connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider 15:35:16,034 INFO [InjectedDataSourceConnectionProvider] Using provided datasource 15:35:17,143 INFO [SettingsFactory] RDBMS: Microsoft SQL Server, version: 9.00.3042 15:35:17,143 INFO [SettingsFactory] JDBC driver: Microsoft SQL Server 2005 JDBC Driver, version: 1.2.2828.100 15:35:17,175 INFO [Dialect] Using dialect: org.hibernate.dialect.SQLServerDialect 15:35:17,190 INFO [TransactionFactoryFactory] Transaction strategy: org.hibernate.ejb.transaction.JoinableCMTTransactionFactory 15:35:17,206 INFO [TransactionManagerLookupFactory] instantiating TransactionManagerLookup: org.hibernate.transaction.JBossTransactionManagerLookup ... 15:35:29,565 INFO [ServletContextListener] Welcome to Seam 2.1.1.GA ... 15:35:51,800 INFO [Initialization] Installing components... ... 15:36:36,175 INFO [Contexts] starting up: org.jboss.seam.security.persistentPermissionResolver 15:36:36,175 WARN [PersistentPermissionResolver] no permission store available - please install a PermissionStore with the name 'org.jboss.seam.security.jpaPermissionStore' if persistent permissions are required. 15:36:36,175 INFO [Contexts] starting up: org.jboss.seam.security.permissionMapper 15:36:36,175 INFO [Contexts] starting up: org.jboss.seam.navigation.pages 15:36:36,659 INFO [Contexts] starting up: testSeamProject2EntityManagerFactory ... (here, the entity manager is supposed to bind the entities, which is not the case. Thus, the first query raises a QuerySyntaxException because the entity is not mapped) We found the following workaround: in the persistence.xml, we added a tag for each entity, so the that when the testSeamProject2EntityManagerFactory is started up, all entities are loaded. The persistence.xml now looks like: org.hibernate.ejb.HibernatePersistence java:/testSeamProject2Datasource org.domain.testseamproject2.entity.MyEntityClass1 org.domain.testseamproject2.entity.MyEntityClass2 org.domain.testseamproject2.entity.MyEntityClass3 At that point, we suppose that there is a loading problem, possibly involving the seam.properties (which must be present in the root directory of a jar so that the jar is inspected for entities) and/or hot deployment. > seam-gen - entity is not mapped in war project on AS5 > ----------------------------------------------------- > > Key: JBSEAM-3821 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3821 > Project: Seam > Issue Type: Bug > Components: Tools > Affects Versions: 2.1.1.CR2 > Environment: JDK5 > JBoss AS 5.0.0.GA > Reporter: Jozef Hartinger > Fix For: 2.1.2.CR1 > > Attachments: genWarRich.txt > > > When accessing generated entity page the application is failing on "org.hibernate.hql.ast.QuerySyntaxException: Vehicle is not mapped [select vehicle from Vehicle vehicle]" . I am using standard release-process.txt database tables. To reproduce the issue: > 1.) Create new war project and generate entities. > 2.) Log into the application and click PersonList or VehicleList -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 8 10:17:03 2009 From: jira-events at lists.jboss.org (Julien Kronegg (JIRA)) Date: Thu, 8 Jan 2009 10:17:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3821) seam-gen - entity is not mapped in war project on AS5 In-Reply-To: <9544242.1228754556504.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <24225899.1231427823995.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12445879#action_12445879 ] Julien Kronegg commented on JBSEAM-3821: ---------------------------------------- I forgot to mention: we use Seam 2.1.1.GA, eclipse-jee-ganymede-SR1-win32, JBossTools-3.0.0.CR1-R200812191611-ALL-win32, jboss-5.0.0.GA-jdk6, jdk-6u11-windows-i586-p > seam-gen - entity is not mapped in war project on AS5 > ----------------------------------------------------- > > Key: JBSEAM-3821 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3821 > Project: Seam > Issue Type: Bug > Components: Tools > Affects Versions: 2.1.1.CR2 > Environment: JDK5 > JBoss AS 5.0.0.GA > Reporter: Jozef Hartinger > Fix For: 2.1.2.CR1 > > Attachments: genWarRich.txt > > > When accessing generated entity page the application is failing on "org.hibernate.hql.ast.QuerySyntaxException: Vehicle is not mapped [select vehicle from Vehicle vehicle]" . I am using standard release-process.txt database tables. To reproduce the issue: > 1.) Create new war project and generate entities. > 2.) Log into the application and click PersonList or VehicleList -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 8 10:46:06 2009 From: jira-events at lists.jboss.org (Clint Popetz (JIRA)) Date: Thu, 8 Jan 2009 10:46:06 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3645) Support co-existence of multiple view layers in same deployment In-Reply-To: <8315714.1225285820908.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <21252116.1231429567064.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clint Popetz updated JBSEAM-3645: --------------------------------- Attachment: Instantiator.java This newest version of Instantiator marks the ImplementationSelectionDelegate as Serializable (and adds a serialVersionUID), because an instance of this is held by StatusMessages and the like, and therefore may need to be serialized in clusters. > Support co-existence of multiple view layers in same deployment > --------------------------------------------------------------- > > Key: JBSEAM-3645 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3645 > Project: Seam > Issue Type: Patch > Reporter: Clint Popetz > Assignee: Clint Popetz > Attachments: Instantiator.java, Instantiator.java, multi-view-take-2.patch, multi-view-take-3.patch, multi-view.diff > > > Currently one must choose between wicket and jsf when using seam, because the wicket support works by overriding certain faces components. This patch eliminates that limitation. > This patch should be applied after the patches from the issues linked to this issue, which are also related to wicket development. There are four parts of this patch. > (1) The Manager and StatusMessages components are currently implemented in jsf with FacesManager and FacesMessages, and in wicket with WicketManager and WicketStatusMessages. Since a mixed deployment would need all managers to be @Installed, this patch makes each have a separate @Name, and makes the base classes (Manager and StatusMessages) @Unwrap themselves as one of the subclass components. Each subclass component registers itself with the base class component (by observing the postInitialization event) as a possible implementation. When Manager.instance() or StatusMessages.instance() is invoked, and the base component is created, @Unwrap is called, and that method asks each subclass component whether they should be used for that event scope. The Wicket implementations say yes if the wicket Application.exists() (which uses a ThreadLocal) returns true. The Faces implementations says yes if facesContext is not null. This patch assumes that both will not simultaneously return true, and if so, the behavior is undefined, as it's first-come-first-serve. If neither return true, the default Manager and StatusMessages implementation will be used. This happens during initialization and other edge cases where a manager is needed for event contexts that aren't tied to real requests. Note that since the FacesMessages component no longer has the same @Name as the StatusMessages component, it is now "org.jboss.seam.faces.facesMessages" which means the two factories for that name and its unqualified form in jboss-seam.jar's components.xml have been removed. > (2) Seam's WicketFilter currently sets up scopes unconditionally if it is installed. This causes faces requests to fail because the SeamPhaseListener also sets up and tears down scopes, and so when the wicket filter finishes and tries to tear down its scopes, it finds them gone and an exception occurs. I've changed WicketFilter to not set up scopes, but instead to have WicketFilterInstantiator's anonymous subclass of the real WicketFilter install the scopes _if_ wicket has determined the request is a wicket request. > (3) WicketExceptionFilter existed only to turn off the base ExceptionFilter for wicket classes. I've removed this class, and we'll need to add to the wicket seam documentation the need to map the ExceptionFilter in components.xml to jsf paths if wicket is to be used alongside jsf. > (4) WicketRedirectFilter now co-exists with the base RedirectFilter, rather than replacing it. It checks to see if Wicket is active (via the same Application.exists() call as above) before doing any work to redirects, so that it doesn't duplicate work that the jsf RedirectFilter does. Likewise, The jsf RedirectFilter now checks to see if there is a faces context before doing any work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 8 11:34:03 2009 From: jira-events at lists.jboss.org (Clint Popetz (JIRA)) Date: Thu, 8 Jan 2009 11:34:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3880) Wicket interception doesn't throw error on missing required injections In-Reply-To: <12660077.1231255084052.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <21733479.1231432443998.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clint Popetz updated JBSEAM-3880: --------------------------------- Attachment: WicketComponent.java.patch This fixes it, and brings WicketComponent.inject() more in line with the core Component.inject(). > Wicket interception doesn't throw error on missing required injections > ----------------------------------------------------------------------- > > Key: JBSEAM-3880 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3880 > Project: Seam > Issue Type: Bug > Reporter: Clint Popetz > Assignee: Clint Popetz > Attachments: WicketComponent.java.patch > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 8 12:54:04 2009 From: jira-events at lists.jboss.org (Simon Gibbs (JIRA)) Date: Thu, 8 Jan 2009 12:54:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3424) Support Hibernate in IdentityManager In-Reply-To: <1922351.1221586100892.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <24156989.1231437244178.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12446216#action_12446216 ] Simon Gibbs commented on JBSEAM-3424: ------------------------------------- I need to use Hibernate directly, but would like to avoid writing my own identity store to read identity from the database - so it seems as though I need to work around this issue until its fixed. Are there any work arounds available yet? > Support Hibernate in IdentityManager > ------------------------------------ > > Key: JBSEAM-3424 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3424 > Project: Seam > Issue Type: Feature Request > Affects Versions: 2.1.0.BETA1 > Reporter: Scott Olcott > Assignee: Shane Bryzak > Attachments: seamspaceChanges.txt, securityChanges.txt, securityXsdChanges.txt > > > The JpaIdentityStore could easily work with hibernate also. If you abstracted out the EntityManager and the hiberate Session from the JpaIdentityStore kind of like the AbstractEntityLoader does for the EntityConverter, you could continue to use the JpaIdentityStore for both JPA and Hibernate. Although you would probably want to rename JpaIdentityStore -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 8 14:31:04 2009 From: jira-events at lists.jboss.org (Daniel Roth (JIRA)) Date: Thu, 8 Jan 2009 14:31:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-3881) Typo in XML in Getting_Started_With_JBoss_Tools.xml In-Reply-To: <16912616.1231286463963.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <20513897.1231443064057.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roth reassigned JBSEAM-3881: ----------------------------------- Assignee: Daniel Roth > Typo in XML in Getting_Started_With_JBoss_Tools.xml > --------------------------------------------------- > > Key: JBSEAM-3881 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3881 > Project: Seam > Issue Type: Patch > Components: Documentation Issues > Affects Versions: 2.1.1.GA > Environment: N/A > Reporter: Ian Darwin > Assignee: Daniel Roth > Fix For: 2.1.2.CR1 > > Attachments: seamref.diff > > > Typo in XML element. Patch attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 8 14:31:04 2009 From: jira-events at lists.jboss.org (Daniel Roth (JIRA)) Date: Thu, 8 Jan 2009 14:31:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3881) Typo in XML in Getting_Started_With_JBoss_Tools.xml In-Reply-To: <16912616.1231286463963.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <10895863.1231443064542.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roth closed JBSEAM-3881. ------------------------------- Resolution: Done Fixed. Thanks Ian. > Typo in XML in Getting_Started_With_JBoss_Tools.xml > --------------------------------------------------- > > Key: JBSEAM-3881 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3881 > Project: Seam > Issue Type: Patch > Components: Documentation Issues > Affects Versions: 2.1.1.GA > Environment: N/A > Reporter: Ian Darwin > Assignee: Daniel Roth > Fix For: 2.1.2.CR1 > > Attachments: seamref.diff > > > Typo in XML element. Patch attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 8 14:37:04 2009 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ond=3Fej_=C5=BDi=C5=BEka_=28JIRA=29?=) Date: Thu, 8 Jan 2009 14:37:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3845) NullPointerException in org.jboss.seam.exception.Exceptions.parse In-Reply-To: <19616339.1229350549866.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <193384.1231443424015.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12446234#action_12446234 ] Ond?ej ?i?ka commented on JBSEAM-3845: -------------------------------------- I've found a condition upon which the Exception occurs: Current build of Embedded Jopr uses ServletRedirector internally from Maven cargo plugin. When used outside cargo (i.e. war is deployed to the server and then accessed at http://:8080/admin-console/ServletRedirector.jsfunit , this happens. > NullPointerException in org.jboss.seam.exception.Exceptions.parse > ----------------------------------------------------------------- > > Key: JBSEAM-3845 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3845 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.0.SP1 > Environment: JBoss EAP 4.3.0 default, JSFUnit, run using Cactus ServletTestRunner > Reporter: Ond?ej ?i?ka > Fix For: 2.1.2.CR1 > > Attachments: SeamNPE.txt > > > Seam throws a NPE when I run a JSFUnit test case. The test may be fault, but at least the NPE should be handled. > Full stack trace: > ------------------------------------------------------- > 15:11:11,933 ERROR [BaseXMLFilter] Exception in the filter chain > javax.servlet.ServletException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions > at org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:126) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) > at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) > at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) > at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) > at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:595) > Caused by: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions > at org.jboss.seam.Component.newInstance(Component.java:2096) > at org.jboss.seam.Component.getInstance(Component.java:1978) > at org.jboss.seam.Component.getInstance(Component.java:1957) > at org.jboss.seam.Component.getInstance(Component.java:1951) > at org.jboss.seam.Component.getInstance(Component.java:1924) > at org.jboss.seam.Component.getInstance(Component.java:1919) > at org.jboss.seam.exception.Exceptions.instance(Exceptions.java:256) > at org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114) > ... 31 more > Caused by: java.lang.NullPointerException > at org.jboss.seam.exception.Exceptions.parse(Exceptions.java:195) > at org.jboss.seam.exception.Exceptions.initialize(Exceptions.java:119) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) > at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:138) > at org.jboss.seam.Component.callComponentMethod(Component.java:2201) > at org.jboss.seam.Component.callCreateMethod(Component.java:2124) > at org.jboss.seam.Component.newInstance(Component.java:2084) > ... 38 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 8 19:21:03 2009 From: jira-events at lists.jboss.org (Vladimir Kovalyuk (JIRA)) Date: Thu, 8 Jan 2009 19:21:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3645) Support co-existence of multiple view layers in same deployment In-Reply-To: <8315714.1225285820908.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <12024447.1231460463989.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12446274#action_12446274 ] Vladimir Kovalyuk commented on JBSEAM-3645: ------------------------------------------- Clint, did you commit this in to the trunk? > Support co-existence of multiple view layers in same deployment > --------------------------------------------------------------- > > Key: JBSEAM-3645 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3645 > Project: Seam > Issue Type: Patch > Reporter: Clint Popetz > Assignee: Clint Popetz > Attachments: Instantiator.java, Instantiator.java, multi-view-take-2.patch, multi-view-take-3.patch, multi-view.diff > > > Currently one must choose between wicket and jsf when using seam, because the wicket support works by overriding certain faces components. This patch eliminates that limitation. > This patch should be applied after the patches from the issues linked to this issue, which are also related to wicket development. There are four parts of this patch. > (1) The Manager and StatusMessages components are currently implemented in jsf with FacesManager and FacesMessages, and in wicket with WicketManager and WicketStatusMessages. Since a mixed deployment would need all managers to be @Installed, this patch makes each have a separate @Name, and makes the base classes (Manager and StatusMessages) @Unwrap themselves as one of the subclass components. Each subclass component registers itself with the base class component (by observing the postInitialization event) as a possible implementation. When Manager.instance() or StatusMessages.instance() is invoked, and the base component is created, @Unwrap is called, and that method asks each subclass component whether they should be used for that event scope. The Wicket implementations say yes if the wicket Application.exists() (which uses a ThreadLocal) returns true. The Faces implementations says yes if facesContext is not null. This patch assumes that both will not simultaneously return true, and if so, the behavior is undefined, as it's first-come-first-serve. If neither return true, the default Manager and StatusMessages implementation will be used. This happens during initialization and other edge cases where a manager is needed for event contexts that aren't tied to real requests. Note that since the FacesMessages component no longer has the same @Name as the StatusMessages component, it is now "org.jboss.seam.faces.facesMessages" which means the two factories for that name and its unqualified form in jboss-seam.jar's components.xml have been removed. > (2) Seam's WicketFilter currently sets up scopes unconditionally if it is installed. This causes faces requests to fail because the SeamPhaseListener also sets up and tears down scopes, and so when the wicket filter finishes and tries to tear down its scopes, it finds them gone and an exception occurs. I've changed WicketFilter to not set up scopes, but instead to have WicketFilterInstantiator's anonymous subclass of the real WicketFilter install the scopes _if_ wicket has determined the request is a wicket request. > (3) WicketExceptionFilter existed only to turn off the base ExceptionFilter for wicket classes. I've removed this class, and we'll need to add to the wicket seam documentation the need to map the ExceptionFilter in components.xml to jsf paths if wicket is to be used alongside jsf. > (4) WicketRedirectFilter now co-exists with the base RedirectFilter, rather than replacing it. It checks to see if Wicket is active (via the same Application.exists() call as above) before doing any work to redirects, so that it doesn't duplicate work that the jsf RedirectFilter does. Likewise, The jsf RedirectFilter now checks to see if there is a faces context before doing any work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 8 19:42:05 2009 From: jira-events at lists.jboss.org (Clint Popetz (JIRA)) Date: Thu, 8 Jan 2009 19:42:05 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3645) Support co-existence of multiple view layers in same deployment In-Reply-To: <8315714.1225285820908.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <11537071.1231461725182.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12446277#action_12446277 ] Clint Popetz commented on JBSEAM-3645: -------------------------------------- >Clint, did you commit this in to the trunk? No, it's a patch that affects the core, and has ramifications for all view layers, so it's being reviewed by more senior Seam committers. > Support co-existence of multiple view layers in same deployment > --------------------------------------------------------------- > > Key: JBSEAM-3645 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3645 > Project: Seam > Issue Type: Patch > Reporter: Clint Popetz > Assignee: Clint Popetz > Attachments: Instantiator.java, Instantiator.java, multi-view-take-2.patch, multi-view-take-3.patch, multi-view.diff > > > Currently one must choose between wicket and jsf when using seam, because the wicket support works by overriding certain faces components. This patch eliminates that limitation. > This patch should be applied after the patches from the issues linked to this issue, which are also related to wicket development. There are four parts of this patch. > (1) The Manager and StatusMessages components are currently implemented in jsf with FacesManager and FacesMessages, and in wicket with WicketManager and WicketStatusMessages. Since a mixed deployment would need all managers to be @Installed, this patch makes each have a separate @Name, and makes the base classes (Manager and StatusMessages) @Unwrap themselves as one of the subclass components. Each subclass component registers itself with the base class component (by observing the postInitialization event) as a possible implementation. When Manager.instance() or StatusMessages.instance() is invoked, and the base component is created, @Unwrap is called, and that method asks each subclass component whether they should be used for that event scope. The Wicket implementations say yes if the wicket Application.exists() (which uses a ThreadLocal) returns true. The Faces implementations says yes if facesContext is not null. This patch assumes that both will not simultaneously return true, and if so, the behavior is undefined, as it's first-come-first-serve. If neither return true, the default Manager and StatusMessages implementation will be used. This happens during initialization and other edge cases where a manager is needed for event contexts that aren't tied to real requests. Note that since the FacesMessages component no longer has the same @Name as the StatusMessages component, it is now "org.jboss.seam.faces.facesMessages" which means the two factories for that name and its unqualified form in jboss-seam.jar's components.xml have been removed. > (2) Seam's WicketFilter currently sets up scopes unconditionally if it is installed. This causes faces requests to fail because the SeamPhaseListener also sets up and tears down scopes, and so when the wicket filter finishes and tries to tear down its scopes, it finds them gone and an exception occurs. I've changed WicketFilter to not set up scopes, but instead to have WicketFilterInstantiator's anonymous subclass of the real WicketFilter install the scopes _if_ wicket has determined the request is a wicket request. > (3) WicketExceptionFilter existed only to turn off the base ExceptionFilter for wicket classes. I've removed this class, and we'll need to add to the wicket seam documentation the need to map the ExceptionFilter in components.xml to jsf paths if wicket is to be used alongside jsf. > (4) WicketRedirectFilter now co-exists with the base RedirectFilter, rather than replacing it. It checks to see if Wicket is active (via the same Application.exists() call as above) before doing any work to redirects, so that it doesn't duplicate work that the jsf RedirectFilter does. Likewise, The jsf RedirectFilter now checks to see if there is a faces context before doing any work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 9 01:51:04 2009 From: jira-events at lists.jboss.org (Vladimir Kovalyuk (JIRA)) Date: Fri, 9 Jan 2009 01:51:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3645) Support co-existence of multiple view layers in same deployment In-Reply-To: <8315714.1225285820908.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <4511341.1231483864040.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12446306#action_12446306 ] Vladimir Kovalyuk commented on JBSEAM-3645: ------------------------------------------- This "issue" is not on roadmap. May you plan it for 2.1.2 CR1? > Support co-existence of multiple view layers in same deployment > --------------------------------------------------------------- > > Key: JBSEAM-3645 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3645 > Project: Seam > Issue Type: Patch > Reporter: Clint Popetz > Assignee: Clint Popetz > Attachments: Instantiator.java, Instantiator.java, multi-view-take-2.patch, multi-view-take-3.patch, multi-view.diff > > > Currently one must choose between wicket and jsf when using seam, because the wicket support works by overriding certain faces components. This patch eliminates that limitation. > This patch should be applied after the patches from the issues linked to this issue, which are also related to wicket development. There are four parts of this patch. > (1) The Manager and StatusMessages components are currently implemented in jsf with FacesManager and FacesMessages, and in wicket with WicketManager and WicketStatusMessages. Since a mixed deployment would need all managers to be @Installed, this patch makes each have a separate @Name, and makes the base classes (Manager and StatusMessages) @Unwrap themselves as one of the subclass components. Each subclass component registers itself with the base class component (by observing the postInitialization event) as a possible implementation. When Manager.instance() or StatusMessages.instance() is invoked, and the base component is created, @Unwrap is called, and that method asks each subclass component whether they should be used for that event scope. The Wicket implementations say yes if the wicket Application.exists() (which uses a ThreadLocal) returns true. The Faces implementations says yes if facesContext is not null. This patch assumes that both will not simultaneously return true, and if so, the behavior is undefined, as it's first-come-first-serve. If neither return true, the default Manager and StatusMessages implementation will be used. This happens during initialization and other edge cases where a manager is needed for event contexts that aren't tied to real requests. Note that since the FacesMessages component no longer has the same @Name as the StatusMessages component, it is now "org.jboss.seam.faces.facesMessages" which means the two factories for that name and its unqualified form in jboss-seam.jar's components.xml have been removed. > (2) Seam's WicketFilter currently sets up scopes unconditionally if it is installed. This causes faces requests to fail because the SeamPhaseListener also sets up and tears down scopes, and so when the wicket filter finishes and tries to tear down its scopes, it finds them gone and an exception occurs. I've changed WicketFilter to not set up scopes, but instead to have WicketFilterInstantiator's anonymous subclass of the real WicketFilter install the scopes _if_ wicket has determined the request is a wicket request. > (3) WicketExceptionFilter existed only to turn off the base ExceptionFilter for wicket classes. I've removed this class, and we'll need to add to the wicket seam documentation the need to map the ExceptionFilter in components.xml to jsf paths if wicket is to be used alongside jsf. > (4) WicketRedirectFilter now co-exists with the base RedirectFilter, rather than replacing it. It checks to see if Wicket is active (via the same Application.exists() call as above) before doing any work to redirects, so that it doesn't duplicate work that the jsf RedirectFilter does. Likewise, The jsf RedirectFilter now checks to see if there is a faces context before doing any work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 9 03:11:03 2009 From: jira-events at lists.jboss.org (Alexander Sparkowsky (JIRA)) Date: Fri, 9 Jan 2009 03:11:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3743) Renderer gets confuesed when sending of email throws exception In-Reply-To: <13308781.1227345096950.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <13040042.1231488664004.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12446311#action_12446311 ] Alexander Sparkowsky commented on JBSEAM-3743: ---------------------------------------------- I've attached a patch to Issue JBSEAM-3698 > Renderer gets confuesed when sending of email throws exception > -------------------------------------------------------------- > > Key: JBSEAM-3743 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3743 > Project: Seam > Issue Type: Bug > Components: Mail > Affects Versions: 2.1.0.GA, 2.1.0.SP1 > Environment: Mac OS X 10.5.5, Java 5, JBoss 4.0.5 modified for seam 2.x > Reporter: Alexander Sparkowsky > Fix For: 2.1.2.CR1 > > Attachments: emailtest.xhtml, EmailTestBean.java, test.xhtml > > > When sending of an email fails and an exception is thrown (i.e. mail server not available) the renderer seems to get into a wrong state. > present on the page get the application context "project". So "/myseamapp/foo/bar" becomes "/project/foo/bar". > If the action that is trying to send the mail is called by this link gets the path of the email view itself (including the "project" application context). > I've attached a Bean sending the email, the email template (/test.xhtml) and a simple view. > This is the mail session configuration from components.xml > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 9 05:50:04 2009 From: jira-events at lists.jboss.org (Shane Bryzak (JIRA)) Date: Fri, 9 Jan 2009 05:50:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-3885) Make CookiePath for RememberMe cookies optionally fixed In-Reply-To: <8637402.1231354984046.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <6748274.1231498204063.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Bryzak reassigned JBSEAM-3885: ------------------------------------ Assignee: Shane Bryzak > Make CookiePath for RememberMe cookies optionally fixed > ------------------------------------------------------- > > Key: JBSEAM-3885 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3885 > Project: Seam > Issue Type: Feature Request > Components: Security > Affects Versions: 2.1.1.GA > Reporter: Klaasjan te Voortwis > Assignee: Shane Bryzak > > The RememberMe cookies are stored on the same path as where the page was served from. > When providing a user/pass field in the top of all pages, a user can for example > - log in on http://domain.name/issuesystem/issue/create.seam, and mark RememberMe true > - come back to the site http://domain.name/someotherpath, and now the user is not logged in > (optionally) fixing the CookiePath for the RememberMe cookies to "/" instead of ctx.getExternalContext().getRequestContextPath() will solve this issue. > Setting the cookiePath is done in RememberMe.java on lines 221 and 238. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 9 10:53:04 2009 From: jira-events at lists.jboss.org (David Rosell (JIRA)) Date: Fri, 9 Jan 2009 10:53:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3888) QueryParser to restrictive, does not allow hash sign (#) in string literal Message-ID: <13667977.1231516384634.JavaMail.jira@cloud.prod.atl2.jboss.com> QueryParser to restrictive, does not allow hash sign (#) in string literal -------------------------------------------------------------------------- Key: JBSEAM-3888 URL: https://jira.jboss.org/jira/browse/JBSEAM-3888 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA Environment: jboss-seam-2.0.2.SP1, hibernate-entitymanager-3.4.0.GA, spring-2.5.6 Reporter: David Rosell The QueryParser are to restrictive when validating a query expression. It is not possible to use a hash sign (#) in a String literal query expression. An IllegalArgumentException are thrown for this query: String ejbql = "SELECT s FROM Service s WHERE s.name = 'DB#CORE' "; Query q = em.createQuery(ejbql); Rather than using: StringTokenizer tokens = new StringTokenizer(ejbql, "#}", true); it would be better to be more precise in selecting what should be processed, use regexp and splitting the ejbql expression for #{...} instead. Exception stacktrace: java.lang.IllegalArgumentException: missing { after # in query fragment at org.jboss.seam.persistence.QueryParser.(QueryParser.java:52) at org.jboss.seam.persistence.QueryParser.(QueryParser.java:33) at org.jboss.seam.persistence.EntityManagerProxy.createQuery(EntityManagerProxy.java:66) at sun.reflect.GeneratedMethodAccessor72.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.seam.ioc.spring.SeamManagedEntityManagerFactory$SeamManagedPersistenceContextHandler.invoke(SeamManagedEntityManagerFactory.java:142) at $Proxy71.createQuery(Unknown Source) at sun.reflect.GeneratedMethodAccessor72.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.orm.jpa.SharedEntityManagerCreator$SharedEntityManagerInvocationHandler.invoke(SharedEntityManagerCreator.java:198) at $Proxy58.createQuery(Unknown Source) at com.ford.volvocars.r2r.db.jpa.GenericDaoJpa.executeJpaQuery(GenericDaoJpa.java:40) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 9 12:51:04 2009 From: jira-events at lists.jboss.org (Francisco Jose Peredo Noguez (JIRA)) Date: Fri, 9 Jan 2009 12:51:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3797) ConversationInterceptor.aroundInvoke broken stacktrace In-Reply-To: <15882360.1228444246897.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <32792487.1231523464032.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12447034#action_12447034 ] Francisco Jose Peredo Noguez commented on JBSEAM-3797: ------------------------------------------------------ Mmmm, I don't see any value in breaking the stacktrace... ;-) I don't really want to "wrap the exception ", what I want is to preserve the full stacktrace so that I can trace the real root cause of the problem by reading the stacktrace (instead of having to start a step by step debugger). Do you know of another way of preserving the stacktrace? > ConversationInterceptor.aroundInvoke broken stacktrace > ------------------------------------------------------ > > Key: JBSEAM-3797 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3797 > Project: Seam > Issue Type: Bug > Reporter: Francisco Jose Peredo Noguez > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > Attachments: patch.txt > > > catch (Exception e) > { > if ( isEndConversationRequired(e) ) > { > endConversation(false, false); > } > throw e; //<---HERE! > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 9 14:00:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Fri, 9 Jan 2009 14:00:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3797) ConversationInterceptor.aroundInvoke broken stacktrace In-Reply-To: <15882360.1228444246897.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <4771833.1231527604185.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12447051#action_12447051 ] Norman Richards commented on JBSEAM-3797: ----------------------------------------- The stack trace of the original error is preserved. This is cleanup code, like a finally block. > ConversationInterceptor.aroundInvoke broken stacktrace > ------------------------------------------------------ > > Key: JBSEAM-3797 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3797 > Project: Seam > Issue Type: Bug > Reporter: Francisco Jose Peredo Noguez > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > Attachments: patch.txt > > > catch (Exception e) > { > if ( isEndConversationRequired(e) ) > { > endConversation(false, false); > } > throw e; //<---HERE! > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 9 14:43:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Fri, 9 Jan 2009 14:43:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3771) URL Rewriting Not Occurring In-Reply-To: <10072980.1228147776458.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <26385148.1231530184148.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3771. ----------------------------------- Resolution: Done The https issue should be solved now. Please let me know if there are still problems with this. > URL Rewriting Not Occurring > --------------------------- > > Key: JBSEAM-3771 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3771 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.1.CR1 > Environment: Windows Vista, JBoss 4.2.0, JRockit 1.5 > Reporter: Dave Everson > Assignee: Norman Richards > > We have just updated Seam to 2.1.1CR1 > We started to use the rewrite functionality within pages.xml. > We have the following pages defined: > > > > > > > > > > > > > > > > > > We are able to access /newFamilyAccount without issue and a conversation is started > After entering data that already exists in the database, we should be taken to the /existingAccounts (/pages/account/existing.xhtml) view. We are taken to the view, however the URL shows: https://localhost/a/pages/account/existing.seam?cid=9. > We have tried several things and can't see to ever have the rewritten URL appear. Does anyone have any suggestions on what we are doing incorrectly. Thanks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 9 19:27:04 2009 From: jira-events at lists.jboss.org (John Ament (JIRA)) Date: Fri, 9 Jan 2009 19:27:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3889) Easier RestEasy paths Message-ID: <1129984.1231547224121.JavaMail.jira@cloud.prod.atl2.jboss.com> Easier RestEasy paths --------------------- Key: JBSEAM-3889 URL: https://jira.jboss.org/jira/browse/JBSEAM-3889 Project: Seam Issue Type: Feature Request Components: Remoting Environment: JSF based apps Reporter: John Ament Assignee: Shane Bryzak The rest easy integration is missing a few important integrations that would make using it in applications considerably easier. - s:link integrated resource paths based on actions. If I have a restful service defines as: @Path("/viewimage") @Name("viewImage") public class ViewImage implements java.io.Serializable .... @GET @Path("/{username}/{filename}") public byte[] viewImage(@PathParam("username")String username, at PathParam("filename")String filename) I should be able to define an s:link something like... Or even a specialized graphicImage implementation that does soemthing similar... Second, the resource path configuration in web.xml should be optional. The seam filter should be able to pull out the resources without needing the resource servlet directly handling the values. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sat Jan 10 09:10:04 2009 From: jira-events at lists.jboss.org (Pete Muir (JIRA)) Date: Sat, 10 Jan 2009 09:10:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3698) Error during rendering of an EMail in an event listener causes failure in rendering of next page In-Reply-To: <29395838.1226611716771.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <31762346.1231596604934.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated JBSEAM-3698: ------------------------------ Fix Version/s: 2.1.2.CR1 Assignee: (was: Pete Muir) > Error during rendering of an EMail in an event listener causes failure in rendering of next page > ------------------------------------------------------------------------------------------------ > > Key: JBSEAM-3698 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3698 > Project: Seam > Issue Type: Bug > Components: Mail > Affects Versions: 2.1.0.SP1 > Environment: Windows XP, Java 6, 2GB RAM, JBoss 4.2.2.GA > Reporter: Wayne Bagguley > Fix For: 2.1.2.CR1 > > Attachments: RendererRequest.diff > > > I have a method that is defined as a listener like this : > @Observer(JpaIdentityStore.EVENT_USER_CREATED) > This attempts to send an email to the user when he registers but if the email rendering fails for some reason the exception is caught and the method returns normally. However, instead of the next page being rendered, the original page gets rendered incorrectly, with parts of the form in the wrong place. The failure of rendering the EMail should not affect the progress of the rendering of the next page if the exception is caught. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sat Jan 10 09:12:04 2009 From: jira-events at lists.jboss.org (Pete Muir (JIRA)) Date: Sat, 10 Jan 2009 09:12:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3880) Wicket interception doesn't throw error on missing required injections In-Reply-To: <12660077.1231255084052.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <4696909.1231596724478.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12447107#action_12447107 ] Pete Muir commented on JBSEAM-3880: ----------------------------------- Please apply :-) > Wicket interception doesn't throw error on missing required injections > ----------------------------------------------------------------------- > > Key: JBSEAM-3880 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3880 > Project: Seam > Issue Type: Bug > Reporter: Clint Popetz > Assignee: Clint Popetz > Attachments: WicketComponent.java.patch > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sat Jan 10 09:24:08 2009 From: jira-events at lists.jboss.org (Clint Popetz (JIRA)) Date: Sat, 10 Jan 2009 09:24:08 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3880) Wicket interception doesn't throw error on missing required injections In-Reply-To: <12660077.1231255084052.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <24733940.1231597448724.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clint Popetz closed JBSEAM-3880. -------------------------------- Resolution: Done Applied, r9910 > Wicket interception doesn't throw error on missing required injections > ----------------------------------------------------------------------- > > Key: JBSEAM-3880 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3880 > Project: Seam > Issue Type: Bug > Reporter: Clint Popetz > Assignee: Clint Popetz > Attachments: WicketComponent.java.patch > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Jan 11 16:40:14 2009 From: jira-events at lists.jboss.org (Daniel Roth (JIRA)) Date: Sun, 11 Jan 2009 16:40:14 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3789) Useless conditional in MailResponseWriter.write In-Reply-To: <20359769.1228439976425.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <20203241.1231710014561.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roth closed JBSEAM-3789. ------------------------------- Resolution: Done Assignee: Daniel Roth Fixed. Thanks Francisco. > Useless conditional in MailResponseWriter.write > ----------------------------------------------- > > Key: JBSEAM-3789 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3789 > Project: Seam > Issue Type: Bug > Reporter: Francisco Jose Peredo Noguez > Assignee: Daniel Roth > Fix For: 2.1.2.CR1 > > Attachments: patch.txt > > > Method org.jboss.seam.mail.ui.context.MailResponseWriter.write(String) uses the same code for two branches -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 12 08:47:04 2009 From: jira-events at lists.jboss.org (Denis Forveille (JIRA)) Date: Mon, 12 Jan 2009 08:47:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3890) Update the samples to user "credentials" instead of "identity" Message-ID: <3522464.1231768024138.JavaMail.jira@cloud.prod.atl2.jboss.com> Update the samples to user "credentials" instead of "identity" -------------------------------------------------------------- Key: JBSEAM-3890 URL: https://jira.jboss.org/jira/browse/JBSEAM-3890 Project: Seam Issue Type: Bug Components: Documentation Issues, Security Affects Versions: 2.1.1.GA Reporter: Denis Forveille Priority: Minor In the security chapters, section 15.3.2 and 15.3.3, the code snippets use the "Credentials" class to store the username and the password of the user that is performing a login. The samples still use the "old" (?) way, ie use the identity class to store this data, at leat for the "blog", "booking", "dvdstore", etc... It seems that not one sample use the "Cedentials" class -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 12 08:49:04 2009 From: jira-events at lists.jboss.org (Denis Forveille (JIRA)) Date: Mon, 12 Jan 2009 08:49:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3886) Document the usage of to disable identity managment In-Reply-To: <4633773.1231359124040.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <776702.1231768144304.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Forveille updated JBSEAM-3886: ------------------------------------ Component/s: Security > Document the usage of to disable identity managment > ----------------------------------------------------------------------------------------- > > Key: JBSEAM-3886 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3886 > Project: Seam > Issue Type: Bug > Components: Documentation Issues, Security > Affects Versions: 2.1.1.GA > Reporter: Denis Forveille > Priority: Minor > > Document the usage of to disable identity managment in seam v2.1 as stated in jira JBSEAM-3629 > Maybe this should be included in section 15.2 (Security/Disabling security) ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 12 09:29:03 2009 From: jira-events at lists.jboss.org (Denis Forveille (JIRA)) Date: Mon, 12 Jan 2009 09:29:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3890) Update the samples to user "credentials" instead of "identity" In-Reply-To: <3522464.1231768024138.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <3258611.1231770543974.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Forveille updated JBSEAM-3890: ------------------------------------ Component/s: Examples (was: Documentation Issues) > Update the samples to user "credentials" instead of "identity" > -------------------------------------------------------------- > > Key: JBSEAM-3890 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3890 > Project: Seam > Issue Type: Bug > Components: Examples, Security > Affects Versions: 2.1.1.GA > Reporter: Denis Forveille > Priority: Minor > > In the security chapters, section 15.3.2 and 15.3.3, the code snippets use the "Credentials" class to store the username and the password of the user that is performing a login. > The samples still use the "old" (?) way, ie use the identity class to store this data, at leat for the "blog", "booking", "dvdstore", etc... > It seems that not one sample use the "Cedentials" class -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 12 10:32:06 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Mon, 12 Jan 2009 10:32:06 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3891) openid fails on port 80 Message-ID: <30124007.1231774326077.JavaMail.jira@cloud.prod.atl2.jboss.com> openid fails on port 80 ----------------------- Key: JBSEAM-3891 URL: https://jira.jboss.org/jira/browse/JBSEAM-3891 Project: Seam Issue Type: Feature Request Reporter: Norman Richards Fix For: 2.1.2.CR1 See forum posting -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 12 10:36:05 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Mon, 12 Jan 2009 10:36:05 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-3891) openid fails on port 80 In-Reply-To: <30124007.1231774326077.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <18705226.1231774566085.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards reassigned JBSEAM-3891: --------------------------------------- Assignee: Norman Richards > openid fails on port 80 > ----------------------- > > Key: JBSEAM-3891 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3891 > Project: Seam > Issue Type: Feature Request > Reporter: Norman Richards > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > > See forum posting -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 12 13:18:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Mon, 12 Jan 2009 13:18:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3787) Useless conditional in SeamComponentPostProcessor.postProcessAfterInitialization In-Reply-To: <6004383.1228439856496.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <14276312.1231784284183.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3787. ----------------------------------- Resolution: Done Thanks. > Useless conditional in SeamComponentPostProcessor.postProcessAfterInitialization > -------------------------------------------------------------------------------- > > Key: JBSEAM-3787 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3787 > Project: Seam > Issue Type: Bug > Reporter: Francisco Jose Peredo Noguez > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > Attachments: patch.txt > > > instanceof will always return true in org.jboss.seam.ioc.spring.SeamComponentPostProcessor.postProcessAfterInitialization(Object, String), since all org.jboss.seam.ioc.spring.SpringComponent are instances of org.jboss.seam.ioc.spring.SpringComponent -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 12 13:36:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Mon, 12 Jan 2009 13:36:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3792) Invocation of toString on args in org.jboss.seam.util.DelegatingInvocationHandler.invoke In-Reply-To: <10128184.1228440876502.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <25192839.1231785364039.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3792. ----------------------------------- Resolution: Done Thanks. > Invocation of toString on args in org.jboss.seam.util.DelegatingInvocationHandler.invoke > ---------------------------------------------------------------------------------------- > > Key: JBSEAM-3792 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3792 > Project: Seam > Issue Type: Bug > Reporter: Francisco Jose Peredo Noguez > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > Attachments: patch.txt > > > nvocation of toString on args in org.jboss.seam.util.DelegatingInvocationHandler.invoke(Object, Method, Object[]): > if (target == null) > { > throw new IllegalStateException("Proxied session does not implement method " + method.getName() + > " with args [" + args + "]"); > } > > if (log.isTraceEnabled()) > { > log.trace("Delegating method " + method.getName() + " with args " + args); > } > args will not be logged (or thrown) as something nice to read. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 12 13:42:03 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Mon, 12 Jan 2009 13:42:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3799) AsynchronousMailProcessor.scheduleSend should be using logging API In-Reply-To: <31061915.1228445016420.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <27838906.1231785724019.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3799. ----------------------------------- Resolution: Done Thanks. > AsynchronousMailProcessor.scheduleSend should be using logging API > ------------------------------------------------------------------ > > Key: JBSEAM-3799 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3799 > Project: Seam > Issue Type: Bug > Reporter: Francisco Jose Peredo Noguez > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > Attachments: patch.txt > > > } catch (Exception e) { > e.printStackTrace(); > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 12 13:52:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Mon, 12 Jan 2009 13:52:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3794) Method org.jboss.seam.remoting.Call.findMethod(String, Class) makes inefficient use of keySet iterator instead of entrySet iterator In-Reply-To: <22175103.1228442797010.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <20264244.1231786324263.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3794. ----------------------------------- Resolution: Done Thanks. > Method org.jboss.seam.remoting.Call.findMethod(String, Class) makes inefficient use of keySet iterator instead of entrySet iterator > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBSEAM-3794 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3794 > Project: Seam > Issue Type: Bug > Reporter: Francisco Jose Peredo Noguez > Assignee: Norman Richards > Priority: Minor > Fix For: 2.1.2.CR1 > > Attachments: patch.txt > > > for (Method m : candidates.keySet()) > { > int thisScore = candidates.get(m).intValue(); <-- HERE! > if (bestMethod == null || thisScore > bestScore) > { > bestMethod = m; > bestScore = thisScore; > } > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 12 13:54:11 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Mon, 12 Jan 2009 13:54:11 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1032) Integration with JBoss SSO In-Reply-To: <15228579.1173663774108.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <21090262.1231786451678.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards updated JBSEAM-1032: ------------------------------------ Fix Version/s: The future (was: 2.1.2.CR1) > Integration with JBoss SSO > -------------------------- > > Key: JBSEAM-1032 > URL: https://jira.jboss.org/jira/browse/JBSEAM-1032 > Project: Seam > Issue Type: Feature Request > Components: Security > Affects Versions: 1.2.0.GA > Reporter: Shane Bryzak > Assignee: Norman Richards > Priority: Blocker > Fix For: The future > > > We should provide integration of Seam Security with JBoss SSO. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 12 13:56:14 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Mon, 12 Jan 2009 13:56:14 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-2791) Support CJK in a chart. In-Reply-To: <10110540.1206721960161.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <14129987.1231786574234.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-2791. ----------------------------------- Resolution: Done Done. If you change your mind about the japanese example, please let me know. We could really use it. > Support CJK in a chart. > ----------------------- > > Key: JBSEAM-2791 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2791 > Project: Seam > Issue Type: Feature Request > Components: PDF > Affects Versions: 2.1.0.A1 > Environment: ubuntu linux 7.10 > jdk1.5.0_14 > jboss seam 2.1.0A > Reporter: Nobuyuki Inaba > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > Attachments: chart.patch, cjkChart.xhtml, screenshot( not apply patch version).jpg, screenshot(apply patch version).jpg > > > Hi, > Seam 2.1.0A does not support CJK character in a chart( in a PDF file). > because, UIChart class use DefaultFontMapper class. > I think UIChart class should use settings. > I attached the patch against this issue to this ticket.Please check the patch. > When apply the patch to Seam, Seam can support CJK chacter in a chart. > and In a chart, developer have to appoint the following to use CJK. > 1. Appoint the 'locale' in . e.g. . Now, 'ja' has not mean. but I think that this is necessary when Seam supports other multi-byte languages. > 2. Setting of . already fixed in JBSEAM-1039. > best regards, > Nobuyuki Inaba -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 12 14:19:03 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Mon, 12 Jan 2009 14:19:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3875) Seam's Rewrite filter breaks URL-session-id-rewriting In-Reply-To: <2782549.1231110294248.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <26053692.1231787944004.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3875. ----------------------------------- Resolution: Done Fixed in CVS, as far as I can tell. Let me know if it isn't working right for you > Seam's Rewrite filter breaks URL-session-id-rewriting > ----------------------------------------------------- > > Key: JBSEAM-3875 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3875 > Project: Seam > Issue Type: Bug > Components: Core > Reporter: Stephen Friedrich > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > > If Seam's rewrite filter is enabled, the session id is never added as a parameter to URLs. > That should happen when one of the HttpServletResponse.encode...() methods is called and no session cookie is found. > However the rewrite filter adds a response wrapper that delegates all encode methods to a method that only (possibly) rewrites the URL according to defined rewrite-rules, but never actually let's the servlet container encode the url. > Fix: In org.jboss.seam.web.RewritingResponse.encodeURL(String) add this line: > result = ((HttpServletResponse) getResponse()).encodeURL(result); > before returning the result. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 12 14:27:05 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Mon, 12 Jan 2009 14:27:05 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3772) Seam Blog example throws IncompatibleClassChangeError on AS5 In-Reply-To: <5091773.1228150596675.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <7060490.1231788425309.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3772. ----------------------------------- Resolution: Cannot Reproduce Bug > Seam Blog example throws IncompatibleClassChangeError on AS5 > ------------------------------------------------------------ > > Key: JBSEAM-3772 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3772 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.1.1.CR2 > Reporter: Stan Silvert > Fix For: 2.1.2.CR1 > > > I'm running the Seam blog example against AS5. Both are using the latest code from trunk. > The example starts up without error. However, if you click on "All Posts" and then click on "Seam book excerpt on InfoQ ", you will get: > 11:50:04,173 ERROR [[Faces Servlet]] Servlet.service() for servlet Faces Servlet > threw exception > java.lang.IncompatibleClassChangeError > at org.jboss.seam.cache.JbossCacheProvider.get(JbossCacheProvider.java:8 > 3) > at org.jboss.seam.ui.renderkit.CacheRendererBase.doEncodeChildren(CacheR > endererBase.java:38) > at org.jboss.seam.ui.util.cdk.RendererBase.encodeChildren(RendererBase.j > ava:92) > at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase. > java:837) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:930) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:933) > at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.jav > a:592) > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePha > se.java:110) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl > icationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF > ilterChain.java:206) > at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisp > atcher.java:638) > at org.apache.catalina.core.ApplicationDispatcher.processRequest(Applica > tionDispatcher.java:444) > at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationD > ispatcher.java:382) > at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDis > patcher.java:310) > at org.jboss.seam.web.RewriteFilter.process(RewriteFilter.java:98) > at org.jboss.seam.web.RewriteFilter.doFilter(RewriteFilter.java:57) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter > .java:69) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter > .java:69) > at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter > .java:69) > at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter > .java:69) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter > .java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter > .java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl > icationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF > ilterChain.java:206) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi > lter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl > icationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF > ilterChain.java:206) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV > alve.java:235) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV > alve.java:191) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit > yAssociationValve.java:190) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv > e.java:92) > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.proce > ss(SecurityContextEstablishmentValve.java:126) > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invok > e(SecurityContextEstablishmentValve.java:70) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j > ava:127) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j > ava:102) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedC > onnectionValve.java:158) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal > ve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav > a:330) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java > :828) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce > ss(Http11Protocol.java:601) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:44 > 7) > at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 12 14:44:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Mon, 12 Jan 2009 14:44:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3671) Initialization swallows exception In-Reply-To: <30937487.1225829720791.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <30787217.1231789444402.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3671. ----------------------------------- Resolution: Out of Date This looks already done. > Initialization swallows exception > --------------------------------- > > Key: JBSEAM-3671 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3671 > Project: Seam > Issue Type: Bug > Components: Core > Reporter: Clint Popetz > Priority: Minor > Fix For: 2.1.2.CR1 > > Attachments: swallowed-exception.patch > > > Patch attached -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 12 14:46:04 2009 From: jira-events at lists.jboss.org (Clint Popetz (JIRA)) Date: Mon, 12 Jan 2009 14:46:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3671) Initialization swallows exception In-Reply-To: <30937487.1225829720791.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <14160395.1231789564192.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12447433#action_12447433 ] Clint Popetz commented on JBSEAM-3671: -------------------------------------- Sorry, I committed this per Pete's comment, but forgot to close the issue. > Initialization swallows exception > --------------------------------- > > Key: JBSEAM-3671 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3671 > Project: Seam > Issue Type: Bug > Components: Core > Reporter: Clint Popetz > Priority: Minor > Fix For: 2.1.2.CR1 > > Attachments: swallowed-exception.patch > > > Patch attached -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 12 17:06:08 2009 From: jira-events at lists.jboss.org (John Gilbert (JIRA)) Date: Mon, 12 Jan 2009 17:06:08 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3555) SeamMailAgain In-Reply-To: <3978595.1223977760796.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <28398373.1231797968678.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Gilbert updated JBSEAM-3555: --------------------------------- Attachment: RendererFacesContextFactory.java SUCCESS!!! I managed to make this work in not too "hacky" a fashion. I extended RendererFacesContextFactory (see attached) and bumped up the precedence to replace the built-in implementation. Copy the class to your project and desired package. I'm not sure this approach is a candidate for a patch, but it appears to work. The create() method was extended to setup a MockLifecycle if one does not already exist. This solves the original exception mentioned in this ticket. The getFacesContext() method was extended to setup a MockFacesContext if one does not already exist. This was the 2nd problem I encountered once I got past the first. Give it a try... > SeamMailAgain > ------------- > > Key: JBSEAM-3555 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3555 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.0.CR1 > Environment: JBoss AS 4.2.1.GA > JBoss Seam 2.1.0-SNAPSHOT (10.10. HudsonNo330) > Reporter: Markus Heidt > Assignee: Pete Muir > Fix For: 2.1.2.CR1 > > Attachments: RendererFacesContextFactory.java, server.log > > > Simple Mailing via Renderer doesn't work. > 'Seam-gen'erated a new project and added a new action 'sendMail' > Added the line to the action code: > Renderer.instance().render("/simple.xhtml"); > simple.xhtml is a modified version of the seam example (without #{person}) > Error after executing the action: > 2008-10-14 11:40:21,847 FATAL [javax.enterprise.resource.webcontainer.jsf.application] org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > javax.faces.el.EvaluationException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:91) > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:91) > ... > Caused by: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory > at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:256) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 12 18:15:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Mon, 12 Jan 2009 18:15:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3774) Interpolator does not support # in choice/MessageFormat does In-Reply-To: <2531307.1228218456431.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <10745280.1231802104077.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12447463#action_12447463 ] Norman Richards commented on JBSEAM-3774: ----------------------------------------- Can you possibly show the context in which you are using that message? > Interpolator does not support # in choice/MessageFormat does > ------------------------------------------------------------ > > Key: JBSEAM-3774 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3774 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.0.3.CR1, 2.1.0.CR1 > Reporter: Guy Di Fulvio > Priority: Minor > Fix For: 2.1.2.CR1 > > > In my properties file: > my.choice.message = {0,choice,0#No choice|1# 1 choice|1< {0,number,integer} choices} > This is working with MessageFormat but Interpolator returns only {0} and my choices are lost. > After checking the code the problem is coming from the #. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 12 18:15:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Mon, 12 Jan 2009 18:15:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-3774) Interpolator does not support # in choice/MessageFormat does In-Reply-To: <2531307.1228218456431.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <28622930.1231802104228.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards reassigned JBSEAM-3774: --------------------------------------- Assignee: Norman Richards > Interpolator does not support # in choice/MessageFormat does > ------------------------------------------------------------ > > Key: JBSEAM-3774 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3774 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.0.3.CR1, 2.1.0.CR1 > Reporter: Guy Di Fulvio > Assignee: Norman Richards > Priority: Minor > Fix For: 2.1.2.CR1 > > > In my properties file: > my.choice.message = {0,choice,0#No choice|1# 1 choice|1< {0,number,integer} choices} > This is working with MessageFormat but Interpolator returns only {0} and my choices are lost. > After checking the code the problem is coming from the #. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 13 03:01:04 2009 From: jira-events at lists.jboss.org (Guy Di Fulvio (JIRA)) Date: Tue, 13 Jan 2009 03:01:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3774) Interpolator does not support # in choice/MessageFormat does In-Reply-To: <2531307.1228218456431.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <4413655.1231833664061.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guy Di Fulvio updated JBSEAM-3774: ---------------------------------- In this exemple #{mylistsize} is the number of elements in a list. Depending on the list size the message is diff?rent. .xhtml .properties foundMsg = {0,choice,0#nothing found|1#1 element found|1<{0} elements found} > Interpolator does not support # in choice/MessageFormat does > ------------------------------------------------------------ > > Key: JBSEAM-3774 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3774 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.0.3.CR1, 2.1.0.CR1 > Reporter: Guy Di Fulvio > Assignee: Norman Richards > Priority: Minor > Fix For: 2.1.2.CR1 > > > In my properties file: > my.choice.message = {0,choice,0#No choice|1# 1 choice|1< {0,number,integer} choices} > This is working with MessageFormat but Interpolator returns only {0} and my choices are lost. > After checking the code the problem is coming from the #. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 13 10:42:04 2009 From: jira-events at lists.jboss.org (Ga?l Beaudoin (JIRA)) Date: Tue, 13 Jan 2009 10:42:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3555) SeamMailAgain In-Reply-To: <3978595.1223977760796.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <14690949.1231861324773.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12447621#action_12447621 ] Ga?l Beaudoin commented on JBSEAM-3555: --------------------------------------- Thanks ! Unfortunately It doesn't fix it for me. The first IllegalStateException is catched, a new MockLifecycle(); is instanciated, but then I still get : org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory 16:08:44,842 ERROR [STDERR] at org.jboss.seam.Component.newInstance(Component.java:2106) 16:08:44,842 ERROR [STDERR] at org.jboss.seam.Component.getInstance(Component.java:1988) 16:08:44,842 ERROR [STDERR] at org.jboss.seam.Component.getInstance(Component.java:1967) 16:08:44,843 ERROR [STDERR] at org.jboss.seam.Component.getInstance(Component.java:1961) 16:08:44,843 ERROR [STDERR] at org.jboss.seam.Component.getInstance(Component.java:1934) 16:08:44,843 ERROR [STDERR] at org.jboss.seam.Component.getInstance(Component.java:1929) 16:08:44,843 ERROR [STDERR] at org.jboss.seam.ui.facelet.RendererFacesContextFactory.instance(RendererFacesContextFactory.java:72) 16:08:44,843 ERROR [STDERR] at org.jboss.seam.ui.facelet.RendererRequest.init(RendererRequest.java:45) 16:08:44,843 ERROR [STDERR] at org.jboss.seam.ui.facelet.RendererRequest.run(RendererRequest.java:72) 16:08:44,843 ERROR [STDERR] at org.jboss.seam.ui.facelet.FaceletsRenderer.render(FaceletsRenderer.java:43) 16:08:44,843 ERROR [STDERR] at com.lrb.modules.booksellers.billing.InvoiceHome.sendEmail(InvoiceHome.java:157) 16:08:44,843 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 16:08:44,843 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 16:08:44,843 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 16:08:44,843 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:597) 16:08:44,843 ERROR [STDERR] at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) 16:08:44,843 ERROR [STDERR] at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) 16:08:44,843 ERROR [STDERR] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) 16:08:44,843 ERROR [STDERR] at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:28) 16:08:44,843 ERROR [STDERR] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) 16:08:44,843 ERROR [STDERR] at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:77) 16:08:44,843 ERROR [STDERR] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) 16:08:44,843 ERROR [STDERR] at org.jboss.seam.bpm.BusinessProcessInterceptor.aroundInvoke(BusinessProcessInterceptor.java:51) 16:08:44,844 ERROR [STDERR] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) 16:08:44,844 ERROR [STDERR] at org.jboss.seam.transaction.TransactionInterceptor$1.work(TransactionInterceptor.java:95) 16:08:44,844 ERROR [STDERR] at org.jboss.seam.util.Work.workInTransaction(Work.java:47) 16:08:44,844 ERROR [STDERR] at org.jboss.seam.transaction.TransactionInterceptor.aroundInvoke(TransactionInterceptor.java:89) 16:08:44,844 ERROR [STDERR] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) 16:08:44,844 ERROR [STDERR] at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44) 16:08:44,844 ERROR [STDERR] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) 16:08:44,844 ERROR [STDERR] at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) 16:08:44,844 ERROR [STDERR] at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:185) 16:08:44,844 ERROR [STDERR] at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:103) 16:08:44,844 ERROR [STDERR] at com.lrb.modules.booksellers.billing.InvoiceHome_$$_javassist_22.sendEmail(InvoiceHome_$$_javassist_22.java) 16:08:44,844 ERROR [STDERR] at com.lrb.modules.booksellers.billing.SubscriptionInvoiceGenerator.generateInvoicesForDate(SubscriptionInvoiceGenerator.java:184) 16:08:44,844 ERROR [STDERR] at com.lrb.modules.booksellers.billing.SubscriptionInvoiceGenerator.work(SubscriptionInvoiceGenerator.java:60) 16:08:44,844 ERROR [STDERR] at com.lrb.modules.booksellers.billing.SubscriptionInvoiceGenerator.work(SubscriptionInvoiceGenerator.java:1) 16:08:44,844 ERROR [STDERR] at com.lrb.metabook.util.Work.workInTransaction(Work.java:55) 16:08:44,844 ERROR [STDERR] at com.lrb.modules.booksellers.AbstractJob.schedule(AbstractJob.java:82) 16:08:44,844 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 16:08:44,844 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 16:08:44,845 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 16:08:44,845 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:597) 16:08:44,845 ERROR [STDERR] at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) 16:08:44,845 ERROR [STDERR] at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) 16:08:44,845 ERROR [STDERR] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) 16:08:44,845 ERROR [STDERR] at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:28) 16:08:44,845 ERROR [STDERR] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) 16:08:44,845 ERROR [STDERR] at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:77) 16:08:44,845 ERROR [STDERR] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) 16:08:44,845 ERROR [STDERR] at org.jboss.seam.bpm.BusinessProcessInterceptor.aroundInvoke(BusinessProcessInterceptor.java:51) 16:08:44,845 ERROR [STDERR] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) 16:08:44,845 ERROR [STDERR] at org.jboss.seam.transaction.TransactionInterceptor$1.work(TransactionInterceptor.java:95) 16:08:44,845 ERROR [STDERR] at org.jboss.seam.util.Work.workInTransaction(Work.java:47) 16:08:44,845 ERROR [STDERR] at org.jboss.seam.transaction.TransactionInterceptor.aroundInvoke(TransactionInterceptor.java:89) 16:08:44,845 ERROR [STDERR] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) 16:08:44,845 ERROR [STDERR] at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44) 16:08:44,845 ERROR [STDERR] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) 16:08:44,845 ERROR [STDERR] at org.jboss.seam.async.AsynchronousInterceptor.aroundInvoke(AsynchronousInterceptor.java:52) 16:08:44,845 ERROR [STDERR] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) 16:08:44,845 ERROR [STDERR] at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) 16:08:44,846 ERROR [STDERR] at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:185) 16:08:44,846 ERROR [STDERR] at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:103) 16:08:44,846 ERROR [STDERR] at com.lrb.modules.booksellers.billing.SubscriptionInvoiceGenerator_$$_javassist_17.schedule(SubscriptionInvoiceGenerator_$$_javassist_17.java) 16:08:44,846 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 16:08:44,846 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 16:08:44,846 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 16:08:44,846 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:597) 16:08:44,846 ERROR [STDERR] at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) 16:08:44,846 ERROR [STDERR] at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:144) 16:08:44,846 ERROR [STDERR] at org.jboss.seam.async.AsynchronousInvocation$1.process(AsynchronousInvocation.java:62) 16:08:44,846 ERROR [STDERR] at org.jboss.seam.async.Asynchronous$ContextualAsynchronousRequest.run(Asynchronous.java:80) 16:08:44,846 ERROR [STDERR] at org.jboss.seam.async.AsynchronousInvocation.execute(AsynchronousInvocation.java:44) 16:08:44,846 ERROR [STDERR] at org.jboss.seam.async.QuartzDispatcher$QuartzJob.execute(QuartzDispatcher.java:243) 16:08:44,846 ERROR [STDERR] at org.quartz.core.JobRunShell.run(JobRunShell.java:203) 16:08:44,846 ERROR [STDERR] at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520) 16:08:44,847 ERROR [STDERR] Caused by: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory 16:08:44,847 ERROR [STDERR] at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:267) 16:08:44,847 ERROR [STDERR] at org.jboss.seam.ui.facelet.RendererFacesContextFactory.create(RendererFacesContextFactory.java:47) 16:08:44,847 ERROR [STDERR] at com.lrb.metabook.core.RendererFacesContextFactory.create(RendererFacesContextFactory.java:44) 16:08:44,847 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 16:08:44,847 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 16:08:44,847 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 16:08:44,847 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:597) 16:08:44,847 ERROR [STDERR] at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) 16:08:44,847 ERROR [STDERR] at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:144) 16:08:44,847 ERROR [STDERR] at org.jboss.seam.Component.callComponentMethod(Component.java:2211) 16:08:44,847 ERROR [STDERR] at org.jboss.seam.Component.callCreateMethod(Component.java:2134) 16:08:44,847 ERROR [STDERR] at org.jboss.seam.Component.newInstance(Component.java:2094) com.lrb.metabook.core.RendererFacesContextFactory is the overridden RendererFacesContextFactory attached here. I've tried with both seam 2.1.1 and trunk r9925. Using jboss 4.2.3 and quartz. I've also tried to use this trick with no success, same exception : http://in.relation.to/2640.lace > SeamMailAgain > ------------- > > Key: JBSEAM-3555 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3555 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.0.CR1 > Environment: JBoss AS 4.2.1.GA > JBoss Seam 2.1.0-SNAPSHOT (10.10. HudsonNo330) > Reporter: Markus Heidt > Assignee: Pete Muir > Fix For: 2.1.2.CR1 > > Attachments: RendererFacesContextFactory.java, server.log > > > Simple Mailing via Renderer doesn't work. > 'Seam-gen'erated a new project and added a new action 'sendMail' > Added the line to the action code: > Renderer.instance().render("/simple.xhtml"); > simple.xhtml is a modified version of the seam example (without #{person}) > Error after executing the action: > 2008-10-14 11:40:21,847 FATAL [javax.enterprise.resource.webcontainer.jsf.application] org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > javax.faces.el.EvaluationException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:91) > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:91) > ... > Caused by: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory > at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:256) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 13 12:04:04 2009 From: jira-events at lists.jboss.org (Ga?l Beaudoin (JIRA)) Date: Tue, 13 Jan 2009 12:04:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3555) SeamMailAgain In-Reply-To: <3978595.1223977760796.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <13686465.1231866244567.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12447632#action_12447632 ] Ga?l Beaudoin commented on JBSEAM-3555: --------------------------------------- Ok, I've given up and switched to EJB3 timer that works without problem. I'll watch for any improvement to switch back to quartz as there are some interesting features. > SeamMailAgain > ------------- > > Key: JBSEAM-3555 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3555 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.0.CR1 > Environment: JBoss AS 4.2.1.GA > JBoss Seam 2.1.0-SNAPSHOT (10.10. HudsonNo330) > Reporter: Markus Heidt > Assignee: Pete Muir > Fix For: 2.1.2.CR1 > > Attachments: RendererFacesContextFactory.java, server.log > > > Simple Mailing via Renderer doesn't work. > 'Seam-gen'erated a new project and added a new action 'sendMail' > Added the line to the action code: > Renderer.instance().render("/simple.xhtml"); > simple.xhtml is a modified version of the seam example (without #{person}) > Error after executing the action: > 2008-10-14 11:40:21,847 FATAL [javax.enterprise.resource.webcontainer.jsf.application] org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > javax.faces.el.EvaluationException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:91) > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:91) > ... > Caused by: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory > at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:256) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 13 13:44:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Tue, 13 Jan 2009 13:44:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3774) Interpolator does not support # in choice/MessageFormat does In-Reply-To: <2531307.1228218456431.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <10844066.1231872244449.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12447650#action_12447650 ] Norman Richards commented on JBSEAM-3774: ----------------------------------------- This works fine for me in CVS. > Interpolator does not support # in choice/MessageFormat does > ------------------------------------------------------------ > > Key: JBSEAM-3774 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3774 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.0.3.CR1, 2.1.0.CR1 > Reporter: Guy Di Fulvio > Assignee: Norman Richards > Priority: Minor > Fix For: 2.1.2.CR1 > > > In my properties file: > my.choice.message = {0,choice,0#No choice|1# 1 choice|1< {0,number,integer} choices} > This is working with MessageFormat but Interpolator returns only {0} and my choices are lost. > After checking the code the problem is coming from the #. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 13 14:06:03 2009 From: jira-events at lists.jboss.org (Tony Kay (JIRA)) Date: Tue, 13 Jan 2009 14:06:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3892) Some additional notes about using JBPM with Seam (States and API access) Message-ID: <31289240.1231873563998.JavaMail.jira@cloud.prod.atl2.jboss.com> Some additional notes about using JBPM with Seam (States and API access) ------------------------------------------------------------------------ Key: JBSEAM-3892 URL: https://jira.jboss.org/jira/browse/JBSEAM-3892 Project: Seam Issue Type: Task Components: Documentation Issues Affects Versions: 2.1.1.GA Reporter: Tony Kay Attachments: jBPM-patch I have written an addition to the jBPM section of the reference guide which gives a quick example of using jBPM process states in addition to tasks. This gives new users a bit more exposure to the power of jBPM, and also gives them some leads on how to access the jBPM processes when the Seam API does not cover a use-case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 13 14:06:04 2009 From: jira-events at lists.jboss.org (Tony Kay (JIRA)) Date: Tue, 13 Jan 2009 14:06:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3892) Some additional notes about using JBPM with Seam (States and API access) In-Reply-To: <31289240.1231873563998.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <7526026.1231873564205.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Kay updated JBSEAM-3892: ----------------------------- Attachment: jBPM-patch A patch to the jbpm XML file. Media file required (to follow) > Some additional notes about using JBPM with Seam (States and API access) > ------------------------------------------------------------------------ > > Key: JBSEAM-3892 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3892 > Project: Seam > Issue Type: Task > Components: Documentation Issues > Affects Versions: 2.1.1.GA > Reporter: Tony Kay > Attachments: jBPM-patch > > > I have written an addition to the jBPM section of the reference guide which gives a quick example of using jBPM process states in addition to tasks. This gives new users a bit more exposure to the power of jBPM, and also gives them some leads on how to access the jBPM processes when the Seam API does not cover a use-case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 13 14:08:14 2009 From: jira-events at lists.jboss.org (Tony Kay (JIRA)) Date: Tue, 13 Jan 2009 14:08:14 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3892) Some additional notes about using JBPM with Seam (States and API access) In-Reply-To: <31289240.1231873563998.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <6441026.1231873694136.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Kay updated JBSEAM-3892: ----------------------------- Attachment: plugin-jbpm-processstates.png PNG of the process described in the documentation patch. > Some additional notes about using JBPM with Seam (States and API access) > ------------------------------------------------------------------------ > > Key: JBSEAM-3892 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3892 > Project: Seam > Issue Type: Task > Components: Documentation Issues > Affects Versions: 2.1.1.GA > Reporter: Tony Kay > Attachments: jBPM-patch, plugin-jbpm-processstates.png > > > I have written an addition to the jBPM section of the reference guide which gives a quick example of using jBPM process states in addition to tasks. This gives new users a bit more exposure to the power of jBPM, and also gives them some leads on how to access the jBPM processes when the Seam API does not cover a use-case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 13 14:30:14 2009 From: jira-events at lists.jboss.org (Tony Herstell (JIRA)) Date: Tue, 13 Jan 2009 14:30:14 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3555) SeamMailAgain In-Reply-To: <3978595.1223977760796.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <3737402.1231875014238.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12447655#action_12447655 ] Tony Herstell commented on JBSEAM-3555: --------------------------------------- You are lucky as I can't get the EJB3 timer to work with seam mail asynch. > SeamMailAgain > ------------- > > Key: JBSEAM-3555 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3555 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.0.CR1 > Environment: JBoss AS 4.2.1.GA > JBoss Seam 2.1.0-SNAPSHOT (10.10. HudsonNo330) > Reporter: Markus Heidt > Assignee: Pete Muir > Fix For: 2.1.2.CR1 > > Attachments: RendererFacesContextFactory.java, server.log > > > Simple Mailing via Renderer doesn't work. > 'Seam-gen'erated a new project and added a new action 'sendMail' > Added the line to the action code: > Renderer.instance().render("/simple.xhtml"); > simple.xhtml is a modified version of the seam example (without #{person}) > Error after executing the action: > 2008-10-14 11:40:21,847 FATAL [javax.enterprise.resource.webcontainer.jsf.application] org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > javax.faces.el.EvaluationException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:91) > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:91) > ... > Caused by: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory > at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:256) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 13 15:02:04 2009 From: jira-events at lists.jboss.org (Ga?l Beaudoin (JIRA)) Date: Tue, 13 Jan 2009 15:02:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3555) SeamMailAgain In-Reply-To: <3978595.1223977760796.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <4121653.1231876924295.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12447656#action_12447656 ] Ga?l Beaudoin commented on JBSEAM-3555: --------------------------------------- What's the issue ? Have you followed the seam documentation ? > SeamMailAgain > ------------- > > Key: JBSEAM-3555 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3555 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.0.CR1 > Environment: JBoss AS 4.2.1.GA > JBoss Seam 2.1.0-SNAPSHOT (10.10. HudsonNo330) > Reporter: Markus Heidt > Assignee: Pete Muir > Fix For: 2.1.2.CR1 > > Attachments: RendererFacesContextFactory.java, server.log > > > Simple Mailing via Renderer doesn't work. > 'Seam-gen'erated a new project and added a new action 'sendMail' > Added the line to the action code: > Renderer.instance().render("/simple.xhtml"); > simple.xhtml is a modified version of the seam example (without #{person}) > Error after executing the action: > 2008-10-14 11:40:21,847 FATAL [javax.enterprise.resource.webcontainer.jsf.application] org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > javax.faces.el.EvaluationException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:91) > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:91) > ... > Caused by: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory > at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:256) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 13 15:23:04 2009 From: jira-events at lists.jboss.org (Tony Herstell (JIRA)) Date: Tue, 13 Jan 2009 15:23:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3555) SeamMailAgain In-Reply-To: <3978595.1223977760796.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <26624086.1231878184078.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12447658#action_12447658 ] Tony Herstell commented on JBSEAM-3555: --------------------------------------- I dont want to clutter the JIRA... here are the details: http://www.seamframework.org/Community/SeamMailProblemNPE#comment58020 Seam J53RE ==> Seam 2.1.1. EJB3 RF3.2.2.SR1 JBoss 4.2.1.GA. (now old and I should move to 5 but people seem to having problems so waiting till they cool down). > SeamMailAgain > ------------- > > Key: JBSEAM-3555 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3555 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.0.CR1 > Environment: JBoss AS 4.2.1.GA > JBoss Seam 2.1.0-SNAPSHOT (10.10. HudsonNo330) > Reporter: Markus Heidt > Assignee: Pete Muir > Fix For: 2.1.2.CR1 > > Attachments: RendererFacesContextFactory.java, server.log > > > Simple Mailing via Renderer doesn't work. > 'Seam-gen'erated a new project and added a new action 'sendMail' > Added the line to the action code: > Renderer.instance().render("/simple.xhtml"); > simple.xhtml is a modified version of the seam example (without #{person}) > Error after executing the action: > 2008-10-14 11:40:21,847 FATAL [javax.enterprise.resource.webcontainer.jsf.application] org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > javax.faces.el.EvaluationException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:91) > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:91) > ... > Caused by: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory > at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:256) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 14 00:17:04 2009 From: jira-events at lists.jboss.org (Dain Kaplan (JIRA)) Date: Wed, 14 Jan 2009 00:17:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1242) Entity converter for managed Hibernate sessions In-Reply-To: <11713963.1177441653594.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <7138347.1231910224283.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12447688#action_12447688 ] Dain Kaplan commented on JBSEAM-1242: ------------------------------------- The attached workaround file (HibernateEntityConverter) does not compile. Half the import statements are also invalid, which is less than confidence inspiring. > Entity converter for managed Hibernate sessions > ----------------------------------------------- > > Key: JBSEAM-1242 > URL: https://jira.jboss.org/jira/browse/JBSEAM-1242 > Project: Seam > Issue Type: Feature Request > Components: Core > Affects Versions: 1.2.1.GA > Reporter: Patrick Ruhkopf > Assignee: Pete Muir > Priority: Minor > Fix For: 2.0.1.CR1 > > Attachments: components_xml_sample.txt, HibernateEntityConverter.java, taglib_extract.txt > > > The EntityConverter () only works with an EntityManager but not with Hibernate managed sessions. Please find attached a HibernateEntityConverter for 1.2.1 GA. > I didn't supply a patch yet, because, as petemuir pointed out, the current HEAD contains a lot of refactoring. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 14 02:22:04 2009 From: jira-events at lists.jboss.org (Jesper Tejlgaard Pedersen (JIRA)) Date: Wed, 14 Jan 2009 02:22:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1179) Security functions not working in dvdstore In-Reply-To: <13619049.1176457018413.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <11775662.1231917724009.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12447694#action_12447694 ] Jesper Tejlgaard Pedersen commented on JBSEAM-1179: --------------------------------------------------- Check my comment here: http://www.seamframework.org/Community/ClassNotFoundExceptionOnPostback > Security functions not working in dvdstore > ------------------------------------------ > > Key: JBSEAM-1179 > URL: https://jira.jboss.org/jira/browse/JBSEAM-1179 > Project: Seam > Issue Type: Bug > Components: JSF Integration, Security > Environment: AS 4.2 > Reporter: Pete Muir > Assignee: Shane Bryzak > Priority: Blocker > Fix For: 1.3.0.ALPHA > > > Replicate by logging in as manager and attempting to change the order process > 10:32:34,117 ERROR [STDERR] java.lang.ClassNotFoundException: org.jboss.seam.security.SecurityFunctions > 10:32:34,117 ERROR [STDERR] at java.lang.Class.forName(Ljava.lang.String;ZLjava.lang.ClassLoader;)Ljava.lang.Class;(Unknown Source) > 10:32:34,117 ERROR [STDERR] at java.lang.Class.forName(Ljava.lang.String;I)Ljava.lang.Class;(Unknown Source) > 10:32:34,117 ERROR [STDERR] at org.apache.el.lang.FunctionMapperImpl$Function.getMethod(FunctionMapperImpl.java:147) > 10:32:34,117 ERROR [STDERR] at org.apache.el.lang.FunctionMapperImpl.resolveFunction(FunctionMapperImpl.java:53) > 10:32:34,117 ERROR [STDERR] at org.apache.el.parser.AstFunction.getValue(AstFunction.java:71) > 10:32:34,117 ERROR [STDERR] at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) > 10:32:34,117 ERROR [STDERR] at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:71) > 10:32:34,117 ERROR [STDERR] at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:384) > 10:32:34,117 ERROR [STDERR] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:981) > 10:32:34,117 ERROR [STDERR] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:989) > 10:32:34,117 ERROR [STDERR] at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:494) > 10:32:34,117 ERROR [STDERR] at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:101) > 10:32:34,117 ERROR [STDERR] at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248) > 10:32:34,117 ERROR [STDERR] at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) > 10:32:34,117 ERROR [STDERR] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) > 10:32:34,117 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > 10:32:34,117 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:63) > 10:32:34,117 ERROR [STDERR] at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:60) > 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) > 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) > 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57) > 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) > 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:79) > 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) > 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84) > 10:32:34,117 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > 10:32:34,117 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > 10:32:34,117 ERROR [STDERR] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > 10:32:34,117 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > 10:32:34,117 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > 10:32:34,117 WARN [lifecycle] javax.el.ELException: /WEB-INF/incl/stats.xhtml @7,49 rendered="#{s:hasRole('admin')}": Function 's:hasRole' not found > javax.faces.FacesException: javax.el.ELException: /WEB-INF/incl/stats.xhtml @7,49 rendered="#{s:hasRole('admin')}": Function 's:hasRole' not found > at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:387) > at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:981) > at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:989) > at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:494) > at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:101) > at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248) > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:63) > at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:60) > at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57) > at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) > at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:79) > at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) > at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:228) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 14 02:35:04 2009 From: jira-events at lists.jboss.org (Jesper Tejlgaard Pedersen (JIRA)) Date: Wed, 14 Jan 2009 02:35:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1179) Security functions not working in dvdstore In-Reply-To: <13619049.1176457018413.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <14539005.1231918504169.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12447696#action_12447696 ] Jesper Tejlgaard Pedersen commented on JBSEAM-1179: --------------------------------------------------- In above comment I should have mentioned, that anyone reading this issue and still needing an explanation for the ClassNotFoundException occuring with EL functions can read the above link. > Security functions not working in dvdstore > ------------------------------------------ > > Key: JBSEAM-1179 > URL: https://jira.jboss.org/jira/browse/JBSEAM-1179 > Project: Seam > Issue Type: Bug > Components: JSF Integration, Security > Environment: AS 4.2 > Reporter: Pete Muir > Assignee: Shane Bryzak > Priority: Blocker > Fix For: 1.3.0.ALPHA > > > Replicate by logging in as manager and attempting to change the order process > 10:32:34,117 ERROR [STDERR] java.lang.ClassNotFoundException: org.jboss.seam.security.SecurityFunctions > 10:32:34,117 ERROR [STDERR] at java.lang.Class.forName(Ljava.lang.String;ZLjava.lang.ClassLoader;)Ljava.lang.Class;(Unknown Source) > 10:32:34,117 ERROR [STDERR] at java.lang.Class.forName(Ljava.lang.String;I)Ljava.lang.Class;(Unknown Source) > 10:32:34,117 ERROR [STDERR] at org.apache.el.lang.FunctionMapperImpl$Function.getMethod(FunctionMapperImpl.java:147) > 10:32:34,117 ERROR [STDERR] at org.apache.el.lang.FunctionMapperImpl.resolveFunction(FunctionMapperImpl.java:53) > 10:32:34,117 ERROR [STDERR] at org.apache.el.parser.AstFunction.getValue(AstFunction.java:71) > 10:32:34,117 ERROR [STDERR] at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) > 10:32:34,117 ERROR [STDERR] at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:71) > 10:32:34,117 ERROR [STDERR] at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:384) > 10:32:34,117 ERROR [STDERR] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:981) > 10:32:34,117 ERROR [STDERR] at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:989) > 10:32:34,117 ERROR [STDERR] at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:494) > 10:32:34,117 ERROR [STDERR] at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:101) > 10:32:34,117 ERROR [STDERR] at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248) > 10:32:34,117 ERROR [STDERR] at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) > 10:32:34,117 ERROR [STDERR] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) > 10:32:34,117 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > 10:32:34,117 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:63) > 10:32:34,117 ERROR [STDERR] at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:60) > 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) > 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) > 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57) > 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) > 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:79) > 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) > 10:32:34,117 ERROR [STDERR] at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84) > 10:32:34,117 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > 10:32:34,117 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > 10:32:34,117 ERROR [STDERR] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > 10:32:34,117 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > 10:32:34,117 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > 10:32:34,117 WARN [lifecycle] javax.el.ELException: /WEB-INF/incl/stats.xhtml @7,49 rendered="#{s:hasRole('admin')}": Function 's:hasRole' not found > javax.faces.FacesException: javax.el.ELException: /WEB-INF/incl/stats.xhtml @7,49 rendered="#{s:hasRole('admin')}": Function 's:hasRole' not found > at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:387) > at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:981) > at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:989) > at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:494) > at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:101) > at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248) > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:63) > at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:60) > at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57) > at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) > at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:79) > at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) > at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:228) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 14 03:39:04 2009 From: jira-events at lists.jboss.org (Guy Di Fulvio (JIRA)) Date: Wed, 14 Jan 2009 03:39:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3774) Interpolator does not support # in choice/MessageFormat does In-Reply-To: <2531307.1228218456431.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <4472236.1231922344182.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12447704#action_12447704 ] Guy Di Fulvio commented on JBSEAM-3774: --------------------------------------- It seams the issue has been fixed in 2.1.0, I checked the code. The problem was occuring when params where null and MessageFormat was expecting params. The fix is the following: if (params.length == 0) { builder.append(expr.toString()); } else { String value = new MessageFormat(expr.toString(), Locale.instance()).format(params); builder.append(value); } In 2.0.3CR1 the test on params.length was not there... try to use MessageFormat with a choice and a params length to 0 and you will see. So we can say it is fixed. > Interpolator does not support # in choice/MessageFormat does > ------------------------------------------------------------ > > Key: JBSEAM-3774 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3774 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.0.3.CR1, 2.1.0.CR1 > Reporter: Guy Di Fulvio > Assignee: Norman Richards > Priority: Minor > Fix For: 2.1.2.CR1 > > > In my properties file: > my.choice.message = {0,choice,0#No choice|1# 1 choice|1< {0,number,integer} choices} > This is working with MessageFormat but Interpolator returns only {0} and my choices are lost. > After checking the code the problem is coming from the #. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 14 05:20:04 2009 From: jira-events at lists.jboss.org (Jozef Hartinger (JIRA)) Date: Wed, 14 Jan 2009 05:20:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3473) seambay example throws an exception when viewing "Whistler's Mother" item In-Reply-To: <26399691.1222703125603.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <28618896.1231928404075.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jozef Hartinger updated JBSEAM-3473: ------------------------------------ Fix Version/s: 2.1.2.CR1 Assignee: Shane Bryzak > seambay example throws an exception when viewing "Whistler's Mother" item > ------------------------------------------------------------------------- > > Key: JBSEAM-3473 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3473 > Project: Seam > Issue Type: Bug > Components: Examples > Affects Versions: 2.1.0.CR1 > Environment: jdk5 > JBoss AS 4.2.3 > Reporter: Jozef Hartinger > Assignee: Shane Bryzak > Priority: Minor > Fix For: 2.1.2.CR1 > > > When attempting to view the "Whistler's Mother" item the browser shows a JSF error page, and the exception below is in the logs: > Caused by: line 1:346: unexpected char: 0xFFFD > at org.jboss.seam.text.SeamTextLexer.nextToken(SeamTextLexer.java:230) > at antlr.TokenBuffer.fill(Unknown Source) > at antlr.TokenBuffer.LA(Unknown Source) > at antlr.LLkParser.LA(Unknown Source) > at org.jboss.seam.text.SeamTextParser.line(SeamTextParser.java:651) > at org.jboss.seam.text.SeamTextParser.paragraph(SeamTextParser.java:401) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 14 05:25:03 2009 From: jira-events at lists.jboss.org (Jozef Hartinger (JIRA)) Date: Wed, 14 Jan 2009 05:25:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3893) Seambay example - debug page after submitting empty registration form Message-ID: <27956112.1231928703980.JavaMail.jira@cloud.prod.atl2.jboss.com> Seambay example - debug page after submitting empty registration form --------------------------------------------------------------------- Key: JBSEAM-3893 URL: https://jira.jboss.org/jira/browse/JBSEAM-3893 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.1.GA Environment: JDK 5 JBoss AS 4.2.3.GA Reporter: Jozef Hartinger Assignee: Jozef Hartinger Priority: Minor Fix For: 2.1.2.CR1 Submitting empty registration results into debug page caused by org.hibernate.validator.InvalidStateException -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 14 05:39:04 2009 From: jira-events at lists.jboss.org (Jozef Hartinger (JIRA)) Date: Wed, 14 Jan 2009 05:39:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3893) Seambay example - debug page after submitting empty registration form In-Reply-To: <27956112.1231928703980.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <5505083.1231929544156.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jozef Hartinger updated JBSEAM-3893: ------------------------------------ Assignee: Shane Bryzak (was: Jozef Hartinger) > Seambay example - debug page after submitting empty registration form > --------------------------------------------------------------------- > > Key: JBSEAM-3893 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3893 > Project: Seam > Issue Type: Bug > Components: Examples > Affects Versions: 2.1.1.GA > Environment: JDK 5 > JBoss AS 4.2.3.GA > Reporter: Jozef Hartinger > Assignee: Shane Bryzak > Priority: Minor > Fix For: 2.1.2.CR1 > > > Submitting empty registration results into debug page caused by org.hibernate.validator.InvalidStateException -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 14 11:56:05 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Wed, 14 Jan 2009 11:56:05 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3774) Interpolator does not support # in choice/MessageFormat does In-Reply-To: <2531307.1228218456431.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <27935645.1231952165922.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3774. ----------------------------------- Resolution: Out of Date > Interpolator does not support # in choice/MessageFormat does > ------------------------------------------------------------ > > Key: JBSEAM-3774 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3774 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.0.3.CR1, 2.1.0.CR1 > Reporter: Guy Di Fulvio > Assignee: Norman Richards > Priority: Minor > Fix For: 2.1.2.CR1 > > > In my properties file: > my.choice.message = {0,choice,0#No choice|1# 1 choice|1< {0,number,integer} choices} > This is working with MessageFormat but Interpolator returns only {0} and my choices are lost. > After checking the code the problem is coming from the #. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 14 11:58:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Wed, 14 Jan 2009 11:58:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3781) Interpolator does not support {0,date,short} {0,time,short} {0,number,integer} In-Reply-To: <6703031.1228376926658.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <355566.1231952284069.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3781. ----------------------------------- Resolution: Out of Date > Interpolator does not support {0,date,short} {0,time,short} {0,number,integer} > -------------------------------------------------------------------------------- > > Key: JBSEAM-3781 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3781 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.0.3.CR1 > Reporter: Guy Di Fulvio > Assignee: Norman Richards > Priority: Minor > Fix For: 2.1.2.CR1 > > > In the interpolate method in Interpolator, you use : > new MessageFormat(expr.toString(), Locale.instance()).format(params); with params = Object[0], if in the expr you have {0,date,short} (an co) the returned value is modified in {0}. > You may use in this case new MessageFormat(expr.toString(), Locale.instance()).toPattern(); or something like that. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 14 13:34:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Wed, 14 Jan 2009 13:34:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3753) SeamResourceBundle.getBundle(String baseName) fails to return correct message based on Locale In-Reply-To: <11420851.1227561876694.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <16779965.1231958044212.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12447838#action_12447838 ] Norman Richards commented on JBSEAM-3753: ----------------------------------------- There's not a lot we can do. That is a static final method on ResourceBundle, so Seam can't override it. I can add a differently named function to do what you are doing, or you can just call the method the way you are, passing in the desired locale. > SeamResourceBundle.getBundle(String baseName) fails to return correct message based on Locale > --------------------------------------------------------------------------------------------- > > Key: JBSEAM-3753 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3753 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.0.2.SP1, 2.0.3.CR1, 2.1.1.CR1 > Reporter: Samuel Mendenhall > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > > When specifying the Locale directly, everything works as expected, when not, the default locale is used, which is incorrect. Ex. > log.info("SeamResourceBundle.getBundle w/o passing Local: " + SeamResourceBundle.getBundle("ECISConfig").getString("ecis.hello")); > log.info("SeamResourceBundle.getBundle w passing Local: " + SeamResourceBundle.getBundle("ECISConfig", LocaleSelector.instance().getLocale()).getString("ecis.hello")); > Produces: > 15:08:45,438 INFO [TestAction] SeamResourceBundle.getBundle w/o passing Local: Hello from ECISConfig_en.properties > 15:08:45,439 INFO [TestAction] SeamResourceBundle.getBundle w passing Local: Hello from ECISConfig_en_US_tmwa.properties > When both should be saying "Hello from ECISConfig_en_US_tmwa.properties" because the locale and resource bundle are defined in components.xml as: > > > > messages > ECISConfig > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 14 19:19:07 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Wed, 14 Jan 2009 19:19:07 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-3888) QueryParser to restrictive, does not allow hash sign (#) in string literal In-Reply-To: <13667977.1231516384634.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <33528535.1231978747441.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards reassigned JBSEAM-3888: --------------------------------------- Assignee: Norman Richards > QueryParser to restrictive, does not allow hash sign (#) in string literal > -------------------------------------------------------------------------- > > Key: JBSEAM-3888 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3888 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.1.1.GA > Environment: jboss-seam-2.0.2.SP1, hibernate-entitymanager-3.4.0.GA, spring-2.5.6 > Reporter: David Rosell > Assignee: Norman Richards > > The QueryParser are to restrictive when validating a query expression. > It is not possible to use a hash sign (#) in a String literal query expression. > An IllegalArgumentException are thrown for this query: > String ejbql = "SELECT s FROM Service s WHERE s.name = 'DB#CORE' "; > Query q = em.createQuery(ejbql); > Rather than using: > StringTokenizer tokens = new StringTokenizer(ejbql, "#}", true); > it would be better to be more precise in selecting what should be processed, use regexp and splitting the ejbql expression for #{...} instead. > Exception stacktrace: > java.lang.IllegalArgumentException: missing { after # in query fragment > at org.jboss.seam.persistence.QueryParser.(QueryParser.java:52) > at org.jboss.seam.persistence.QueryParser.(QueryParser.java:33) > at org.jboss.seam.persistence.EntityManagerProxy.createQuery(EntityManagerProxy.java:66) > at sun.reflect.GeneratedMethodAccessor72.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.seam.ioc.spring.SeamManagedEntityManagerFactory$SeamManagedPersistenceContextHandler.invoke(SeamManagedEntityManagerFactory.java:142) > at $Proxy71.createQuery(Unknown Source) > at sun.reflect.GeneratedMethodAccessor72.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.springframework.orm.jpa.SharedEntityManagerCreator$SharedEntityManagerInvocationHandler.invoke(SharedEntityManagerCreator.java:198) > at $Proxy58.createQuery(Unknown Source) > at com.ford.volvocars.r2r.db.jpa.GenericDaoJpa.executeJpaQuery(GenericDaoJpa.java:40) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 14 22:07:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Wed, 14 Jan 2009 22:07:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-3883) URL rewriting broken for view-id of redirects in exceptions In-Reply-To: <31240748.1231313464202.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <11882032.1231988824221.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards reassigned JBSEAM-3883: --------------------------------------- Assignee: Norman Richards > URL rewriting broken for view-id of redirects in exceptions > ----------------------------------------------------------- > > Key: JBSEAM-3883 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3883 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.1.1.GA > Reporter: Stephen Friedrich > Assignee: Norman Richards > > When a configured exception handler redirects to a view-id, then the URL for that view-id is not processed by Seam's URL rewriting filter. > As a result you cannot re-write the URL for your login page if you want to redirect to the login page when a ViewExpiredSException occurs. > The problem is that the RewriteFilter is deeper in the filter chain than the ExceptionFilter, so at the time when the exception filter is handling an exception no RewritingResponse is on the chain of wrapped responses. > Norman RIchards suggested to split incoming and outgoing rewriting and place it at opposite ends of the filter chain. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 15 00:24:57 2009 From: jira-events at lists.jboss.org (Gerry Matte (JIRA)) Date: Thu, 15 Jan 2009 00:24:57 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3661) ldapIdentityStore assumes roles are attributes of users - please support groupOfNames with attributes that identify users in that role In-Reply-To: <25330694.1225782080762.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <20335582.1231997097753.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12447897#action_12447897 ] Gerry Matte commented on JBSEAM-3661: ------------------------------------- Hi Shane. In the referenced forum topic November 4, you indicated that you would add this support to version 2.1.1 Did you manage to do so ? Since we use LDAP for authentication (and soon for authorisation) we are waiting with great anticipation. Thanks Gerry > ldapIdentityStore assumes roles are attributes of users - please support groupOfNames with attributes that identify users in that role > -------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBSEAM-3661 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3661 > Project: Seam > Issue Type: Feature Request > Components: Security > Affects Versions: 2.1.0.SP1 > Environment: All SEAM supported environments > Reporter: Gerry Matte > Assignee: Shane Bryzak > > Please modify ldapIdentityStore to support the same (or equivalent) attributes as the Jboss login module LdapExtLoginModule. Currently the role attribute is assumed to be associated with the user object. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 15 04:13:04 2009 From: jira-events at lists.jboss.org (Kenneth Zhang (JIRA)) Date: Thu, 15 Jan 2009 04:13:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1788) s:graphicImage fails to transform GIF images In-Reply-To: <15111747.1186956300957.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <27250327.1232010784134.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12447936#action_12447936 ] Kenneth Zhang commented on JBSEAM-1788: --------------------------------------- yes. Cannot use to show the transform GIF image. > s:graphicImage fails to transform GIF images > -------------------------------------------- > > Key: JBSEAM-1788 > URL: https://jira.jboss.org/jira/browse/JBSEAM-1788 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.0.0.BETA1 > Environment: windows xp, JDK 1.6.0 > Reporter: henrik lindberg > Assignee: Pete Muir > Fix For: The future > > > The org.jboss.seam.ui.graphicImage.Image class fails to rescale GIF images. > This is caused by the use of BICUBIC INTERPOLATION not working for GIF images. > I see three solutions (tested in similar code in one of my servlets that suffered from the same problem): > - Use this rendering hint (in use now) > g2d.setRenderingHint(RenderingHints.KEY_INTERPOLATION, RenderingHints.VALUE_INTERPOLATION_BICUBIC); > but then change the format name to "png" when writing with image IO > - Use this rendering hint > g2d.setRenderingHint(RenderingHints.KEY_INTERPOLATION, RenderingHints.VALUE_INTERPOLATION_NEAREST_NEIGHBOR); > and render as "gif" > - Use NEAREST_NEIGHBOR if image is written as a GIF, and BICUBIC otherwise. > The combination INTERPOLATION_BICUBIC (as well as INTERPOLATION_LINEAR) simply does not work if the image is written with ImageIO in "gif" format. > The result is all white pixels. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 15 12:04:03 2009 From: jira-events at lists.jboss.org (Jay Balunas (JIRA)) Date: Thu, 15 Jan 2009 12:04:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3894) Upgrade to RichFaces 3.3.0.GA Message-ID: <1399517.1232039043969.JavaMail.jira@cloud.prod.atl2.jboss.com> Upgrade to RichFaces 3.3.0.GA ----------------------------- Key: JBSEAM-3894 URL: https://jira.jboss.org/jira/browse/JBSEAM-3894 Project: Seam Issue Type: Task Components: Build Reporter: Jay Balunas Priority: Critical Fix For: 2.1.2.CR1 RichFaces 3.3.0 has been released and Seam should upgrade to it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 16 02:57:05 2009 From: jira-events at lists.jboss.org (Nicklas Karlsson (JIRA)) Date: Fri, 16 Jan 2009 02:57:05 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-3458) UI control for in-page real-time viewing debug info on conversations, context contents, credentials etc In-Reply-To: <4422641.1222286360821.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <16330579.1232092625157.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicklas Karlsson reassigned JBSEAM-3458: ---------------------------------------- Assignee: Daniel Roth (was: Nicklas Karlsson) Tag. You're it! > UI control for in-page real-time viewing debug info on conversations, context contents, credentials etc > ------------------------------------------------------------------------------------------------------- > > Key: JBSEAM-3458 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3458 > Project: Seam > Issue Type: Feature Request > Components: JSF Controls > Reporter: Nicklas Karlsson > Assignee: Daniel Roth > Fix For: 2.1.2.CR1 > > Attachments: debug.html, screenshot-1.jpg > > > As discussed on the dev-list, it would be nice to have a s:debug control that would give summarized information on the state of the application -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 16 03:21:03 2009 From: jira-events at lists.jboss.org (Julien Kronegg (JIRA)) Date: Fri, 16 Jan 2009 03:21:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3895) org.jboss.seam.log.Logging.getLogProvider(String,boolean) should be made public Message-ID: <13897928.1232094064030.JavaMail.jira@cloud.prod.atl2.jboss.com> org.jboss.seam.log.Logging.getLogProvider(String,boolean) should be made public ------------------------------------------------------------------------------- Key: JBSEAM-3895 URL: https://jira.jboss.org/jira/browse/JBSEAM-3895 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.1.GA, 2.0.0.GA Environment: environment independent feature Reporter: Julien Kronegg Priority: Minor We would like to create our own implementation of the org.jboss.seam.log.Log interface, like it is done in the org.jboss.seam.log.LogImpl class. The goal is to enrich the log message by adding some information. Because the org.jboss.seam.log.Logging.getLogProvider(String,boolean) method has a default access mode, it is only callable from a class in the same package (which is the case for LogImpl). So the feature request is: please make the org.jboss.seam.log.Logging.getLogProvider(String,boolean) method as public. The workaround is to call the method by introspection: Method m = Logging.class.getDeclaredMethod("getLogProvider", new Class[] {String.class, boolean.class}); m.setAccessible(true); LogProvider log = (LogProvider)m.invoke(null, new Object[] {category, wrapped}); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 16 08:32:05 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Fri, 16 Jan 2009 08:32:05 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-3895) org.jboss.seam.log.Logging.getLogProvider(String,boolean) should be made public In-Reply-To: <13897928.1232094064030.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <22680454.1232112725263.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards reassigned JBSEAM-3895: --------------------------------------- Assignee: Norman Richards > org.jboss.seam.log.Logging.getLogProvider(String,boolean) should be made public > ------------------------------------------------------------------------------- > > Key: JBSEAM-3895 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3895 > Project: Seam > Issue Type: Feature Request > Components: Core > Affects Versions: 2.0.0.GA, 2.1.1.GA > Environment: environment independent feature > Reporter: Julien Kronegg > Assignee: Norman Richards > Priority: Minor > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > We would like to create our own implementation of the org.jboss.seam.log.Log interface, like it is done in the org.jboss.seam.log.LogImpl class. The goal is to enrich the log message by adding some information. > Because the org.jboss.seam.log.Logging.getLogProvider(String,boolean) method has a default access mode, it is only callable from a class in the same package (which is the case for LogImpl). > So the feature request is: please make the org.jboss.seam.log.Logging.getLogProvider(String,boolean) method as public. > The workaround is to call the method by introspection: > Method m = Logging.class.getDeclaredMethod("getLogProvider", new Class[] {String.class, boolean.class}); > m.setAccessible(true); > LogProvider log = (LogProvider)m.invoke(null, new Object[] {category, wrapped}); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 16 09:54:05 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Fri, 16 Jan 2009 09:54:05 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3895) org.jboss.seam.log.Logging.getLogProvider(String,boolean) should be made public In-Reply-To: <13897928.1232094064030.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <9763425.1232117645144.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards updated JBSEAM-3895: ------------------------------------ Fix Version/s: 2.1.2.CR1 > org.jboss.seam.log.Logging.getLogProvider(String,boolean) should be made public > ------------------------------------------------------------------------------- > > Key: JBSEAM-3895 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3895 > Project: Seam > Issue Type: Feature Request > Components: Core > Affects Versions: 2.0.0.GA, 2.1.1.GA > Environment: environment independent feature > Reporter: Julien Kronegg > Assignee: Norman Richards > Priority: Minor > Fix For: 2.1.2.CR1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > We would like to create our own implementation of the org.jboss.seam.log.Log interface, like it is done in the org.jboss.seam.log.LogImpl class. The goal is to enrich the log message by adding some information. > Because the org.jboss.seam.log.Logging.getLogProvider(String,boolean) method has a default access mode, it is only callable from a class in the same package (which is the case for LogImpl). > So the feature request is: please make the org.jboss.seam.log.Logging.getLogProvider(String,boolean) method as public. > The workaround is to call the method by introspection: > Method m = Logging.class.getDeclaredMethod("getLogProvider", new Class[] {String.class, boolean.class}); > m.setAccessible(true); > LogProvider log = (LogProvider)m.invoke(null, new Object[] {category, wrapped}); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 16 11:44:03 2009 From: jira-events at lists.jboss.org (Francisco Jose Peredo Noguez (JIRA)) Date: Fri, 16 Jan 2009 11:44:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3896) Use the DataTableScroller for pagination in seam-gen generated web applications Message-ID: <30282160.1232124243992.JavaMail.jira@cloud.prod.atl2.jboss.com> Use the DataTableScroller for pagination in seam-gen generated web applications ------------------------------------------------------------------------------- Key: JBSEAM-3896 URL: https://jira.jboss.org/jira/browse/JBSEAM-3896 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.1.GA Reporter: Francisco Jose Peredo Noguez Use the DataTableScroller for pagination in seam-gen generated web applications (Full AJAX pagination). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 16 11:50:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Fri, 16 Jan 2009 11:50:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3895) org.jboss.seam.log.Logging.getLogProvider(String,boolean) should be made public In-Reply-To: <13897928.1232094064030.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <21440242.1232124604270.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3895. ----------------------------------- Resolution: Done Done. > org.jboss.seam.log.Logging.getLogProvider(String,boolean) should be made public > ------------------------------------------------------------------------------- > > Key: JBSEAM-3895 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3895 > Project: Seam > Issue Type: Feature Request > Components: Core > Affects Versions: 2.0.0.GA, 2.1.1.GA > Environment: environment independent feature > Reporter: Julien Kronegg > Assignee: Norman Richards > Priority: Minor > Fix For: 2.1.2.CR1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > We would like to create our own implementation of the org.jboss.seam.log.Log interface, like it is done in the org.jboss.seam.log.LogImpl class. The goal is to enrich the log message by adding some information. > Because the org.jboss.seam.log.Logging.getLogProvider(String,boolean) method has a default access mode, it is only callable from a class in the same package (which is the case for LogImpl). > So the feature request is: please make the org.jboss.seam.log.Logging.getLogProvider(String,boolean) method as public. > The workaround is to call the method by introspection: > Method m = Logging.class.getDeclaredMethod("getLogProvider", new Class[] {String.class, boolean.class}); > m.setAccessible(true); > LogProvider log = (LogProvider)m.invoke(null, new Object[] {category, wrapped}); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 16 12:08:03 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Fri, 16 Jan 2009 12:08:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3891) openid fails on port 80 In-Reply-To: <30124007.1231774326077.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <12360195.1232125683980.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12448346#action_12448346 ] Norman Richards commented on JBSEAM-3891: ----------------------------------------- Comments in the forums. I'm not seeing the problem after all. I'll leave the issue open for comments, but if there's no new info, I'll close it in a while. > openid fails on port 80 > ----------------------- > > Key: JBSEAM-3891 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3891 > Project: Seam > Issue Type: Feature Request > Reporter: Norman Richards > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > > See forum posting -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 16 12:45:24 2009 From: jira-events at lists.jboss.org (Bryan Brouckaert (JIRA)) Date: Fri, 16 Jan 2009 12:45:24 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3897) MultipartRequest Error: 100% CPU (for 2.0.2.GA) or Missing data (for trunk) Message-ID: <21419101.1232127924157.JavaMail.jira@cloud.prod.atl2.jboss.com> MultipartRequest Error: 100% CPU (for 2.0.2.GA) or Missing data (for trunk) --------------------------------------------------------------------------- Key: JBSEAM-3897 URL: https://jira.jboss.org/jira/browse/JBSEAM-3897 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.0.2.GA, The future Environment: Seam 2.0.2.GA Reporter: Bryan Brouckaert Priority: Critical There is a fundamental error in MultipartRequest that causes 100% CPU usage in a very specific case. I had it for version 2.0.2.GA, but I saw in the code that the issue is still in the trunk. In the trunk version it will not caus 100% CPU, but the rest of the request will be ignored. The errors that cause it -------------------------------- 1) If a multipart header is longer then 2K, the class will at a certain point start reading blocks of 0 bytes. It does this because it only reads the amound of bytes that are still free in the buffer. Because the buffer is only 2 K big and a header must be entirely in the buffer in order to be processed, this can be 0 bytes if the header is bigger then 2 K. The trunk solves this by using a loop counter, while it should test if there is still place in the buffer before reading that amount of bytes. Of course, 2 K headers should not occur, but it should be detected. 2) The code assumes that the CR-LF that devides the data and the headers are in the same block of the buffer as the header itself. If this isn't the case (you must be unlucky for this to happen) the emtpy line isn't treated as the divider between headers and data but as a header itself. Because the empty lines is treated as a header, the data below it is also treated as a header. Because data can easly be more then 2 K, you get quickly into error 1. I had a case where the first 2K of the request is always the same for a specific user. Unfortuantely, the only part that did not fit in the first 2K was the viewstate, which is easly bigger then 2K. Because the boundary has a random number, the size varried slightly and for about 50% of the requests made by a certain user we got the above problem. The only thing the "fix" of the trunk would have done, is throwing an error instaid of using 100% CPU but the user would have been very unhapy. My solution to the problem ------------------------------------ I did not have time to wait for a fix, I do use seam for a very critical healthcare platform, I fixed it myself. 1) Dynamicly growning buffers in case the headers are bigger then 2K. At 128 K I throw an error, no header should be longer then that (probably that is more then frendly enough) 2) Check if a header isn't an empty line, if so threat it as the devider between the header and data. Some closure notes ---------------------------- I included the patched version (2.0.2.GA) that I'm using now. My unlucky user confirmed that it solved the problem, all his files where uploaded without any problem. The loopcount is a good idea, it is always possible that a stream keeps returning 0 bytes even if you request more then that. But I assure you, that was not the problem, the problem was that the code only requested 0 bytes. I have a 1.8 G logfile to prove it, and I will send it to you if you don't beleave me ;-) I had to add some TRACE info in order find the solution. Since nobody in his right mind has trace on by default I left it in. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 16 12:59:04 2009 From: jira-events at lists.jboss.org (Bryan Brouckaert (JIRA)) Date: Fri, 16 Jan 2009 12:59:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3897) MultipartRequest Error: 100% CPU (for 2.0.2.GA) or Missing data (for trunk) In-Reply-To: <21419101.1232127924157.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <33457039.1232128744092.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Brouckaert updated JBSEAM-3897: ------------------------------------- Attachment: MultipartRequest.java Fixed version of MultipartRequest (2.0.2.GA) Solution for problem 1: Line 463-464: Dynamic buffer size (limited) Solution for problem 2: Line 331 & 350: check if empty header Line 353: was emtpy header, so do not exclude empty line > MultipartRequest Error: 100% CPU (for 2.0.2.GA) or Missing data (for trunk) > --------------------------------------------------------------------------- > > Key: JBSEAM-3897 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3897 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.0.2.GA, The future > Environment: Seam 2.0.2.GA > Reporter: Bryan Brouckaert > Priority: Critical > Attachments: MultipartRequest.java > > > There is a fundamental error in MultipartRequest that causes 100% CPU usage in a very specific case. I had it for version 2.0.2.GA, but I saw in the code that the issue is still in the trunk. In the trunk version it will not caus 100% CPU, but the rest of the request will be ignored. > The errors that cause it > -------------------------------- > 1) If a multipart header is longer then 2K, the class will at a certain point start reading blocks of 0 bytes. It does this because it only reads the amound of bytes that are still free in the buffer. Because the buffer is only 2 K big and a header must be entirely in the buffer in order to be processed, this can be 0 bytes if the header is bigger then 2 K. The trunk solves this by using a loop counter, while it should test if there is still place in the buffer before reading that amount of bytes. Of course, 2 K headers should not occur, but it should be detected. > 2) The code assumes that the CR-LF that devides the data and the headers are in the same block of the buffer as the header itself. If this isn't the case (you must be unlucky for this to happen) the emtpy line isn't treated as the divider between headers and data but as a header itself. Because the empty lines is treated as a header, the data below it is also treated as a header. Because data can easly be more then 2 K, you get quickly into error 1. > I had a case where the first 2K of the request is always the same for a specific user. Unfortuantely, the only part that did not fit in the first 2K was the viewstate, which is easly bigger then 2K. Because the boundary has a random number, the size varried slightly and for about 50% of the requests made by a certain user we got the above problem. The only thing the "fix" of the trunk would have done, is throwing an error instaid of using 100% CPU but the user would have been very unhapy. > My solution to the problem > ------------------------------------ > I did not have time to wait for a fix, I do use seam for a very critical healthcare platform, I fixed it myself. > 1) Dynamicly growning buffers in case the headers are bigger then 2K. At 128 K I throw an error, no header should be longer then that (probably that is more then frendly enough) > 2) Check if a header isn't an empty line, if so threat it as the devider between the header and data. > Some closure notes > ---------------------------- > I included the patched version (2.0.2.GA) that I'm using now. My unlucky user confirmed that it solved the problem, all his files where uploaded without any problem. > The loopcount is a good idea, it is always possible that a stream keeps returning 0 bytes even if you request more then that. But I assure you, that was not the problem, the problem was that the code only requested 0 bytes. I have a 1.8 G logfile to prove it, and I will send it to you if you don't beleave me ;-) > I had to add some TRACE info in order find the solution. Since nobody in his right mind has trace on by default I left it in. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 16 14:32:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Fri, 16 Jan 2009 14:32:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3888) QueryParser to restrictive, does not allow hash sign (#) in string literal In-Reply-To: <13667977.1231516384634.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <21796285.1232134324174.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3888. ----------------------------------- Fix Version/s: 2.1.2.CR1 Resolution: Done Thanks. I've fixed this in trunk. Even though the parsing mechanism here is quite poor, I'm hesitant to make any large changes to the way it works. Instead, I've made the minimum change I could to allow non-expression uses of # without changing the overall mechanism. Please let me know if it it works for you. > QueryParser to restrictive, does not allow hash sign (#) in string literal > -------------------------------------------------------------------------- > > Key: JBSEAM-3888 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3888 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.1.1.GA > Environment: jboss-seam-2.0.2.SP1, hibernate-entitymanager-3.4.0.GA, spring-2.5.6 > Reporter: David Rosell > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > > The QueryParser are to restrictive when validating a query expression. > It is not possible to use a hash sign (#) in a String literal query expression. > An IllegalArgumentException are thrown for this query: > String ejbql = "SELECT s FROM Service s WHERE s.name = 'DB#CORE' "; > Query q = em.createQuery(ejbql); > Rather than using: > StringTokenizer tokens = new StringTokenizer(ejbql, "#}", true); > it would be better to be more precise in selecting what should be processed, use regexp and splitting the ejbql expression for #{...} instead. > Exception stacktrace: > java.lang.IllegalArgumentException: missing { after # in query fragment > at org.jboss.seam.persistence.QueryParser.(QueryParser.java:52) > at org.jboss.seam.persistence.QueryParser.(QueryParser.java:33) > at org.jboss.seam.persistence.EntityManagerProxy.createQuery(EntityManagerProxy.java:66) > at sun.reflect.GeneratedMethodAccessor72.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.seam.ioc.spring.SeamManagedEntityManagerFactory$SeamManagedPersistenceContextHandler.invoke(SeamManagedEntityManagerFactory.java:142) > at $Proxy71.createQuery(Unknown Source) > at sun.reflect.GeneratedMethodAccessor72.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.springframework.orm.jpa.SharedEntityManagerCreator$SharedEntityManagerInvocationHandler.invoke(SharedEntityManagerCreator.java:198) > at $Proxy58.createQuery(Unknown Source) > at com.ford.volvocars.r2r.db.jpa.GenericDaoJpa.executeJpaQuery(GenericDaoJpa.java:40) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 16 14:46:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Fri, 16 Jan 2009 14:46:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3595) Concurrent problem with BasicContext In-Reply-To: <27780487.1224566120808.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <7304580.1232135164161.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3595. ----------------------------------- Fix Version/s: (was: 2.1.2.CR1) Resolution: Incomplete Description No response for several months. This looks like debug mode to me. If that isn't it, please reopen with more info. > Concurrent problem with BasicContext > ------------------------------------ > > Key: JBSEAM-3595 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3595 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.0.2.SP1 > Reporter: Jonah Lee > Attachments: components.xml > > > When I run concurrent test for my SEAM application with 10 concurrent users, I got the error below and my application still run. > 2008-10-20 14:59:39,162 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/csms]] Session event listener threw exception > java.lang.ArrayIndexOutOfBoundsException: 195 > at org.jboss.seam.contexts.BasicContext.getNames(BasicContext.java:60) > at org.jboss.seam.contexts.Contexts.startup(Contexts.java:270) > at org.jboss.seam.contexts.Lifecycle.beginSession(Lifecycle.java:191) > at org.jboss.seam.contexts.ServletLifecycle.beginSession(ServletLifecycle.java:124) > at org.jboss.seam.servlet.SeamListener.sessionCreated(SeamListener.java:44) > at org.apache.catalina.session.StandardSession.tellNew(StandardSession.java:397) > at org.apache.catalina.session.StandardSession.setId(StandardSession.java:369) > at org.apache.catalina.session.ManagerBase.createSession(ManagerBase.java:828) > at org.apache.catalina.session.StandardManager.createSession(StandardManager.java:291) > at org.apache.catalina.connector.Request.doGetSession(Request.java:2312) > at org.apache.catalina.connector.Request.getSession(Request.java:2075) > at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:833) > at com.sun.faces.context.SessionMap.getSession(ExternalContextImpl.java:1002) > at com.sun.faces.context.SessionMap.get(ExternalContextImpl.java:962) > at org.jboss.seam.contexts.BasicContext.get(BasicContext.java:48) > at org.jboss.seam.Component.getInstance(Component.java:1854) > at org.jboss.seam.Component.getInstance(Component.java:1832) > at org.jboss.seam.web.Session.getInstance(Session.java:122) > at org.jboss.seam.contexts.FacesLifecycle.beginRequest(FacesLifecycle.java:54) > at org.jboss.seam.jsf.SeamPhaseListener.beforeRestoreView(SeamPhaseListener.java:377) > at org.jboss.seam.jsf.SeamPhaseListener.beforeServletPhase(SeamPhaseListener.java:137) > at org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:114) > at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:222) > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) > at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:154) > at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:260) > at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:366) > at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:493) > at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) > at java.lang.Thread.run(Thread.java:595) > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 16 14:53:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Fri, 16 Jan 2009 14:53:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3566) Conversation.isLongRunning() causes NPE In-Reply-To: <4204870.1224068180728.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <6304517.1232135584500.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards updated JBSEAM-3566: ------------------------------------ Fix Version/s: (was: 2.1.2.CR1) > Conversation.isLongRunning() causes NPE > --------------------------------------- > > Key: JBSEAM-3566 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3566 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.0.3.CR1 > Environment: JBoss 4.2.2, Seam 2.0.3.CR1 > Reporter: Nikolay Elenkov > Attachments: trace.log > > > I have a couple of methods that log conversation start/end for debugging purposes in may app. > The code is pretty simple: > @Observer(value = "org.jboss.seam.beginConversation") > public void onConversationStart() { > log.debug("CONVERSATION Started"); > Conversation c = Conversation.instance(); > log.debug(String.format("id: %s; isLongRunning %s; viewId: %s", > c.getId(), c.isLongRunning(), c.getViewId())); > } > Most of the time that works OK, but I get an occasional NPE, seems to happen when > you access the app right after JBoss has started. Here is the trace: > Caused by: java.lang.NullPointerException > at org.jboss.seam.core.Manager.isReallyLongRunningConversation(Manager.java:230) > at org.jboss.seam.core.Conversation.isLongRunning(Conversation.java:308) > at myapp.LoggerBean.onConversationEnd(LoggerBean.java:145) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sat Jan 17 11:18:06 2009 From: jira-events at lists.jboss.org (Przemyslaw Jaskierski (JIRA)) Date: Sat, 17 Jan 2009 11:18:06 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3897) MultipartRequest Error: 100% CPU (for 2.0.2.GA) or Missing data (for trunk) In-Reply-To: <21419101.1232127924157.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <6335292.1232209086351.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12448401#action_12448401 ] Przemyslaw Jaskierski commented on JBSEAM-3897: ----------------------------------------------- Thanks for sharing this. I'm pretty sure I've just run into the same problem but I'm weeks behind schedule and had no time to try to deal with this. Still stuck to early Seam 2.1.x CR builds. Great, great job and thanks again :) > MultipartRequest Error: 100% CPU (for 2.0.2.GA) or Missing data (for trunk) > --------------------------------------------------------------------------- > > Key: JBSEAM-3897 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3897 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.0.2.GA, The future > Environment: Seam 2.0.2.GA > Reporter: Bryan Brouckaert > Priority: Critical > Attachments: MultipartRequest.java > > > There is a fundamental error in MultipartRequest that causes 100% CPU usage in a very specific case. I had it for version 2.0.2.GA, but I saw in the code that the issue is still in the trunk. In the trunk version it will not caus 100% CPU, but the rest of the request will be ignored. > The errors that cause it > -------------------------------- > 1) If a multipart header is longer then 2K, the class will at a certain point start reading blocks of 0 bytes. It does this because it only reads the amound of bytes that are still free in the buffer. Because the buffer is only 2 K big and a header must be entirely in the buffer in order to be processed, this can be 0 bytes if the header is bigger then 2 K. The trunk solves this by using a loop counter, while it should test if there is still place in the buffer before reading that amount of bytes. Of course, 2 K headers should not occur, but it should be detected. > 2) The code assumes that the CR-LF that devides the data and the headers are in the same block of the buffer as the header itself. If this isn't the case (you must be unlucky for this to happen) the emtpy line isn't treated as the divider between headers and data but as a header itself. Because the empty lines is treated as a header, the data below it is also treated as a header. Because data can easly be more then 2 K, you get quickly into error 1. > I had a case where the first 2K of the request is always the same for a specific user. Unfortuantely, the only part that did not fit in the first 2K was the viewstate, which is easly bigger then 2K. Because the boundary has a random number, the size varried slightly and for about 50% of the requests made by a certain user we got the above problem. The only thing the "fix" of the trunk would have done, is throwing an error instaid of using 100% CPU but the user would have been very unhapy. > My solution to the problem > ------------------------------------ > I did not have time to wait for a fix, I do use seam for a very critical healthcare platform, I fixed it myself. > 1) Dynamicly growning buffers in case the headers are bigger then 2K. At 128 K I throw an error, no header should be longer then that (probably that is more then frendly enough) > 2) Check if a header isn't an empty line, if so threat it as the devider between the header and data. > Some closure notes > ---------------------------- > I included the patched version (2.0.2.GA) that I'm using now. My unlucky user confirmed that it solved the problem, all his files where uploaded without any problem. > The loopcount is a good idea, it is always possible that a stream keeps returning 0 bytes even if you request more then that. But I assure you, that was not the problem, the problem was that the code only requested 0 bytes. I have a 1.8 G logfile to prove it, and I will send it to you if you don't beleave me ;-) > I had to add some TRACE info in order find the solution. Since nobody in his right mind has trace on by default I left it in. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Jan 18 19:07:04 2009 From: jira-events at lists.jboss.org (Devon Hillard (JIRA)) Date: Sun, 18 Jan 2009 19:07:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2419) IAE: factory method with defined scope outjected a value: guestRole In-Reply-To: <18383174.1198179708517.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <2714638.1232323624335.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12448451#action_12448451 ] Devon Hillard commented on JBSEAM-2419: --------------------------------------- I also think it is a concurrency issue. I have the same error from my application. I have a rich:column which is filtered based on user input. If I type too quickly in the filter box I get the error: java.lang.IllegalArgumentException: factory method with defined scope outjected a value: If I type slowly, I do not get the error. The only difference is how rapidly the AJAX requests are made to the server. > IAE: factory method with defined scope outjected a value: guestRole > ------------------------------------------------------------------- > > Key: JBSEAM-2419 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2419 > Project: Seam > Issue Type: Bug > Components: Core > Reporter: Christian Bauer > Priority: Minor > > I can see this on the log on seamframework.org but can't reproduce it: > java.lang.IllegalArgumentException: factory method with defined scope outjected a value: guestRole > at org.jboss.seam.Component.handleFactoryMethodResult(Component.java:1953) > at org.jboss.seam.Component.getInstanceFromFactory(Component.java:1927) > at org.jboss.seam.Component.getInstance(Component.java:1863) > at org.jboss.seam.Component.getInstance(Component.java:1840) > at org.jboss.seam.Component.getInstance(Component.java:1834) > at org.jboss.seam.wiki.core.action.Authenticator.getGuestAccessLevel(Authenticator.java:199) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) > at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) > at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) > at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:31) > at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) > at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:46) > at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) > at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42) > at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) > at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) > at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166) > at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102) > at org.jboss.seam.wiki.core.action.Authenticator_$$_javassist_9.getGuestAccessLevel(Authenticator_$$_javassist_9.java) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) > at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:125) > at org.jboss.seam.Component.callComponentMethod(Component.java:2082) > at org.jboss.seam.Component.getInstanceFromFactory(Component.java:1926) > at org.jboss.seam.Component.getInstance(Component.java:1863) > at org.jboss.seam.Component.getInstance(Component.java:1840) > at org.jboss.seam.Namespace.getComponentInstance(Namespace.java:55) > at org.jboss.seam.Namespace.getComponentInstance(Namespace.java:50) > at org.jboss.seam.el.SeamELResolver.resolveBase(SeamELResolver.java:166) > at org.jboss.seam.el.SeamELResolver.getValue(SeamELResolver.java:53) > at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) > at org.jboss.el.parser.AstIdentifier.getValue(AstIdentifier.java:44) > at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) > at org.jboss.seam.core.Expressions$1.getValue(Expressions.java:111) > at org.jboss.seam.persistence.HibernatePersistenceProvider.enableFilter(HibernatePersistenceProvider.java:205) > at org.jboss.seam.persistence.ManagedPersistenceContext.initEntityManager(ManagedPersistenceContext.java:88) > at org.jboss.seam.persistence.ManagedPersistenceContext.getEntityManager(ManagedPersistenceContext.java:108) > This is thrown from the FeedServlet. > The code doesn't do what the exception says it is doing: > /** > * Assigns the context variable 'currentAccessLevel' when no user is logged in. > * @return Integer Guest access level. > */ > @Factory(value = "currentAccessLevel", scope = ScopeType.SESSION, autoCreate = true) > public Integer getGuestAccessLevel() { > return ((Role)Component.getInstance("guestRole")).getAccessLevel(); > } > This has to be investigated further. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Jan 18 21:24:03 2009 From: jira-events at lists.jboss.org (Clint Popetz (JIRA)) Date: Sun, 18 Jan 2009 21:24:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3898) Transaction not rolled back by Work if exception is thrown during UTTransaction.begin Message-ID: <28169984.1232331843988.JavaMail.jira@cloud.prod.atl2.jboss.com> Transaction not rolled back by Work if exception is thrown during UTTransaction.begin ------------------------------------------------------------------------------------- Key: JBSEAM-3898 URL: https://jira.jboss.org/jira/browse/JBSEAM-3898 Project: Seam Issue Type: Bug Components: Core Reporter: Clint Popetz Attachments: Work.java.diff The Work class doesn't rollback if an exception is thrown during UTTransaction.begin(), which can happen if getSynchronizations().afterTransactionBegin() dies. This can happen in an EJB3 environment, even though the method on EjbSynchronizations does nothing, because EjbSynchronizations is a SFSB, and for example there are classloading bugs for SFSBs in Quartz threads, which lead to spurious exceptions. When using jta, this means the tx for the async thread is left open, and eventually times out, but is never rolled back. When subsequent async jobs use that thread, all tx operations will fail because the tx exists but is aborted. I think that the try block should start before the call to begin(). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Jan 18 21:24:04 2009 From: jira-events at lists.jboss.org (Clint Popetz (JIRA)) Date: Sun, 18 Jan 2009 21:24:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3898) Transaction not rolled back by Work if exception is thrown during UTTransaction.begin In-Reply-To: <28169984.1232331843988.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <18843247.1232331844141.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clint Popetz updated JBSEAM-3898: --------------------------------- Attachment: Work.java.diff A patch to do this. > Transaction not rolled back by Work if exception is thrown during UTTransaction.begin > ------------------------------------------------------------------------------------- > > Key: JBSEAM-3898 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3898 > Project: Seam > Issue Type: Bug > Components: Core > Reporter: Clint Popetz > Attachments: Work.java.diff > > > The Work class doesn't rollback if an exception is thrown during > UTTransaction.begin(), which can happen if getSynchronizations().afterTransactionBegin() dies. > This can happen in an EJB3 environment, even though the method on EjbSynchronizations does nothing, because EjbSynchronizations is a SFSB, and for example there are classloading bugs for SFSBs in Quartz threads, which lead to > spurious exceptions. When using jta, this means the tx for the async thread is left open, and eventually times out, but is never rolled back. When subsequent async jobs use that thread, all tx operations will fail because the tx exists but is aborted. > I think that the try block should start before the call to begin(). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 19 01:04:03 2009 From: jira-events at lists.jboss.org (Zoltan Tiringer (JIRA)) Date: Mon, 19 Jan 2009 01:04:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3899) breaks OrderBy of list columns backed by Conversation scoped components Message-ID: <8798220.1232345043963.JavaMail.jira@cloud.prod.atl2.jboss.com> breaks OrderBy of list columns backed by Conversation scoped components ---------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3899 URL: https://jira.jboss.org/jira/browse/JBSEAM-3899 Project: Seam Issue Type: Bug Components: JSF Controls Affects Versions: 2.1.1.GA Environment: JBoss 4.2.3GA, Seam 2.1.1.GA, Windows Vista Reporter: Zoltan Tiringer breaks OrderBy in Conversation scoped components. To reproduce: create a new seam-gen project, change any List class to Conversation scope. Create a link in the menu, like: and OrderBy stops working on the list colums. Works fine with conversationPropagation "end" or "none". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 19 07:32:03 2009 From: jira-events at lists.jboss.org (Pete Muir (JIRA)) Date: Mon, 19 Jan 2009 07:32:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3898) Transaction not rolled back by Work if exception is thrown during UTTransaction.begin In-Reply-To: <28169984.1232331843988.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <17683976.1232368323971.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12448528#action_12448528 ] Pete Muir commented on JBSEAM-3898: ----------------------------------- Looks good to me. > Transaction not rolled back by Work if exception is thrown during UTTransaction.begin > ------------------------------------------------------------------------------------- > > Key: JBSEAM-3898 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3898 > Project: Seam > Issue Type: Bug > Components: Core > Reporter: Clint Popetz > Attachments: Work.java.diff > > > The Work class doesn't rollback if an exception is thrown during > UTTransaction.begin(), which can happen if getSynchronizations().afterTransactionBegin() dies. > This can happen in an EJB3 environment, even though the method on EjbSynchronizations does nothing, because EjbSynchronizations is a SFSB, and for example there are classloading bugs for SFSBs in Quartz threads, which lead to > spurious exceptions. When using jta, this means the tx for the async thread is left open, and eventually times out, but is never rolled back. When subsequent async jobs use that thread, all tx operations will fail because the tx exists but is aborted. > I think that the try block should start before the call to begin(). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 19 07:43:04 2009 From: jira-events at lists.jboss.org (Thiru Neela (JIRA)) Date: Mon, 19 Jan 2009 07:43:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3900) error in creating seam entity Message-ID: <11553190.1232368984573.JavaMail.jira@cloud.prod.atl2.jboss.com> error in creating seam entity ----------------------------- Key: JBSEAM-3900 URL: https://jira.jboss.org/jira/browse/JBSEAM-3900 Project: Seam Issue Type: Task Components: Seam Text Affects Versions: 2.0.1.GA Reporter: Thiru Neela Fix For: 2.0.1.GA Hi ! I am creating one single seam-entity, but the code is not created completly my table has the following fields (tid,tname,date1,Id), the seam generated code as follows package org.domain.hi.entity; import java.io.Serializable; import javax.persistence.Entity; import javax.persistence.Id; import javax.persistence.GeneratedValue; import javax.persistence.Version; import org.hibernate.validator.Length; @Entity public class Tramsactopm1 implements Serializable { //seam-gen attributes (you should probably edit these) private Long id; private Integer version; private String name; //add additional entity attributes //seam-gen attribute getters/setters with annotations (you probably should edit) @Id @GeneratedValue public Long getId() { return id; } public void setId(Long id) { this.id = id; } @Version public Integer getVersion() { return version; } private void setVersion(Integer version) { this.version = version; } @Length(max=20) public String getName() { return name; } public void setName(String name) { this.name = name; } } my question is why is not creating complete code for all the fileds cany any one help to solve this problem thanks in advance -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 19 08:04:04 2009 From: jira-events at lists.jboss.org (Pete Muir (JIRA)) Date: Mon, 19 Jan 2009 08:04:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3900) error in creating seam entity In-Reply-To: <11553190.1232368984573.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <11856658.1232370244256.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir closed JBSEAM-3900. ----------------------------- Fix Version/s: (was: 2.0.1.GA) Resolution: Rejected DO NOT USE JIRA FOR SUPPORT > error in creating seam entity > ----------------------------- > > Key: JBSEAM-3900 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3900 > Project: Seam > Issue Type: Task > Components: Seam Text > Affects Versions: 2.0.1.GA > Reporter: Thiru Neela > > Hi ! > I am creating one single seam-entity, but the code is not created completly > my table has the following fields (tid,tname,date1,Id), > the seam generated code as follows > package org.domain.hi.entity; > import java.io.Serializable; > import javax.persistence.Entity; > import javax.persistence.Id; > import javax.persistence.GeneratedValue; > import javax.persistence.Version; > import org.hibernate.validator.Length; > @Entity > public class Tramsactopm1 implements Serializable { > > //seam-gen attributes (you should probably edit these) > private Long id; > private Integer version; > private String name; > > //add additional entity attributes > > //seam-gen attribute getters/setters with annotations (you probably should edit) > > @Id @GeneratedValue > public Long getId() { > return id; > } > public void setId(Long id) { > this.id = id; > } > > @Version > public Integer getVersion() { > return version; > } > private void setVersion(Integer version) { > this.version = version; > } > > @Length(max=20) > public String getName() { > return name; > } > public void setName(String name) { > this.name = name; > } > } > my question is why is not creating complete code for all the fileds > cany any one help to solve this problem > thanks in advance -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 19 08:21:04 2009 From: jira-events at lists.jboss.org (Clint Popetz (JIRA)) Date: Mon, 19 Jan 2009 08:21:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3898) Transaction not rolled back by Work if exception is thrown during UTTransaction.begin In-Reply-To: <28169984.1232331843988.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <15767210.1232371264870.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clint Popetz closed JBSEAM-3898. -------------------------------- Fix Version/s: 2.1.2.CR1 Resolution: Done Fixed in r9952. > Transaction not rolled back by Work if exception is thrown during UTTransaction.begin > ------------------------------------------------------------------------------------- > > Key: JBSEAM-3898 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3898 > Project: Seam > Issue Type: Bug > Components: Core > Reporter: Clint Popetz > Fix For: 2.1.2.CR1 > > Attachments: Work.java.diff > > > The Work class doesn't rollback if an exception is thrown during > UTTransaction.begin(), which can happen if getSynchronizations().afterTransactionBegin() dies. > This can happen in an EJB3 environment, even though the method on EjbSynchronizations does nothing, because EjbSynchronizations is a SFSB, and for example there are classloading bugs for SFSBs in Quartz threads, which lead to > spurious exceptions. When using jta, this means the tx for the async thread is left open, and eventually times out, but is never rolled back. When subsequent async jobs use that thread, all tx operations will fail because the tx exists but is aborted. > I think that the try block should start before the call to begin(). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 19 13:04:07 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Mon, 19 Jan 2009 13:04:07 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1841) Need examples/documentation for how to use seamgen generated EntityHome interefaces and related functionality In-Reply-To: <4617680.1187788938137.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <7491935.1232388247797.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards updated JBSEAM-1841: ------------------------------------ Fix Version/s: The future (was: 2.1.2.CR1) Affects: [Documentation (Ref Guide, User Guide, etc.), Interactive Demo/Tutorial] (was: [Interactive Demo/Tutorial, Documentation (Ref Guide, User Guide, etc.)]) > Need examples/documentation for how to use seamgen generated EntityHome interefaces and related functionality > ------------------------------------------------------------------------------------------------------------- > > Key: JBSEAM-1841 > URL: https://jira.jboss.org/jira/browse/JBSEAM-1841 > Project: Seam > Issue Type: Feature Request > Components: Documentation Issues > Affects Versions: 2.0.0.BETA1 > Reporter: steve tynor > Assignee: Norman Richards > Fix For: The future > > > Please add some documentation, perhaps an example project, that uses seamgen-generated EntityHome classes in order to demonstrate the intended use of the wire(), isWired(), createInstance(), getDefinedInstance(), setId(), etc. functions. Some discussion on how these related to and in XHTML is also needed. > As it stands, these are completely undocumented without any explanation of their intended use, so those of us that have boostrapped a project with seamgen, have no guidance on how to maintian these classes as our application changes (new properties added to entities, etc.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 19 13:06:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Mon, 19 Jan 2009 13:06:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2514) Document the scopes in which framework classes can be used In-Reply-To: <9054948.1200913341119.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <30620879.1232388364331.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards updated JBSEAM-2514: ------------------------------------ Fix Version/s: The future (was: 2.1.2.CR1) > Document the scopes in which framework classes can be used > ---------------------------------------------------------- > > Key: JBSEAM-2514 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2514 > Project: Seam > Issue Type: Task > Components: Documentation Issues, Framework > Affects Versions: 2.0.0.GA > Environment: Seam 2.0.0.GA, JBoss AS 4.2.2.GA > Reporter: Martin Hoffmann > Assignee: Norman Richards > Priority: Optional > Fix For: The future > > > The EntityHome is not able to operate in PAGE scope and the documentation says nothing about compatible scopes and framework classes. > It throws an exeption: > aused by: javax.el.ELException: /client/claim_list.xhtml @16,52 value="#{testList.dataModel}": Error reading 'dataModel' on type de.iseki.garantieext.card.Test > List_$$_javassist_0 > at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.ja > va:76) > at javax.faces.component.UIOutput.getValue(UIOutput.java:173) > ... 69 more > Caused by: java.lang.IllegalStateException: EntityManager is closed > at org.hibernate.ejb.EntityManagerImpl.getSession(EntityManagerImpl.java > :42) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 19 13:08:14 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Mon, 19 Jan 2009 13:08:14 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3753) SeamResourceBundle.getBundle(String baseName) fails to return correct message based on Locale In-Reply-To: <11420851.1227561876694.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <14204234.1232388494141.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3753. ----------------------------------- Resolution: Won't Fix See previous comment. If you want a new method to perform this action, I can add one. > SeamResourceBundle.getBundle(String baseName) fails to return correct message based on Locale > --------------------------------------------------------------------------------------------- > > Key: JBSEAM-3753 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3753 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.0.2.SP1, 2.0.3.CR1, 2.1.1.CR1 > Reporter: Samuel Mendenhall > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > > When specifying the Locale directly, everything works as expected, when not, the default locale is used, which is incorrect. Ex. > log.info("SeamResourceBundle.getBundle w/o passing Local: " + SeamResourceBundle.getBundle("ECISConfig").getString("ecis.hello")); > log.info("SeamResourceBundle.getBundle w passing Local: " + SeamResourceBundle.getBundle("ECISConfig", LocaleSelector.instance().getLocale()).getString("ecis.hello")); > Produces: > 15:08:45,438 INFO [TestAction] SeamResourceBundle.getBundle w/o passing Local: Hello from ECISConfig_en.properties > 15:08:45,439 INFO [TestAction] SeamResourceBundle.getBundle w passing Local: Hello from ECISConfig_en_US_tmwa.properties > When both should be saying "Hello from ECISConfig_en_US_tmwa.properties" because the locale and resource bundle are defined in components.xml as: > > > > messages > ECISConfig > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 19 16:47:04 2009 From: jira-events at lists.jboss.org (Preben Ludviksen (JIRA)) Date: Mon, 19 Jan 2009 16:47:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3901) Conversation id is always propagated on redirects Message-ID: <27801944.1232401624374.JavaMail.jira@cloud.prod.atl2.jboss.com> Conversation id is always propagated on redirects ------------------------------------------------- Key: JBSEAM-3901 URL: https://jira.jboss.org/jira/browse/JBSEAM-3901 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA Reporter: Preben Ludviksen According to the documentation, propagation of conversation id's on redirects is controlled by the redirect-filter: http://docs.jboss.com/seam/2.1.1.GA/reference/en-US/html/configuration.html#d0e23274 However, the id propagates even if the filter is swithced off in components.xml: When redirecting using pages.xml: According to the Seam user Peter Hilton in the referenced forum thread: "The results in a call to org.jboss.seam.faces.FacesManager.redirect(String viewId, Map parameters, boolean includeConversationId) This is called from the following code in org.jboss.seam.faces.Navigator which sets includeConversationId to true: FacesManager.instance().redirect(viewId, parameters, true);" The propagation should be possible to disable, for use cases where you don't really rely on conversations, and don't want to clutter the URL. I have also posted a feature request to allow disabling of the propagation on a per-redirect basis. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 19 16:53:04 2009 From: jira-events at lists.jboss.org (Preben Ludviksen (JIRA)) Date: Mon, 19 Jan 2009 16:53:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3902) Allow disabling of conversation id's on a per-redirect basis Message-ID: <5193205.1232401984052.JavaMail.jira@cloud.prod.atl2.jboss.com> Allow disabling of conversation id's on a per-redirect basis ------------------------------------------------------------ Key: JBSEAM-3902 URL: https://jira.jboss.org/jira/browse/JBSEAM-3902 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.1.GA Reporter: Preben Ludviksen Some times you have a redirect rule in pages.xml: And you know that you aren't relying on conversation propagation for the given view. It would be nice to have the possibility to disable the automatic propagation to keep the URLs nice in these cases: -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 19 16:55:04 2009 From: jira-events at lists.jboss.org (Preben Ludviksen (JIRA)) Date: Mon, 19 Jan 2009 16:55:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3901) Conversation id is always propagated on redirects In-Reply-To: <27801944.1232401624374.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <11360728.1232402104559.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Preben Ludviksen updated JBSEAM-3901: ------------------------------------- Description: According to the documentation, propagation of conversation id's on redirects is controlled by the redirect-filter: http://docs.jboss.com/seam/2.1.1.GA/reference/en-US/html/configuration.html#d0e23274 However, the id propagates even if the filter is swithced off in components.xml: When redirecting using pages.xml: According to the Seam user Peter Hilton in the referenced forum thread: "The results in a call to org.jboss.seam.faces.FacesManager.redirect(String viewId, Map parameters, boolean includeConversationId) This is called from the following code in org.jboss.seam.faces.Navigator which sets includeConversationId to true: FacesManager.instance().redirect(viewId, parameters, true);" The propagation should be possible to disable for use cases where you don't really rely on conversations, and don't want to clutter the URL. I have also posted a feature request to allow disabling of the propagation on a per-redirect basis: https://jira.jboss.org/jira/browse/JBSEAM-3902 was: According to the documentation, propagation of conversation id's on redirects is controlled by the redirect-filter: http://docs.jboss.com/seam/2.1.1.GA/reference/en-US/html/configuration.html#d0e23274 However, the id propagates even if the filter is swithced off in components.xml: When redirecting using pages.xml: According to the Seam user Peter Hilton in the referenced forum thread: "The results in a call to org.jboss.seam.faces.FacesManager.redirect(String viewId, Map parameters, boolean includeConversationId) This is called from the following code in org.jboss.seam.faces.Navigator which sets includeConversationId to true: FacesManager.instance().redirect(viewId, parameters, true);" The propagation should be possible to disable, for use cases where you don't really rely on conversations, and don't want to clutter the URL. I have also posted a feature request to allow disabling of the propagation on a per-redirect basis. > Conversation id is always propagated on redirects > ------------------------------------------------- > > Key: JBSEAM-3901 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3901 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.1.1.GA > Reporter: Preben Ludviksen > > According to the documentation, propagation of conversation id's on redirects is controlled by the redirect-filter: > http://docs.jboss.com/seam/2.1.1.GA/reference/en-US/html/configuration.html#d0e23274 > However, the id propagates even if the filter is swithced off in components.xml: > > > When redirecting using pages.xml: > > > > > > > > > According to the Seam user Peter Hilton in the referenced forum thread: > "The results in a call to org.jboss.seam.faces.FacesManager.redirect(String viewId, Map parameters, boolean includeConversationId) > This is called from the following code in org.jboss.seam.faces.Navigator which sets includeConversationId to true: > FacesManager.instance().redirect(viewId, parameters, true);" > The propagation should be possible to disable for use cases where you don't really rely on conversations, and don't want to clutter the URL. I have also posted a feature request to allow disabling of the propagation on a per-redirect basis: > https://jira.jboss.org/jira/browse/JBSEAM-3902 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 19 17:14:04 2009 From: jira-events at lists.jboss.org (Francisco Jose Peredo Noguez (JIRA)) Date: Mon, 19 Jan 2009 17:14:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3903) CRUD is conversational, but seam-gen apps are not conversational enough Message-ID: <6032544.1232403244031.JavaMail.jira@cloud.prod.atl2.jboss.com> CRUD is conversational, but seam-gen apps are not conversational enough ----------------------------------------------------------------------- Key: JBSEAM-3903 URL: https://jira.jboss.org/jira/browse/JBSEAM-3903 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.0.SP1 Reporter: Francisco Jose Peredo Noguez Lets say you have 2 classes: class Parent{ private Long id; private Integer version; private String name; private Set children; } and class Child{ private Long id;private Integer version; private String name; private Parent parent; } with a typical one to many / many to one relationship (Parent.children.Child/Child.parent.Parent) So you want them to become @Entities and add the required @Annotations. Then you run seam-gen on them, and run you generated application: 1. You click the Parent List menu option. 2. You are presented with the page ParentList.seam that allows you search parents, or to create a new one. 3. You click the Create parent button. 4. You write a name for the parent: "Peter". 5. You click "Save". 6. You are presented with the page Parent.seam, that displays you newly persisted entity in a "read-only way" 7. You click "Done" so far so good... but then 1. You click the Child List menu option. 2. You are presented with the page ChildList.seam that allows you search children, or to create a new one 3. You click the Create child button. 4. You are presented with the page ChildEdit.seam. 5. You write a name for your new Child entity: "John" 6. You decide that you want connect this new Child entity with a parent entity, and then you click "Select parent". 7. You are presented again with ParentList.seam that allows you to "select" a parent. 8. So, you select "Peter" by clicking in the "Select" link 9. And you return to ChildEdit.seam, but the value for the name property of the Child is now LOST. I think seam-gen should be able to do this correctly (without losing the values in ChildEdit.seam). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 19 17:18:04 2009 From: jira-events at lists.jboss.org (Francisco Jose Peredo Noguez (JIRA)) Date: Mon, 19 Jan 2009 17:18:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3903) CRUD is conversational problem, but seam-gen apps are not conversational enough In-Reply-To: <6032544.1232403244031.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <21418026.1232403484225.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Jose Peredo Noguez updated JBSEAM-3903: ------------------------------------------------- Summary: CRUD is conversational problem, but seam-gen apps are not conversational enough (was: CRUD is conversational, but seam-gen apps are not conversational enough) > CRUD is conversational problem, but seam-gen apps are not conversational enough > ------------------------------------------------------------------------------- > > Key: JBSEAM-3903 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3903 > Project: Seam > Issue Type: Feature Request > Affects Versions: 2.1.0.SP1 > Reporter: Francisco Jose Peredo Noguez > > Lets say you have 2 classes: > class Parent{ > private Long id; private Integer version; private String name; > private Set children; > } > and > class Child{ > private Long id;private Integer version; private String name; > private Parent parent; > } > with a typical one to many / many to one relationship (Parent.children.Child/Child.parent.Parent) > So you want them to become @Entities and add the required @Annotations. Then you run seam-gen on them, and run you generated application: > 1. You click the Parent List menu option. > 2. You are presented with the page ParentList.seam that allows you search parents, or to create a new one. > 3. You click the Create parent button. > 4. You write a name for the parent: "Peter". > 5. You click "Save". > 6. You are presented with the page Parent.seam, that displays you newly persisted entity in a "read-only way" > 7. You click "Done" > so far so good... but then > 1. You click the Child List menu option. > 2. You are presented with the page ChildList.seam that allows you search children, or to create a new one > 3. You click the Create child button. > 4. You are presented with the page ChildEdit.seam. > 5. You write a name for your new Child entity: "John" > 6. You decide that you want connect this new Child entity with a parent entity, and then you click "Select parent". > 7. You are presented again with ParentList.seam that allows you to "select" a parent. > 8. So, you select "Peter" by clicking in the "Select" link > 9. And you return to ChildEdit.seam, but the value for the name property of the Child is now LOST. > I think seam-gen should be able to do this correctly (without losing the values in ChildEdit.seam). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 19 18:24:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Mon, 19 Jan 2009 18:24:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3143) PDF (patch included): optimized p:image scaling according to parameters In-Reply-To: <18863325.1214974127320.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <25818533.1232407444093.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3143. ----------------------------------- Resolution: Done I've added a scaleToFit option: Does that work for you? I thought that was a little easier to understand. I also thought using height and width and then scale="fit" was another option, but we already have scalePercent. which would probably need to be changed too. > PDF (patch included): optimized p:image scaling according to parameters > ----------------------------------------------------------------------- > > Key: JBSEAM-3143 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3143 > Project: Seam > Issue Type: Feature Request > Components: PDF > Reporter: Ari Takku > Assignee: Norman Richards > Priority: Minor > Fix For: 2.1.2.CR1 > > Attachments: UIImage.java.optimized_dimension.patch > > > While including images in a PDF-document, there is a need to optimize images for certain area (i.e. width x height). Naturally, this optimization should not ruin the proportional dimensions of the image. > A feature request: add two parameters, namely maximumWIdth and maximumHeight to p:image. > One try-out to provide this feature is attached as patch (untested). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 19 22:29:14 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Mon, 19 Jan 2009 22:29:14 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-3902) Allow disabling of conversation id's on a per-redirect basis In-Reply-To: <5193205.1232401984052.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <32247567.1232422154332.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards reassigned JBSEAM-3902: --------------------------------------- Assignee: Norman Richards > Allow disabling of conversation id's on a per-redirect basis > ------------------------------------------------------------ > > Key: JBSEAM-3902 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3902 > Project: Seam > Issue Type: Feature Request > Components: Core > Affects Versions: 2.1.1.GA > Reporter: Preben Ludviksen > Assignee: Norman Richards > > Some times you have a redirect rule in pages.xml: > > > > > > > > And you know that you aren't relying on conversation propagation for the given view. It would be nice to have the possibility to disable the automatic propagation to keep the URLs nice in these cases: > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 19 23:51:03 2009 From: jira-events at lists.jboss.org (Ari Takku (JIRA)) Date: Mon, 19 Jan 2009 23:51:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3143) PDF (patch included): optimized p:image scaling according to parameters In-Reply-To: <18863325.1214974127320.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <31782517.1232427063992.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12448663#action_12448663 ] Ari Takku commented on JBSEAM-3143: ----------------------------------- Currently I'm unable to verify this due to lack of time, but I'll keep it in mind. Anyways, thank you for your valuable work! > PDF (patch included): optimized p:image scaling according to parameters > ----------------------------------------------------------------------- > > Key: JBSEAM-3143 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3143 > Project: Seam > Issue Type: Feature Request > Components: PDF > Reporter: Ari Takku > Assignee: Norman Richards > Priority: Minor > Fix For: 2.1.2.CR1 > > Attachments: UIImage.java.optimized_dimension.patch > > > While including images in a PDF-document, there is a need to optimize images for certain area (i.e. width x height). Naturally, this optimization should not ruin the proportional dimensions of the image. > A feature request: add two parameters, namely maximumWIdth and maximumHeight to p:image. > One try-out to provide this feature is attached as patch (untested). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 20 08:51:03 2009 From: jira-events at lists.jboss.org (=?UTF-8?Q?Lo=C3=83=C2=AFc_Lef=C3=83=C2=A8vre_=28JIRA=29?=) Date: Tue, 20 Jan 2009 08:51:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3904) Property 'logout' not found on type Identity when commeting XHTML Message-ID: <4312243.1232459464030.JavaMail.jira@cloud.prod.atl2.jboss.com> Property 'logout' not found on type Identity when commeting XHTML ----------------------------------------------------------------- Key: JBSEAM-3904 URL: https://jira.jboss.org/jira/browse/JBSEAM-3904 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Environment: Windows XP JBoss AS 5.0.0 Reporter: Lo??c Lef??vre If I comment in booking example the file view/template.xhtml: ...
... for test purposes, I get the following exception: 14:45:12,255 ERROR [viewhandler] Error Rendering View[/main.xhtml] javax.el.PropertyNotFoundException: Property 'logout' not found on type org.jboss.seam.security.Identity at javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:193) at javax.el.BeanELResolver$BeanProperties.access$400(BeanELResolver.java:170) at javax.el.BeanELResolver.property(BeanELResolver.java:279) at javax.el.BeanELResolver.getValue(BeanELResolver.java:60) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72) at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53) at org.jboss.el.parser.AstValue.getValue(AstValue.java:67) at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) at com.sun.facelets.el.ELText$ELTextVariable.toString(ELText.java:174) at com.sun.facelets.el.ELText$ELTextComposite.toString(ELText.java:115) at com.sun.facelets.compiler.CommentInstruction.write(CommentInstruction.java:38) at com.sun.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:39) at com.sun.facelets.compiler.UILeaf.encodeAll(UILeaf.java:149) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:933) at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:592) at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:196) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 20 08:51:04 2009 From: jira-events at lists.jboss.org (=?UTF-8?Q?Lo=C3=83=C2=AFc_Lef=C3=83=C2=A8vre_=28JIRA=29?=) Date: Tue, 20 Jan 2009 08:51:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3904) Property 'logout' not found on type Identity when commenting XHTML In-Reply-To: <4312243.1232459464030.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <7597395.1232459464377.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lo??c Lef??vre updated JBSEAM-3904: ----------------------------------- Summary: Property 'logout' not found on type Identity when commenting XHTML (was: Property 'logout' not found on type Identity when commeting XHTML) > Property 'logout' not found on type Identity when commenting XHTML > ------------------------------------------------------------------ > > Key: JBSEAM-3904 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3904 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.1.GA > Environment: Windows XP > JBoss AS 5.0.0 > Reporter: Lo??c Lef??vre > > If I comment in booking example the file view/template.xhtml: > ... >
> > ... > for test purposes, I get the following exception: > 14:45:12,255 ERROR [viewhandler] Error Rendering View[/main.xhtml] > javax.el.PropertyNotFoundException: Property 'logout' not found on type org.jboss.seam.security.Identity > at javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:193) > at javax.el.BeanELResolver$BeanProperties.access$400(BeanELResolver.java:170) > at javax.el.BeanELResolver.property(BeanELResolver.java:279) > at javax.el.BeanELResolver.getValue(BeanELResolver.java:60) > at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) > at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72) > at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53) > at org.jboss.el.parser.AstValue.getValue(AstValue.java:67) > at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) > at com.sun.facelets.el.ELText$ELTextVariable.toString(ELText.java:174) > at com.sun.facelets.el.ELText$ELTextComposite.toString(ELText.java:115) > at com.sun.facelets.compiler.CommentInstruction.write(CommentInstruction.java:38) > at com.sun.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:39) > at com.sun.facelets.compiler.UILeaf.encodeAll(UILeaf.java:149) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:933) > at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:592) > at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) > at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:196) > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) > at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) > at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) > at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) > at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) > at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 20 08:53:03 2009 From: jira-events at lists.jboss.org (=?UTF-8?Q?Lo=C3=83=C2=AFc_Lef=C3=83=C2=A8vre_=28JIRA=29?=) Date: Tue, 20 Jan 2009 08:53:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3905) s:link swallows preceding space Message-ID: <30583339.1232459583979.JavaMail.jira@cloud.prod.atl2.jboss.com> s:link swallows preceding space ------------------------------- Key: JBSEAM-3905 URL: https://jira.jboss.org/jira/browse/JBSEAM-3905 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Reporter: Lo??c Lef??vre Priority: Trivial Each tag must be preceeded by a   in order to not glue to the preceding word. Annoying. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 20 08:55:04 2009 From: jira-events at lists.jboss.org (Pete Muir (JIRA)) Date: Tue, 20 Jan 2009 08:55:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3905) s:link swallows preceding space In-Reply-To: <30583339.1232459583979.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <3230819.1232459704190.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir closed JBSEAM-3905. ----------------------------- Resolution: Rejected DO NOT USE JIRA FOR SUPPORT > s:link swallows preceding space > ------------------------------- > > Key: JBSEAM-3905 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3905 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.1.GA > Reporter: Lo??c Lef??vre > Priority: Trivial > > Each tag must be preceeded by a   in order to not glue to the preceding word. Annoying. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 20 08:55:04 2009 From: jira-events at lists.jboss.org (Pete Muir (JIRA)) Date: Tue, 20 Jan 2009 08:55:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3904) Property 'logout' not found on type Identity when commenting XHTML In-Reply-To: <4312243.1232459464030.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <12413472.1232459704087.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir closed JBSEAM-3904. ----------------------------- Resolution: Rejected DO NOT USE JIRA FOR SUPPORT > Property 'logout' not found on type Identity when commenting XHTML > ------------------------------------------------------------------ > > Key: JBSEAM-3904 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3904 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.1.GA > Environment: Windows XP > JBoss AS 5.0.0 > Reporter: Lo??c Lef??vre > > If I comment in booking example the file view/template.xhtml: > ... >
> > ... > for test purposes, I get the following exception: > 14:45:12,255 ERROR [viewhandler] Error Rendering View[/main.xhtml] > javax.el.PropertyNotFoundException: Property 'logout' not found on type org.jboss.seam.security.Identity > at javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:193) > at javax.el.BeanELResolver$BeanProperties.access$400(BeanELResolver.java:170) > at javax.el.BeanELResolver.property(BeanELResolver.java:279) > at javax.el.BeanELResolver.getValue(BeanELResolver.java:60) > at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) > at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72) > at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53) > at org.jboss.el.parser.AstValue.getValue(AstValue.java:67) > at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) > at com.sun.facelets.el.ELText$ELTextVariable.toString(ELText.java:174) > at com.sun.facelets.el.ELText$ELTextComposite.toString(ELText.java:115) > at com.sun.facelets.compiler.CommentInstruction.write(CommentInstruction.java:38) > at com.sun.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:39) > at com.sun.facelets.compiler.UILeaf.encodeAll(UILeaf.java:149) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:933) > at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:592) > at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) > at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:196) > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) > at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) > at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) > at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) > at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) > at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 20 08:59:04 2009 From: jira-events at lists.jboss.org (=?UTF-8?Q?Lo=C3=83=C2=AFc_Lef=C3=83=C2=A8vre_=28JIRA=29?=) Date: Tue, 20 Jan 2009 08:59:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3904) Property 'logout' not found on type Identity when commenting XHTML In-Reply-To: <4312243.1232459464030.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <1711371.1232459944065.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12448761#action_12448761 ] Lo??c Lef??vre commented on JBSEAM-3904: ---------------------------------------- Ouch! Very kind of you but I'm NOT asking for support. I'm just saying, it's really weird that a COMMENT can produce an EXCEPTION! > Property 'logout' not found on type Identity when commenting XHTML > ------------------------------------------------------------------ > > Key: JBSEAM-3904 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3904 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.1.GA > Environment: Windows XP > JBoss AS 5.0.0 > Reporter: Lo??c Lef??vre > > If I comment in booking example the file view/template.xhtml: > ... >
> > ... > for test purposes, I get the following exception: > 14:45:12,255 ERROR [viewhandler] Error Rendering View[/main.xhtml] > javax.el.PropertyNotFoundException: Property 'logout' not found on type org.jboss.seam.security.Identity > at javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:193) > at javax.el.BeanELResolver$BeanProperties.access$400(BeanELResolver.java:170) > at javax.el.BeanELResolver.property(BeanELResolver.java:279) > at javax.el.BeanELResolver.getValue(BeanELResolver.java:60) > at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) > at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72) > at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53) > at org.jboss.el.parser.AstValue.getValue(AstValue.java:67) > at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) > at com.sun.facelets.el.ELText$ELTextVariable.toString(ELText.java:174) > at com.sun.facelets.el.ELText$ELTextComposite.toString(ELText.java:115) > at com.sun.facelets.compiler.CommentInstruction.write(CommentInstruction.java:38) > at com.sun.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:39) > at com.sun.facelets.compiler.UILeaf.encodeAll(UILeaf.java:149) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:933) > at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:592) > at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) > at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:196) > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) > at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) > at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) > at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) > at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) > at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 20 09:01:04 2009 From: jira-events at lists.jboss.org (=?UTF-8?Q?Lo=C3=83=C2=AFc_Lef=C3=83=C2=A8vre_=28JIRA=29?=) Date: Tue, 20 Jan 2009 09:01:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Reopened: (JBSEAM-3904) Property 'logout' not found on type Identity when commenting XHTML In-Reply-To: <4312243.1232459464030.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <25733468.1232460064526.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lo??c Lef??vre reopened JBSEAM-3904: ------------------------------------ > Property 'logout' not found on type Identity when commenting XHTML > ------------------------------------------------------------------ > > Key: JBSEAM-3904 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3904 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.1.GA > Environment: Windows XP > JBoss AS 5.0.0 > Reporter: Lo??c Lef??vre > > If I comment in booking example the file view/template.xhtml: > ... >
> > ... > for test purposes, I get the following exception: > 14:45:12,255 ERROR [viewhandler] Error Rendering View[/main.xhtml] > javax.el.PropertyNotFoundException: Property 'logout' not found on type org.jboss.seam.security.Identity > at javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:193) > at javax.el.BeanELResolver$BeanProperties.access$400(BeanELResolver.java:170) > at javax.el.BeanELResolver.property(BeanELResolver.java:279) > at javax.el.BeanELResolver.getValue(BeanELResolver.java:60) > at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) > at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72) > at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53) > at org.jboss.el.parser.AstValue.getValue(AstValue.java:67) > at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) > at com.sun.facelets.el.ELText$ELTextVariable.toString(ELText.java:174) > at com.sun.facelets.el.ELText$ELTextComposite.toString(ELText.java:115) > at com.sun.facelets.compiler.CommentInstruction.write(CommentInstruction.java:38) > at com.sun.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:39) > at com.sun.facelets.compiler.UILeaf.encodeAll(UILeaf.java:149) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:933) > at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:592) > at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) > at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:196) > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) > at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) > at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) > at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) > at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) > at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 20 09:03:04 2009 From: jira-events at lists.jboss.org (=?UTF-8?Q?Lo=C3=83=C2=AFc_Lef=C3=83=C2=A8vre_=28JIRA=29?=) Date: Tue, 20 Jan 2009 09:03:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Reopened: (JBSEAM-3905) s:link swallows preceding space In-Reply-To: <30583339.1232459583979.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <8638904.1232460184217.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lo??c Lef??vre reopened JBSEAM-3905: ------------------------------------ Again, I'm not asking for support, for me this is a bug (trivial) but a bug. Maybe Seam is not responsible of this behaviour, if this is the case please tell me which thirdparty project I should contact. > s:link swallows preceding space > ------------------------------- > > Key: JBSEAM-3905 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3905 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.1.GA > Reporter: Lo??c Lef??vre > Priority: Trivial > > Each tag must be preceeded by a   in order to not glue to the preceding word. Annoying. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 20 09:03:03 2009 From: jira-events at lists.jboss.org (Pete Muir (JIRA)) Date: Tue, 20 Jan 2009 09:03:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3904) Property 'logout' not found on type Identity when commenting XHTML In-Reply-To: <4312243.1232459464030.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <951383.1232460184096.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir closed JBSEAM-3904. ----------------------------- Resolution: Done DO NOT REOPEN REJECTED ISSUES. RTFM. > Property 'logout' not found on type Identity when commenting XHTML > ------------------------------------------------------------------ > > Key: JBSEAM-3904 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3904 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.1.GA > Environment: Windows XP > JBoss AS 5.0.0 > Reporter: Lo??c Lef??vre > > If I comment in booking example the file view/template.xhtml: > ... >
> > ... > for test purposes, I get the following exception: > 14:45:12,255 ERROR [viewhandler] Error Rendering View[/main.xhtml] > javax.el.PropertyNotFoundException: Property 'logout' not found on type org.jboss.seam.security.Identity > at javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:193) > at javax.el.BeanELResolver$BeanProperties.access$400(BeanELResolver.java:170) > at javax.el.BeanELResolver.property(BeanELResolver.java:279) > at javax.el.BeanELResolver.getValue(BeanELResolver.java:60) > at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) > at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72) > at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53) > at org.jboss.el.parser.AstValue.getValue(AstValue.java:67) > at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) > at com.sun.facelets.el.ELText$ELTextVariable.toString(ELText.java:174) > at com.sun.facelets.el.ELText$ELTextComposite.toString(ELText.java:115) > at com.sun.facelets.compiler.CommentInstruction.write(CommentInstruction.java:38) > at com.sun.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:39) > at com.sun.facelets.compiler.UILeaf.encodeAll(UILeaf.java:149) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:933) > at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:592) > at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) > at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:196) > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) > at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) > at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) > at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) > at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) > at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 20 09:05:03 2009 From: jira-events at lists.jboss.org (Pete Muir (JIRA)) Date: Tue, 20 Jan 2009 09:05:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3905) s:link swallows preceding space In-Reply-To: <30583339.1232459583979.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <27072469.1232460304029.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir closed JBSEAM-3905. ----------------------------- Resolution: Done DO NOT REOPEN REJECTED ISSUES. > s:link swallows preceding space > ------------------------------- > > Key: JBSEAM-3905 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3905 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.1.GA > Reporter: Lo??c Lef??vre > Priority: Trivial > > Each tag must be preceeded by a   in order to not glue to the preceding word. Annoying. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 20 11:21:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Tue, 20 Jan 2009 11:21:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3905) s:link swallows preceding space In-Reply-To: <30583339.1232459583979.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <7972043.1232468464086.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12448798#action_12448798 ] Norman Richards commented on JBSEAM-3905: ----------------------------------------- For anyone who stumbles on this, there's a discussion of this facelets issue and the workarounds in the forums: http://seamframework.org/Community/FormatingIssueWithSlinkRemovingSpaces > s:link swallows preceding space > ------------------------------- > > Key: JBSEAM-3905 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3905 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.1.GA > Reporter: Lo??c Lef??vre > Priority: Trivial > > Each tag must be preceeded by a   in order to not glue to the preceding word. Annoying. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 20 12:47:14 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Tue, 20 Jan 2009 12:47:14 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3673) horizontalAlignment="right" broken in PDF cells (regression) In-Reply-To: <29246884.1225868480972.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <13586628.1232473634575.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12448824#action_12448824 ] Norman Richards commented on JBSEAM-3673: ----------------------------------------- Ah - good catch. This is fixed now. > horizontalAlignment="right" broken in PDF cells (regression) > ------------------------------------------------------------ > > Key: JBSEAM-3673 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3673 > Project: Seam > Issue Type: Bug > Components: PDF > Affects Versions: 2.1.0.SP1 > Reporter: Dan Allen > Assignee: Norman Richards > Fix For: 2.1.1.CR1 > > > All of a sudden the horizontal alignment on PDF cells stopped working in Seam 2.1. You can see the discrepancy by deploying the iText example in Seam 2.0 and Seam 2.1 and observing the servlet path /seam-itext/format.seam. You'll notice that the Order Summary table is formatted differently in the two cases, with the right-hand alignment not taking affect under Seam 2.1. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 20 14:00:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Tue, 20 Jan 2009 14:00:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3845) NullPointerException in org.jboss.seam.exception.Exceptions.parse In-Reply-To: <19616339.1229350549866.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <26082244.1232478004940.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12448849#action_12448849 ] Norman Richards commented on JBSEAM-3845: ----------------------------------------- Unfortunately, that doesn't really provide any information that would help me reproduce the issue. > NullPointerException in org.jboss.seam.exception.Exceptions.parse > ----------------------------------------------------------------- > > Key: JBSEAM-3845 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3845 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.0.SP1 > Environment: JBoss EAP 4.3.0 default, JSFUnit, run using Cactus ServletTestRunner > Reporter: Ondrej ?i?ka > Fix For: 2.1.2.CR1 > > Attachments: SeamNPE.txt > > > Seam throws a NPE when I run a JSFUnit test case. The test may be fault, but at least the NPE should be handled. > Full stack trace: > ------------------------------------------------------- > 15:11:11,933 ERROR [BaseXMLFilter] Exception in the filter chain > javax.servlet.ServletException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions > at org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:126) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) > at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) > at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) > at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) > at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:595) > Caused by: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions > at org.jboss.seam.Component.newInstance(Component.java:2096) > at org.jboss.seam.Component.getInstance(Component.java:1978) > at org.jboss.seam.Component.getInstance(Component.java:1957) > at org.jboss.seam.Component.getInstance(Component.java:1951) > at org.jboss.seam.Component.getInstance(Component.java:1924) > at org.jboss.seam.Component.getInstance(Component.java:1919) > at org.jboss.seam.exception.Exceptions.instance(Exceptions.java:256) > at org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114) > ... 31 more > Caused by: java.lang.NullPointerException > at org.jboss.seam.exception.Exceptions.parse(Exceptions.java:195) > at org.jboss.seam.exception.Exceptions.initialize(Exceptions.java:119) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) > at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:138) > at org.jboss.seam.Component.callComponentMethod(Component.java:2201) > at org.jboss.seam.Component.callCreateMethod(Component.java:2124) > at org.jboss.seam.Component.newInstance(Component.java:2084) > ... 38 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 20 14:14:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Tue, 20 Jan 2009 14:14:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-3845) NullPointerException in org.jboss.seam.exception.Exceptions.parse In-Reply-To: <19616339.1229350549866.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <8489778.1232478844031.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards reassigned JBSEAM-3845: --------------------------------------- Assignee: Norman Richards > NullPointerException in org.jboss.seam.exception.Exceptions.parse > ----------------------------------------------------------------- > > Key: JBSEAM-3845 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3845 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.0.SP1 > Environment: JBoss EAP 4.3.0 default, JSFUnit, run using Cactus ServletTestRunner > Reporter: Ondrej ?i?ka > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > Attachments: SeamNPE.txt > > > Seam throws a NPE when I run a JSFUnit test case. The test may be fault, but at least the NPE should be handled. > Full stack trace: > ------------------------------------------------------- > 15:11:11,933 ERROR [BaseXMLFilter] Exception in the filter chain > javax.servlet.ServletException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions > at org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:126) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) > at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) > at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) > at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) > at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:595) > Caused by: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions > at org.jboss.seam.Component.newInstance(Component.java:2096) > at org.jboss.seam.Component.getInstance(Component.java:1978) > at org.jboss.seam.Component.getInstance(Component.java:1957) > at org.jboss.seam.Component.getInstance(Component.java:1951) > at org.jboss.seam.Component.getInstance(Component.java:1924) > at org.jboss.seam.Component.getInstance(Component.java:1919) > at org.jboss.seam.exception.Exceptions.instance(Exceptions.java:256) > at org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114) > ... 31 more > Caused by: java.lang.NullPointerException > at org.jboss.seam.exception.Exceptions.parse(Exceptions.java:195) > at org.jboss.seam.exception.Exceptions.initialize(Exceptions.java:119) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) > at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:138) > at org.jboss.seam.Component.callComponentMethod(Component.java:2201) > at org.jboss.seam.Component.callCreateMethod(Component.java:2124) > at org.jboss.seam.Component.newInstance(Component.java:2084) > ... 38 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 20 14:18:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Tue, 20 Jan 2009 14:18:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3845) NullPointerException in org.jboss.seam.exception.Exceptions.parse In-Reply-To: <19616339.1229350549866.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <14533281.1232479084070.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3845. ----------------------------------- Resolution: Done Since it's not really clear what you are doing here, all I can do is make sure the exception isn't thrown here. If this doesn't solve your problem or if you have more information to add, please reopen. > NullPointerException in org.jboss.seam.exception.Exceptions.parse > ----------------------------------------------------------------- > > Key: JBSEAM-3845 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3845 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.0.SP1 > Environment: JBoss EAP 4.3.0 default, JSFUnit, run using Cactus ServletTestRunner > Reporter: Ondrej ?i?ka > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > Attachments: SeamNPE.txt > > > Seam throws a NPE when I run a JSFUnit test case. The test may be fault, but at least the NPE should be handled. > Full stack trace: > ------------------------------------------------------- > 15:11:11,933 ERROR [BaseXMLFilter] Exception in the filter chain > javax.servlet.ServletException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions > at org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:126) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) > at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) > at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) > at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) > at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:595) > Caused by: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.exception.exceptions > at org.jboss.seam.Component.newInstance(Component.java:2096) > at org.jboss.seam.Component.getInstance(Component.java:1978) > at org.jboss.seam.Component.getInstance(Component.java:1957) > at org.jboss.seam.Component.getInstance(Component.java:1951) > at org.jboss.seam.Component.getInstance(Component.java:1924) > at org.jboss.seam.Component.getInstance(Component.java:1919) > at org.jboss.seam.exception.Exceptions.instance(Exceptions.java:256) > at org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114) > ... 31 more > Caused by: java.lang.NullPointerException > at org.jboss.seam.exception.Exceptions.parse(Exceptions.java:195) > at org.jboss.seam.exception.Exceptions.initialize(Exceptions.java:119) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) > at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:138) > at org.jboss.seam.Component.callComponentMethod(Component.java:2201) > at org.jboss.seam.Component.callCreateMethod(Component.java:2124) > at org.jboss.seam.Component.newInstance(Component.java:2084) > ... 38 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 20 14:34:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Tue, 20 Jan 2009 14:34:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-3820) JEE5 booking example fails on deploy In-Reply-To: <33406872.1228751856933.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <13177740.1232480044359.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards reassigned JBSEAM-3820: --------------------------------------- Assignee: Norman Richards > JEE5 booking example fails on deploy > ------------------------------------ > > Key: JBSEAM-3820 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3820 > Project: Seam > Issue Type: Bug > Components: Examples > Affects Versions: 2.1.1.CR2 > Environment: JDK 5 > JBoss AS 5.0.0.GA > Reporter: Jozef Hartinger > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > Attachments: jee5-as5-jdk5-login.txt, jee5-as5-jdk5.txt > > > When the example is being deployed I can see errors in server log. Despite these errors the main page loads however when I try to login the application fails because it is not able to create an instance of authenticator component. See jee5-as5-jdk5.txt for deployment errors and jee5-as5-jdk5-login.txt for the exception during login attempt. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 20 14:37:14 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Tue, 20 Jan 2009 14:37:14 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3813) Base64 should use logging API not System.out In-Reply-To: <25398471.1228533456452.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <438726.1232480234193.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3813. ----------------------------------- Resolution: Done Assignee: Norman Richards (was: Shane Bryzak) Thanks. > Base64 should use logging API not System.out > -------------------------------------------- > > Key: JBSEAM-3813 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3813 > Project: Seam > Issue Type: Bug > Reporter: Francisco Jose Peredo Noguez > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > Attachments: patch.txt > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 20 14:57:04 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Tue, 20 Jan 2009 14:57:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3702) NotBoundException when undeploying Seam examples on AS5 In-Reply-To: <20618941.1226666437087.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <29461874.1232481424306.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12448865#action_12448865 ] Norman Richards commented on JBSEAM-3702: ----------------------------------------- It's not clear to me that we can fix this. I've added support jboss-structure.xml to the example build, but it's not clear to me that we should be adding this file to the examples unless there's a simple way to craft a single jboss-structure.xml that will work for all examples and would not need to be updated. It seems that is not the case. In my opinion, the best we can do is find out what the officially supported way of undeploying an application is and recommend people use that method if they are concerned about this. In the past you could do this through the MBeans, but I'm not up to speed on JBoss 5 to know if that is still supported. > NotBoundException when undeploying Seam examples on AS5 > ------------------------------------------------------- > > Key: JBSEAM-3702 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3702 > Project: Seam > Issue Type: Bug > Components: EJB3, Examples > Affects Versions: 2.1.0.SP1 > Environment: JDK 6 > AS 5 trunk > Seam trunk r9564 > Reporter: Jozef Hartinger > Fix For: 2.1.2.CR1 > > Attachments: booking-undeploy.txt, dvdstore-undeploy.txt, wicket_undeploy_.txt > > > I am getting NotBoundException when undeploying Seam example when @Remove method is being called on statefull session bean. Affected examples are booking, dvdstore, nestedbooking, icefaces. Basic interaction with the example is needed before undeployment to reproduce the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 20 16:18:04 2009 From: jira-events at lists.jboss.org (Cody Lerum (JIRA)) Date: Tue, 20 Jan 2009 16:18:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3555) SeamMailAgain In-Reply-To: <3978595.1223977760796.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <28509111.1232486284176.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12448890#action_12448890 ] Cody Lerum commented on JBSEAM-3555: ------------------------------------ Seeing this on 2.1.1GA. Is there any workaround? > SeamMailAgain > ------------- > > Key: JBSEAM-3555 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3555 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.0.CR1 > Environment: JBoss AS 4.2.1.GA > JBoss Seam 2.1.0-SNAPSHOT (10.10. HudsonNo330) > Reporter: Markus Heidt > Assignee: Pete Muir > Fix For: 2.1.2.CR1 > > Attachments: RendererFacesContextFactory.java, server.log > > > Simple Mailing via Renderer doesn't work. > 'Seam-gen'erated a new project and added a new action 'sendMail' > Added the line to the action code: > Renderer.instance().render("/simple.xhtml"); > simple.xhtml is a modified version of the seam example (without #{person}) > Error after executing the action: > 2008-10-14 11:40:21,847 FATAL [javax.enterprise.resource.webcontainer.jsf.application] org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > javax.faces.el.EvaluationException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:91) > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:91) > ... > Caused by: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory > at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:256) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 20 17:12:03 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Tue, 20 Jan 2009 17:12:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-3869) Check for problematic component definitions at deployment In-Reply-To: <22337261.1230064747444.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <6653353.1232489523996.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards reassigned JBSEAM-3869: --------------------------------------- Assignee: Norman Richards > Check for problematic component definitions at deployment > --------------------------------------------------------- > > Key: JBSEAM-3869 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3869 > Project: Seam > Issue Type: Feature Request > Components: EJB3 > Reporter: Chris Bredesen > Assignee: Norman Richards > Priority: Minor > > Seam currently allows combinations such as: > @Stateless > @Name("NoConversationHere") > @Scope(ScopeType.CONVERSATION) > Which make no sense and can cause problems. If possible, Seam (or Web Beans!) should check for such things and WARN/ERROR on deployment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 20 17:17:05 2009 From: jira-events at lists.jboss.org (John Sublette (JIRA)) Date: Tue, 20 Jan 2009 17:17:05 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3449) Upgrade to latest RestEasy beta In-Reply-To: <21376851.1222121060720.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <8525618.1232489825098.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sublette updated JBSEAM-3449: ---------------------------------- Attachment: jboss-seam-resteasy-2.1.1.CR2.JBSEAM-3449-patched.jar To get it to work with the current latest (1.0-RC1), I did the resteasyBeta-8.txt patch, the @Startup change from Xiaofeng Lin, and also the following change. I just replaced the class files in the jar with the new ones and tested it out. I'll try to add the jar file for anyone else with this issue. Here's ResteasyResourceAdapter.java - Line108 and onward: HttpRequest in; ResteasyDispatcher dispatcher = (ResteasyDispatcher) Component.getInstance(ResteasyDispatcher.class); HttpResponse theResponse = new HttpServletResponseWrapper(response, dispatcher.getDispatcher().getProviderFactory()); in = new HttpServletInputMessage( request, theResponse, headers, uriInfo, request.getMethod().toUpperCase(), (SynchronousDispatcher)dispatcher.getDispatcher()); dispatcher.getDispatcher().invoke(in, theResponse); } }.run(); } finally { ResteasyProviderFactory.clearContextData(); log.debug("completed processing of REST request"); } } } > Upgrade to latest RestEasy beta > ------------------------------- > > Key: JBSEAM-3449 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3449 > Project: Seam > Issue Type: Feature Request > Components: WS > Affects Versions: 2.1.0.BETA1 > Reporter: Scott Olcott > Assignee: Jozef Hartinger > Fix For: 2.1.2.GA > > Attachments: jboss-seam-resteasy-2.1.1.CR2.JBSEAM-3449-patched.jar, resteasyBeta-8.txt > > > The latest beta is beta-8 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 21 08:01:03 2009 From: jira-events at lists.jboss.org (Ales Justin (JIRA)) Date: Wed, 21 Jan 2009 08:01:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3702) NotBoundException when undeploying Seam examples on AS5 In-Reply-To: <20618941.1226666437087.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <8443233.1232542863993.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12448969#action_12448969 ] Ales Justin commented on JBSEAM-3702: ------------------------------------- I think generating jboss-strucutre.xml should be trivial. You just need a small info about example's contents - could be even derived from application.xml. What did MBeans do? Invoked AS to undeploy and only then do deletion? > NotBoundException when undeploying Seam examples on AS5 > ------------------------------------------------------- > > Key: JBSEAM-3702 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3702 > Project: Seam > Issue Type: Bug > Components: EJB3, Examples > Affects Versions: 2.1.0.SP1 > Environment: JDK 6 > AS 5 trunk > Seam trunk r9564 > Reporter: Jozef Hartinger > Fix For: 2.1.2.CR1 > > Attachments: booking-undeploy.txt, dvdstore-undeploy.txt, wicket_undeploy_.txt > > > I am getting NotBoundException when undeploying Seam example when @Remove method is being called on statefull session bean. Affected examples are booking, dvdstore, nestedbooking, icefaces. Basic interaction with the example is needed before undeployment to reproduce the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 21 09:02:04 2009 From: jira-events at lists.jboss.org (Ales Justin (JIRA)) Date: Wed, 21 Jan 2009 09:02:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3702) NotBoundException when undeploying Seam examples on AS5 In-Reply-To: <20618941.1226666437087.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <4400926.1232546524171.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ales Justin updated JBSEAM-3702: -------------------------------- JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=146401 > NotBoundException when undeploying Seam examples on AS5 > ------------------------------------------------------- > > Key: JBSEAM-3702 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3702 > Project: Seam > Issue Type: Bug > Components: EJB3, Examples > Affects Versions: 2.1.0.SP1 > Environment: JDK 6 > AS 5 trunk > Seam trunk r9564 > Reporter: Jozef Hartinger > Fix For: 2.1.2.CR1 > > Attachments: booking-undeploy.txt, dvdstore-undeploy.txt, wicket_undeploy_.txt > > > I am getting NotBoundException when undeploying Seam example when @Remove method is being called on statefull session bean. Affected examples are booking, dvdstore, nestedbooking, icefaces. Basic interaction with the example is needed before undeployment to reproduce the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 21 09:52:15 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Wed, 21 Jan 2009 09:52:15 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3702) NotBoundException when undeploying Seam examples on AS5 In-Reply-To: <20618941.1226666437087.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <13552612.1232549535349.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12448993#action_12448993 ] Norman Richards commented on JBSEAM-3702: ----------------------------------------- Do you have a complete example of a jboss-structure.xml that works? Whenever I tried to create one, the only effect was that the application would be completely ignored and wouldn't deploy. Is it realistic to create a jboss-structure.xml that will work across multiple example apps with roughly the same structure? What about WAR files? I guess we would need two versions for each app - one for deploying as an EAR and for deploying as a WAR, right? Is there any way we can add metadata to the jboss-app.xml to indicate how we want the app treated? It seems like this should be at most a one-line change for an app, if not the default behavior for the server. Deleting the file from the deploy directory has always been a clean way to undeploy an application, and it's really strange that now we don't have a clean undeploy. I'm not trying to be overly critical. I'm just trying to figure out what our official answer is to someone who asls "How do I undeploy an application?". Before you could use the MBeans to deploy/undeploy an application. Undeploying did not remove the files from the deploy directory. In fact, you could easily use the MBeans to deploy/undeploy an application directly from your own project's build directory if you wanted. We generally didn't do that because making a connection to the MBeanServer required a login, which complicates things. But, it was definitely an option. > NotBoundException when undeploying Seam examples on AS5 > ------------------------------------------------------- > > Key: JBSEAM-3702 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3702 > Project: Seam > Issue Type: Bug > Components: EJB3, Examples > Affects Versions: 2.1.0.SP1 > Environment: JDK 6 > AS 5 trunk > Seam trunk r9564 > Reporter: Jozef Hartinger > Fix For: 2.1.2.CR1 > > Attachments: booking-undeploy.txt, dvdstore-undeploy.txt, wicket_undeploy_.txt > > > I am getting NotBoundException when undeploying Seam example when @Remove method is being called on statefull session bean. Affected examples are booking, dvdstore, nestedbooking, icefaces. Basic interaction with the example is needed before undeployment to reproduce the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 21 10:04:03 2009 From: jira-events at lists.jboss.org (Pete Muir (JIRA)) Date: Wed, 21 Jan 2009 10:04:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3702) NotBoundException when undeploying Seam examples on AS5 In-Reply-To: <20618941.1226666437087.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <2314508.1232550244079.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12448997#action_12448997 ] Pete Muir commented on JBSEAM-3702: ----------------------------------- Ales is going to investigate a generic solution for this tomorrow that we can automatically push into Seam apps. > NotBoundException when undeploying Seam examples on AS5 > ------------------------------------------------------- > > Key: JBSEAM-3702 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3702 > Project: Seam > Issue Type: Bug > Components: EJB3, Examples > Affects Versions: 2.1.0.SP1 > Environment: JDK 6 > AS 5 trunk > Seam trunk r9564 > Reporter: Jozef Hartinger > Fix For: 2.1.2.CR1 > > Attachments: booking-undeploy.txt, dvdstore-undeploy.txt, wicket_undeploy_.txt > > > I am getting NotBoundException when undeploying Seam example when @Remove method is being called on statefull session bean. Affected examples are booking, dvdstore, nestedbooking, icefaces. Basic interaction with the example is needed before undeployment to reproduce the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 21 10:12:03 2009 From: jira-events at lists.jboss.org (Ales Justin (JIRA)) Date: Wed, 21 Jan 2009 10:12:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3702) NotBoundException when undeploying Seam examples on AS5 In-Reply-To: <20618941.1226666437087.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <24055667.1232550724004.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12448999#action_12448999 ] Ales Justin commented on JBSEAM-3702: ------------------------------------- http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203667#4203667 > NotBoundException when undeploying Seam examples on AS5 > ------------------------------------------------------- > > Key: JBSEAM-3702 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3702 > Project: Seam > Issue Type: Bug > Components: EJB3, Examples > Affects Versions: 2.1.0.SP1 > Environment: JDK 6 > AS 5 trunk > Seam trunk r9564 > Reporter: Jozef Hartinger > Fix For: 2.1.2.CR1 > > Attachments: booking-undeploy.txt, dvdstore-undeploy.txt, wicket_undeploy_.txt > > > I am getting NotBoundException when undeploying Seam example when @Remove method is being called on statefull session bean. Affected examples are booking, dvdstore, nestedbooking, icefaces. Basic interaction with the example is needed before undeployment to reproduce the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 21 11:29:03 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Wed, 21 Jan 2009 11:29:03 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3869) Check for problematic component definitions at deployment In-Reply-To: <22337261.1230064747444.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <12788138.1232555344006.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3869. ----------------------------------- Fix Version/s: 2.1.2.CR1 Resolution: Done We already do checks for component/scope mismatches. i've added this one as a WARN. Feel free to open JIRAs for any others you think we should catch. > Check for problematic component definitions at deployment > --------------------------------------------------------- > > Key: JBSEAM-3869 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3869 > Project: Seam > Issue Type: Feature Request > Components: EJB3 > Reporter: Chris Bredesen > Assignee: Norman Richards > Priority: Minor > Fix For: 2.1.2.CR1 > > > Seam currently allows combinations such as: > @Stateless > @Name("NoConversationHere") > @Scope(ScopeType.CONVERSATION) > Which make no sense and can cause problems. If possible, Seam (or Web Beans!) should check for such things and WARN/ERROR on deployment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 21 13:44:04 2009 From: jira-events at lists.jboss.org (Milos Zikic (JIRA)) Date: Wed, 21 Jan 2009 13:44:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3906) Attachements are not shown in outlook Message-ID: <33357125.1232563444632.JavaMail.jira@cloud.prod.atl2.jboss.com> Attachements are not shown in outlook ------------------------------------- Key: JBSEAM-3906 URL: https://jira.jboss.org/jira/browse/JBSEAM-3906 Project: Seam Issue Type: Bug Components: Mail Affects Versions: 2.1.0.SP1 Environment: Any Reporter: Milos Zikic Assignee: Pete Muir When sending mail with attachements, attachments are not shown in Outlook 2007. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 21 14:31:04 2009 From: jira-events at lists.jboss.org (Pawel Wrzeszcz (JIRA)) Date: Wed, 21 Jan 2009 14:31:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3907) Exclude build directories in generated IntelliJ IDEA project Message-ID: <11418642.1232566264251.JavaMail.jira@cloud.prod.atl2.jboss.com> Exclude build directories in generated IntelliJ IDEA project ------------------------------------------------------------ Key: JBSEAM-3907 URL: https://jira.jboss.org/jira/browse/JBSEAM-3907 Project: Seam Issue Type: Patch Components: Tools Affects Versions: 2.1.1.GA Reporter: Pawel Wrzeszcz Assignee: Dan Allen Priority: Minor Directories 'dist' and 'exploded-archives' should be marked as excluded in the IntelliJ IDEA module file created by seam-gen. I realize this is minor, but saves a couple of clicks and prevents IDEA from 1) reloading a whole project during the build and 2) detecting facets in the build directories. Really short path attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 21 14:33:04 2009 From: jira-events at lists.jboss.org (Pawel Wrzeszcz (JIRA)) Date: Wed, 21 Jan 2009 14:33:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3907) Exclude build directories in generated IntelliJ IDEA project In-Reply-To: <11418642.1232566264251.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <12821081.1232566384144.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pawel Wrzeszcz updated JBSEAM-3907: ----------------------------------- Attachment: JBSEAM-3907-IDEA-exclude-dirs.patch > Exclude build directories in generated IntelliJ IDEA project > ------------------------------------------------------------ > > Key: JBSEAM-3907 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3907 > Project: Seam > Issue Type: Patch > Components: Tools > Affects Versions: 2.1.1.GA > Reporter: Pawel Wrzeszcz > Assignee: Dan Allen > Priority: Minor > Attachments: JBSEAM-3907-IDEA-exclude-dirs.patch > > > Directories 'dist' and 'exploded-archives' should be marked as excluded in the IntelliJ IDEA module file created by seam-gen. > I realize this is minor, but saves a couple of clicks and prevents IDEA from 1) reloading a whole project during the build and 2) detecting facets in the build directories. > Really short path attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 21 15:50:04 2009 From: jira-events at lists.jboss.org (Cameron Fieber (JIRA)) Date: Wed, 21 Jan 2009 15:50:04 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3908) RememberMe on JBoss 5 loses part of the username when formatted as an email address Message-ID: <8797594.1232571004411.JavaMail.jira@cloud.prod.atl2.jboss.com> RememberMe on JBoss 5 loses part of the username when formatted as an email address ----------------------------------------------------------------------------------- Key: JBSEAM-3908 URL: https://jira.jboss.org/jira/browse/JBSEAM-3908 Project: Seam Issue Type: Bug Components: Security Affects Versions: 2.1.1.GA, 2.1.1.CR1 Environment: JBoss 5.0.0.GA Java 1.6.0_07 Mac OS X 10.5.6 Both Firefox 3.0.5 and Safari 3.2.1 Reporter: Cameron Fieber This is reproducable with the seam-space sample application: # Deploy seam-space on JBoss 5.0.0.GA # Sign up for a new account, and for username use an email address (user at host.net) # Sign out. # Sign in with the username and password with 'Remember Me' checked # Sign out. You should notice that the username that is autopopulated is only 'user' not 'user at host.net' I've tested it on both 2.1.1.CR1 and 2.1.1.GA. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 21 17:32:05 2009 From: jira-events at lists.jboss.org (Ben Groeneveld (JIRA)) Date: Wed, 21 Jan 2009 17:32:05 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2371) Integration testing Seam components with Maven In-Reply-To: <15535346.1197495953674.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <23039738.1232577125324.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449102#action_12449102 ] Ben Groeneveld commented on JBSEAM-2371: ---------------------------------------- Thanks for the great work! We've downloaded the testproject-master-JBSEAM-2371.zip, added the dependency patch Jason describes as and this works well. Needed to up the version of TestNG to 5.8 because the @BeforeClass annotation fails otherwise. We need @BeforeClass because we use a modified SeamTest that loads only one Hibernate session factory for a group or suite. We have also added dbunit support which brings in dependency conflict for xerces, but that was resolved by adding it also to the dependencies Jason added. Note that these *must* appear first in order to debug with TestNG in eclipse. This is our first maven project and so far we have found a maven solution for each of our hurdles - nice. > Integration testing Seam components with Maven > ---------------------------------------------- > > Key: JBSEAM-2371 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2371 > Project: Seam > Issue Type: Task > Components: Build, Test Harness > Affects Versions: 2.0.0.GA > Environment: Maven 2.0.7 > Reporter: Siarhei Dudzin > Priority: Critical > Fix For: The future > > Attachments: jg-seamtest-1.0.tgz, maven-seam-microcontainer-testng-template.zip, tech-stack-1.0.1.pom, testproject-master-JBSEAM-2371.zip > > > Various users have reported integration testing with Seam is not working in 'Mavenized' projects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 21 20:19:14 2009 From: jira-events at lists.jboss.org (Norman Richards (JIRA)) Date: Wed, 21 Jan 2009 20:19:14 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3851) Seam reflection has lower access than Java reflection In-Reply-To: <1113906.1229538955769.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <7579909.1232587154438.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Richards closed JBSEAM-3851. ----------------------------------- Fix Version/s: 2.1.2.CR1 Resolution: Done Assignee: Norman Richards It took a while to convince myself this was a necessary change. I was not as concerned about setAccessible() access as I was that the proxies will fail on legitimate package protected access. Since we do similar things elsewhere, so it should be ok to assume that anyone who has successfully called into the proxy should be able to call the same method on the proxied object. > Seam reflection has lower access than Java reflection > ----------------------------------------------------- > > Key: JBSEAM-3851 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3851 > Project: Seam > Issue Type: Bug > Affects Versions: 2.0.2.SP1 > Environment: Jboss Embedded, Java 5 > Reporter: Gabriel Go?c > Assignee: Norman Richards > Fix For: 2.1.2.CR1 > > > This simple class is to be unit-tested, the SeamTest way: > @Name("hibean") > public class HiSayerBean { > > public HiSayerBean () { > } > protected void sayHi(){ > System.out.println("hello"); > } > } > All tests occur in the SeamTest framework: > new ComponentTest() { > @Override > protected void testComponents() throws Exception { > //test code > } > }.run(); > Using Java Reflection - works: > HiSayerBean impl = new HiSayerBean(); > Method m = impl.getClass().getDeclaredMethod("sayHi"); > m.setAccessible(true); > m.invoke(impl); > Using Java Reflection with Seam - fails: > HiSayerBean impl = (HiSayerBean) getInstance("hibean"); > Method m = impl.getClass().getDeclaredMethod("sayHi"); > m.setAccessible(true); > m.invoke(impl); > Error log: > java.lang.reflect.InvocationTargetException > (...) > Caused by: java.lang.IllegalAccessException: Class org.jboss.seam.util.Reflections can not access a member of class HiSayerBean with modifiers "protected" > at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65) > at java.lang.reflect.Method.invoke(Method.java:578) > at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) > at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) > at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) > at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:31) > at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) > at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:46) > at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) > at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42) > at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) > at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) > at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166) > at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102) > at HiSayerBean_$$_javassist_0.sayHi(HiSayerBean_$$_javassist_0.java) > ... 29 more > So, using Seam gives me a lower capacity to access methods in a reflected class than with raw Java. I'm not sure if it's a bug or a feature request though. But it would be nice to be granted to do this in unit-testing. > Please note that access to a private method in the same way than above works with Java but produces a java.lang.NoSuchMethodException with Seam. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 22 11:14:44 2009 From: jira-events at lists.jboss.org (Clint Popetz (JIRA)) Date: Thu, 22 Jan 2009 11:14:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3909) Make seamManagedTransactions mean something for wicket/seam apps Message-ID: <9120082.1232640884258.JavaMail.jira@cloud.prod.atl2.jboss.com> Make seamManagedTransactions mean something for wicket/seam apps ---------------------------------------------------------------- Key: JBSEAM-3909 URL: https://jira.jboss.org/jira/browse/JBSEAM-3909 Project: Seam Issue Type: Feature Request Components: Wicket Reporter: Clint Popetz Assignee: Clint Popetz -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 22 11:22:44 2009 From: jira-events at lists.jboss.org (Marek Novotny (JIRA)) Date: Thu, 22 Jan 2009 11:22:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3570) Update the WebSphere reference guide chapter to WebSphere 7.0 In-Reply-To: <22882193.1224087201166.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <27764369.1232641364327.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449241#action_12449241 ] Marek Novotny commented on JBSEAM-3570: --------------------------------------- WAS V7 JSF implementation is somehow broken. The processing is hanging while you send request for home page of jpa example: [22.1.09 16:34:52:861 SE?] 00000013 config I Initializing Sun's JavaServer Faces implementation (1.2_07-b03-FCS) for context '/seam-jpa' [22.1.09 16:34:54:774 SE?] 00000013 servlet I com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0242I: [jboss-seam-jpa_war] [/seam-jpa] [Faces Servlet]: Inicializace prob?hla ?sp??n?. [22.1.09 16:34:54:781 SE?] 00000013 webcontainer I com.ibm.ws.wswebcontainer.VirtualHost addWebApplication SRVE0250I: Webov? modul null byl sv?z?n s virtu?ln?m hostitelem default_host[*:9080,*:80,*:9443,*:5060,*:5061,*:443]. [22.1.09 16:34:54:809 SE?] 00000013 ApplicationMg A WSVR0221I: Application started: jboss-seam-jpa_war [22.1.09 16:34:54:811 SE?] 00000013 CompositionUn A WSVR0191I: Composition unit WebSphere:cuname=jboss-seam-jpa_war in BLA WebSphere:blaname=jboss-seam-jpa_war started. [22.1.09 16:35:28:731 SE?] 00000011 SeamFilter I org.jboss.seam.servlet.SeamFilter init Initializing filter: org.jboss.seam.web.ajax4jsfFilter [22.1.09 16:35:28:814 SE?] 00000011 CacheManager I org.ajax4jsf.cache.CacheManager getCacheFactory Selected [org.ajax4jsf.cache.LRUMapCacheFactory] cache factory [22.1.09 16:46:34:256 SE?] 0000001c ThreadMonitor W WSVR0605W: Thread "WebContainer : 0" (00000011) has been active for 665558 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung. at org.ajax4jsf.cache.ServletContextInitMap$1.size(ServletContextInitMap.java:78) at java.util.AbstractMap.size(Unknown Source) at java.util.AbstractMap.isEmpty(Unknown Source) at java.util.AbstractMap.toString(Unknown Source) at java.lang.String.valueOf(String.java:1511) at java.lang.StringBuilder.append(StringBuilder.java:191) at org.ajax4jsf.cache.LRUMapCacheFactory.createCache(LRUMapCacheFactory.java:44) at org.ajax4jsf.resource.InternetResourceService.init(InternetResourceService.java:107) at org.ajax4jsf.webapp.BaseFilter.init(BaseFilter.java:188) at org.jboss.seam.web.Ajax4jsfFilter.init(Ajax4jsfFilter.java:82) at org.jboss.seam.servlet.SeamFilter.init(SeamFilter.java:97) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.init(FilterInstanceWrapper.java:140) at com.ibm.ws.webcontainer.filter.WebAppFilterManager._loadFilter(WebAppFilterManager.java:509) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.loadFilter(WebAppFilterManager.java:423) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.getFilterInstanceWrapper(WebAppFilterManager.java:282) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.getFilterChain(WebAppFilterManager.java:340) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:812) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:917) at com.ibm.ws.webcontainer.servlet.FileServletWrapper.handleRequest(FileServletWrapper.java:489) at com.ibm.ws.webcontainer.servlet.StaticFileServletWrapperImpl.handleRequest(StaticFileServletWrapperImpl.java:62) at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:803) at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3610) at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:274) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:926) at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1557) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:173) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:455) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:384) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:272) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113) 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$1.run(AsyncChannelFuture.java:205) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1527) [22.1.09 17:05:19:388 SE?] 00000005 ArchiveDeploy W ADMA0142W: Trying to close the archive that is already closed. > Update the WebSphere reference guide chapter to WebSphere 7.0 > ------------------------------------------------------------- > > Key: JBSEAM-3570 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3570 > Project: Seam > Issue Type: Task > Components: Platform interoperability > Affects Versions: 2.1.0.CR1 > Reporter: Jay Balunas > Assignee: Marek Novotny > Fix For: 2.1.2.CR1 > > > WebSphere 7.0 has gone GA and now fully supports jee5 with out the various issues before. This needs to be investigated, tested, and the reference guide needs to be updated. > Search forum, and jira for related issues and notes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 22 12:35:44 2009 From: jira-events at lists.jboss.org (=?UTF-8?Q?Lo=C3=83=C2=AFc_Lef=C3=83=C2=A8vre_=28JIRA=29?=) Date: Thu, 22 Jan 2009 12:35:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3904) Property 'logout' not found on type Identity when commenting XHTML In-Reply-To: <4312243.1232459464030.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <241361.1232645744177.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449282#action_12449282 ] Lo??c Lef??vre commented on JBSEAM-3904: ---------------------------------------- Though I've read the "FM" I didn't find any place to solve this kind of issue. Thanks to google, I finally found: facelets.SKIP_COMMENTS true SO THANKS GOOGLE! (oups my keyboard was locked...) > Property 'logout' not found on type Identity when commenting XHTML > ------------------------------------------------------------------ > > Key: JBSEAM-3904 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3904 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.1.GA > Environment: Windows XP > JBoss AS 5.0.0 > Reporter: Lo??c Lef??vre > > If I comment in booking example the file view/template.xhtml: > ... >
> > ... > for test purposes, I get the following exception: > 14:45:12,255 ERROR [viewhandler] Error Rendering View[/main.xhtml] > javax.el.PropertyNotFoundException: Property 'logout' not found on type org.jboss.seam.security.Identity > at javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:193) > at javax.el.BeanELResolver$BeanProperties.access$400(BeanELResolver.java:170) > at javax.el.BeanELResolver.property(BeanELResolver.java:279) > at javax.el.BeanELResolver.getValue(BeanELResolver.java:60) > at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) > at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72) > at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53) > at org.jboss.el.parser.AstValue.getValue(AstValue.java:67) > at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) > at com.sun.facelets.el.ELText$ELTextVariable.toString(ELText.java:174) > at com.sun.facelets.el.ELText$ELTextComposite.toString(ELText.java:115) > at com.sun.facelets.compiler.CommentInstruction.write(CommentInstruction.java:38) > at com.sun.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:39) > at com.sun.facelets.compiler.UILeaf.encodeAll(UILeaf.java:149) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:933) > at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:592) > at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) > at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:196) > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) > at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) > at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) > at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) > at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) > at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 22 12:41:44 2009 From: jira-events at lists.jboss.org (Pete Muir (JIRA)) Date: Thu, 22 Jan 2009 12:41:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3904) Property 'logout' not found on type Identity when commenting XHTML In-Reply-To: <4312243.1232459464030.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <9440958.1232646104196.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449285#action_12449285 ] Pete Muir commented on JBSEAM-3904: ----------------------------------- It is clearly documented in both the facelets manual https://facelets.dev.java.net/nonav/docs/dev/docbook.html#config-webapp-init and in the Seam FAQ http://seamframework.org/Documentation/WhyIsCommentedCodeInMyXHTMLFileExecuted. Try reading lessons. > Property 'logout' not found on type Identity when commenting XHTML > ------------------------------------------------------------------ > > Key: JBSEAM-3904 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3904 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.1.GA > Environment: Windows XP > JBoss AS 5.0.0 > Reporter: Lo??c Lef??vre > > If I comment in booking example the file view/template.xhtml: > ... >
> > ... > for test purposes, I get the following exception: > 14:45:12,255 ERROR [viewhandler] Error Rendering View[/main.xhtml] > javax.el.PropertyNotFoundException: Property 'logout' not found on type org.jboss.seam.security.Identity > at javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:193) > at javax.el.BeanELResolver$BeanProperties.access$400(BeanELResolver.java:170) > at javax.el.BeanELResolver.property(BeanELResolver.java:279) > at javax.el.BeanELResolver.getValue(BeanELResolver.java:60) > at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) > at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72) > at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53) > at org.jboss.el.parser.AstValue.getValue(AstValue.java:67) > at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) > at com.sun.facelets.el.ELText$ELTextVariable.toString(ELText.java:174) > at com.sun.facelets.el.ELText$ELTextComposite.toString(ELText.java:115) > at com.sun.facelets.compiler.CommentInstruction.write(CommentInstruction.java:38) > at com.sun.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:39) > at com.sun.facelets.compiler.UILeaf.encodeAll(UILeaf.java:149) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:933) > at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:592) > at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) > at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:196) > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) > at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) > at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) > at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) > at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) > at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 22 17:49:44 2009 From: jira-events at lists.jboss.org (=?UTF-8?Q?Rene_Felgentr=C3=83=C2=A4ger_=28JIRA=29?=) Date: Thu, 22 Jan 2009 17:49:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3910) columns to process for workbook generation should be custumizable, as frontend and sheet might differ Message-ID: <7897302.1232664584165.JavaMail.jira@cloud.prod.atl2.jboss.com> columns to process for workbook generation should be custumizable, as frontend and sheet might differ ----------------------------------------------------------------------------------------------------- Key: JBSEAM-3910 URL: https://jira.jboss.org/jira/browse/JBSEAM-3910 Project: Seam Issue Type: Feature Request Components: Excel Affects Versions: 2.1.1.GA Reporter: Rene Felgentr??ger So far, the excel-exporter tries to generate a workbook by copying all columns of the datatable ignoring the rendered attribute. Furthermore, it should be possible to ignore "action/details" columns, as they are useless in an excel-sheet -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 22 18:44:44 2009 From: jira-events at lists.jboss.org (=?UTF-8?Q?Lo=C3=83=C2=AFc_Lef=C3=83=C2=A8vre_=28JIRA=29?=) Date: Thu, 22 Jan 2009 18:44:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3904) Property 'logout' not found on type Identity when commenting XHTML In-Reply-To: <4312243.1232459464030.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <25912419.1232667884178.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449365#action_12449365 ] Lo??c Lef??vre commented on JBSEAM-3904: ---------------------------------------- I'm sorry, I'm generally reading doc\reference\en-US\pdf\seam_reference.pdf (for convenience). As it's "reference" I thought everything could be find here. Maybe a FAQ section in this document could help or a "common troubleshootings" section. This could avoid this kind of issue when a newbie (as I am for Seam, JSF...) encounters this kind of problem. I find Seam very useful and those issues I created is my participation to bring this framework to a larger public. I'll try to read more posts on the seam forum but I'll surely recreate issues if I don't find any clue... Best regards, Lo?c > Property 'logout' not found on type Identity when commenting XHTML > ------------------------------------------------------------------ > > Key: JBSEAM-3904 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3904 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.1.GA > Environment: Windows XP > JBoss AS 5.0.0 > Reporter: Lo??c Lef??vre > > If I comment in booking example the file view/template.xhtml: > ... >
> > ... > for test purposes, I get the following exception: > 14:45:12,255 ERROR [viewhandler] Error Rendering View[/main.xhtml] > javax.el.PropertyNotFoundException: Property 'logout' not found on type org.jboss.seam.security.Identity > at javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:193) > at javax.el.BeanELResolver$BeanProperties.access$400(BeanELResolver.java:170) > at javax.el.BeanELResolver.property(BeanELResolver.java:279) > at javax.el.BeanELResolver.getValue(BeanELResolver.java:60) > at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) > at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72) > at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53) > at org.jboss.el.parser.AstValue.getValue(AstValue.java:67) > at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) > at com.sun.facelets.el.ELText$ELTextVariable.toString(ELText.java:174) > at com.sun.facelets.el.ELText$ELTextComposite.toString(ELText.java:115) > at com.sun.facelets.compiler.CommentInstruction.write(CommentInstruction.java:38) > at com.sun.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:39) > at com.sun.facelets.compiler.UILeaf.encodeAll(UILeaf.java:149) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:933) > at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:592) > at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) > at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:196) > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) > at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) > at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) > at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) > at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) > at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 22 18:50:44 2009 From: jira-events at lists.jboss.org (Pete Muir (JIRA)) Date: Thu, 22 Jan 2009 18:50:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3904) Property 'logout' not found on type Identity when commenting XHTML In-Reply-To: <4312243.1232459464030.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <4674578.1232668244168.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449368#action_12449368 ] Pete Muir commented on JBSEAM-3904: ----------------------------------- If you do this I will have your JIRA account disabled. JIRA is not for support. > Property 'logout' not found on type Identity when commenting XHTML > ------------------------------------------------------------------ > > Key: JBSEAM-3904 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3904 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.1.GA > Environment: Windows XP > JBoss AS 5.0.0 > Reporter: Lo??c Lef??vre > > If I comment in booking example the file view/template.xhtml: > ... >
> > ... > for test purposes, I get the following exception: > 14:45:12,255 ERROR [viewhandler] Error Rendering View[/main.xhtml] > javax.el.PropertyNotFoundException: Property 'logout' not found on type org.jboss.seam.security.Identity > at javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:193) > at javax.el.BeanELResolver$BeanProperties.access$400(BeanELResolver.java:170) > at javax.el.BeanELResolver.property(BeanELResolver.java:279) > at javax.el.BeanELResolver.getValue(BeanELResolver.java:60) > at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) > at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72) > at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53) > at org.jboss.el.parser.AstValue.getValue(AstValue.java:67) > at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) > at com.sun.facelets.el.ELText$ELTextVariable.toString(ELText.java:174) > at com.sun.facelets.el.ELText$ELTextComposite.toString(ELText.java:115) > at com.sun.facelets.compiler.CommentInstruction.write(CommentInstruction.java:38) > at com.sun.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:39) > at com.sun.facelets.compiler.UILeaf.encodeAll(UILeaf.java:149) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:933) > at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:592) > at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) > at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:196) > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) > at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) > at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) > at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) > at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) > at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 23 05:38:44 2009 From: jira-events at lists.jboss.org (Marek Novotny (JIRA)) Date: Fri, 23 Jan 2009 05:38:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3570) Update the WebSphere reference guide chapter to WebSphere 7.0 In-Reply-To: <22882193.1224087201166.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <20147974.1232707124550.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449404#action_12449404 ] Marek Novotny commented on JBSEAM-3570: --------------------------------------- When I created previous comment I was not right about the cause :-/, the root cause is Richfaces 3.2.2.SR1 and its implementation org.ajax4jsf.cache.ServletContextInitMap of java.util.AbstractMap. It is in an infinite loop in method size. I have found the related JIRA issue https://jira.jboss.org/jira/browse/RF-4537. So it points us to the upgrade of Richfaces to 3.3.0 version > Update the WebSphere reference guide chapter to WebSphere 7.0 > ------------------------------------------------------------- > > Key: JBSEAM-3570 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3570 > Project: Seam > Issue Type: Task > Components: Platform interoperability > Affects Versions: 2.1.0.CR1 > Reporter: Jay Balunas > Assignee: Marek Novotny > Fix For: 2.1.2.CR1 > > > WebSphere 7.0 has gone GA and now fully supports jee5 with out the various issues before. This needs to be investigated, tested, and the reference guide needs to be updated. > Search forum, and jira for related issues and notes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 23 05:52:44 2009 From: jira-events at lists.jboss.org (Daniel Roth (JIRA)) Date: Fri, 23 Jan 2009 05:52:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3910) columns to process for workbook generation should be custumizable, as frontend and sheet might differ In-Reply-To: <7897302.1232664584165.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <25664947.1232707964692.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Roth updated JBSEAM-3910: -------------------------------- JBoss Forum Reference: http://www.seamframework.org/Community/ExcelGenerationFromDataTable Assignee: Daniel Roth > columns to process for workbook generation should be custumizable, as frontend and sheet might differ > ----------------------------------------------------------------------------------------------------- > > Key: JBSEAM-3910 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3910 > Project: Seam > Issue Type: Feature Request > Components: Excel > Affects Versions: 2.1.1.GA > Reporter: Rene Felgentr??ger > Assignee: Daniel Roth > > So far, the excel-exporter tries to generate a workbook by copying all columns of the datatable ignoring the rendered attribute. > Furthermore, it should be possible to ignore "action/details" columns, as they are useless in an excel-sheet -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 23 09:18:44 2009 From: jira-events at lists.jboss.org (Marek Novotny (JIRA)) Date: Fri, 23 Jan 2009 09:18:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3570) Update the WebSphere reference guide chapter to WebSphere 7.0 In-Reply-To: <22882193.1224087201166.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <21326945.1232720324413.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449450#action_12449450 ] Marek Novotny commented on JBSEAM-3570: --------------------------------------- workaround from RF-4537 is not working for me > Update the WebSphere reference guide chapter to WebSphere 7.0 > ------------------------------------------------------------- > > Key: JBSEAM-3570 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3570 > Project: Seam > Issue Type: Task > Components: Platform interoperability > Affects Versions: 2.1.0.CR1 > Reporter: Jay Balunas > Assignee: Marek Novotny > Fix For: 2.1.2.CR1 > > > WebSphere 7.0 has gone GA and now fully supports jee5 with out the various issues before. This needs to be investigated, tested, and the reference guide needs to be updated. > Search forum, and jira for related issues and notes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 23 16:02:54 2009 From: jira-events at lists.jboss.org (Adam Montague (JIRA)) Date: Fri, 23 Jan 2009 16:02:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3911) zipped ear files cause seam NullPointerException on deployment Message-ID: <6944574.1232744574629.JavaMail.jira@cloud.prod.atl2.jboss.com> zipped ear files cause seam NullPointerException on deployment -------------------------------------------------------------- Key: JBSEAM-3911 URL: https://jira.jboss.org/jira/browse/JBSEAM-3911 Project: Seam Issue Type: Bug Environment: Jboss 5.0.0-GA, jdk 1.6.0_07 Reporter: Adam Montague A webapp using seam that is deployed as a zipped ear fails to deploy. First you get an exception like this for each war that uses seam: 15:55:08,634 WARN [URLScanner] could not read entries java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.(ZipFile.java:114) at java.util.zip.ZipFile.(ZipFile.java:131) at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:111) at org.jboss.seam.deployment.URLScanner.handle(URLScanner.java:98) at org.jboss.seam.deployment.URLScanner.scanResources(URLScanner.java:81) at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrateg y.java:67) at org.jboss.seam.init.Initialization.create(Initialization.java:102) at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3910) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4393) at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(Tomca tDeployment.java:367) at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeploym ent.java:146) at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:460) at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) at org.jboss.web.deployers.WebModule.start(WebModule.java:96) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:2 5) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) at $Proxy36.start(Unknown Source) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLif ecycleAction.java:42) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLif ecycleAction.java:37) at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallActi on(SimpleControllerContextAction.java:62) at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessCon trollerContextAction.java:71) at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractContr ollerContextActions.java:51) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerCo ntext.java:348) at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerC ontext.java:286) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:159 8) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.j ava:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. java:1062) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.system.ServiceController.doChange(ServiceController.java:688) at org.jboss.system.ServiceController.start(ServiceController.java:460) at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:146) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:104) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:45) at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy( AbstractSimpleRealDeployer.java:62) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDe ployer.java:50) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:1 71) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:143 9) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersI mpl.java:1157) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersI mpl.java:1178) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersI mpl.java:1210) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098 ) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerCo ntext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:159 8) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.j ava:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. java:1062) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545 ) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileS erviceBootstrap.java:304) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileService Bootstrap.java:205) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) at org.jboss.Main.boot(Main.java:209) at org.jboss.Main$1.run(Main.java:547) at java.lang.Thread.run(Thread.java:619) Then you get the following exception for the first war, causing deployment to fail: 15:16:26,981 ERROR [[/merlin/affiliate]] Exception sending context initialized event to listen er instance of class org.jboss.seam.servlet.SeamListener java.lang.NullPointerException at org.jboss.seam.init.Initialization.installComponents(Initialization.java:958) at org.jboss.seam.init.Initialization.init(Initialization.java:589) at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3910) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4393) at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(Tomca tDeployment.java:367) at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeploym ent.java:146) at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:460) at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) at org.jboss.web.deployers.WebModule.start(WebModule.java:96) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:2 5) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) at $Proxy36.start(Unknown Source) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLif ecycleAction.java:42) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLif ecycleAction.java:37) at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallActi on(SimpleControllerContextAction.java:62) at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessCon trollerContextAction.java:71) at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractContr ollerContextActions.java:51) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerCo ntext.java:348) at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerC ontext.java:286) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:159 8) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.j ava:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. java:1062) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.system.ServiceController.doChange(ServiceController.java:688) at org.jboss.system.ServiceController.start(ServiceController.java:460) at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:146) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:104) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:45) at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy( AbstractSimpleRealDeployer.java:62) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDe ployer.java:50) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:1 71) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:143 9) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersI mpl.java:1157) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersI mpl.java:1178) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersI mpl.java:1210) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098 ) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerCo ntext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:159 8) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.j ava:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. java:1062) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545 ) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileS erviceBootstrap.java:304) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileService Bootstrap.java:205) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) at org.jboss.Main.boot(Main.java:209) at org.jboss.Main$1.run(Main.java:547) at java.lang.Thread.run(Thread.java:619) If you unzip the ear, then you still get the zipexceptions for each war in the ear, but the final exception does not happen and the deployment succeeds. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 23 16:04:44 2009 From: jira-events at lists.jboss.org (Adam Montague (JIRA)) Date: Fri, 23 Jan 2009 16:04:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3911) zipped ear files cause seam NullPointerException on deployment In-Reply-To: <6944574.1232744574629.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <1096912.1232744684207.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Montague updated JBSEAM-3911: ---------------------------------- Affects Version/s: 2.0.2.SP1 > zipped ear files cause seam NullPointerException on deployment > -------------------------------------------------------------- > > Key: JBSEAM-3911 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3911 > Project: Seam > Issue Type: Bug > Affects Versions: 2.0.2.SP1 > Environment: Jboss 5.0.0-GA, jdk 1.6.0_07 > Reporter: Adam Montague > > A webapp using seam that is deployed as a zipped ear fails to deploy. First you get an exception like this for each war that uses seam: > 15:55:08,634 WARN [URLScanner] could not read entries > java.util.zip.ZipException: error in opening zip file > at java.util.zip.ZipFile.open(Native Method) > at java.util.zip.ZipFile.(ZipFile.java:114) > at java.util.zip.ZipFile.(ZipFile.java:131) > at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:111) > at org.jboss.seam.deployment.URLScanner.handle(URLScanner.java:98) > at org.jboss.seam.deployment.URLScanner.scanResources(URLScanner.java:81) > at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrateg > y.java:67) > at org.jboss.seam.init.Initialization.create(Initialization.java:102) > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34) > at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3910) > at org.apache.catalina.core.StandardContext.start(StandardContext.java:4393) > at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(Tomca > tDeployment.java:367) > at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeploym > ent.java:146) > at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:460) > at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) > at org.jboss.web.deployers.WebModule.start(WebModule.java:96) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:2 > 5) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) > at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) > at $Proxy36.start(Unknown Source) > at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLif > ecycleAction.java:42) > at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLif > ecycleAction.java:37) > at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallActi > on(SimpleControllerContextAction.java:62) > at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessCon > trollerContextAction.java:71) > at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractContr > ollerContextActions.java:51) > at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerCo > ntext.java:348) > at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerC > ontext.java:286) > at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:159 > 8) > at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.j > ava:934) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. > java:1062) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. > java:984) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) > at org.jboss.system.ServiceController.doChange(ServiceController.java:688) > at org.jboss.system.ServiceController.start(ServiceController.java:460) > at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:146) > at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:104) > at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:45) > at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy( > AbstractSimpleRealDeployer.java:62) > at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDe > ployer.java:50) > at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:1 > 71) > at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:143 > 9) > at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersI > mpl.java:1157) > at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersI > mpl.java:1178) > at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersI > mpl.java:1210) > at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098 > ) > at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerCo > ntext.java:348) > at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:159 > 8) > at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.j > ava:934) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. > java:1062) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. > java:984) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) > at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) > at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545 > ) > at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileS > erviceBootstrap.java:304) > at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileService > Bootstrap.java:205) > at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) > at org.jboss.Main.boot(Main.java:209) > at org.jboss.Main$1.run(Main.java:547) > at java.lang.Thread.run(Thread.java:619) > Then you get the following exception for the first war, causing deployment to fail: > 15:16:26,981 ERROR [[/merlin/affiliate]] Exception sending context initialized event to listen > er instance of class org.jboss.seam.servlet.SeamListener > java.lang.NullPointerException > at org.jboss.seam.init.Initialization.installComponents(Initialization.java:958) > at org.jboss.seam.init.Initialization.init(Initialization.java:589) > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34) > at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3910) > at org.apache.catalina.core.StandardContext.start(StandardContext.java:4393) > at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(Tomca > tDeployment.java:367) > at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeploym > ent.java:146) > at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:460) > at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) > at org.jboss.web.deployers.WebModule.start(WebModule.java:96) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:2 > 5) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) > at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) > at $Proxy36.start(Unknown Source) > at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLif > ecycleAction.java:42) > at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLif > ecycleAction.java:37) > at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallActi > on(SimpleControllerContextAction.java:62) > at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessCon > trollerContextAction.java:71) > at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractContr > ollerContextActions.java:51) > at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerCo > ntext.java:348) > at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerC > ontext.java:286) > at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:159 > 8) > at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.j > ava:934) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. > java:1062) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. > java:984) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) > at org.jboss.system.ServiceController.doChange(ServiceController.java:688) > at org.jboss.system.ServiceController.start(ServiceController.java:460) > at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:146) > at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:104) > at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:45) > at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy( > AbstractSimpleRealDeployer.java:62) > at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDe > ployer.java:50) > at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:1 > 71) > at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:143 > 9) > at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersI > mpl.java:1157) > at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersI > mpl.java:1178) > at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersI > mpl.java:1210) > at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098 > ) > at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerCo > ntext.java:348) > at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:159 > 8) > at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.j > ava:934) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. > java:1062) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. > java:984) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) > at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) > at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545 > ) > at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileS > erviceBootstrap.java:304) > at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileService > Bootstrap.java:205) > at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) > at org.jboss.Main.boot(Main.java:209) > at org.jboss.Main$1.run(Main.java:547) > at java.lang.Thread.run(Thread.java:619) > If you unzip the ear, then you still get the zipexceptions for each war in the ear, but the final exception does not happen and the deployment succeeds. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sat Jan 24 07:06:44 2009 From: jira-events at lists.jboss.org (Jozef Hartinger (JIRA)) Date: Sat, 24 Jan 2009 07:06:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Work started: (JBSEAM-3449) Upgrade to latest RestEasy beta In-Reply-To: <21376851.1222121060720.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <16474849.1232798804377.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBSEAM-3449 started by Jozef Hartinger. > Upgrade to latest RestEasy beta > ------------------------------- > > Key: JBSEAM-3449 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3449 > Project: Seam > Issue Type: Feature Request > Components: WS > Affects Versions: 2.1.0.BETA1 > Reporter: Scott Olcott > Assignee: Jozef Hartinger > Fix For: 2.1.2.GA > > Attachments: jboss-seam-resteasy-2.1.1.CR2.JBSEAM-3449-patched.jar, resteasyBeta-8.txt > > > The latest beta is beta-8 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sat Jan 24 07:12:44 2009 From: jira-events at lists.jboss.org (manuel kallenbach (JIRA)) Date: Sat, 24 Jan 2009 07:12:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-633) remoting extension in handling exceptions on client side In-Reply-To: <23273225.1167826167160.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <32159567.1232799164324.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449587#action_12449587 ] manuel kallenbach commented on JBSEAM-633: ------------------------------------------ Thanks for implementing this. However, there is one thing I think that's not working properly. If you start a batch of remote calls and specify only an exception handler for each but the last call (callback is null for the first calls), the callback of the last call in the batch won't be called. I hope you could understand that. My english is not the best ;-) > remoting extension in handling exceptions on client side > -------------------------------------------------------- > > Key: JBSEAM-633 > URL: https://jira.jboss.org/jira/browse/JBSEAM-633 > Project: Seam > Issue Type: Feature Request > Components: Exception Handling, Remoting > Affects Versions: 1.1.0.GA > Reporter: Nico Gau > Assignee: Shane Bryzak > Priority: Optional > Fix For: 2.1.1.CR1 > > > Hi all, > I don't really know what JIRA is by the way, so hopefully nobody is upset by this post. I first mailed Gavin but he told me I should put it in JIRA. > I currently work on a project which uses Seam Remoting directly and I didn't find a neat way in handling errors on the client side as Exceptions are not propagated to it. Therefore I changed Seam to transmit all exceptions which can be handled in the javascript part via another callback. E.g.: > Seam.Component.getInstance('userManager').currentUser(function(user) { > alert("user: " + user); > }, > function(ex) { > alert("exception occured: " + ex.getMessage()); > }); > As the exception handler is optional, the change would not brake any client code. If you are interested in the change, you can reach me at heinzbeinz AT googlemail.com -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Jan 25 03:09:44 2009 From: jira-events at lists.jboss.org (Carey Foushee (JIRA)) Date: Sun, 25 Jan 2009 03:09:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3555) SeamMailAgain In-Reply-To: <3978595.1223977760796.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <28532423.1232870984323.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449602#action_12449602 ] Carey Foushee commented on JBSEAM-3555: --------------------------------------- I found a work around in 2.1.1GA to send periodic email async: Took out the from components.xml then just used a standard java.util.Timer like this: @In(create=true) AsynchronousMailProcessor asynchronousMailProcessor; long pollingInterval = 30000L; @Observer("org.jboss.seam.postInitialization") public void observe() { new Timer().schedule(new PollTask(asynchronousMailProcessor), pollingInterval, 2*pollingInterval); } private class PollTask extends TimerTask { AsynchronousMailProcessor asynchronousMailProcessor; public PollTask(AsynchronousMailProcessor asynchronousMailProcessor){ this.asynchronousMailProcessor = asynchronousMailProcessor; } public void run(){ asynchronousMailProcessor.sendMail(0); } } @Name("asynchronousMailProcessor") public class AsynchronousMailProcessor { @Asynchronous public void sendMail(@Duration long interval) { renderer.render("/email/reminder.xhtml"); } > SeamMailAgain > ------------- > > Key: JBSEAM-3555 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3555 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.0.CR1 > Environment: JBoss AS 4.2.1.GA > JBoss Seam 2.1.0-SNAPSHOT (10.10. HudsonNo330) > Reporter: Markus Heidt > Assignee: Pete Muir > Fix For: 2.1.2.CR1 > > Attachments: RendererFacesContextFactory.java, server.log > > > Simple Mailing via Renderer doesn't work. > 'Seam-gen'erated a new project and added a new action 'sendMail' > Added the line to the action code: > Renderer.instance().render("/simple.xhtml"); > simple.xhtml is a modified version of the seam example (without #{person}) > Error after executing the action: > 2008-10-14 11:40:21,847 FATAL [javax.enterprise.resource.webcontainer.jsf.application] org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > javax.faces.el.EvaluationException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:91) > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:91) > ... > Caused by: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory > at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:256) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Jan 25 11:27:44 2009 From: jira-events at lists.jboss.org (Cody Lerum (JIRA)) Date: Sun, 25 Jan 2009 11:27:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3555) SeamMailAgain In-Reply-To: <3978595.1223977760796.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <27449129.1232900864839.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449612#action_12449612 ] Cody Lerum commented on JBSEAM-3555: ------------------------------------ Are there multiple issues here? I'm running into "16:08:44,847 ERROR [STDERR] Caused by: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory" whether I define it as Async or not. and others are hitting some kind of Async issue. Should these be split? > SeamMailAgain > ------------- > > Key: JBSEAM-3555 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3555 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.0.CR1 > Environment: JBoss AS 4.2.1.GA > JBoss Seam 2.1.0-SNAPSHOT (10.10. HudsonNo330) > Reporter: Markus Heidt > Assignee: Pete Muir > Fix For: 2.1.2.CR1 > > Attachments: RendererFacesContextFactory.java, server.log > > > Simple Mailing via Renderer doesn't work. > 'Seam-gen'erated a new project and added a new action 'sendMail' > Added the line to the action code: > Renderer.instance().render("/simple.xhtml"); > simple.xhtml is a modified version of the seam example (without #{person}) > Error after executing the action: > 2008-10-14 11:40:21,847 FATAL [javax.enterprise.resource.webcontainer.jsf.application] org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > javax.faces.el.EvaluationException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:91) > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:91) > ... > Caused by: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory > at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:256) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Jan 25 14:54:44 2009 From: jira-events at lists.jboss.org (Tony Herstell (JIRA)) Date: Sun, 25 Jan 2009 14:54:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3555) SeamMailAgain In-Reply-To: <3978595.1223977760796.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <10321079.1232913284374.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449625#action_12449625 ] Tony Herstell commented on JBSEAM-3555: --------------------------------------- http://www.seamframework.org/Community/SeamEmailIn211GAEvenWorse I have been posting about seammail for about a year. Lets hope it gets priorotised soon as its a VERY useful feature of Seam and its a real shame its letting the side down. > SeamMailAgain > ------------- > > Key: JBSEAM-3555 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3555 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.0.CR1 > Environment: JBoss AS 4.2.1.GA > JBoss Seam 2.1.0-SNAPSHOT (10.10. HudsonNo330) > Reporter: Markus Heidt > Assignee: Pete Muir > Fix For: 2.1.2.CR1 > > Attachments: RendererFacesContextFactory.java, server.log > > > Simple Mailing via Renderer doesn't work. > 'Seam-gen'erated a new project and added a new action 'sendMail' > Added the line to the action code: > Renderer.instance().render("/simple.xhtml"); > simple.xhtml is a modified version of the seam example (without #{person}) > Error after executing the action: > 2008-10-14 11:40:21,847 FATAL [javax.enterprise.resource.webcontainer.jsf.application] org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > javax.faces.el.EvaluationException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:91) > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:91) > ... > Caused by: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory > at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:256) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Jan 25 14:58:54 2009 From: jira-events at lists.jboss.org (Tony Herstell (JIRA)) Date: Sun, 25 Jan 2009 14:58:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3555) SeamMailAgain In-Reply-To: <3978595.1223977760796.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <9963203.1232913534441.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449627#action_12449627 ] Tony Herstell commented on JBSEAM-3555: --------------------------------------- There are multiple problems: 1. Seam Mail doesnt work in Asynch mode as per the manual. 2. Seam Mail crashes when its a long list of messages and the crash is "hidden" in render so you cant actually do much about it. 3. Seam Mail when rendering seems to re-use objects from a previous "loop" iteration (in the case above it was Entity Image) > SeamMailAgain > ------------- > > Key: JBSEAM-3555 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3555 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.0.CR1 > Environment: JBoss AS 4.2.1.GA > JBoss Seam 2.1.0-SNAPSHOT (10.10. HudsonNo330) > Reporter: Markus Heidt > Assignee: Pete Muir > Fix For: 2.1.2.CR1 > > Attachments: RendererFacesContextFactory.java, server.log > > > Simple Mailing via Renderer doesn't work. > 'Seam-gen'erated a new project and added a new action 'sendMail' > Added the line to the action code: > Renderer.instance().render("/simple.xhtml"); > simple.xhtml is a modified version of the seam example (without #{person}) > Error after executing the action: > 2008-10-14 11:40:21,847 FATAL [javax.enterprise.resource.webcontainer.jsf.application] org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > javax.faces.el.EvaluationException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:91) > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:91) > ... > Caused by: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory > at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:256) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Sun Jan 25 17:06:44 2009 From: jira-events at lists.jboss.org (Cody Lerum (JIRA)) Date: Sun, 25 Jan 2009 17:06:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3555) SeamMailAgain In-Reply-To: <3978595.1223977760796.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <2100254.1232921204428.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449630#action_12449630 ] Cody Lerum commented on JBSEAM-3555: ------------------------------------ Which of those three is causing this? Caused by: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory > SeamMailAgain > ------------- > > Key: JBSEAM-3555 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3555 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.0.CR1 > Environment: JBoss AS 4.2.1.GA > JBoss Seam 2.1.0-SNAPSHOT (10.10. HudsonNo330) > Reporter: Markus Heidt > Assignee: Pete Muir > Fix For: 2.1.2.CR1 > > Attachments: RendererFacesContextFactory.java, server.log > > > Simple Mailing via Renderer doesn't work. > 'Seam-gen'erated a new project and added a new action 'sendMail' > Added the line to the action code: > Renderer.instance().render("/simple.xhtml"); > simple.xhtml is a modified version of the seam example (without #{person}) > Error after executing the action: > 2008-10-14 11:40:21,847 FATAL [javax.enterprise.resource.webcontainer.jsf.application] org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > javax.faces.el.EvaluationException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:91) > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:91) > ... > Caused by: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory > at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:256) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 26 03:08:44 2009 From: jira-events at lists.jboss.org (Jarek Gilewski (JIRA)) Date: Mon, 26 Jan 2009 03:08:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3912) s:link and s:button action problem with ui:include Message-ID: <21506086.1232957324249.JavaMail.jira@cloud.prod.atl2.jboss.com> s:link and s:button action problem with ui:include -------------------------------------------------- Key: JBSEAM-3912 URL: https://jira.jboss.org/jira/browse/JBSEAM-3912 Project: Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.1.1.GA Reporter: Jarek Gilewski Priority: Blocker Hi, I have something like this in my xhtml page: In remove.xhtml I have: ... ... The link from s:link looks like: http://localhost:8080/myapp/ComponentView.seam?componentId=1018&actionMethod=ComponentView.xhtml%3AentityHome.remove&cid=16 and from h:commandLink http://localhost:8080/myapp/ComponentView.seam?componentId=1018&actionOutcome=componentHome.remove&cid=14# In the s:link there is entityHome.remove instead of componentHome.remove and the link does not work. If i change the link manually it is ok. h:commandLink works ok. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 26 05:29:44 2009 From: jira-events at lists.jboss.org (Juan Miguel Bernal Gonzalez (JIRA)) Date: Mon, 26 Jan 2009 05:29:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3555) SeamMailAgain In-Reply-To: <3978595.1223977760796.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <21137175.1232965784360.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449657#action_12449657 ] Juan Miguel Bernal Gonzalez commented on JBSEAM-3555: ----------------------------------------------------- I?ve an example with en EJB that it works in Seam 2.0.3.CR1 but it doesn?t work in Seam 2.1.1.GA. If I convert the EJB to POJO, this example work well in Seam 2.1.1.GA. > SeamMailAgain > ------------- > > Key: JBSEAM-3555 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3555 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.0.CR1 > Environment: JBoss AS 4.2.1.GA > JBoss Seam 2.1.0-SNAPSHOT (10.10. HudsonNo330) > Reporter: Markus Heidt > Assignee: Pete Muir > Fix For: 2.1.2.CR1 > > Attachments: RendererFacesContextFactory.java, server.log > > > Simple Mailing via Renderer doesn't work. > 'Seam-gen'erated a new project and added a new action 'sendMail' > Added the line to the action code: > Renderer.instance().render("/simple.xhtml"); > simple.xhtml is a modified version of the seam example (without #{person}) > Error after executing the action: > 2008-10-14 11:40:21,847 FATAL [javax.enterprise.resource.webcontainer.jsf.application] org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > javax.faces.el.EvaluationException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:91) > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:91) > ... > Caused by: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory > at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:256) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 26 07:23:45 2009 From: jira-events at lists.jboss.org (Pete Muir (JIRA)) Date: Mon, 26 Jan 2009 07:23:45 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3911) zipped ear files cause seam NullPointerException on deployment In-Reply-To: <6944574.1232744574629.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <7449360.1232972625577.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449673#action_12449673 ] Pete Muir commented on JBSEAM-3911: ----------------------------------- Never seen this, you'll have to provide a method to reproduce. > zipped ear files cause seam NullPointerException on deployment > -------------------------------------------------------------- > > Key: JBSEAM-3911 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3911 > Project: Seam > Issue Type: Bug > Affects Versions: 2.0.2.SP1 > Environment: Jboss 5.0.0-GA, jdk 1.6.0_07 > Reporter: Adam Montague > > A webapp using seam that is deployed as a zipped ear fails to deploy. First you get an exception like this for each war that uses seam: > 15:55:08,634 WARN [URLScanner] could not read entries > java.util.zip.ZipException: error in opening zip file > at java.util.zip.ZipFile.open(Native Method) > at java.util.zip.ZipFile.(ZipFile.java:114) > at java.util.zip.ZipFile.(ZipFile.java:131) > at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:111) > at org.jboss.seam.deployment.URLScanner.handle(URLScanner.java:98) > at org.jboss.seam.deployment.URLScanner.scanResources(URLScanner.java:81) > at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrateg > y.java:67) > at org.jboss.seam.init.Initialization.create(Initialization.java:102) > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34) > at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3910) > at org.apache.catalina.core.StandardContext.start(StandardContext.java:4393) > at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(Tomca > tDeployment.java:367) > at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeploym > ent.java:146) > at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:460) > at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) > at org.jboss.web.deployers.WebModule.start(WebModule.java:96) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:2 > 5) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) > at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) > at $Proxy36.start(Unknown Source) > at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLif > ecycleAction.java:42) > at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLif > ecycleAction.java:37) > at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallActi > on(SimpleControllerContextAction.java:62) > at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessCon > trollerContextAction.java:71) > at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractContr > ollerContextActions.java:51) > at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerCo > ntext.java:348) > at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerC > ontext.java:286) > at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:159 > 8) > at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.j > ava:934) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. > java:1062) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. > java:984) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) > at org.jboss.system.ServiceController.doChange(ServiceController.java:688) > at org.jboss.system.ServiceController.start(ServiceController.java:460) > at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:146) > at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:104) > at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:45) > at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy( > AbstractSimpleRealDeployer.java:62) > at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDe > ployer.java:50) > at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:1 > 71) > at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:143 > 9) > at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersI > mpl.java:1157) > at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersI > mpl.java:1178) > at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersI > mpl.java:1210) > at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098 > ) > at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerCo > ntext.java:348) > at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:159 > 8) > at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.j > ava:934) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. > java:1062) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. > java:984) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) > at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) > at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545 > ) > at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileS > erviceBootstrap.java:304) > at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileService > Bootstrap.java:205) > at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) > at org.jboss.Main.boot(Main.java:209) > at org.jboss.Main$1.run(Main.java:547) > at java.lang.Thread.run(Thread.java:619) > Then you get the following exception for the first war, causing deployment to fail: > 15:16:26,981 ERROR [[/merlin/affiliate]] Exception sending context initialized event to listen > er instance of class org.jboss.seam.servlet.SeamListener > java.lang.NullPointerException > at org.jboss.seam.init.Initialization.installComponents(Initialization.java:958) > at org.jboss.seam.init.Initialization.init(Initialization.java:589) > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34) > at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3910) > at org.apache.catalina.core.StandardContext.start(StandardContext.java:4393) > at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(Tomca > tDeployment.java:367) > at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeploym > ent.java:146) > at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:460) > at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) > at org.jboss.web.deployers.WebModule.start(WebModule.java:96) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:2 > 5) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) > at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) > at $Proxy36.start(Unknown Source) > at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLif > ecycleAction.java:42) > at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLif > ecycleAction.java:37) > at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallActi > on(SimpleControllerContextAction.java:62) > at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessCon > trollerContextAction.java:71) > at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractContr > ollerContextActions.java:51) > at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerCo > ntext.java:348) > at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerC > ontext.java:286) > at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:159 > 8) > at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.j > ava:934) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. > java:1062) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. > java:984) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) > at org.jboss.system.ServiceController.doChange(ServiceController.java:688) > at org.jboss.system.ServiceController.start(ServiceController.java:460) > at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:146) > at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:104) > at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:45) > at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy( > AbstractSimpleRealDeployer.java:62) > at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDe > ployer.java:50) > at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:1 > 71) > at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:143 > 9) > at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersI > mpl.java:1157) > at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersI > mpl.java:1178) > at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersI > mpl.java:1210) > at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098 > ) > at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerCo > ntext.java:348) > at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:159 > 8) > at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.j > ava:934) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. > java:1062) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. > java:984) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) > at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) > at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545 > ) > at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileS > erviceBootstrap.java:304) > at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileService > Bootstrap.java:205) > at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) > at org.jboss.Main.boot(Main.java:209) > at org.jboss.Main$1.run(Main.java:547) > at java.lang.Thread.run(Thread.java:619) > If you unzip the ear, then you still get the zipexceptions for each war in the ear, but the final exception does not happen and the deployment succeeds. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 26 07:34:44 2009 From: jira-events at lists.jboss.org (Pete Muir (JIRA)) Date: Mon, 26 Jan 2009 07:34:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3912) s:link and s:button action problem with ui:include In-Reply-To: <21506086.1232957324249.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <20244500.1232973284597.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir closed JBSEAM-3912. ----------------------------- Resolution: Duplicate Issue Please don't set the priority. > s:link and s:button action problem with ui:include > -------------------------------------------------- > > Key: JBSEAM-3912 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3912 > Project: Seam > Issue Type: Bug > Components: JSF Integration > Affects Versions: 2.1.1.GA > Reporter: Jarek Gilewski > Priority: Blocker > > Hi, > I have something like this in my xhtml page: > > > > In remove.xhtml I have: > ... > > > > ... > The link from s:link looks like: > http://localhost:8080/myapp/ComponentView.seam?componentId=1018&actionMethod=ComponentView.xhtml%3AentityHome.remove&cid=16 > and from h:commandLink > http://localhost:8080/myapp/ComponentView.seam?componentId=1018&actionOutcome=componentHome.remove&cid=14# > In the s:link there is entityHome.remove instead of componentHome.remove and the link does not work. If i change the link manually it is ok. > h:commandLink works ok. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 26 11:16:44 2009 From: jira-events at lists.jboss.org (Julien Kronegg (JIRA)) Date: Mon, 26 Jan 2009 11:16:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3913) Lower web site performance once logged in at seamframework.org Message-ID: <16656670.1232986604972.JavaMail.jira@cloud.prod.atl2.jboss.com> Lower web site performance once logged in at seamframework.org -------------------------------------------------------------- Key: JBSEAM-3913 URL: https://jira.jboss.org/jira/browse/JBSEAM-3913 Project: Seam Issue Type: Bug Components: WS Environment: MSIE 6.0 and Firefox 3.0.5 Reporter: Julien Kronegg Priority: Minor The Seam web site performance is much lower once logged in (i.e. the pages take much longer to load). For example, on 2009.01.26, the page http://seamframework.org/Community/Forums loads in: - when not logged in: 2 seconds - when logged in: 9 seconds The timings are reproductible when reloading the pages. Since the forum is implemented using Seam technology, this is not a good advertizing. ;-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 26 11:37:44 2009 From: jira-events at lists.jboss.org (Pete Muir (JIRA)) Date: Mon, 26 Jan 2009 11:37:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3913) Lower web site performance once logged in at seamframework.org In-Reply-To: <16656670.1232986604972.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <28527321.1232987864213.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated JBSEAM-3913: ------------------------------ Component/s: Wiki (was: WS) > Lower web site performance once logged in at seamframework.org > -------------------------------------------------------------- > > Key: JBSEAM-3913 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3913 > Project: Seam > Issue Type: Bug > Components: Wiki > Environment: MSIE 6.0 and Firefox 3.0.5 > Reporter: Julien Kronegg > Priority: Minor > > The Seam web site performance is much lower once logged in (i.e. the pages take much longer to load). > For example, on 2009.01.26, the page http://seamframework.org/Community/Forums loads in: > - when not logged in: 2 seconds > - when logged in: 9 seconds > The timings are reproductible when reloading the pages. > Since the forum is implemented using Seam technology, this is not a good advertizing. ;-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Mon Jan 26 18:05:44 2009 From: jira-events at lists.jboss.org (Clint Popetz (JIRA)) Date: Mon, 26 Jan 2009 18:05:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3914) Hot deploying doesn't pick up changes in non-@Named classes Message-ID: <31799197.1233011144160.JavaMail.jira@cloud.prod.atl2.jboss.com> Hot deploying doesn't pick up changes in non- at Named classes ----------------------------------------------------------- Key: JBSEAM-3914 URL: https://jira.jboss.org/jira/browse/JBSEAM-3914 Project: Seam Issue Type: Bug Components: Wicket Affects Versions: 2.1.1.GA Reporter: Clint Popetz Assignee: Clint Popetz The default deployment scanner don't pay attention to changes in hot-deployed wicket classes, because they aren't @Named. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 27 03:06:44 2009 From: jira-events at lists.jboss.org (Viggo Navarsete (JIRA)) Date: Tue, 27 Jan 2009 03:06:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3915) RESTEasy GET request: java.lang.RuntimeException: Bad arguments passed to public java.lang.String method Message-ID: <21596809.1233043604153.JavaMail.jira@cloud.prod.atl2.jboss.com> RESTEasy GET request: java.lang.RuntimeException: Bad arguments passed to public java.lang.String method --------------------------------------------------------------------------------------------------------- Key: JBSEAM-3915 URL: https://jira.jboss.org/jira/browse/JBSEAM-3915 Project: Seam Issue Type: Bug Environment: JDK 1.6 Jboss 5.0.0.GA for JDK 1.6 Seam 2.1.1.GA Reporter: Viggo Navarsete Deploying the attached project and going to the following url: http://localhost:8080/app-cci-seam/seam/resource/rest/gqiResource/getShelfLife/arg1/arg2 results in the following stacktrace: 09:00:03,046 ERROR [STDERR] java.lang.RuntimeException: Bad arguments passed to public java.lang.String com.tracetracker.cci.session.GqiResourceBean.getShelfLife(java.lang.String,java.lang.String) ( arg1, arg2 09:00:03,047 ERROR [STDERR] at org.resteasy.MethodInjectorImpl.invoke(MethodInjectorImpl.java:133) 09:00:03,047 ERROR [STDERR] at org.resteasy.ResourceMethod.invoke(ResourceMethod.java:162) 09:00:03,047 ERROR [STDERR] at org.resteasy.ResourceMethod.invoke(ResourceMethod.java:134) 09:00:03,047 ERROR [STDERR] at org.resteasy.Dispatcher.invoke(Dispatcher.java:161) 09:00:03,047 ERROR [STDERR] at org.jboss.seam.resteasy.ResteasyResourceAdapter$1.process(ResteasyResourceAdapter.java:127) 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:53) 09:00:03,047 ERROR [STDERR] at org.jboss.seam.resteasy.ResteasyResourceAdapter.getResource(ResteasyResourceAdapter.java:71) 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80) 09:00:03,047 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) 09:00:03,047 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) 09:00:03,047 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) 09:00:03,047 ERROR [STDERR] at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) 09:00:03,047 ERROR [STDERR] at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) 09:00:03,047 ERROR [STDERR] at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) 09:00:03,047 ERROR [STDERR] at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) 09:00:03,047 ERROR [STDERR] at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) 09:00:03,048 ERROR [STDERR] at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) 09:00:03,048 ERROR [STDERR] at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) 09:00:03,048 ERROR [STDERR] at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) 09:00:03,048 ERROR [STDERR] at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) 09:00:03,048 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) 09:00:03,048 ERROR [STDERR] at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) 09:00:03,048 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) 09:00:03,048 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) 09:00:03,048 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 09:00:03,048 ERROR [STDERR] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) 09:00:03,048 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) 09:00:03,048 ERROR [STDERR] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) 09:00:03,048 ERROR [STDERR] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) 09:00:03,048 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) 09:00:03,048 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) 09:00:03,048 ERROR [STDERR] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) 09:00:03,049 ERROR [STDERR] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) 09:00:03,049 ERROR [STDERR] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) 09:00:03,049 ERROR [STDERR] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) 09:00:03,049 ERROR [STDERR] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) 09:00:03,049 ERROR [STDERR] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) 09:00:03,049 ERROR [STDERR] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) 09:00:03,049 ERROR [STDERR] at java.lang.Thread.run(Thread.java:619) 09:00:03,049 ERROR [STDERR] Caused by: java.lang.IllegalArgumentException: object is not an instance of declaring class 09:00:03,049 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 09:00:03,049 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 09:00:03,049 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 09:00:03,049 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:597) 09:00:03,049 ERROR [STDERR] at org.resteasy.MethodInjectorImpl.invoke(MethodInjectorImpl.java:72) 09:00:03,049 ERROR [STDERR] ... 50 more The interface for the RESTEasy webservice is com.tracetracker.cci.GqiResource The implementation is com.tracetracker.cci.GqiResourceBean I have tried to change the parameter types resulting in the same error. It looks the argumentss are not handlet corectly for GET requests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 27 03:23:44 2009 From: jira-events at lists.jboss.org (Viggo Navarsete (JIRA)) Date: Tue, 27 Jan 2009 03:23:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3915) RESTEasy GET request: java.lang.RuntimeException: Bad arguments passed to public java.lang.String method In-Reply-To: <21596809.1233043604153.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <21517118.1233044624161.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449820#action_12449820 ] Viggo Navarsete commented on JBSEAM-3915: ----------------------------------------- There seams to be a problem attaching our code to the issue (to big). I will paste the interface and implementation in. All implementation has been done following the seam reference guide Interface: package com.tracetracker.cci.session; import javax.ejb.Local; import javax.ws.rs.GET; import javax.ws.rs.Path; import javax.ws.rs.PathParam; import javax.ws.rs.ProduceMime; @Local public interface GqiResource { // seam-gen method public void gqiResource(); @GET @Path("/getShelfLife/{1}/{2}") @ProduceMime("text/plain") public String getShelfLife( @PathParam("1") String station, @PathParam("2") String date ); } implementation: package com.tracetracker.cci.session; import javax.ejb.Stateless; import javax.ws.rs.GET; import javax.ws.rs.Path; import javax.ws.rs.PathParam; import javax.ws.rs.ProduceMime; import org.jboss.seam.annotations.In; import org.jboss.seam.annotations.Logger; import org.jboss.seam.annotations.Name; import org.jboss.seam.international.StatusMessages; import org.jboss.seam.log.Log; @Stateless @Name("gqiResource") @Path("/gqiResource") public class GqiResourceBean implements GqiResource { @Logger private Log log; @In StatusMessages statusMessages; public void gqiResource() { // implement your business logic here log.info("gqiResource.gqiResource() action called"); statusMessages.add("gqiResource"); } @GET @Path("/getShelfLife/{1}/{2}") @ProduceMime("text/plain") public String getShelfLife( @PathParam("1") String station, @PathParam("2") String date ) { return "This is a test, 1: " + station + " 2 " + date; } } > RESTEasy GET request: java.lang.RuntimeException: Bad arguments passed to public java.lang.String method > --------------------------------------------------------------------------------------------------------- > > Key: JBSEAM-3915 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3915 > Project: Seam > Issue Type: Bug > Environment: JDK 1.6 > Jboss 5.0.0.GA for JDK 1.6 > Seam 2.1.1.GA > Reporter: Viggo Navarsete > > Deploying the attached project and going to the following url: http://localhost:8080/app-cci-seam/seam/resource/rest/gqiResource/getShelfLife/arg1/arg2 > results in the following stacktrace: > 09:00:03,046 ERROR [STDERR] java.lang.RuntimeException: Bad arguments passed to public java.lang.String com.tracetracker.cci.session.GqiResourceBean.getShelfLife(java.lang.String,java.lang.String) ( arg1, arg2 > 09:00:03,047 ERROR [STDERR] at org.resteasy.MethodInjectorImpl.invoke(MethodInjectorImpl.java:133) > 09:00:03,047 ERROR [STDERR] at org.resteasy.ResourceMethod.invoke(ResourceMethod.java:162) > 09:00:03,047 ERROR [STDERR] at org.resteasy.ResourceMethod.invoke(ResourceMethod.java:134) > 09:00:03,047 ERROR [STDERR] at org.resteasy.Dispatcher.invoke(Dispatcher.java:161) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.resteasy.ResteasyResourceAdapter$1.process(ResteasyResourceAdapter.java:127) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:53) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.resteasy.ResteasyResourceAdapter.getResource(ResteasyResourceAdapter.java:71) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80) > 09:00:03,047 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > 09:00:03,047 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > 09:00:03,047 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > 09:00:03,047 ERROR [STDERR] at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) > 09:00:03,048 ERROR [STDERR] at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) > 09:00:03,048 ERROR [STDERR] at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) > 09:00:03,048 ERROR [STDERR] at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) > 09:00:03,048 ERROR [STDERR] at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) > 09:00:03,048 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > 09:00:03,048 ERROR [STDERR] at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) > 09:00:03,048 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > 09:00:03,048 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) > 09:00:03,048 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > 09:00:03,048 ERROR [STDERR] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > 09:00:03,048 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) > 09:00:03,048 ERROR [STDERR] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) > 09:00:03,048 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) > 09:00:03,048 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > 09:00:03,049 ERROR [STDERR] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) > 09:00:03,049 ERROR [STDERR] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > 09:00:03,049 ERROR [STDERR] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) > 09:00:03,049 ERROR [STDERR] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) > 09:00:03,049 ERROR [STDERR] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) > 09:00:03,049 ERROR [STDERR] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > 09:00:03,049 ERROR [STDERR] at java.lang.Thread.run(Thread.java:619) > 09:00:03,049 ERROR [STDERR] Caused by: java.lang.IllegalArgumentException: object is not an instance of declaring class > 09:00:03,049 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > 09:00:03,049 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > 09:00:03,049 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > 09:00:03,049 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:597) > 09:00:03,049 ERROR [STDERR] at org.resteasy.MethodInjectorImpl.invoke(MethodInjectorImpl.java:72) > 09:00:03,049 ERROR [STDERR] ... 50 more > The interface for the RESTEasy webservice is com.tracetracker.cci.GqiResource > The implementation is com.tracetracker.cci.GqiResourceBean > I have tried to change the parameter types resulting in the same error. It looks the argumentss are not handlet corectly for GET requests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 27 04:14:44 2009 From: jira-events at lists.jboss.org (Viggo Navarsete (JIRA)) Date: Tue, 27 Jan 2009 04:14:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3915) RESTEasy GET request: java.lang.RuntimeException: Bad arguments passed to public java.lang.String method In-Reply-To: <21596809.1233043604153.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <19633939.1233047684175.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viggo Navarsete updated JBSEAM-3915: ------------------------------------ Affects Version/s: 2.1.1.GA > RESTEasy GET request: java.lang.RuntimeException: Bad arguments passed to public java.lang.String method > --------------------------------------------------------------------------------------------------------- > > Key: JBSEAM-3915 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3915 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.1.GA > Environment: JDK 1.6 > Jboss 5.0.0.GA for JDK 1.6 > Seam 2.1.1.GA > Reporter: Viggo Navarsete > > Deploying the attached project and going to the following url: http://localhost:8080/app-cci-seam/seam/resource/rest/gqiResource/getShelfLife/arg1/arg2 > results in the following stacktrace: > 09:00:03,046 ERROR [STDERR] java.lang.RuntimeException: Bad arguments passed to public java.lang.String com.tracetracker.cci.session.GqiResourceBean.getShelfLife(java.lang.String,java.lang.String) ( arg1, arg2 > 09:00:03,047 ERROR [STDERR] at org.resteasy.MethodInjectorImpl.invoke(MethodInjectorImpl.java:133) > 09:00:03,047 ERROR [STDERR] at org.resteasy.ResourceMethod.invoke(ResourceMethod.java:162) > 09:00:03,047 ERROR [STDERR] at org.resteasy.ResourceMethod.invoke(ResourceMethod.java:134) > 09:00:03,047 ERROR [STDERR] at org.resteasy.Dispatcher.invoke(Dispatcher.java:161) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.resteasy.ResteasyResourceAdapter$1.process(ResteasyResourceAdapter.java:127) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:53) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.resteasy.ResteasyResourceAdapter.getResource(ResteasyResourceAdapter.java:71) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80) > 09:00:03,047 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > 09:00:03,047 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > 09:00:03,047 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > 09:00:03,047 ERROR [STDERR] at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) > 09:00:03,048 ERROR [STDERR] at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) > 09:00:03,048 ERROR [STDERR] at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) > 09:00:03,048 ERROR [STDERR] at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) > 09:00:03,048 ERROR [STDERR] at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) > 09:00:03,048 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > 09:00:03,048 ERROR [STDERR] at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) > 09:00:03,048 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > 09:00:03,048 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) > 09:00:03,048 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > 09:00:03,048 ERROR [STDERR] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > 09:00:03,048 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) > 09:00:03,048 ERROR [STDERR] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) > 09:00:03,048 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) > 09:00:03,048 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > 09:00:03,049 ERROR [STDERR] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) > 09:00:03,049 ERROR [STDERR] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > 09:00:03,049 ERROR [STDERR] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) > 09:00:03,049 ERROR [STDERR] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) > 09:00:03,049 ERROR [STDERR] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) > 09:00:03,049 ERROR [STDERR] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > 09:00:03,049 ERROR [STDERR] at java.lang.Thread.run(Thread.java:619) > 09:00:03,049 ERROR [STDERR] Caused by: java.lang.IllegalArgumentException: object is not an instance of declaring class > 09:00:03,049 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > 09:00:03,049 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > 09:00:03,049 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > 09:00:03,049 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:597) > 09:00:03,049 ERROR [STDERR] at org.resteasy.MethodInjectorImpl.invoke(MethodInjectorImpl.java:72) > 09:00:03,049 ERROR [STDERR] ... 50 more > The interface for the RESTEasy webservice is com.tracetracker.cci.GqiResource > The implementation is com.tracetracker.cci.GqiResourceBean > I have tried to change the parameter types resulting in the same error. It looks the argumentss are not handlet corectly for GET requests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 27 06:30:44 2009 From: jira-events at lists.jboss.org (Damian Harvey (JIRA)) Date: Tue, 27 Jan 2009 06:30:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2658) s:defaultAction only works 1 submit In-Reply-To: <16876596.1203504645567.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <14480501.1233055844208.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449832#action_12449832 ] Damian Harvey commented on JBSEAM-2658: --------------------------------------- I have this problem only on Firefox and only when you reRender (via ajax4jsf) the button/link that has the defaultAction. And then only when you reRender the form as well as the elements within it. Safari = OK Chrome = OK IE7 = OK Firefox 3.0.5 (Mac) = ERROR Firefox 3.0.1 (Win Vista) = ERROR Here's a small example (the page scoped backing Bean - testBean - just outputs to system out) : Note that if you move the testDiv inside the form then it works fine. > s:defaultAction only works 1 submit > ----------------------------------- > > Key: JBSEAM-2658 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2658 > Project: Seam > Issue Type: Bug > Components: JSF Controls > Affects Versions: 2.0.1.GA > Environment: JBoss 4.2.2, RichFaces 3.1.4, Firefox 2.0.0.12, Windows XP > Reporter: Susanne Jarl > Assignee: Pete Muir > Fix For: 2.0.2.CR1, 2.1.0.BETA1 > > > I use the s:defaultAction and it works the first time i hit enter, but if the inputtextfield is not validated and/or I get an error message, and then hit enter in the inputtextfield again it does not work. But if I click the submitbutton instead the second time it works. So there is a difference between clicking the button and hit enter the second time. > This is my code: > > > > > > > > > > > > > > > > I have this form in a RichFaces modal panel. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 27 06:39:44 2009 From: jira-events at lists.jboss.org (Damian Harvey (JIRA)) Date: Tue, 27 Jan 2009 06:39:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2658) s:defaultAction only works 1 submit In-Reply-To: <16876596.1203504645567.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <20934576.1233056384266.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449834#action_12449834 ] Damian Harvey commented on JBSEAM-2658: --------------------------------------- the above example will result it every second action working. > s:defaultAction only works 1 submit > ----------------------------------- > > Key: JBSEAM-2658 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2658 > Project: Seam > Issue Type: Bug > Components: JSF Controls > Affects Versions: 2.0.1.GA > Environment: JBoss 4.2.2, RichFaces 3.1.4, Firefox 2.0.0.12, Windows XP > Reporter: Susanne Jarl > Assignee: Pete Muir > Fix For: 2.0.2.CR1, 2.1.0.BETA1 > > > I use the s:defaultAction and it works the first time i hit enter, but if the inputtextfield is not validated and/or I get an error message, and then hit enter in the inputtextfield again it does not work. But if I click the submitbutton instead the second time it works. So there is a difference between clicking the button and hit enter the second time. > This is my code: > > > > > > > > > > > > > > > > I have this form in a RichFaces modal panel. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 27 06:39:44 2009 From: jira-events at lists.jboss.org (Damian Harvey (JIRA)) Date: Tue, 27 Jan 2009 06:39:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2658) s:defaultAction only works 1 submit In-Reply-To: <16876596.1203504645567.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <29933393.1233056384433.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449835#action_12449835 ] Damian Harvey commented on JBSEAM-2658: --------------------------------------- and the workaround is to move the div #testDiv inside the form - ie. don't reRender forms. > s:defaultAction only works 1 submit > ----------------------------------- > > Key: JBSEAM-2658 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2658 > Project: Seam > Issue Type: Bug > Components: JSF Controls > Affects Versions: 2.0.1.GA > Environment: JBoss 4.2.2, RichFaces 3.1.4, Firefox 2.0.0.12, Windows XP > Reporter: Susanne Jarl > Assignee: Pete Muir > Fix For: 2.0.2.CR1, 2.1.0.BETA1 > > > I use the s:defaultAction and it works the first time i hit enter, but if the inputtextfield is not validated and/or I get an error message, and then hit enter in the inputtextfield again it does not work. But if I click the submitbutton instead the second time it works. So there is a difference between clicking the button and hit enter the second time. > This is my code: > > > > > > > > > > > > > > > > I have this form in a RichFaces modal panel. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 27 13:41:44 2009 From: jira-events at lists.jboss.org (Jozef Hartinger (JIRA)) Date: Tue, 27 Jan 2009 13:41:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-3915) RESTEasy GET request: java.lang.RuntimeException: Bad arguments passed to public java.lang.String method In-Reply-To: <21596809.1233043604153.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <9668556.1233081704377.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jozef Hartinger reassigned JBSEAM-3915: --------------------------------------- Assignee: Jozef Hartinger > RESTEasy GET request: java.lang.RuntimeException: Bad arguments passed to public java.lang.String method > --------------------------------------------------------------------------------------------------------- > > Key: JBSEAM-3915 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3915 > Project: Seam > Issue Type: Bug > Components: WS > Affects Versions: 2.1.1.GA > Environment: JDK 1.6 > Jboss 5.0.0.GA for JDK 1.6 > Seam 2.1.1.GA > Reporter: Viggo Navarsete > Assignee: Jozef Hartinger > > Deploying the attached project and going to the following url: http://localhost:8080/app-cci-seam/seam/resource/rest/gqiResource/getShelfLife/arg1/arg2 > results in the following stacktrace: > 09:00:03,046 ERROR [STDERR] java.lang.RuntimeException: Bad arguments passed to public java.lang.String com.tracetracker.cci.session.GqiResourceBean.getShelfLife(java.lang.String,java.lang.String) ( arg1, arg2 > 09:00:03,047 ERROR [STDERR] at org.resteasy.MethodInjectorImpl.invoke(MethodInjectorImpl.java:133) > 09:00:03,047 ERROR [STDERR] at org.resteasy.ResourceMethod.invoke(ResourceMethod.java:162) > 09:00:03,047 ERROR [STDERR] at org.resteasy.ResourceMethod.invoke(ResourceMethod.java:134) > 09:00:03,047 ERROR [STDERR] at org.resteasy.Dispatcher.invoke(Dispatcher.java:161) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.resteasy.ResteasyResourceAdapter$1.process(ResteasyResourceAdapter.java:127) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:53) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.resteasy.ResteasyResourceAdapter.getResource(ResteasyResourceAdapter.java:71) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80) > 09:00:03,047 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > 09:00:03,047 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > 09:00:03,047 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > 09:00:03,047 ERROR [STDERR] at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) > 09:00:03,048 ERROR [STDERR] at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) > 09:00:03,048 ERROR [STDERR] at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) > 09:00:03,048 ERROR [STDERR] at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) > 09:00:03,048 ERROR [STDERR] at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) > 09:00:03,048 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > 09:00:03,048 ERROR [STDERR] at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) > 09:00:03,048 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > 09:00:03,048 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) > 09:00:03,048 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > 09:00:03,048 ERROR [STDERR] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > 09:00:03,048 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) > 09:00:03,048 ERROR [STDERR] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) > 09:00:03,048 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) > 09:00:03,048 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > 09:00:03,049 ERROR [STDERR] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) > 09:00:03,049 ERROR [STDERR] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > 09:00:03,049 ERROR [STDERR] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) > 09:00:03,049 ERROR [STDERR] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) > 09:00:03,049 ERROR [STDERR] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) > 09:00:03,049 ERROR [STDERR] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > 09:00:03,049 ERROR [STDERR] at java.lang.Thread.run(Thread.java:619) > 09:00:03,049 ERROR [STDERR] Caused by: java.lang.IllegalArgumentException: object is not an instance of declaring class > 09:00:03,049 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > 09:00:03,049 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > 09:00:03,049 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > 09:00:03,049 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:597) > 09:00:03,049 ERROR [STDERR] at org.resteasy.MethodInjectorImpl.invoke(MethodInjectorImpl.java:72) > 09:00:03,049 ERROR [STDERR] ... 50 more > The interface for the RESTEasy webservice is com.tracetracker.cci.GqiResource > The implementation is com.tracetracker.cci.GqiResourceBean > I have tried to change the parameter types resulting in the same error. It looks the argumentss are not handlet corectly for GET requests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 27 13:41:44 2009 From: jira-events at lists.jboss.org (Jozef Hartinger (JIRA)) Date: Tue, 27 Jan 2009 13:41:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3915) RESTEasy GET request: java.lang.RuntimeException: Bad arguments passed to public java.lang.String method In-Reply-To: <21596809.1233043604153.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <31117031.1233081704592.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jozef Hartinger updated JBSEAM-3915: ------------------------------------ Component/s: WS Affects: [Release Notes] > RESTEasy GET request: java.lang.RuntimeException: Bad arguments passed to public java.lang.String method > --------------------------------------------------------------------------------------------------------- > > Key: JBSEAM-3915 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3915 > Project: Seam > Issue Type: Bug > Components: WS > Affects Versions: 2.1.1.GA > Environment: JDK 1.6 > Jboss 5.0.0.GA for JDK 1.6 > Seam 2.1.1.GA > Reporter: Viggo Navarsete > Assignee: Jozef Hartinger > > Deploying the attached project and going to the following url: http://localhost:8080/app-cci-seam/seam/resource/rest/gqiResource/getShelfLife/arg1/arg2 > results in the following stacktrace: > 09:00:03,046 ERROR [STDERR] java.lang.RuntimeException: Bad arguments passed to public java.lang.String com.tracetracker.cci.session.GqiResourceBean.getShelfLife(java.lang.String,java.lang.String) ( arg1, arg2 > 09:00:03,047 ERROR [STDERR] at org.resteasy.MethodInjectorImpl.invoke(MethodInjectorImpl.java:133) > 09:00:03,047 ERROR [STDERR] at org.resteasy.ResourceMethod.invoke(ResourceMethod.java:162) > 09:00:03,047 ERROR [STDERR] at org.resteasy.ResourceMethod.invoke(ResourceMethod.java:134) > 09:00:03,047 ERROR [STDERR] at org.resteasy.Dispatcher.invoke(Dispatcher.java:161) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.resteasy.ResteasyResourceAdapter$1.process(ResteasyResourceAdapter.java:127) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:53) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.resteasy.ResteasyResourceAdapter.getResource(ResteasyResourceAdapter.java:71) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80) > 09:00:03,047 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > 09:00:03,047 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > 09:00:03,047 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > 09:00:03,047 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > 09:00:03,047 ERROR [STDERR] at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) > 09:00:03,048 ERROR [STDERR] at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) > 09:00:03,048 ERROR [STDERR] at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) > 09:00:03,048 ERROR [STDERR] at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) > 09:00:03,048 ERROR [STDERR] at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) > 09:00:03,048 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > 09:00:03,048 ERROR [STDERR] at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) > 09:00:03,048 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > 09:00:03,048 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) > 09:00:03,048 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > 09:00:03,048 ERROR [STDERR] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > 09:00:03,048 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) > 09:00:03,048 ERROR [STDERR] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) > 09:00:03,048 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) > 09:00:03,048 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > 09:00:03,048 ERROR [STDERR] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > 09:00:03,049 ERROR [STDERR] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) > 09:00:03,049 ERROR [STDERR] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > 09:00:03,049 ERROR [STDERR] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) > 09:00:03,049 ERROR [STDERR] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) > 09:00:03,049 ERROR [STDERR] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) > 09:00:03,049 ERROR [STDERR] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > 09:00:03,049 ERROR [STDERR] at java.lang.Thread.run(Thread.java:619) > 09:00:03,049 ERROR [STDERR] Caused by: java.lang.IllegalArgumentException: object is not an instance of declaring class > 09:00:03,049 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > 09:00:03,049 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > 09:00:03,049 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > 09:00:03,049 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:597) > 09:00:03,049 ERROR [STDERR] at org.resteasy.MethodInjectorImpl.invoke(MethodInjectorImpl.java:72) > 09:00:03,049 ERROR [STDERR] ... 50 more > The interface for the RESTEasy webservice is com.tracetracker.cci.GqiResource > The implementation is com.tracetracker.cci.GqiResourceBean > I have tried to change the parameter types resulting in the same error. It looks the argumentss are not handlet corectly for GET requests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 27 17:40:44 2009 From: jira-events at lists.jboss.org (Ian Springer (JIRA)) Date: Tue, 27 Jan 2009 17:40:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3916) SeamELResolver.resolveInMap() will resolve a property "size" to ((Map)base).size() even if the Map contains a key named "base" - instead, it should return null and allow javax.el.MapELResolver to resolve the property to ((Map)base).get("size") Message-ID: <19503838.1233096044156.JavaMail.jira@cloud.prod.atl2.jboss.com> SeamELResolver.resolveInMap() will resolve a property "size" to ((Map)base).size() even if the Map contains a key named "base" - instead, it should return null and allow javax.el.MapELResolver to resolve the property to ((Map)base).get("size") --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3916 URL: https://jira.jboss.org/jira/browse/JBSEAM-3916 Project: Seam Issue Type: Bug Components: EL Affects Versions: 2.1.0.SP1 Reporter: Ian Springer Priority: Critical I have an expression: #{MyBean.someMap['size']} In my non-Seam JSF app, this expression was resolving to MyBean.getSomeMap().get("size"). However, when I integrated Seam into my app, the expression started instead resolving to MyBean.getSomeMap().size(), which broke my app. This is occurring because SeamELResolver is ahead of javax.el.MapELResolver in the CompositeELResolver resolver list, and its resolveInMap() function ensures a property named "size" resolves to ((Map)base).size() This makes it impossible for me to obtain the value of the element with key "size" from my Map via EL. To solve this, I suggest changing SeamELResolver.resolveInMap() to the following: private Object resolveInMap(ELContext context, Object base, Object property) { if ( !( (Map) base ).containsKey("size") && "size".equals(property) ) { context.setPropertyResolved(true); return ( (Map) base ).size(); } else if ( !( (Map) base ).containsKey("values") && "values".equals(property) ) { context.setPropertyResolved(true); return ( (Map) base ).values(); } else if ( !( (Map) base ).containsKey("keySet") && "keySet".equals(property) ) { context.setPropertyResolved(true); return ( (Map) base ).keySet(); } else if ( !( (Map) base ).containsKey("entrySet") && "entrySet".equals(property) ) { context.setPropertyResolved(true); return ( (Map) base ).entrySet(); } else { return null; } } The only disadvantage of this is that if you actually are trying to get at map.size(), there will be no way to do so if the Map happens to contain a key named "size". However, in such a case, #{MyBean.someMap.keySet.size} or #{MyBean.someMap.values.size} could instead be used to obtain the Map's size. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 27 17:46:44 2009 From: jira-events at lists.jboss.org (Ian Springer (JIRA)) Date: Tue, 27 Jan 2009 17:46:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3916) SeamELResolver.resolveInMap() will resolve a property "size" to ((Map)base).size() even if the Map contains a key named "size" - instead, it should return null and allow javax.el.MapELResolver to resolve the property to ((Map)base).get("size") In-Reply-To: <19503838.1233096044156.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <4565618.1233096404259.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Springer updated JBSEAM-3916: --------------------------------- Summary: SeamELResolver.resolveInMap() will resolve a property "size" to ((Map)base).size() even if the Map contains a key named "size" - instead, it should return null and allow javax.el.MapELResolver to resolve the property to ((Map)base).get("size") (was: SeamELResolver.resolveInMap() will resolve a property "size" to ((Map)base).size() even if the Map contains a key named "base" - instead, it should return null and allow javax.el.MapELResolver to resolve the property to ((Map)base).get("size")) > SeamELResolver.resolveInMap() will resolve a property "size" to ((Map)base).size() even if the Map contains a key named "size" - instead, it should return null and allow javax.el.MapELResolver to resolve the property to ((Map)base).get("size") > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBSEAM-3916 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3916 > Project: Seam > Issue Type: Bug > Components: EL > Affects Versions: 2.1.0.SP1 > Reporter: Ian Springer > Priority: Critical > > I have an expression: > #{MyBean.someMap['size']} > In my non-Seam JSF app, this expression was resolving to MyBean.getSomeMap().get("size"). However, when I integrated Seam into my app, the expression started instead resolving to MyBean.getSomeMap().size(), which broke my app. This is occurring because SeamELResolver is ahead of javax.el.MapELResolver in the CompositeELResolver resolver list, and its resolveInMap() function ensures a property named "size" resolves to ((Map)base).size() This makes it impossible for me to obtain the value of the element with key "size" from my Map via EL. > To solve this, I suggest changing SeamELResolver.resolveInMap() to the following: > private Object resolveInMap(ELContext context, Object base, Object property) > { > if ( !( (Map) base ).containsKey("size") && "size".equals(property) ) > { > context.setPropertyResolved(true); > return ( (Map) base ).size(); > } > else if ( !( (Map) base ).containsKey("values") && "values".equals(property) ) > { > context.setPropertyResolved(true); > return ( (Map) base ).values(); > } > else if ( !( (Map) base ).containsKey("keySet") && "keySet".equals(property) ) > { > context.setPropertyResolved(true); > return ( (Map) base ).keySet(); > } > else if ( !( (Map) base ).containsKey("entrySet") && "entrySet".equals(property) ) > { > context.setPropertyResolved(true); > return ( (Map) base ).entrySet(); > } > else > { > return null; > } > } > The only disadvantage of this is that if you actually are trying to get at map.size(), there will be no way to do so if the Map happens to contain a key named "size". However, in such a case, #{MyBean.someMap.keySet.size} or #{MyBean.someMap.values.size} could instead be used to obtain the Map's size. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Tue Jan 27 18:03:44 2009 From: jira-events at lists.jboss.org (Ian Springer (JIRA)) Date: Tue, 27 Jan 2009 18:03:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3916) SeamELResolver.resolveInMap() will resolve a property "size" to ((Map)base).size() even if the Map contains a key named "size" - instead, it should return null and allow javax.el.MapELResolver to resolve the property to ((Map)base).get("size") In-Reply-To: <19503838.1233096044156.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <5841600.1233097424168.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449950#action_12449950 ] Ian Springer commented on JBSEAM-3916: -------------------------------------- Note, this bug is an issue for RHQ/Jopr/JON (see http://jira.rhq-project.org/browse/RHQ-1415). > SeamELResolver.resolveInMap() will resolve a property "size" to ((Map)base).size() even if the Map contains a key named "size" - instead, it should return null and allow javax.el.MapELResolver to resolve the property to ((Map)base).get("size") > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBSEAM-3916 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3916 > Project: Seam > Issue Type: Bug > Components: EL > Affects Versions: 2.1.0.SP1 > Reporter: Ian Springer > Priority: Critical > > I have an expression: > #{MyBean.someMap['size']} > In my non-Seam JSF app, this expression was resolving to MyBean.getSomeMap().get("size"). However, when I integrated Seam into my app, the expression started instead resolving to MyBean.getSomeMap().size(), which broke my app. This is occurring because SeamELResolver is ahead of javax.el.MapELResolver in the CompositeELResolver resolver list, and its resolveInMap() function ensures a property named "size" resolves to ((Map)base).size() This makes it impossible for me to obtain the value of the element with key "size" from my Map via EL. > To solve this, I suggest changing SeamELResolver.resolveInMap() to the following: > private Object resolveInMap(ELContext context, Object base, Object property) > { > if ( !( (Map) base ).containsKey("size") && "size".equals(property) ) > { > context.setPropertyResolved(true); > return ( (Map) base ).size(); > } > else if ( !( (Map) base ).containsKey("values") && "values".equals(property) ) > { > context.setPropertyResolved(true); > return ( (Map) base ).values(); > } > else if ( !( (Map) base ).containsKey("keySet") && "keySet".equals(property) ) > { > context.setPropertyResolved(true); > return ( (Map) base ).keySet(); > } > else if ( !( (Map) base ).containsKey("entrySet") && "entrySet".equals(property) ) > { > context.setPropertyResolved(true); > return ( (Map) base ).entrySet(); > } > else > { > return null; > } > } > The only disadvantage of this is that if you actually are trying to get at map.size(), there will be no way to do so if the Map happens to contain a key named "size". However, in such a case, #{MyBean.someMap.keySet.size} or #{MyBean.someMap.values.size} could instead be used to obtain the Map's size. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 28 09:02:44 2009 From: jira-events at lists.jboss.org (Jozef Hartinger (JIRA)) Date: Wed, 28 Jan 2009 09:02:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Work started: (JBSEAM-3805) Automate wickets buildtime/runtime instrumentation builds in functional tests In-Reply-To: <30765757.1228490316618.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <17473379.1233151364254.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBSEAM-3805 started by Jozef Hartinger. > Automate wickets buildtime/runtime instrumentation builds in functional tests > ----------------------------------------------------------------------------- > > Key: JBSEAM-3805 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3805 > Project: Seam > Issue Type: Task > Components: Test Harness > Affects Versions: 2.1.1.CR2 > Reporter: Jay Balunas > Assignee: Jozef Hartinger > Fix For: 2.1.2.CR1 > > > The wicket example now have two ways that it can be instrumented and both need to be tested using functional test suite. See wicket's readme and build.xml for instructions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 28 09:07:44 2009 From: jira-events at lists.jboss.org (Daniel Wiell (JIRA)) Date: Wed, 28 Jan 2009 09:07:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3917) NPE in Image.getImage() for images with unsupported content type Message-ID: <23910203.1233151664277.JavaMail.jira@cloud.prod.atl2.jboss.com> NPE in Image.getImage() for images with unsupported content type ---------------------------------------------------------------- Key: JBSEAM-3917 URL: https://jira.jboss.org/jira/browse/JBSEAM-3917 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA Reporter: Daniel Wiell Image.readImage(InputStream) sets contentType to null if the type of the image is unknown (say a bmp). When invoking Image.getImage(), a NPE is thrown: java.lang.NullPointerException at org.jboss.seam.ui.graphicImage.Image.getImage(Image.java:154) ImageIO.write(bufferedImage, getContentType().getImageFormatName(), outputStream); getContentType() returns null. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 28 12:07:48 2009 From: jira-events at lists.jboss.org (Julien Kronegg (JIRA)) Date: Wed, 28 Jan 2009 12:07:48 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3278) seam-gen generate-ui problem - entity in a different package In-Reply-To: <25946222.1219070458895.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <9126273.1233162468966.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12450079#action_12450079 ] Julien Kronegg commented on JBSEAM-3278: ---------------------------------------- Occurs at least under Seam 2.0.0.GA when the package name is specified in the seam-gen.reveng.xml file: There is a "patch" (better than proposed in the associated forum thread, I think): In the {SEAMHOME}/seam-gen/src/EntityHome.java.ftl, replace the following strings: 1) line 74: ${parentPojo.shortName} ${property.name}=${parentHomeName}.getDefinedInstance(); must be replaced by: <#if parentPojo.packageName != "">${pojo.importType("${parentPojo.packageName}.${parentPojo.shortName}")}<#else>${parentPojo.shortName} ${property.name}=${parentHomeName}.getDefinedInstance(); 2) line 104: public ${pojo.importType("java.util.List")}<${childPojo.shortName}> ${getter}() { must be replaced by: public ${pojo.importType("java.util.List")}<<#if childPojo.packageName != "">${pojo.importType("${childPojo.packageName}.${childPojo.shortName}")}<#else>${childPojo.shortName}> ${getter}() { IMHO, this "patch" is better than the ones proposed in the forum thread because it imports the missing classes. The only use case which is does not work is if an EntityHome in a package "A" uses a class without package: there will be no import but the class will not compile because the class cannot be found. However, this use cases seems to be not planned in the Java specification (see http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4361575). Moreover, using a class without package name is discouraged by best practices. > seam-gen generate-ui problem - entity in a different package > ------------------------------------------------------------- > > Key: JBSEAM-3278 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3278 > Project: Seam > Issue Type: Bug > Components: Tools > Reporter: Guido Simone > > Here is an example: > The entity class PersonAddress has a ManyToOne relationship with Address which happens to be in a different package. The seam generate-ui command will generate (among other things) an EntityHome class named PersonAddressHome. > //================================== > // PersonAddress > package com.domain.model.person; > import com.domain.model.location.Address; > @Entity > public class PersonAddress > { > private Address address; > private PersonAddressTypeLookup addressTypeLookup; > private Person person; > @ManyToOne @NotNull > public Address getAddress() {return address;} > @ManyToOne @NotNull > public PersonAddressTypeLookup getAddressTypeLookup() > { return addressTypeLookup; } > @ManyToOne @NotNull > public Person getPerson() {return person;} > // setters omitted > } > which generates: > //================================== > // PersonAddressHome > package com.domain.action; > import com.domain.model.person.*; > import org.jboss.seam.annotations.In; > import org.jboss.seam.annotations.Name; > import org.jboss.seam.framework.EntityHome; > @Name("personAddressHome") > public class PersonAddressHome extends EntityHome > { > // code omitted... > public void wire() > { > getInstance(); > Address address = addressHome.getDefinedInstance(); > if (address != null) > { > getInstance().setAddress(address); > } > PersonAddressTypeLookup addressTypeLookup = addressTypeLookupHome > .getDefinedInstance(); > if (addressTypeLookup != null) > { > getInstance().setAddressTypeLookup(addressTypeLookup); > } > Person person = personHome.getDefinedInstance(); > if (person != null) > { > getInstance().setPerson(person); > } > } > The generated code imports all entities in com.domain.model.person, but does not import anything from com.domain.model.location so the compilation fails in the second line of the wire() method (Address cannot be resolved to a type). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Wed Jan 28 13:27:44 2009 From: jira-events at lists.jboss.org (Dan Hinojosa (JIRA)) Date: Wed, 28 Jan 2009 13:27:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3918) org.jboss.seam.security.Identity needs to be decoupled from system for testing purposes Message-ID: <26827884.1233167264370.JavaMail.jira@cloud.prod.atl2.jboss.com> org.jboss.seam.security.Identity needs to be decoupled from system for testing purposes --------------------------------------------------------------------------------------- Key: JBSEAM-3918 URL: https://jira.jboss.org/jira/browse/JBSEAM-3918 Project: Seam Issue Type: Feature Request Components: Security Affects Versions: 2.1.1.GA Environment: JBoss Seam 2.1.1.GA Reporter: Dan Hinojosa org.jboss.seam.security.Identity cannot be used in unit testing. Unit testing being defined as an isolated (no db, no app server) test. If I provide an identity into a test, once I call assertTrue(identity.hasRole("xxx")); I get an understandable NullPointerException because there is no Seam Context available. If I may recommend that org.jboss.seam.security.Identity be either an interface or a POJO with no dependencies as an API so TDD advocates can test their code easily. This would also fulfill Seam's idea that everything for the end user is testable. Example Test @Test(groups = "unit") public void testAuthenticateSuccessWithRoles() { Log log = createMock(Log.class); EntityManager entityManager = createMock(EntityManager.class); Query query = createMock(Query.class); Calendar createdDate = Calendar.getInstance(); Calendar updatedDate = Calendar.getInstance(); User user = new User(); user.setCreatedDate(createdDate); user.setEmail("ricardo at aol.com"); user.setFirstName("Ricardo"); user.setLastName("Montalban"); user.setName("rmontalban"); user.setNotes("userNotes2"); user.setPassword("passw0rd"); user.setId(220L); user.setUpdatedDate(updatedDate); Role role = new Role(); role.setName("mgmt"); role.setId(665L); Calendar createdDate2 = Calendar.getInstance(); createdDate2.set(2009, 1, 15, 12, 14, 15); role.setCreatedDate(createdDate2); Calendar updatedDate2 = Calendar.getInstance(); updatedDate2.set(2009, 1, 17, 13, 16, 20); role.setUpdatedDate(updatedDate2); role.setNotes("notes"); user.addRole(role); role.addUser(user); Credentials credentials = new Credentials(); credentials.setUsername("rmontalban"); credentials.setPassword("passw0rd"); Identity identity = new Identity(); log.info("authenticating #0", "rmontalban"); expect(entityManager.createQuery("SELECT u from User u " + "WHERE u.name = #{credentials.username} AND u.password = #{credentials.password}")).andReturn(query); expect(query.getSingleResult()).andReturn(user); replay(entityManager, query, log); Authenticator authenticator = new Authenticator(); authenticator.setLog(log); authenticator.setIdentity(identity); authenticator.setEntityManager(entityManager); authenticator.setCredentials(credentials); assertTrue(authenticator.authenticate()); assertTrue(identity.hasRole("mgmt")); //NullPointerException here verify(entityManager, query, log); } Output from the above test: java.lang.NullPointerException at org.jboss.seam.security.Identity.tryLogin(Identity.java:164) at org.jboss.seam.security.Identity.hasRole(Identity.java:444) at com.manning.mymanning.AuthenticatorTest.testAuthenticateSuccessWithRoles(AuthenticatorTest.java:128) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 29 02:36:44 2009 From: jira-events at lists.jboss.org (Julien Kronegg (JIRA)) Date: Thu, 29 Jan 2009 02:36:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3919) Add a boolean property "enable live preview" in the user profile properties Message-ID: <19684365.1233214604248.JavaMail.jira@cloud.prod.atl2.jboss.com> Add a boolean property "enable live preview" in the user profile properties --------------------------------------------------------------------------- Key: JBSEAM-3919 URL: https://jira.jboss.org/jira/browse/JBSEAM-3919 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.1.GA Environment: Seam forum Reporter: Julien Kronegg Priority: Minor When posting messages on the Seam forum, it is required to check the "Enable live preview" checkbox to enable post live preview. Checking the "enable live preview" for each post is really boring... It would be nice to add a boolean property in the user profile preferences to pre-check this checkbox. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 29 08:58:44 2009 From: jira-events at lists.jboss.org (philip andrew (JIRA)) Date: Thu, 29 Jan 2009 08:58:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3920) Seam-gen creates code which will not compile for multiple foreign keys (mysql) Message-ID: <27877952.1233237524850.JavaMail.jira@cloud.prod.atl2.jboss.com> Seam-gen creates code which will not compile for multiple foreign keys (mysql) ------------------------------------------------------------------------------ Key: JBSEAM-3920 URL: https://jira.jboss.org/jira/browse/JBSEAM-3920 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Reporter: philip andrew The bug is described at forum reference. Duplicate description is below. Hi, I have two mysql tables, user and staff. On my user table I have three foreign keys, social_security_assistance_confirmed_by_staff_id, approved_by_staff_id, rejected_by_staff_id, all reference staff.id. I seam-gen with seam generate-entities and one problem is it makes my UserHome class wrong with: @Name("userHome") public class UserHome extends EntityHome { @In(create = true) StaffHome staffHome; @In(create = true) StaffHome staffHome; @In(create = true) StaffHome staffHome; That does NOT compile, how come it generates this? Everything is ok if I delete the multiples and cut it down to one. Here are the mysql tables CREATE TABLE `staff` ( `id` int(10) NOT NULL auto_increment, `user` varchar(80) collate utf8_unicode_ci NOT NULL, `password` varchar(80) collate utf8_unicode_ci NOT NULL, PRIMARY KEY (`id`), UNIQUE KEY `user` (`user`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; CREATE TABLE `user` ( `id` int(10) NOT NULL auto_increment, `user` varchar(80) collate utf8_unicode_ci NOT NULL, `password` varchar(80) collate utf8_unicode_ci NOT NULL, `first_name_chinese` varchar(80) collate utf8_unicode_ci default NULL, `last_name_chinese` varchar(80) collate utf8_unicode_ci default NULL, `first_name_english` varchar(80) collate utf8_unicode_ci default NULL, `last_name_english` varchar(80) collate utf8_unicode_ci default NULL, `hk_id_number` varchar(20) collate utf8_unicode_ci NOT NULL, `date_of_birth` date NOT NULL, `contact_phone_number` varchar(20) collate utf8_unicode_ci default NULL, `email` varchar(80) collate utf8_unicode_ci NOT NULL, `address` varchar(255) collate utf8_unicode_ci default NULL, `school` varchar(80) collate utf8_unicode_ci default NULL, `social_security_assistance_indicated` tinyint(1) NOT NULL, `social_security_assistance_confirmed` tinyint(1) NOT NULL default '0', `social_security_assistance_confirmed_by_staff_id` int(10) default NULL, `date_signed` date default NULL, `approved_by_staff` tinyint(1) NOT NULL default '0', `approved_by_staff_id` int(10) default NULL, `rejected_by_staff` tinyint(1) NOT NULL default '0', `rejected_by_staff_id` int(10) default NULL, `blacklist` tinyint(1) NOT NULL default '0', `created` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP, `updated` timestamp NOT NULL default '0000-00-00 00:00:00', PRIMARY KEY (`id`), UNIQUE KEY `user` (`user`), UNIQUE KEY `hk_id_number` (`hk_id_number`), UNIQUE KEY `email` (`email`), KEY `social_security_assistance_confirmed_by_staff_id_idxfk` (`social_security_assistance_confirmed_by_staff_id`), KEY `approved_by_staff_id_idxfk` (`approved_by_staff_id`), KEY `rejected_by_staff_id_idxfk` (`rejected_by_staff_id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; ALTER TABLE `user` ADD CONSTRAINT `user_ibfk_3` FOREIGN KEY (`rejected_by_staff_id`) REFERENCES `staff` (`id`), ADD CONSTRAINT `user_ibfk_1` FOREIGN KEY (`social_security_assistance_confirmed_by_staff_id`) REFERENCES `staff` (`id`), ADD CONSTRAINT `user_ibfk_2` FOREIGN KEY (`approved_by_staff_id`) REFERENCES `staff` (`id`); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 29 10:06:44 2009 From: jira-events at lists.jboss.org (Marek Novotny (JIRA)) Date: Thu, 29 Jan 2009 10:06:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-3894) Upgrade to RichFaces 3.3.0.GA In-Reply-To: <1399517.1232039043969.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <1241163.1233241604262.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny reassigned JBSEAM-3894: ------------------------------------- Assignee: Marek Novotny > Upgrade to RichFaces 3.3.0.GA > ----------------------------- > > Key: JBSEAM-3894 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3894 > Project: Seam > Issue Type: Task > Components: Build > Reporter: Jay Balunas > Assignee: Marek Novotny > Priority: Critical > Fix For: 2.1.2.CR1 > > > RichFaces 3.3.0 has been released and Seam should upgrade to it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 29 11:07:44 2009 From: jira-events at lists.jboss.org (Adrian Mitev (JIRA)) Date: Thu, 29 Jan 2009 11:07:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1021) Don't log exceptions if they are handled in pages.xml In-Reply-To: <23674580.1173489027705.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <8314039.1233245264326.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12450278#action_12450278 ] Adrian Mitev commented on JBSEAM-1021: -------------------------------------- This doesn't work for me (with Seam 2.1.1). For more info look here - http://seamframework.org/Community/HowNOTToLogAnExceptionInTheLogFile > Don't log exceptions if they are handled in pages.xml > ----------------------------------------------------- > > Key: JBSEAM-1021 > URL: https://jira.jboss.org/jira/browse/JBSEAM-1021 > Project: Seam > Issue Type: Bug > Components: Security > Reporter: Christian Bauer > Assignee: Shane Bryzak > Priority: Minor > Fix For: 2.1.0.A1 > > > Mostly relevant for security: > 01:54:16,042 ERROR [SeamPhaseListener] uncaught exception > javax.faces.el.EvaluationException: Exception while invoking expression #{documentHome.checkNodePermission} > ... > You get hundreds of these when you run a site with security. Didn't find an open JIRA case for that. > I think the SeamPhaseListener should not log.error() "uncaught exception" and print the whole thing _and_ pass it on to Exceptions.instance().handle(e). The phase listener doesn't know if it's handled or not. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 29 15:59:44 2009 From: jira-events at lists.jboss.org (Marek Novotny (JIRA)) Date: Thu, 29 Jan 2009 15:59:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Resolved: (JBSEAM-3894) Upgrade to RichFaces 3.3.0.GA In-Reply-To: <1399517.1232039043969.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <27239645.1233262784317.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny resolved JBSEAM-3894. ----------------------------------- Resolution: Done richfaces was upgraded to 3.3.0.GA > Upgrade to RichFaces 3.3.0.GA > ----------------------------- > > Key: JBSEAM-3894 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3894 > Project: Seam > Issue Type: Task > Components: Build > Reporter: Jay Balunas > Assignee: Marek Novotny > Priority: Critical > Fix For: 2.1.2.CR1 > > > RichFaces 3.3.0 has been released and Seam should upgrade to it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 29 16:49:44 2009 From: jira-events at lists.jboss.org (Eric Schneider (JIRA)) Date: Thu, 29 Jan 2009 16:49:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3921) rewrite-filter not working with scheme in page descriptor Message-ID: <6379993.1233265784182.JavaMail.jira@cloud.prod.atl2.jboss.com> rewrite-filter not working with scheme in page descriptor --------------------------------------------------------- Key: JBSEAM-3921 URL: https://jira.jboss.org/jira/browse/JBSEAM-3921 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA Environment: Windows XP / jdk1.5.0_06 / jboss-4.2.3.GA Reporter: Eric Schneider Using scheme="http" (or https) in *.page.xml breaks rewrite of outgoing patterns. Incoming pattern still maps. Given: Two pages, one with a scheme specified and on without * s:links to /NoScheme.xhtml will rewrite properly * s:links to /Scheme.xhtml will not be rewritten ( keeps Scheme.seam format) * The scheme of the page containing the links has no effect. * Incoming rewrites are applied: /Scheme, /Scheme.seam, /NoScheme, /NoScheme.seam all work Same behavior with Seam 2.1.0.SP1. Briefly tried svn trunk, but there seems to be other problems there (losing project name from context path on rewrites). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 29 16:51:44 2009 From: jira-events at lists.jboss.org (Eric Schneider (JIRA)) Date: Thu, 29 Jan 2009 16:51:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3921) rewrite-filter not working with scheme in page descriptor In-Reply-To: <6379993.1233265784182.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <8667113.1233265904355.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Schneider updated JBSEAM-3921: ----------------------------------- Attachment: NoScheme.page.xml NoScheme.xhtml Scheme.page.xml > rewrite-filter not working with scheme in page descriptor > --------------------------------------------------------- > > Key: JBSEAM-3921 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3921 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.1.1.GA > Environment: Windows XP / jdk1.5.0_06 / jboss-4.2.3.GA > Reporter: Eric Schneider > Attachments: NoScheme.page.xml, NoScheme.xhtml, Scheme.page.xml, Scheme.xhtml > > > Using scheme="http" (or https) in *.page.xml breaks rewrite of outgoing patterns. Incoming pattern still maps. > Given: Two pages, one with a scheme specified and on without > * s:links to /NoScheme.xhtml will rewrite properly > * s:links to /Scheme.xhtml will not be rewritten ( keeps Scheme.seam format) > * The scheme of the page containing the links has no effect. > * Incoming rewrites are applied: /Scheme, /Scheme.seam, /NoScheme, /NoScheme.seam all work > Same behavior with Seam 2.1.0.SP1. Briefly tried svn trunk, but there seems to be other problems there (losing project name from context path on rewrites). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Thu Jan 29 16:51:44 2009 From: jira-events at lists.jboss.org (Eric Schneider (JIRA)) Date: Thu, 29 Jan 2009 16:51:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3921) rewrite-filter not working with scheme in page descriptor In-Reply-To: <6379993.1233265784182.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <16093551.1233265904480.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Schneider updated JBSEAM-3921: ----------------------------------- Attachment: Scheme.xhtml > rewrite-filter not working with scheme in page descriptor > --------------------------------------------------------- > > Key: JBSEAM-3921 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3921 > Project: Seam > Issue Type: Bug > Components: Core > Affects Versions: 2.1.1.GA > Environment: Windows XP / jdk1.5.0_06 / jboss-4.2.3.GA > Reporter: Eric Schneider > Attachments: NoScheme.page.xml, NoScheme.xhtml, Scheme.page.xml, Scheme.xhtml > > > Using scheme="http" (or https) in *.page.xml breaks rewrite of outgoing patterns. Incoming pattern still maps. > Given: Two pages, one with a scheme specified and on without > * s:links to /NoScheme.xhtml will rewrite properly > * s:links to /Scheme.xhtml will not be rewritten ( keeps Scheme.seam format) > * The scheme of the page containing the links has no effect. > * Incoming rewrites are applied: /Scheme, /Scheme.seam, /NoScheme, /NoScheme.seam all work > Same behavior with Seam 2.1.0.SP1. Briefly tried svn trunk, but there seems to be other problems there (losing project name from context path on rewrites). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 30 04:47:54 2009 From: jira-events at lists.jboss.org (Ondrej Skutka (JIRA)) Date: Fri, 30 Jan 2009 04:47:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3920) Seam-gen creates code which will not compile for multiple foreign keys (mysql) In-Reply-To: <27877952.1233237524850.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <9115283.1233308874535.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondrej Skutka closed JBSEAM-3920. --------------------------------- Resolution: Duplicate Issue > Seam-gen creates code which will not compile for multiple foreign keys (mysql) > ------------------------------------------------------------------------------ > > Key: JBSEAM-3920 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3920 > Project: Seam > Issue Type: Bug > Affects Versions: 2.1.1.GA > Reporter: philip andrew > > The bug is described at forum reference. Duplicate description is below. > Hi, > I have two mysql tables, user and staff. On my user table I have three foreign keys, social_security_assistance_confirmed_by_staff_id, approved_by_staff_id, rejected_by_staff_id, all reference staff.id. > I seam-gen with seam generate-entities and one problem is it makes my UserHome class wrong with: > @Name("userHome") > public class UserHome extends EntityHome { > @In(create = true) > StaffHome staffHome; > @In(create = true) > StaffHome staffHome; > @In(create = true) > StaffHome staffHome; > That does NOT compile, how come it generates this? Everything is ok if I delete the multiples and cut it down to one. > Here are the mysql tables > CREATE TABLE `staff` ( > `id` int(10) NOT NULL auto_increment, > `user` varchar(80) collate utf8_unicode_ci NOT NULL, > `password` varchar(80) collate utf8_unicode_ci NOT NULL, > PRIMARY KEY (`id`), > UNIQUE KEY `user` (`user`) > ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; > CREATE TABLE `user` ( > `id` int(10) NOT NULL auto_increment, > `user` varchar(80) collate utf8_unicode_ci NOT NULL, > `password` varchar(80) collate utf8_unicode_ci NOT NULL, > `first_name_chinese` varchar(80) collate utf8_unicode_ci default NULL, > `last_name_chinese` varchar(80) collate utf8_unicode_ci default NULL, > `first_name_english` varchar(80) collate utf8_unicode_ci default NULL, > `last_name_english` varchar(80) collate utf8_unicode_ci default NULL, > `hk_id_number` varchar(20) collate utf8_unicode_ci NOT NULL, > `date_of_birth` date NOT NULL, > `contact_phone_number` varchar(20) collate utf8_unicode_ci default NULL, > `email` varchar(80) collate utf8_unicode_ci NOT NULL, > `address` varchar(255) collate utf8_unicode_ci default NULL, > `school` varchar(80) collate utf8_unicode_ci default NULL, > `social_security_assistance_indicated` tinyint(1) NOT NULL, > `social_security_assistance_confirmed` tinyint(1) NOT NULL default '0', > `social_security_assistance_confirmed_by_staff_id` int(10) default NULL, > `date_signed` date default NULL, > `approved_by_staff` tinyint(1) NOT NULL default '0', > `approved_by_staff_id` int(10) default NULL, > `rejected_by_staff` tinyint(1) NOT NULL default '0', > `rejected_by_staff_id` int(10) default NULL, > `blacklist` tinyint(1) NOT NULL default '0', > `created` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP, > `updated` timestamp NOT NULL default '0000-00-00 00:00:00', > PRIMARY KEY (`id`), > UNIQUE KEY `user` (`user`), > UNIQUE KEY `hk_id_number` (`hk_id_number`), > UNIQUE KEY `email` (`email`), > KEY `social_security_assistance_confirmed_by_staff_id_idxfk` (`social_security_assistance_confirmed_by_staff_id`), > KEY `approved_by_staff_id_idxfk` (`approved_by_staff_id`), > KEY `rejected_by_staff_id_idxfk` (`rejected_by_staff_id`) > ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; > ALTER TABLE `user` > ADD CONSTRAINT `user_ibfk_3` FOREIGN KEY (`rejected_by_staff_id`) REFERENCES `staff` (`id`), > ADD CONSTRAINT `user_ibfk_1` FOREIGN KEY (`social_security_assistance_confirmed_by_staff_id`) REFERENCES `staff` (`id`), > ADD CONSTRAINT `user_ibfk_2` FOREIGN KEY (`approved_by_staff_id`) REFERENCES `staff` (`id`); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 30 06:06:44 2009 From: jira-events at lists.jboss.org (Jozef Hartinger (JIRA)) Date: Fri, 30 Jan 2009 06:06:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3922) Wicket example - build/run time instrumentation switch cannot be controlled from outside of build script Message-ID: <29085860.1233313604156.JavaMail.jira@cloud.prod.atl2.jboss.com> Wicket example - build/run time instrumentation switch cannot be controlled from outside of build script -------------------------------------------------------------------------------------------------------- Key: JBSEAM-3922 URL: https://jira.jboss.org/jira/browse/JBSEAM-3922 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.1.GA Reporter: Jozef Hartinger Assignee: Jozef Hartinger Priority: Minor Fix For: 2.1.2.CR1 Property "instrumentAtBuildTime" definition has to be removed from build.xml in order to deploy the example using runtime instrumentation. This is not suitable for automation framework. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 30 06:45:44 2009 From: jira-events at lists.jboss.org (philip andrew (JIRA)) Date: Fri, 30 Jan 2009 06:45:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3923) Seam-gen should create drop-down combo for ENUM field types Message-ID: <25744006.1233315944567.JavaMail.jira@cloud.prod.atl2.jboss.com> Seam-gen should create drop-down combo for ENUM field types ----------------------------------------------------------- Key: JBSEAM-3923 URL: https://jira.jboss.org/jira/browse/JBSEAM-3923 Project: Seam Issue Type: Feature Request Reporter: philip andrew Priority: Minor When I run seam-gen to create the UI, for ENUM field types of my table (mysql) it should create drop-down combo box for the ENUM input. The current behavior is to create a text input field, if the user enters a value that does not match the ENUM then a exception is thrown, this is ugly for the user. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 30 06:56:44 2009 From: jira-events at lists.jboss.org (Jozef Hartinger (JIRA)) Date: Fri, 30 Jan 2009 06:56:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3922) Wicket example - build/run time instrumentation switch cannot be controlled from outside of build script In-Reply-To: <29085860.1233313604156.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <17522122.1233316604414.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jozef Hartinger closed JBSEAM-3922. ----------------------------------- Resolution: Done > Wicket example - build/run time instrumentation switch cannot be controlled from outside of build script > -------------------------------------------------------------------------------------------------------- > > Key: JBSEAM-3922 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3922 > Project: Seam > Issue Type: Bug > Components: Examples > Affects Versions: 2.1.1.GA > Reporter: Jozef Hartinger > Assignee: Jozef Hartinger > Priority: Minor > Fix For: 2.1.2.CR1 > > > Property "instrumentAtBuildTime" definition has to be removed from build.xml in order to deploy the example using runtime instrumentation. This is not suitable for automation framework. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 30 09:35:44 2009 From: jira-events at lists.jboss.org (Jozef Hartinger (JIRA)) Date: Fri, 30 Jan 2009 09:35:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3449) Upgrade to latest RestEasy beta In-Reply-To: <21376851.1222121060720.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <9194088.1233326144299.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12450396#action_12450396 ] Jozef Hartinger commented on JBSEAM-3449: ----------------------------------------- Updated to RESTEasy 1.0.1.GA. Basic functionality verified. Now working on better testcase. Thanks to Scott Olcott, Xiaofeng Lin and John Sublette for patches. > Upgrade to latest RestEasy beta > ------------------------------- > > Key: JBSEAM-3449 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3449 > Project: Seam > Issue Type: Feature Request > Components: WS > Affects Versions: 2.1.0.BETA1 > Reporter: Scott Olcott > Assignee: Jozef Hartinger > Fix For: 2.1.2.GA > > Attachments: jboss-seam-resteasy-2.1.1.CR2.JBSEAM-3449-patched.jar, resteasyBeta-8.txt > > > The latest beta is beta-8 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 30 10:34:44 2009 From: jira-events at lists.jboss.org (John Sublette (JIRA)) Date: Fri, 30 Jan 2009 10:34:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3449) Upgrade to latest RestEasy beta In-Reply-To: <21376851.1222121060720.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <12634244.1233329684276.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12450412#action_12450412 ] John Sublette commented on JBSEAM-3449: --------------------------------------- After doing that patch, I noticed several additional bugs. For the Resteasy client interface, you can share an interface and implement it in a class without the tags and it should find it. The code as it existed with my patch would break if it found tags on interfaces, and wouldn't register tagless classes that implement tagged interfaces. The resteasy bootstrapper uses Scannotation to search and find them, and that worked for me, though I cludged it in a bit poorly. Also, I had difficulty trying to get two web-applications to use Seam+Resteasy, only the last web-application worked. I had to make a ResteasyProviderFactory in the mold of ThreadLocalResteasyProviderFactory that used Component to retrieve the right Application scoped ResteasyDispatcher, where I stored the providerFactory that should be used in that application. Then I had to change the ResteasyDispatcher.onStartup() to register my factory with the Resteasy library, and to provide access to the stored instance of ResteasyProviderFactory. In order to do this, though I had to replicate all seam and resteasy libraries in each application's WEB-INF/lib directory. I couldn't seem to get things to go into Tomcat's common library directory and still work - it would get the last loaded's context. I probably have to understand Seam's library structure better. e.g.: **ResteasyDispatcher** .... @Create public void onStartup() { log.debug("assigning registered RESTEasy resources and providers"); providerFactory = new ResteasyProviderFactory(); ResteasyProviderFactory providerFactory = new SeamApplicationLocalResteasyProviderFactory(); ResteasyProviderFactory.setInstance(providerFactory); // This is really necessary .... public ResteasyProviderFactory getProviderFactory() { return providerFactory; } **SeamApplicationLocalResteasyProviderFactory** public class SeamApplicationLocalResteasyProviderFactory extends ResteasyProviderFactory public ResteasyProviderFactory getDelegate() { ResteasyDispatcher dispatcher = (ResteasyDispatcher)Component.getInstance(ResteasyDispatcher.class, ScopeType.APPLICATION); if (dispatcher == null) return defaultFactory; return dispatcher.getProviderFactory(); } ... ...(Everything else is pretty much identical to ThreadLocalResteasyProviderFactory) > Upgrade to latest RestEasy beta > ------------------------------- > > Key: JBSEAM-3449 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3449 > Project: Seam > Issue Type: Feature Request > Components: WS > Affects Versions: 2.1.0.BETA1 > Reporter: Scott Olcott > Assignee: Jozef Hartinger > Fix For: 2.1.2.GA > > Attachments: jboss-seam-resteasy-2.1.1.CR2.JBSEAM-3449-patched.jar, resteasyBeta-8.txt > > > The latest beta is beta-8 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 30 19:51:44 2009 From: jira-events at lists.jboss.org (Nicolae Tabusca (JIRA)) Date: Fri, 30 Jan 2009 19:51:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3924) This patch adds full integration of seam with gwt 1.5. Message-ID: <3370166.1233363104171.JavaMail.jira@cloud.prod.atl2.jboss.com> This patch adds full integration of seam with gwt 1.5. ------------------------------------------------------ Key: JBSEAM-3924 URL: https://jira.jboss.org/jira/browse/JBSEAM-3924 Project: Seam Issue Type: Patch Components: GWT Affects Versions: 2.1.1.GA Environment: Any Reporter: Nicolae Tabusca Priority: Critical Fix For: 2.1.2.GA ### Eclipse Workspace Patch 1.0 #P jboss-seam Index: src/remoting/org/jboss/seam/remoting/gwt/GWTService.java =================================================================== --- src/remoting/org/jboss/seam/remoting/gwt/GWTService.java (revision 9989) +++ src/remoting/org/jboss/seam/remoting/gwt/GWTService.java (working copy) @@ -1,976 +1,178 @@ package org.jboss.seam.remoting.gwt; +import static org.jboss.seam.ScopeType.APPLICATION; +import static org.jboss.seam.annotations.Install.BUILT_IN; + import java.io.IOException; -import java.io.InputStream; -import java.lang.reflect.InvocationTargetException; import java.lang.reflect.Method; -import java.net.MalformedURLException; -import java.net.URL; -import java.text.ParseException; -import java.util.Arrays; -import java.util.HashMap; -import java.util.Map; import javax.servlet.ServletContext; import javax.servlet.ServletException; import javax.servlet.http.HttpServletRequest; import javax.servlet.http.HttpServletResponse; -import org.jboss.seam.core.ConversationPropagation; +import org.jboss.seam.Component; +import org.jboss.seam.annotations.Install; +import org.jboss.seam.annotations.Name; +import org.jboss.seam.annotations.Scope; +import org.jboss.seam.annotations.intercept.BypassInterceptors; +import org.jboss.seam.annotations.remoting.WebRemote; +import org.jboss.seam.contexts.ServletLifecycle; import org.jboss.seam.log.LogProvider; import org.jboss.seam.log.Logging; import org.jboss.seam.servlet.ContextualHttpServletRequest; +import org.jboss.seam.util.EJB; import org.jboss.seam.web.AbstractResource; import com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException; -import com.google.gwt.user.client.rpc.RemoteService; import com.google.gwt.user.client.rpc.SerializationException; import com.google.gwt.user.server.rpc.RPC; import com.google.gwt.user.server.rpc.RPCRequest; -import com.google.gwt.user.server.rpc.RPCServletUtils; import com.google.gwt.user.server.rpc.RemoteServiceServlet; -import com.google.gwt.user.server.rpc.SerializationPolicy; -import com.google.gwt.user.server.rpc.SerializationPolicyLoader; -import com.google.gwt.user.server.rpc.SerializationPolicyProvider; -import com.google.gwt.user.server.rpc.UnexpectedException; import com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader; -import com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter; /** - * Abstract base class for GWT 1.5 integration. + * GWT integration. * - * @author Shane Bryzak + * @author Nicolae Tabusca */ -public abstract class GWTService extends AbstractResource implements SerializationPolicyProvider -{ - protected static final LogProvider log = Logging.getLogProvider(GWTService.class); + at Scope(APPLICATION) + at Name("org.jboss.seam.remoting.gwt.gwtRemoteService") + at Install(precedence = BUILT_IN, classDependencies = {"com.google.gwt.user.client.rpc.RemoteService"}) + at BypassInterceptors +public class GWTService extends AbstractResource { + + protected static final LogProvider log + = Logging.getLogProvider(GWTService.class); - private static final HashMap> TYPE_NAMES; + public GWTService() { + } - static - { - TYPE_NAMES = new HashMap>(); - TYPE_NAMES.put("Z", boolean.class); - TYPE_NAMES.put("B", byte.class); - TYPE_NAMES.put("C", char.class); - TYPE_NAMES.put("D", double.class); - TYPE_NAMES.put("F", float.class); - TYPE_NAMES.put("I", int.class); - TYPE_NAMES.put("J", long.class); - TYPE_NAMES.put("S", short.class); + @Override + public String getResourcePath() { + return "/gwt"; + } - } - - /** - * A cache of moduleBaseURL and serialization policy strong name to - * {@link SerializationPolicy}. - */ - private final Map serializationPolicyCache = new HashMap(); + /** + * This is called internally. + * + * @see RemoteServiceServlet#doPost + */ + @Override + public final void getResource(final HttpServletRequest request, + final HttpServletResponse response) + throws ServletException, IOException { - @Override - public String getResourcePath() - { - return "/gwt"; - } + ContextualHttpServletRequest contextualRequest + = new ContextualHttpServletRequest(request) { - protected abstract ServerSerializationStreamReader getStreamReader(); + private GWTController controller = new GWTController(); - protected abstract ServerSerializationStreamWriter getStreamWriter(); - - protected abstract String createResponse( - ServerSerializationStreamWriter stream, Class responseType, - Object responseObj, boolean isException); - - // private final Set knownImplementedInterfaces = new HashSet(); - private final ThreadLocal perThreadRequest = new ThreadLocal(); - - private final ThreadLocal perThreadResponse = new ThreadLocal(); - - /** - * This is called internally. - * - * @see RemoteServiceServlet#doPost - */ - @Override - public final void getResource(final HttpServletRequest request, - final HttpServletResponse response) throws ServletException, - IOException - { - try - { - // Store the request & response objects in thread-local storage. - perThreadRequest.set(request); - perThreadResponse.set(response); - - new ContextualHttpServletRequest(request) { @Override - public void process() throws Exception - { - - try - { - // Read the request fully. - // - String requestPayload = RemoteServiceServlet_readContent(request); - - RemoteServiceServlet_onBeforeRequestDeserialized(requestPayload); - - // Invoke the core dispatching logic, which returns the - // serialized result - String responsePayload = processCall(requestPayload); - - RemoteServiceServlet_onAfterResponseSerialized(responsePayload); - - // Write the response. - // - RemoteServiceServlet_writeResponse(request, response, - responsePayload); - - } catch (Throwable e) - { - RemoteServiceServlet_doUnexpectedFailure(e); - } - + public void process() throws Exception { + + controller.service(request, response); } + }; - @Override - protected void restoreConversationId() - { - ConversationPropagation.instance().setConversationId( - GWTService.this.perThreadRequest.get().getParameter( - "conversationId")); - } + contextualRequest.run(); - @Override - protected void handleConversationPropagation() - { - } - }.run(); - } finally - { - perThreadRequest.remove(); - perThreadResponse.remove(); - } - } + } - /** - * This is public so that it can be unit tested easily without HTTP. - */ - public String processCall(String payload) throws SerializationException - { - // Create a stream to deserialize the request. - // - // ServerSerializationStreamReader streamReader = getStreamReader(); - // streamReader.prepareToRead(payload); - // - // // Read the service interface - // // - // String serviceIntfName = streamReader.readString(); - // - // // Read the method name. - // // - // String methodName = streamReader.readString(); - // - // // Read the number and names of the parameter classes from the stream. - // // We have to do this so that we can find the correct overload of the - // // method. - // // - // int paramCount = streamReader.readInt(); - // Class[] paramTypes = new Class[paramCount]; - // for (int i = 0; i < paramTypes.length; i++) - // { - // String paramClassName = streamReader.readString(); - // try - // { - // paramTypes[i] = getClassOrPrimitiveFromName(paramClassName); - // } catch (ClassNotFoundException e) - // { - // throw new SerializationException("Unknown parameter " + i - // + " type '" + paramClassName + "'", e); - // } - // } - // - // // Deserialize the parameters. - // // - // Object[] args = new Object[paramCount]; - // for (int i = 0; i < args.length; i++) - // { - // args[i] = streamReader.deserializeValue(paramTypes[i]); - // } + @SuppressWarnings("serial") + private class GWTController extends RemoteServiceServlet { - try - { - SeamRPCRequest rpcRequest = RPC_decodeRequest(payload, - this.getClass(), this); + @Override + public ServletContext getServletContext() { + return ServletLifecycle.getServletContext(); + } + + + @Override + @SuppressWarnings("unchecked") + public String processCall(String payload) throws SerializationException { + try { + Component remoteService = getRemoteServiceComponent(payload); + + Class beanClass = remoteService.getBeanClass(); + RPCRequest rpcRequest = RPC.decodeRequest(payload, beanClass, this); - return RPC_invokeAndEncodeResponse(this, rpcRequest.getMethod(), - rpcRequest.getParameterTypes(), rpcRequest.getParameters(), - rpcRequest.getSerializationPolicy()); - } catch (IncompatibleRemoteServiceException ex) - { - getServletContext() - .log( - "An IncompatibleRemoteServiceException was thrown while processing this call.", - ex); - return RPC.encodeResponseForFailure(null, ex); - } + Method serviceDef = rpcRequest.getMethod(); + Method serviceImpl = beanClass.getMethod(serviceDef.getName(), + serviceDef.getParameterTypes()); + if (isWebRemoteAnnotated(serviceImpl) == false) { + throw new RuntimeException( + "Unable to access a service method called [" + + serviceImpl.getName() + "] on class [" + + beanClass.getName() + + "] without the @WebRemote attribute. "); + } - // Make the call via reflection. - // - // String responsePayload = GENERIC_FAILURE_MSG; - // ServerSerializationStreamWriter streamWriter = getStreamWriter(); - // Throwable caught = null; - // try - // { - // GWTToSeamAdapter.ReturnedObject returnedObject = - // adapter.callWebRemoteMethod( - // serviceIntfName, methodName, paramTypes, args); - // Class returnType = returnedObject.returnType; - // Object returnVal = returnedObject.returnedObject; - // // Class returnType = serviceIntfMethod.getReturnType(); - // // Object returnVal = serviceIntfMethod.invoke(this, args); - // responsePayload = createResponse(streamWriter, returnType, returnVal, - // false); - // } catch (IllegalArgumentException e) - // { - // caught = e; - // } catch (IllegalAccessException e) - // { - // caught = e; - // } catch (InvocationTargetException e) - // { - // // Try to serialize the caught exception if the client is expecting it, - // // otherwise log the exception server-side. - // caught = e; - // Throwable cause = e.getCause(); - // if (cause != null) - // { - // // Update the caught exception to the underlying cause - // caught = cause; - // // Serialize the exception back to the client if it's a declared - // // exception - // if (cause instanceof SerializableException) - // { - // Class thrownClass = cause.getClass(); - // responsePayload = createResponse(streamWriter, thrownClass, - // cause, true); - // // Don't log the exception on the server - // caught = null; - // } - // } - // } - // - // if (caught != null) - // { - // responsePayload = GENERIC_FAILURE_MSG; - // ServletContext servletContext = getServletContext(); - // // servletContext may be null (for example, when unit testing) - // if (servletContext != null) - // { - // // Log the exception server side - // servletContext.log("Exception while dispatching incoming RPC call", - // caught); - // } - // } - } + return RPC.invokeAndEncodeResponse( + Component.getInstance(remoteService.getName()), + rpcRequest.getMethod(), rpcRequest.getParameters(), + rpcRequest.getSerializationPolicy()); - /** - * Gets the HttpServletRequest object for the current call. It - * is stored thread-locally so that simultaneous invocations can have - * different request objects. - */ - protected final HttpServletRequest getThreadLocalRequest() - { - return perThreadRequest.get(); - } - - /** - * Gets the HttpServletResponse object for the current call. It - * is stored thread-locally so that simultaneous invocations can have - * different response objects. - */ - protected final HttpServletResponse getThreadLocalResponse() - { - return perThreadResponse.get(); - } - - /** - * Returns an {@link RPCRequest} that is built by decoding the contents of an - * encoded RPC request and optionally validating that type can handle the - * request. If the type parameter is not null, the - * implementation checks that the type is assignable to the - * {@link com.google.gwt.user.client.rpc.RemoteService} interface requested - * in the encoded request string. - * - *

- * If the serializationPolicyProvider parameter is not null, it - * is asked for a {@link SerializationPolicy} to use to restrict the set of - * types that can be decoded from the request. If this parameter is - * null, then only subtypes of - * {@link com.google.gwt.user.client.rpc.IsSerializable IsSerializable} or - * types which have custom field serializers can be decoded. - *

- * - *

- * Invoking this method with null for the type parameter, - * decodeRequest(encodedRequest, null), is equivalent to calling - * decodeRequest(encodedRequest). - *

- * - * @param encodedRequest - * a string that encodes the - * {@link com.google.gwt.user.client.rpc.RemoteService} interface, - * the service method, and the arguments to pass to the service - * method - * @param type - * if not null, the implementation checks that the - * type is assignable to the - * {@link com.google.gwt.user.client.rpc.RemoteService} interface - * encoded in the encoded request string. - * @param serializationPolicyProvider - * if not null, the implementation asks this provider - * for a {@link SerializationPolicy} which will be used to restrict - * the set of types that can be decoded from this request - * @return an {@link RPCRequest} instance - * - * @throws NullPointerException - * if the encodedRequest is null - * @throws IllegalArgumentException - * if the encodedRequest is an empty string - * @throws IncompatibleRemoteServiceException - * if any of the following conditions apply: - *
    - *
  • if the types in the encoded request cannot be deserialized
    • - *
  • if the {@link ClassLoader} acquired from - * Thread.currentThread().getContextClassLoader() - * cannot load the service interface or any of the types specified - * in the encodedRequest
    • - *
  • the requested interface is not assignable to - * {@link com.google.gwt.user.client.rpc.RemoteService}
    • - *
  • the service method requested in the encodedRequest is not a - * member of the requested service interface
    • - *
  • the type parameter is not null and is not - * assignable to the requested - * {@link com.google.gwt.user.client.rpc.RemoteService} interface - *
- */ - public static SeamRPCRequest RPC_decodeRequest(String encodedRequest, - Class type, SerializationPolicyProvider serializationPolicyProvider) - { - if (encodedRequest == null) - { - throw new NullPointerException("encodedRequest cannot be null"); - } - - if (encodedRequest.length() == 0) - { - throw new IllegalArgumentException("encodedRequest cannot be empty"); - } - - ClassLoader classLoader = Thread.currentThread().getContextClassLoader(); - - try - { - ServerSerializationStreamReader streamReader = new ServerSerializationStreamReader( - classLoader, serializationPolicyProvider); - streamReader.prepareToRead(encodedRequest); - - // Read the name of the RemoteService interface - String serviceIntfName = streamReader.readString(); - - /* - * todo?? if (type != null) { if (!implementsInterface(type, - * serviceIntfName)) { // The service does not implement the requested - * interface throw new IncompatibleRemoteServiceException( - * "Blocked attempt to access interface '" + serviceIntfName + - * "', which is not implemented by '" + printTypeName(type) + - * "'; this is either misconfiguration or a hack attempt"); } } - */ - - SerializationPolicy serializationPolicy = streamReader - .getSerializationPolicy(); - Class serviceIntf; - try - { - serviceIntf = RPC_getClassFromSerializedName(serviceIntfName, - classLoader); - if (!RemoteService.class.isAssignableFrom(serviceIntf)) - { - // The requested interface is not a RemoteService interface - throw new IncompatibleRemoteServiceException( - "Blocked attempt to access interface '" - + printTypeName(serviceIntf) - + "', which doesn't extend RemoteService; this is either misconfiguration or a hack attempt"); + } catch (IncompatibleRemoteServiceException ex) { + log.error(ex.getMessage(), ex); + return RPC.encodeResponseForFailure(null, ex); + } catch (SecurityException e) { + log.error(e.getMessage(), e); + return RPC.encodeResponseForFailure(null, e); + } catch (NoSuchMethodException e) { + log.error(e.getMessage(), e); + return RPC.encodeResponseForFailure(null, e); } - } catch (ClassNotFoundException e) - { - throw new IncompatibleRemoteServiceException( - "Could not locate requested interface '" + serviceIntfName - + "' in default classloader", e); - } + } - String serviceMethodName = streamReader.readString(); + @SuppressWarnings("unchecked") + private Component getRemoteServiceComponent(String payload) + throws SerializationException { - int paramCount = streamReader.readInt(); - Class[] parameterTypes = new Class[paramCount]; + ClassLoader classLoader = Thread.currentThread() + .getContextClassLoader(); + ServerSerializationStreamReader streamReader + = new ServerSerializationStreamReader(classLoader, this); - for (int i = 0; i < parameterTypes.length; i++) - { - String paramClassName = streamReader.readString(); - try - { - parameterTypes[i] = RPC_getClassFromSerializedName( - paramClassName, classLoader); - } catch (ClassNotFoundException e) - { - throw new IncompatibleRemoteServiceException("Parameter " + i - + " of is of an unknown type '" + paramClassName + "'", e); - } - } + streamReader.prepareToRead(payload); - try - { - Method method = serviceIntf.getMethod(serviceMethodName, - parameterTypes); + // Read the name of the RemoteService interface + String serviceIntfName = streamReader.readString(); - Object[] parameterValues = new Object[parameterTypes.length]; - for (int i = 0; i < parameterValues.length; i++) - { - parameterValues[i] = streamReader - .deserializeValue(parameterTypes[i]); + Component component = Component.forName(serviceIntfName); + if (null == component) { + throw new RuntimeException("No such component: " + + serviceIntfName); } - return new SeamRPCRequest(method, parameterValues, parameterTypes, - serializationPolicy); + if (component.getType().isSessionBean() + && component.getBusinessInterfaces().size() > 0) { - } catch (NoSuchMethodException e) - { - throw new IncompatibleRemoteServiceException( - formatMethodNotFoundErrorMessage(serviceIntf, - serviceMethodName, parameterTypes)); - } - } catch (SerializationException ex) - { - throw new IncompatibleRemoteServiceException(ex.getMessage(), ex); - } - } + boolean localDefined = false; + for (Class c : component.getBusinessInterfaces()) { + if (c.isAnnotationPresent(EJB.LOCAL)) { + localDefined = true; + break; + } + } - /** - * Returns the {@link Class} instance for the named class or primitive type. - * - * @param serializedName - * the serialized name of a class or primitive type - * @param classLoader - * the classLoader used to load {@link Class}es - * @return Class instance for the given type name - * @throws ClassNotFoundException - * if the named type was not found - */ - private static Class RPC_getClassFromSerializedName( - String serializedName, ClassLoader classLoader) - throws ClassNotFoundException - { - Class value = TYPE_NAMES.get(serializedName); - if (value != null) - { - return value; - } - - return Class.forName(serializedName, false, classLoader); - } - - /** - * Returns a string that encodes the result of calling a service method, - * which could be the value returned by the method or an exception thrown by - * it. - * - *

- * If the serializationPolicy parameter is not null, it is used - * to determine what types can be encoded as part of this response. If this - * parameter is null, then only subtypes of - * {@link com.google.gwt.user.client.rpc.IsSerializable IsSerializable} or - * types which have custom field serializers may be encoded. - *

- * - *

- * This method does no security checking; security checking must be done on - * the method prior to this invocation. - *

- * - * @param target - * instance on which to invoke the serviceMethod - * @param serviceMethod - * the method to invoke - * @param args - * arguments used for the method invocation - * @param serializationPolicy - * determines the serialization policy to be used - * @return a string which encodes either the method's return or a checked - * exception thrown by the method - * - * @throws NullPointerException - * if the serviceMethod or the serializationPolicy are - * null - * @throws SecurityException - * if the method cannot be accessed or if the number or type of - * actual and formal arguments differ - * @throws SerializationException - * if an object could not be serialized by the stream - * @throws UnexpectedException - * if the serviceMethod throws a checked exception that is not - * declared in its signature - */ - public static String RPC_invokeAndEncodeResponse(Object target, - Method serviceMethod, Class[] paramTypes, Object[] args, - SerializationPolicy serializationPolicy) throws SerializationException - { - if (serviceMethod == null) - { - throw new NullPointerException("serviceMethod"); - } - - if (serializationPolicy == null) - { - throw new NullPointerException("serializationPolicy"); - } - - String responsePayload; - try - { - GWTToSeamAdapter adapter = GWTToSeamAdapter.instance(); - - String serviceIntfName = serviceMethod.getDeclaringClass().getName(); - - GWTToSeamAdapter.ReturnedObject returnedObject = adapter - .callWebRemoteMethod(serviceIntfName, serviceMethod.getName(), - paramTypes, args); - - // Object result = serviceMethod.invoke(target, args); - - responsePayload = RPC.encodeResponseForSuccess(serviceMethod, - returnedObject.returnedObject, serializationPolicy); - } catch (IllegalAccessException e) - { - SecurityException securityException = new SecurityException( - formatIllegalAccessErrorMessage(target, serviceMethod)); - securityException.initCause(e); - throw securityException; - } catch (IllegalArgumentException e) - { - SecurityException securityException = new SecurityException( - formatIllegalArgumentErrorMessage(target, serviceMethod, args)); - securityException.initCause(e); - throw securityException; - } catch (InvocationTargetException e) - { - // Try to encode the caught exception - // - Throwable cause = e.getCause(); - - responsePayload = RPC.encodeResponseForFailure(serviceMethod, cause, - serializationPolicy); - } - - return responsePayload; - } - - /** - * Override this method to examine the serialized response that will be - * returned to the client. The default implementation does nothing and need - * not be called by subclasses. - */ - protected void RemoteServiceServlet_onAfterResponseSerialized( - String serializedResponse) - { - } - - /** - * Override this method to examine the serialized version of the request - * payload before it is deserialized into objects. The default implementation - * does nothing and need not be called by subclasses. - */ - protected void RemoteServiceServlet_onBeforeRequestDeserialized( - String serializedRequest) - { - } - - /** - * Override this method in order to control the parsing of the incoming - * request. For example, you may want to bypass the check of the Content-Type - * and character encoding headers in the request, as some proxies re-write - * the request headers. Note that bypassing these checks may expose the - * servlet to some cross-site vulnerabilities. - * - * @param request - * the incoming request - * @return the content of the incoming request encoded as a string. - */ - protected String RemoteServiceServlet_readContent(HttpServletRequest request) - throws ServletException, IOException - { - return RPCServletUtils.readContentAsUtf8(request, true); - } - - public final SerializationPolicy getSerializationPolicy( - String moduleBaseURL, String strongName) - { - - SerializationPolicy serializationPolicy = getCachedSerializationPolicy( - moduleBaseURL, strongName); - if (serializationPolicy != null) - { - return serializationPolicy; - } - - serializationPolicy = doGetSerializationPolicy(getThreadLocalRequest(), - moduleBaseURL, strongName); - - if (serializationPolicy == null) - { - // Failed to get the requested serialization policy; use the default - getServletContext() - .log( - "WARNING: Failed to get the SerializationPolicy '" - + strongName - + "' for module '" - + moduleBaseURL - + "'; a legacy, 1.3.3 compatible, serialization policy will be used. You may experience SerializationExceptions as a result."); - serializationPolicy = RPC.getDefaultSerializationPolicy(); - } - - // This could cache null or an actual instance. Either way we will not - // attempt to lookup the policy again. - putCachedSerializationPolicy(moduleBaseURL, strongName, - serializationPolicy); - - return serializationPolicy; - } - - private SerializationPolicy getCachedSerializationPolicy( - String moduleBaseURL, String strongName) - { - synchronized (serializationPolicyCache) - { - return serializationPolicyCache.get(moduleBaseURL + strongName); - } - } - - private void putCachedSerializationPolicy(String moduleBaseURL, - String strongName, SerializationPolicy serializationPolicy) - { - synchronized (serializationPolicyCache) - { - serializationPolicyCache.put(moduleBaseURL + strongName, - serializationPolicy); - } - } - - /** - * Gets the {@link SerializationPolicy} for given module base URL and strong - * name if there is one. - * - * Override this method to provide a {@link SerializationPolicy} using an - * alternative approach. - * - * @param request - * the HTTP request being serviced - * @param moduleBaseURL - * as specified in the incoming payload - * @param strongName - * a strong name that uniquely identifies a serialization policy - * file - * @return a {@link SerializationPolicy} for the given module base URL and - * strong name, or null if there is none - */ - protected SerializationPolicy doGetSerializationPolicy( - HttpServletRequest request, String moduleBaseURL, String strongName) - { - // The request can tell you the path of the web app relative to the - // container root. - String contextPath = request.getContextPath(); - - String modulePath = null; - if (moduleBaseURL != null) - { - try - { - modulePath = new URL(moduleBaseURL).getPath(); - } catch (MalformedURLException ex) - { - // log the information, we will default - getServletContext().log( - "Malformed moduleBaseURL: " + moduleBaseURL, ex); - } - } - - SerializationPolicy serializationPolicy = null; - - /* - * Check that the module path must be in the same web app as the servlet - * itself. If you need to implement a scheme different than this, override - * this method. - */ - if (modulePath == null || !modulePath.startsWith(contextPath)) - { - String message = "ERROR: The module path requested, " - + modulePath - + ", is not in the same web application as this servlet, " - + contextPath - + ". Your module may not be properly configured or your client and server code maybe out of date."; - getServletContext().log(message); - } else - { - // Strip off the context path from the module base URL. It should be a - // strict prefix. - String contextRelativePath = modulePath - .substring(contextPath.length()); - - String serializationPolicyFilePath = SerializationPolicyLoader - .getSerializationPolicyFileName(contextRelativePath + strongName); - - // Open the RPC resource file read its contents. - InputStream is = getServletContext().getResourceAsStream( - serializationPolicyFilePath); - try - { - if (is != null) - { - try - { - serializationPolicy = SerializationPolicyLoader - .loadFromStream(is, null); - } catch (ParseException e) - { - getServletContext().log( - "ERROR: Failed to parse the policy file '" - + serializationPolicyFilePath + "'", e); - } catch (IOException e) - { - getServletContext().log( - "ERROR: Could not read the policy file '" - + serializationPolicyFilePath + "'", e); - } - } else - { - String message = "ERROR: The serialization policy file '" - + serializationPolicyFilePath - + "' was not found; did you forget to include it in this deployment?"; - getServletContext().log(message); + if (localDefined == false) { + throw new RuntimeException( + String.format("Type cannot be determined for component [%s]. Please ensure that it has a local interface.", + component)); + } } - } finally - { - if (is != null) - { - try - { - is.close(); - } catch (IOException e) - { - // Ignore this error - } - } - } - } + + return component; + } - return serializationPolicy; - } - - private void RemoteServiceServlet_writeResponse(HttpServletRequest request, - HttpServletResponse response, String responsePayload) - throws IOException - { - boolean gzipEncode = RPCServletUtils.acceptsGzipEncoding(request) - && shouldCompressResponse(request, response, responsePayload); - - RPCServletUtils.writeResponse(getServletContext(), response, - responsePayload, gzipEncode); - } - - /** - * Override this method to control what should happen when an exception - * escapes the {@link #processCall(String)} method. The default - * implementation will log the failure and send a generic failure response to - * the client. - *

- * - * An "expected failure" is an exception thrown by a service method that is - * declared in the signature of the service method. These exceptions are - * serialized back to the client, and are not passed to this method. This - * method is called only for exceptions or errors that are not part of the - * service method's signature, or that result from SecurityExceptions, - * SerializationExceptions, or other failures within the RPC framework. - *

- * - * Note that if the desired behavior is to both send the GENERIC_FAILURE_MSG - * response AND to rethrow the exception, then this method should first send - * the GENERIC_FAILURE_MSG response itself (using getThreadLocalResponse), - * and then rethrow the exception. Rethrowing the exception will cause it to - * escape into the servlet container. - * - * @param e - * the exception which was thrown - */ - protected void RemoteServiceServlet_doUnexpectedFailure(Throwable e) - { - ServletContext servletContext = getServletContext(); - RPCServletUtils.writeResponseForUnexpectedFailure(servletContext, - getThreadLocalResponse(), e); - } - - /** - * Determines whether the response to a given servlet request should or - * should not be GZIP compressed. This method is only called in cases where - * the requester accepts GZIP encoding. - *

- * This implementation currently returns true if the response - * string's estimated byte length is longer than 256 bytes. Subclasses can - * override this logic. - *

- * - * @param request - * the request being served - * @param response - * the response that will be written into - * @param responsePayload - * the payload that is about to be sent to the client - * @return true if responsePayload should be GZIP compressed, - * otherwise false. - */ - protected boolean shouldCompressResponse(HttpServletRequest request, - HttpServletResponse response, String responsePayload) - { - return RPCServletUtils - .exceedsUncompressedContentLengthLimit(responsePayload); - } - - private static String formatMethodNotFoundErrorMessage(Class serviceIntf, - String serviceMethodName, Class[] parameterTypes) - { - StringBuffer sb = new StringBuffer(); - - sb.append("Could not locate requested method '"); - sb.append(serviceMethodName); - sb.append("("); - for (int i = 0; i < parameterTypes.length; ++i) - { - if (i > 0) - { - sb.append(", "); - } - sb.append(printTypeName(parameterTypes[i])); - } - sb.append(")'"); - - sb.append(" in interface '"); - sb.append(printTypeName(serviceIntf)); - sb.append("'"); - - return sb.toString(); - } - - private static String formatIllegalAccessErrorMessage(Object target, - Method serviceMethod) - { - StringBuffer sb = new StringBuffer(); - sb.append("Blocked attempt to access inaccessible method '"); - sb.append(getSourceRepresentation(serviceMethod)); - sb.append("'"); - - if (target != null) - { - sb.append(" on target '"); - sb.append(printTypeName(target.getClass())); - sb.append("'"); - } - - sb.append("; this is either misconfiguration or a hack attempt"); - - return sb.toString(); - } - - private static String formatIllegalArgumentErrorMessage(Object target, - Method serviceMethod, Object[] args) - { - StringBuffer sb = new StringBuffer(); - sb.append("Blocked attempt to invoke method '"); - sb.append(getSourceRepresentation(serviceMethod)); - sb.append("'"); - - if (target != null) - { - sb.append(" on target '"); - sb.append(printTypeName(target.getClass())); - sb.append("'"); - } - - sb.append(" with invalid arguments"); - - if (args != null && args.length > 0) - { - sb.append(Arrays.asList(args)); - } - - return sb.toString(); - } - - /** - * Returns the source representation for a method signature. - * - * @param method - * method to get the source signature for - * @return source representation for a method signature - */ - private static String getSourceRepresentation(Method method) - { - return method.toString().replace('$', '.'); - } - - /** - * Straight copy from - * {@link com.google.gwt.dev.util.TypeInfo#getSourceRepresentation(Class)} to - * avoid runtime dependency on gwt-dev. - */ - private static String printTypeName(Class type) - { - // Primitives - // - if (type.equals(Integer.TYPE)) - { - return "int"; - } else if (type.equals(Long.TYPE)) - { - return "long"; - } else if (type.equals(Short.TYPE)) - { - return "short"; - } else if (type.equals(Byte.TYPE)) - { - return "byte"; - } else if (type.equals(Character.TYPE)) - { - return "char"; - } else if (type.equals(Boolean.TYPE)) - { - return "boolean"; - } else if (type.equals(Float.TYPE)) - { - return "float"; - } else if (type.equals(Double.TYPE)) - { - return "double"; - } - - // Arrays - // - if (type.isArray()) - { - Class componentType = type.getComponentType(); - return printTypeName(componentType) + "[]"; - } - - // Everything else - // - return type.getName().replace('$', '.'); - } - -} + /** + * Only allow methods annotated with @WebRemote for security reasons. + */ + private boolean isWebRemoteAnnotated(Method method) { + if (method == null) + return false; + return method.getAnnotation(WebRemote.class) != null; + } + } +} \ No newline at end of file Index: src/remoting/org/jboss/seam/remoting/gwt/GWTToSeamAdapter.java =================================================================== --- src/remoting/org/jboss/seam/remoting/gwt/GWTToSeamAdapter.java (revision 9989) +++ src/remoting/org/jboss/seam/remoting/gwt/GWTToSeamAdapter.java (working copy) @@ -1,210 +0,0 @@ -package org.jboss.seam.remoting.gwt; - -import static org.jboss.seam.ScopeType.APPLICATION; -import static org.jboss.seam.annotations.Install.BUILT_IN; - -import java.lang.reflect.InvocationTargetException; -import java.lang.reflect.Method; -import java.util.HashMap; -import java.util.Map; - -import org.jboss.seam.Component; -import org.jboss.seam.annotations.Install; -import org.jboss.seam.annotations.Name; -import org.jboss.seam.annotations.Scope; -import org.jboss.seam.annotations.intercept.BypassInterceptors; -import org.jboss.seam.annotations.remoting.WebRemote; -import org.jboss.seam.util.EJB; - -/** - * This class adapts GWT RPC mechanism to Seam actions. - * - * @author Michael Neale - */ - at Scope(APPLICATION) - at Name("org.jboss.seam.remoting.gwt.gwtToSeamAdapter") - at BypassInterceptors - at Install(precedence=BUILT_IN) -public class GWTToSeamAdapter { - - /** A very simple cache of previously looked up methods */ - private final Map METHOD_CACHE = new HashMap(); - - public static GWTToSeamAdapter instance() - { - GWTToSeamAdapter adapter = (GWTToSeamAdapter) Component.getInstance(GWTToSeamAdapter.class); - - if (adapter == null) - { - throw new IllegalStateException("No GWTToSeamAdapter exists"); - } - - return adapter; - } - - /** - * Call the service. - * - * @param serviceIntfName - * The interface name - this will be the fully qualified name of - * the remote service interface as understood by GWT. This - * correlates to a component name in seam. - * @param methodName - * The method name of the service being invoked. - * @param paramTypes - * The types of parameters - needed for method lookup for - * polymorphism. - * @param args - * The values to be passed to the service method. - * @return A populated ReturnedObject - the returned object payload may be - * null, but the type will not be. - * @throws InvocationTargetException - * @throws IllegalAccessException - */ - public ReturnedObject callWebRemoteMethod(String serviceIntfName, - String methodName, Class[] paramTypes, Object[] args) - throws InvocationTargetException, IllegalAccessException, - SecurityException { - - // Find the component we're calling - Component component = Component.forName(serviceIntfName); - - if (component == null) - throw new RuntimeException("No such component: " + serviceIntfName); - - Object instance = getServiceComponent(serviceIntfName); - Class clz = null; - - if (component.getType().isSessionBean() - && component.getBusinessInterfaces().size() > 0) { - for (Class c : component.getBusinessInterfaces()) { - if (c.isAnnotationPresent(EJB.LOCAL)) { - clz = c; - break; - } - } - - if (clz == null) - throw new RuntimeException( - String - .format( - "Type cannot be determined for component [%s]. Please ensure that it has a local interface.", - component)); - } - - if (clz == null) - clz = component.getBeanClass(); - - Method method = getMethod(serviceIntfName, methodName, clz, paramTypes); - - Object result = method.invoke(instance, args); - return new ReturnedObject(method.getReturnType(), result); - } - - /** - * Get the method on the class, including walking up the class heirarchy if - * needed. Methods have to be marked as "@WebRemote" to be allowed. - * - * @param methodName - * @param clz - * @param paramTypes - */ - private Method getMethod(String serviceName, String methodName, Class clz, - Class[] paramTypes) { - String key = getKey(serviceName, methodName, paramTypes); - if (METHOD_CACHE.containsKey(key)) { - return (Method) METHOD_CACHE.get(key); - } else { - try { - synchronized (METHOD_CACHE) { - Method m = findMethod(clz, methodName, paramTypes); - if (m == null) - throw new NoSuchMethodException(); - METHOD_CACHE.put(key, m); - return m; - } - - } catch (NoSuchMethodException e) { - throw new SecurityException( - "Unable to access a service method called [" - + methodName - + "] on class [" - + clz.getName() - + "] without the @WebRemote attribute. " - + "This may be a hack attempt, or someone simply neglected to use the @WebRemote attribute to indicate a method as" - + " remotely accessible."); - } - } - } - - private String getKey(String serviceName, String methodName, - Class[] paramTypes) { - if (paramTypes == null) { - return serviceName + "." + methodName; - } else { - String pTypes = ""; - for (int i = 0; i < paramTypes.length; i++) { - pTypes += paramTypes[i].getName(); - } - return serviceName + "." + methodName + "(" + pTypes + ")"; - } - - } - - /** - * Recurse up the class hierarchy, looking for a compatable method that is - * marked as "@WebRemote". If one is not found (or we hit Object.class) then - * we barf - basically trust nothing from the client other then what we want - * to allow them to call. - */ - private Method findMethod(Class clz, String methodName, Class[] paramTypes) - throws NoSuchMethodException { - if (clz == Object.class) { - return null; - } else { - Method m = clz.getMethod(methodName, paramTypes); - if (isWebRemoteAnnotated(m)) { - return m; - } else { - return findMethod(clz.getSuperclass(), methodName, paramTypes); - } - } - } - - /** - * Only allow methods annotated with - * - * @WebRemote for security reasons. - */ - private boolean isWebRemoteAnnotated(Method method) { - if (method == null) - return false; - return method.getAnnotation(WebRemote.class) != null; - } - - /** - * Return the service component that has been bound to the given name. - */ - protected Object getServiceComponent(String serviceIntfName) { - return Component.getInstance(serviceIntfName); - } - - /** - * This is used for returning results to the GWT service endpoint. The class - * is needed even if the result is null. a void.class responseType is - * perfectly acceptable. - * - * @author Michael Neale - */ - static class ReturnedObject { - public ReturnedObject(Class type, Object result) { - this.returnType = type; - this.returnedObject = result; - } - - public Class returnType; - - public Object returnedObject; - } - -} Index: src/remoting/org/jboss/seam/remoting/gwt/SeamRPCRequest.java =================================================================== --- src/remoting/org/jboss/seam/remoting/gwt/SeamRPCRequest.java (revision 9989) +++ src/remoting/org/jboss/seam/remoting/gwt/SeamRPCRequest.java (working copy) @@ -1,47 +0,0 @@ -package org.jboss.seam.remoting.gwt; - -import com.google.gwt.user.server.rpc.SerializationPolicy; - -import java.lang.reflect.Method; - -/** - * @author Tomaz Cerar - * @version $Revision$ - * @modifiedBy $Author$ - * @modified $Date$ - */ -public class SeamRPCRequest -{ - private final java.lang.reflect.Method method; - private final java.lang.Object[] parameters; - private final Class[] parameterTypes; - private final com.google.gwt.user.server.rpc.SerializationPolicy serializationPolicy; - - public SeamRPCRequest(Method method, Object[] parameters, - Class[] parameterTypes, SerializationPolicy serializationPolicy) { - this.method = method; - this.parameters = parameters; - this.parameterTypes = parameterTypes; - this.serializationPolicy = serializationPolicy; - } - - public Method getMethod() - { - return method; - } - - public Object[] getParameters() - { - return parameters; - } - - public Class[] getParameterTypes() - { - return parameterTypes; - } - - public SerializationPolicy getSerializationPolicy() - { - return serializationPolicy; - } -} Index: src/remoting/org/jboss/seam/remoting/gwt/GWT14Service.java =================================================================== --- src/remoting/org/jboss/seam/remoting/gwt/GWT14Service.java (revision 9989) +++ src/remoting/org/jboss/seam/remoting/gwt/GWT14Service.java (working copy) @@ -1,113 +0,0 @@ -package org.jboss.seam.remoting.gwt; - -import static org.jboss.seam.ScopeType.APPLICATION; -import static org.jboss.seam.annotations.Install.BUILT_IN; - -import java.lang.reflect.Constructor; -import java.lang.reflect.Method; - -import org.jboss.seam.annotations.Create; -import org.jboss.seam.annotations.Install; -import org.jboss.seam.annotations.Name; -import org.jboss.seam.annotations.Scope; -import org.jboss.seam.annotations.intercept.BypassInterceptors; - -import com.google.gwt.user.client.rpc.SerializationException; -import com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader; -import com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter; - -/** - * - * @author Shane Bryzak - */ - at Scope(APPLICATION) - at Name("org.jboss.seam.remoting.gwt.gwtRemoteService") - at Install(precedence = BUILT_IN, classDependencies = {"com.google.gwt.user.client.rpc.RemoteService"}) - at BypassInterceptors -public class GWT14Service extends GWTService -{ - private static final String SERIALIZATION_POLICY_PROVIDER_CLASS = "com.google.gwt.user.server.rpc.SerializationPolicyProvider"; - - private static final String SERIALIZATION_POLICY_CLASS = "com.google.gwt.user.server.rpc.SerializationPolicy"; - private static final String LEGACY_SERIALIZATION_POLICY_CLASS = "com.google.gwt.user.server.rpc.impl.LegacySerializationPolicy"; - - - private Constructor streamReaderConstructor; - private Constructor streamWriterConstructor; - - private Object legacySerializationPolicy; - - @Create - public void startup() throws Exception - { - try - { - log.trace("GWT14Service starting up"); - - Class policyProviderClass = Class.forName(SERIALIZATION_POLICY_PROVIDER_CLASS); - Class serializationPolicyClass = Class.forName(SERIALIZATION_POLICY_CLASS); - - streamReaderConstructor = ServerSerializationStreamReader.class.getConstructor( - new Class[] { ClassLoader.class, policyProviderClass } ); - streamWriterConstructor = ServerSerializationStreamWriter.class.getConstructor( - new Class[] { serializationPolicyClass } ); - - Class legacySerializationPolicyClass = Class.forName(LEGACY_SERIALIZATION_POLICY_CLASS); - Method m = legacySerializationPolicyClass.getDeclaredMethod("getInstance"); - legacySerializationPolicy = m.invoke(null); - } - catch (Exception ex) - { - log.error("Error initializing GWT14Service. Please ensure " + - "the GWT 1.4 libraries are in the classpath."); - throw ex; - } - } - - @Override - protected String createResponse(ServerSerializationStreamWriter stream, - Class responseType, Object responseObj, boolean isException) - { - stream.prepareToWrite(); - if (responseType != void.class) - { - try - { - stream.serializeValue(responseObj, responseType); - } catch (SerializationException e) - { - responseObj = e; - isException = true; - } - } - - return (isException ? "//EX" : "//OK") + stream.toString(); - } - - @Override - public ServerSerializationStreamReader getStreamReader() - { - try - { - return (ServerSerializationStreamReader) streamReaderConstructor.newInstance( - Thread.currentThread().getContextClassLoader(), null); - } - catch (Exception ex) - { - throw new RuntimeException("Unable to create stream reader", ex); - } - } - - @Override - public ServerSerializationStreamWriter getStreamWriter() - { - try - { - return (ServerSerializationStreamWriter) streamWriterConstructor.newInstance(legacySerializationPolicy); - } - catch (Exception ex) - { - throw new RuntimeException("Unable to create stream writer", ex); - } - } -} -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 30 19:57:44 2009 From: jira-events at lists.jboss.org (Nicolae Tabusca (JIRA)) Date: Fri, 30 Jan 2009 19:57:44 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3924) This patch adds full integration of seam with gwt 1.5. In-Reply-To: <3370166.1233363104171.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <2138888.1233363464183.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolae Tabusca updated JBSEAM-3924: ------------------------------------ Attachment: GWTService.java New GWTService implementation > This patch adds full integration of seam with gwt 1.5. > ------------------------------------------------------ > > Key: JBSEAM-3924 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3924 > Project: Seam > Issue Type: Patch > Components: GWT > Affects Versions: 2.1.1.GA > Environment: Any > Reporter: Nicolae Tabusca > Priority: Critical > Fix For: 2.1.2.GA > > Attachments: GWTService.java > > > ### Eclipse Workspace Patch 1.0 > #P jboss-seam > Index: src/remoting/org/jboss/seam/remoting/gwt/GWTService.java > =================================================================== > --- src/remoting/org/jboss/seam/remoting/gwt/GWTService.java (revision 9989) > +++ src/remoting/org/jboss/seam/remoting/gwt/GWTService.java (working copy) > @@ -1,976 +1,178 @@ > package org.jboss.seam.remoting.gwt; > > +import static org.jboss.seam.ScopeType.APPLICATION; > +import static org.jboss.seam.annotations.Install.BUILT_IN; > + > import java.io.IOException; > -import java.io.InputStream; > -import java.lang.reflect.InvocationTargetException; > import java.lang.reflect.Method; > -import java.net.MalformedURLException; > -import java.net.URL; > -import java.text.ParseException; > -import java.util.Arrays; > -import java.util.HashMap; > -import java.util.Map; > > import javax.servlet.ServletContext; > import javax.servlet.ServletException; > import javax.servlet.http.HttpServletRequest; > import javax.servlet.http.HttpServletResponse; > > -import org.jboss.seam.core.ConversationPropagation; > +import org.jboss.seam.Component; > +import org.jboss.seam.annotations.Install; > +import org.jboss.seam.annotations.Name; > +import org.jboss.seam.annotations.Scope; > +import org.jboss.seam.annotations.intercept.BypassInterceptors; > +import org.jboss.seam.annotations.remoting.WebRemote; > +import org.jboss.seam.contexts.ServletLifecycle; > import org.jboss.seam.log.LogProvider; > import org.jboss.seam.log.Logging; > import org.jboss.seam.servlet.ContextualHttpServletRequest; > +import org.jboss.seam.util.EJB; > import org.jboss.seam.web.AbstractResource; > > import com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException; > -import com.google.gwt.user.client.rpc.RemoteService; > import com.google.gwt.user.client.rpc.SerializationException; > import com.google.gwt.user.server.rpc.RPC; > import com.google.gwt.user.server.rpc.RPCRequest; > -import com.google.gwt.user.server.rpc.RPCServletUtils; > import com.google.gwt.user.server.rpc.RemoteServiceServlet; > -import com.google.gwt.user.server.rpc.SerializationPolicy; > -import com.google.gwt.user.server.rpc.SerializationPolicyLoader; > -import com.google.gwt.user.server.rpc.SerializationPolicyProvider; > -import com.google.gwt.user.server.rpc.UnexpectedException; > import com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader; > -import com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter; > > /** > - * Abstract base class for GWT 1.5 integration. > + * GWT integration. > * > - * @author Shane Bryzak > + * @author Nicolae Tabusca > */ > -public abstract class GWTService extends AbstractResource implements SerializationPolicyProvider > -{ > - protected static final LogProvider log = Logging.getLogProvider(GWTService.class); > + at Scope(APPLICATION) > + at Name("org.jboss.seam.remoting.gwt.gwtRemoteService") > + at Install(precedence = BUILT_IN, classDependencies = {"com.google.gwt.user.client.rpc.RemoteService"}) > + at BypassInterceptors > +public class GWTService extends AbstractResource { > + > + protected static final LogProvider log > + = Logging.getLogProvider(GWTService.class); > > - private static final HashMap> TYPE_NAMES; > + public GWTService() { > + } > > - static > - { > - TYPE_NAMES = new HashMap>(); > - TYPE_NAMES.put("Z", boolean.class); > - TYPE_NAMES.put("B", byte.class); > - TYPE_NAMES.put("C", char.class); > - TYPE_NAMES.put("D", double.class); > - TYPE_NAMES.put("F", float.class); > - TYPE_NAMES.put("I", int.class); > - TYPE_NAMES.put("J", long.class); > - TYPE_NAMES.put("S", short.class); > + @Override > + public String getResourcePath() { > + return "/gwt"; > + } > > - } > - > - /** > - * A cache of moduleBaseURL and serialization policy strong name to > - * {@link SerializationPolicy}. > - */ > - private final Map serializationPolicyCache = new HashMap(); > + /** > + * This is called internally. > + * > + * @see RemoteServiceServlet#doPost > + */ > + @Override > + public final void getResource(final HttpServletRequest request, > + final HttpServletResponse response) > + throws ServletException, IOException { > > - @Override > - public String getResourcePath() > - { > - return "/gwt"; > - } > + ContextualHttpServletRequest contextualRequest > + = new ContextualHttpServletRequest(request) { > > - protected abstract ServerSerializationStreamReader getStreamReader(); > + private GWTController controller = new GWTController(); > > - protected abstract ServerSerializationStreamWriter getStreamWriter(); > - > - protected abstract String createResponse( > - ServerSerializationStreamWriter stream, Class responseType, > - Object responseObj, boolean isException); > - > - // private final Set knownImplementedInterfaces = new HashSet(); > - private final ThreadLocal perThreadRequest = new ThreadLocal(); > - > - private final ThreadLocal perThreadResponse = new ThreadLocal(); > - > - /** > - * This is called internally. > - * > - * @see RemoteServiceServlet#doPost > - */ > - @Override > - public final void getResource(final HttpServletRequest request, > - final HttpServletResponse response) throws ServletException, > - IOException > - { > - try > - { > - // Store the request & response objects in thread-local storage. > - perThreadRequest.set(request); > - perThreadResponse.set(response); > - > - new ContextualHttpServletRequest(request) { > @Override > - public void process() throws Exception > - { > - > - try > - { > - // Read the request fully. > - // > - String requestPayload = RemoteServiceServlet_readContent(request); > - > - RemoteServiceServlet_onBeforeRequestDeserialized(requestPayload); > - > - // Invoke the core dispatching logic, which returns the > - // serialized result > - String responsePayload = processCall(requestPayload); > - > - RemoteServiceServlet_onAfterResponseSerialized(responsePayload); > - > - // Write the response. > - // > - RemoteServiceServlet_writeResponse(request, response, > - responsePayload); > - > - } catch (Throwable e) > - { > - RemoteServiceServlet_doUnexpectedFailure(e); > - } > - > + public void process() throws Exception { > + > + controller.service(request, response); > } > + }; > > - @Override > - protected void restoreConversationId() > - { > - ConversationPropagation.instance().setConversationId( > - GWTService.this.perThreadRequest.get().getParameter( > - "conversationId")); > - } > + contextualRequest.run(); > > - @Override > - protected void handleConversationPropagation() > - { > - } > - }.run(); > - } finally > - { > - perThreadRequest.remove(); > - perThreadResponse.remove(); > - } > - } > + } > > - /** > - * This is public so that it can be unit tested easily without HTTP. > - */ > - public String processCall(String payload) throws SerializationException > - { > - // Create a stream to deserialize the request. > - // > - // ServerSerializationStreamReader streamReader = getStreamReader(); > - // streamReader.prepareToRead(payload); > - // > - // // Read the service interface > - // // > - // String serviceIntfName = streamReader.readString(); > - // > - // // Read the method name. > - // // > - // String methodName = streamReader.readString(); > - // > - // // Read the number and names of the parameter classes from the stream. > - // // We have to do this so that we can find the correct overload of the > - // // method. > - // // > - // int paramCount = streamReader.readInt(); > - // Class[] paramTypes = new Class[paramCount]; > - // for (int i = 0; i < paramTypes.length; i++) > - // { > - // String paramClassName = streamReader.readString(); > - // try > - // { > - // paramTypes[i] = getClassOrPrimitiveFromName(paramClassName); > - // } catch (ClassNotFoundException e) > - // { > - // throw new SerializationException("Unknown parameter " + i > - // + " type '" + paramClassName + "'", e); > - // } > - // } > - // > - // // Deserialize the parameters. > - // // > - // Object[] args = new Object[paramCount]; > - // for (int i = 0; i < args.length; i++) > - // { > - // args[i] = streamReader.deserializeValue(paramTypes[i]); > - // } > + @SuppressWarnings("serial") > + private class GWTController extends RemoteServiceServlet { > > - try > - { > - SeamRPCRequest rpcRequest = RPC_decodeRequest(payload, > - this.getClass(), this); > + @Override > + public ServletContext getServletContext() { > + return ServletLifecycle.getServletContext(); > + } > + > + > + @Override > + @SuppressWarnings("unchecked") > + public String processCall(String payload) throws SerializationException { > + try { > + Component remoteService = getRemoteServiceComponent(payload); > + > + Class beanClass = remoteService.getBeanClass(); > + RPCRequest rpcRequest = RPC.decodeRequest(payload, beanClass, this); > > - return RPC_invokeAndEncodeResponse(this, rpcRequest.getMethod(), > - rpcRequest.getParameterTypes(), rpcRequest.getParameters(), > - rpcRequest.getSerializationPolicy()); > - } catch (IncompatibleRemoteServiceException ex) > - { > - getServletContext() > - .log( > - "An IncompatibleRemoteServiceException was thrown while processing this call.", > - ex); > - return RPC.encodeResponseForFailure(null, ex); > - } > + Method serviceDef = rpcRequest.getMethod(); > + Method serviceImpl = beanClass.getMethod(serviceDef.getName(), > + serviceDef.getParameterTypes()); > + if (isWebRemoteAnnotated(serviceImpl) == false) { > + throw new RuntimeException( > + "Unable to access a service method called [" > + + serviceImpl.getName() + "] on class [" > + + beanClass.getName() > + + "] without the @WebRemote attribute. "); > + } > > - // Make the call via reflection. > - // > - // String responsePayload = GENERIC_FAILURE_MSG; > - // ServerSerializationStreamWriter streamWriter = getStreamWriter(); > - // Throwable caught = null; > - // try > - // { > - // GWTToSeamAdapter.ReturnedObject returnedObject = > - // adapter.callWebRemoteMethod( > - // serviceIntfName, methodName, paramTypes, args); > - // Class returnType = returnedObject.returnType; > - // Object returnVal = returnedObject.returnedObject; > - // // Class returnType = serviceIntfMethod.getReturnType(); > - // // Object returnVal = serviceIntfMethod.invoke(this, args); > - // responsePayload = createResponse(streamWriter, returnType, returnVal, > - // false); > - // } catch (IllegalArgumentException e) > - // { > - // caught = e; > - // } catch (IllegalAccessException e) > - // { > - // caught = e; > - // } catch (InvocationTargetException e) > - // { > - // // Try to serialize the caught exception if the client is expecting it, > - // // otherwise log the exception server-side. > - // caught = e; > - // Throwable cause = e.getCause(); > - // if (cause != null) > - // { > - // // Update the caught exception to the underlying cause > - // caught = cause; > - // // Serialize the exception back to the client if it's a declared > - // // exception > - // if (cause instanceof SerializableException) > - // { > - // Class thrownClass = cause.getClass(); > - // responsePayload = createResponse(streamWriter, thrownClass, > - // cause, true); > - // // Don't log the exception on the server > - // caught = null; > - // } > - // } > - // } > - // > - // if (caught != null) > - // { > - // responsePayload = GENERIC_FAILURE_MSG; > - // ServletContext servletContext = getServletContext(); > - // // servletContext may be null (for example, when unit testing) > - // if (servletContext != null) > - // { > - // // Log the exception server side > - // servletContext.log("Exception while dispatching incoming RPC call", > - // caught); > - // } > - // } > - } > + return RPC.invokeAndEncodeResponse( > + Component.getInstance(remoteService.getName()), > + rpcRequest.getMethod(), rpcRequest.getParameters(), > + rpcRequest.getSerializationPolicy()); > > - /** > - * Gets the HttpServletRequest object for the current call. It > - * is stored thread-locally so that simultaneous invocations can have > - * different request objects. > - */ > - protected final HttpServletRequest getThreadLocalRequest() > - { > - return perThreadRequest.get(); > - } > - > - /** > - * Gets the HttpServletResponse object for the current call. It > - * is stored thread-locally so that simultaneous invocations can have > - * different response objects. > - */ > - protected final HttpServletResponse getThreadLocalResponse() > - { > - return perThreadResponse.get(); > - } > - > - /** > - * Returns an {@link RPCRequest} that is built by decoding the contents of an > - * encoded RPC request and optionally validating that type can handle the > - * request. If the type parameter is not null, the > - * implementation checks that the type is assignable to the > - * {@link com.google.gwt.user.client.rpc.RemoteService} interface requested > - * in the encoded request string. > - * > - *

> - * If the serializationPolicyProvider parameter is not null, it > - * is asked for a {@link SerializationPolicy} to use to restrict the set of > - * types that can be decoded from the request. If this parameter is > - * null, then only subtypes of > - * {@link com.google.gwt.user.client.rpc.IsSerializable IsSerializable} or > - * types which have custom field serializers can be decoded. > - *

> - * > - *

> - * Invoking this method with null for the type parameter, > - * decodeRequest(encodedRequest, null), is equivalent to calling > - * decodeRequest(encodedRequest). > - *

> - * > - * @param encodedRequest > - * a string that encodes the > - * {@link com.google.gwt.user.client.rpc.RemoteService} interface, > - * the service method, and the arguments to pass to the service > - * method > - * @param type > - * if not null, the implementation checks that the > - * type is assignable to the > - * {@link com.google.gwt.user.client.rpc.RemoteService} interface > - * encoded in the encoded request string. > - * @param serializationPolicyProvider > - * if not null, the implementation asks this provider > - * for a {@link SerializationPolicy} which will be used to restrict > - * the set of types that can be decoded from this request > - * @return an {@link RPCRequest} instance > - * > - * @throws NullPointerException > - * if the encodedRequest is null > - * @throws IllegalArgumentException > - * if the encodedRequest is an empty string > - * @throws IncompatibleRemoteServiceException > - * if any of the following conditions apply: > - *
    > - *
  • if the types in the encoded request cannot be deserialized
    • > - *
  • if the {@link ClassLoader} acquired from > - * Thread.currentThread().getContextClassLoader() > - * cannot load the service interface or any of the types specified > - * in the encodedRequest
    • > - *
  • the requested interface is not assignable to > - * {@link com.google.gwt.user.client.rpc.RemoteService}
    • > - *
  • the service method requested in the encodedRequest is not a > - * member of the requested service interface
    • > - *
  • the type parameter is not null and is not > - * assignable to the requested > - * {@link com.google.gwt.user.client.rpc.RemoteService} interface > - *
> - */ > - public static SeamRPCRequest RPC_decodeRequest(String encodedRequest, > - Class type, SerializationPolicyProvider serializationPolicyProvider) > - { > - if (encodedRequest == null) > - { > - throw new NullPointerException("encodedRequest cannot be null"); > - } > - > - if (encodedRequest.length() == 0) > - { > - throw new IllegalArgumentException("encodedRequest cannot be empty"); > - } > - > - ClassLoader classLoader = Thread.currentThread().getContextClassLoader(); > - > - try > - { > - ServerSerializationStreamReader streamReader = new ServerSerializationStreamReader( > - classLoader, serializationPolicyProvider); > - streamReader.prepareToRead(encodedRequest); > - > - // Read the name of the RemoteService interface > - String serviceIntfName = streamReader.readString(); > - > - /* > - * todo?? if (type != null) { if (!implementsInterface(type, > - * serviceIntfName)) { // The service does not implement the requested > - * interface throw new IncompatibleRemoteServiceException( > - * "Blocked attempt to access interface '" + serviceIntfName + > - * "', which is not implemented by '" + printTypeName(type) + > - * "'; this is either misconfiguration or a hack attempt"); } } > - */ > - > - SerializationPolicy serializationPolicy = streamReader > - .getSerializationPolicy(); > - Class serviceIntf; > - try > - { > - serviceIntf = RPC_getClassFromSerializedName(serviceIntfName, > - classLoader); > - if (!RemoteService.class.isAssignableFrom(serviceIntf)) > - { > - // The requested interface is not a RemoteService interface > - throw new IncompatibleRemoteServiceException( > - "Blocked attempt to access interface '" > - + printTypeName(serviceIntf) > - + "', which doesn't extend RemoteService; this is either misconfiguration or a hack attempt"); > + } catch (IncompatibleRemoteServiceException ex) { > + log.error(ex.getMessage(), ex); > + return RPC.encodeResponseForFailure(null, ex); > + } catch (SecurityException e) { > + log.error(e.getMessage(), e); > + return RPC.encodeResponseForFailure(null, e); > + } catch (NoSuchMethodException e) { > + log.error(e.getMessage(), e); > + return RPC.encodeResponseForFailure(null, e); > } > - } catch (ClassNotFoundException e) > - { > - throw new IncompatibleRemoteServiceException( > - "Could not locate requested interface '" + serviceIntfName > - + "' in default classloader", e); > - } > + } > > - String serviceMethodName = streamReader.readString(); > + @SuppressWarnings("unchecked") > + private Component getRemoteServiceComponent(String payload) > + throws SerializationException { > > - int paramCount = streamReader.readInt(); > - Class[] parameterTypes = new Class[paramCount]; > + ClassLoader classLoader = Thread.currentThread() > + .getContextClassLoader(); > + ServerSerializationStreamReader streamReader > + = new ServerSerializationStreamReader(classLoader, this); > > - for (int i = 0; i < parameterTypes.length; i++) > - { > - String paramClassName = streamReader.readString(); > - try > - { > - parameterTypes[i] = RPC_getClassFromSerializedName( > - paramClassName, classLoader); > - } catch (ClassNotFoundException e) > - { > - throw new IncompatibleRemoteServiceException("Parameter " + i > - + " of is of an unknown type '" + paramClassName + "'", e); > - } > - } > + streamReader.prepareToRead(payload); > > - try > - { > - Method method = serviceIntf.getMethod(serviceMethodName, > - parameterTypes); > + // Read the name of the RemoteService interface > + String serviceIntfName = streamReader.readString(); > > - Object[] parameterValues = new Object[parameterTypes.length]; > - for (int i = 0; i < parameterValues.length; i++) > - { > - parameterValues[i] = streamReader > - .deserializeValue(parameterTypes[i]); > + Component component = Component.forName(serviceIntfName); > + if (null == component) { > + throw new RuntimeException("No such component: " > + + serviceIntfName); > } > > - return new SeamRPCRequest(method, parameterValues, parameterTypes, > - serializationPolicy); > + if (component.getType().isSessionBean() > + && component.getBusinessInterfaces().size() > 0) { > > - } catch (NoSuchMethodException e) > - { > - throw new IncompatibleRemoteServiceException( > - formatMethodNotFoundErrorMessage(serviceIntf, > - serviceMethodName, parameterTypes)); > - } > - } catch (SerializationException ex) > - { > - throw new IncompatibleRemoteServiceException(ex.getMessage(), ex); > - } > - } > + boolean localDefined = false; > + for (Class c : component.getBusinessInterfaces()) { > + if (c.isAnnotationPresent(EJB.LOCAL)) { > + localDefined = true; > + break; > + } > + } > > - /** > - * Returns the {@link Class} instance for the named class or primitive type. > - * > - * @param serializedName > - * the serialized name of a class or primitive type > - * @param classLoader > - * the classLoader used to load {@link Class}es > - * @return Class instance for the given type name > - * @throws ClassNotFoundException > - * if the named type was not found > - */ > - private static Class RPC_getClassFromSerializedName( > - String serializedName, ClassLoader classLoader) > - throws ClassNotFoundException > - { > - Class value = TYPE_NAMES.get(serializedName); > - if (value != null) > - { > - return value; > - } > - > - return Class.forName(serializedName, false, classLoader); > - } > - > - /** > - * Returns a string that encodes the result of calling a service method, > - * which could be the value returned by the method or an exception thrown by > - * it. > - * > - *

> - * If the serializationPolicy parameter is not null, it is used > - * to determine what types can be encoded as part of this response. If this > - * parameter is null, then only subtypes of > - * {@link com.google.gwt.user.client.rpc.IsSerializable IsSerializable} or > - * types which have custom field serializers may be encoded. > - *

> - * > - *

> - * This method does no security checking; security checking must be done on > - * the method prior to this invocation. > - *

> - * > - * @param target > - * instance on which to invoke the serviceMethod > - * @param serviceMethod > - * the method to invoke > - * @param args > - * arguments used for the method invocation > - * @param serializationPolicy > - * determines the serialization policy to be used > - * @return a string which encodes either the method's return or a checked > - * exception thrown by the method > - * > - * @throws NullPointerException > - * if the serviceMethod or the serializationPolicy are > - * null > - * @throws SecurityException > - * if the method cannot be accessed or if the number or type of > - * actual and formal arguments differ > - * @throws SerializationException > - * if an object could not be serialized by the stream > - * @throws UnexpectedException > - * if the serviceMethod throws a checked exception that is not > - * declared in its signature > - */ > - public static String RPC_invokeAndEncodeResponse(Object target, > - Method serviceMethod, Class[] paramTypes, Object[] args, > - SerializationPolicy serializationPolicy) throws SerializationException > - { > - if (serviceMethod == null) > - { > - throw new NullPointerException("serviceMethod"); > - } > - > - if (serializationPolicy == null) > - { > - throw new NullPointerException("serializationPolicy"); > - } > - > - String responsePayload; > - try > - { > - GWTToSeamAdapter adapter = GWTToSeamAdapter.instance(); > - > - String serviceIntfName = serviceMethod.getDeclaringClass().getName(); > - > - GWTToSeamAdapter.ReturnedObject returnedObject = adapter > - .callWebRemoteMethod(serviceIntfName, serviceMethod.getName(), > - paramTypes, args); > - > - // Object result = serviceMethod.invoke(target, args); > - > - responsePayload = RPC.encodeResponseForSuccess(serviceMethod, > - returnedObject.returnedObject, serializationPolicy); > - } catch (IllegalAccessException e) > - { > - SecurityException securityException = new SecurityException( > - formatIllegalAccessErrorMessage(target, serviceMethod)); > - securityException.initCause(e); > - throw securityException; > - } catch (IllegalArgumentException e) > - { > - SecurityException securityException = new SecurityException( > - formatIllegalArgumentErrorMessage(target, serviceMethod, args)); > - securityException.initCause(e); > - throw securityException; > - } catch (InvocationTargetException e) > - { > - // Try to encode the caught exception > - // > - Throwable cause = e.getCause(); > - > - responsePayload = RPC.encodeResponseForFailure(serviceMethod, cause, > - serializationPolicy); > - } > - > - return responsePayload; > - } > - > - /** > - * Override this method to examine the serialized response that will be > - * returned to the client. The default implementation does nothing and need > - * not be called by subclasses. > - */ > - protected void RemoteServiceServlet_onAfterResponseSerialized( > - String serializedResponse) > - { > - } > - > - /** > - * Override this method to examine the serialized version of the request > - * payload before it is deserialized into objects. The default implementation > - * does nothing and need not be called by subclasses. > - */ > - protected void RemoteServiceServlet_onBeforeRequestDeserialized( > - String serializedRequest) > - { > - } > - > - /** > - * Override this method in order to control the parsing of the incoming > - * request. For example, you may want to bypass the check of the Content-Type > - * and character encoding headers in the request, as some proxies re-write > - * the request headers. Note that bypassing these checks may expose the > - * servlet to some cross-site vulnerabilities. > - * > - * @param request > - * the incoming request > - * @return the content of the incoming request encoded as a string. > - */ > - protected String RemoteServiceServlet_readContent(HttpServletRequest request) > - throws ServletException, IOException > - { > - return RPCServletUtils.readContentAsUtf8(request, true); > - } > - > - public final SerializationPolicy getSerializationPolicy( > - String moduleBaseURL, String strongName) > - { > - > - SerializationPolicy serializationPolicy = getCachedSerializationPolicy( > - moduleBaseURL, strongName); > - if (serializationPolicy != null) > - { > - return serializationPolicy; > - } > - > - serializationPolicy = doGetSerializationPolicy(getThreadLocalRequest(), > - moduleBaseURL, strongName); > - > - if (serializationPolicy == null) > - { > - // Failed to get the requested serialization policy; use the default > - getServletContext() > - .log( > - "WARNING: Failed to get the SerializationPolicy '" > - + strongName > - + "' for module '" > - + moduleBaseURL > - + "'; a legacy, 1.3.3 compatible, serialization policy will be used. You may experience SerializationExceptions as a result."); > - serializationPolicy = RPC.getDefaultSerializationPolicy(); > - } > - > - // This could cache null or an actual instance. Either way we will not > - // attempt to lookup the policy again. > - putCachedSerializationPolicy(moduleBaseURL, strongName, > - serializationPolicy); > - > - return serializationPolicy; > - } > - > - private SerializationPolicy getCachedSerializationPolicy( > - String moduleBaseURL, String strongName) > - { > - synchronized (serializationPolicyCache) > - { > - return serializationPolicyCache.get(moduleBaseURL + strongName); > - } > - } > - > - private void putCachedSerializationPolicy(String moduleBaseURL, > - String strongName, SerializationPolicy serializationPolicy) > - { > - synchronized (serializationPolicyCache) > - { > - serializationPolicyCache.put(moduleBaseURL + strongName, > - serializationPolicy); > - } > - } > - > - /** > - * Gets the {@link SerializationPolicy} for given module base URL and strong > - * name if there is one. > - * > - * Override this method to provide a {@link SerializationPolicy} using an > - * alternative approach. > - * > - * @param request > - * the HTTP request being serviced > - * @param moduleBaseURL > - * as specified in the incoming payload > - * @param strongName > - * a strong name that uniquely identifies a serialization policy > - * file > - * @return a {@link SerializationPolicy} for the given module base URL and > - * strong name, or null if there is none > - */ > - protected SerializationPolicy doGetSerializationPolicy( > - HttpServletRequest request, String moduleBaseURL, String strongName) > - { > - // The request can tell you the path of the web app relative to the > - // container root. > - String contextPath = request.getContextPath(); > - > - String modulePath = null; > - if (moduleBaseURL != null) > - { > - try > - { > - modulePath = new URL(moduleBaseURL).getPath(); > - } catch (MalformedURLException ex) > - { > - // log the information, we will default > - getServletContext().log( > - "Malformed moduleBaseURL: " + moduleBaseURL, ex); > - } > - } > - > - SerializationPolicy serializationPolicy = null; > - > - /* > - * Check that the module path must be in the same web app as the servlet > - * itself. If you need to implement a scheme different than this, override > - * this method. > - */ > - if (modulePath == null || !modulePath.startsWith(contextPath)) > - { > - String message = "ERROR: The module path requested, " > - + modulePath > - + ", is not in the same web application as this servlet, " > - + contextPath > - + ". Your module may not be properly configured or your client and server code maybe out of date."; > - getServletContext().log(message); > - } else > - { > - // Strip off the context path from the module base URL. It should be a > - // strict prefix. > - String contextRelativePath = modulePath > - .substring(contextPath.length()); > - > - String serializationPolicyFilePath = SerializationPolicyLoader > - .getSerializationPolicyFileName(contextRelativePath + strongName); > - > - // Open the RPC resource file read its contents. > - InputStream is = getServletContext().getResourceAsStream( > - serializationPolicyFilePath); > - try > - { > - if (is != null) > - { > - try > - { > - serializationPolicy = SerializationPolicyLoader > - .loadFromStream(is, null); > - } catch (ParseException e) > - { > - getServletContext().log( > - "ERROR: Failed to parse the policy file '" > - + serializationPolicyFilePath + "'", e); > - } catch (IOException e) > - { > - getServletContext().log( > - "ERROR: Could not read the policy file '" > - + serializationPolicyFilePath + "'", e); > - } > - } else > - { > - String message = "ERROR: The serialization policy file '" > - + serializationPolicyFilePath > - + "' was not found; did you forget to include it in this deployment?"; > - getServletContext().log(message); > + if (localDefined == false) { > + throw new RuntimeException( > + String.format("Type cannot be determined for component [%s]. Please ensure that it has a local interface.", > + component)); > + } > } > - } finally > - { > - if (is != null) > - { > - try > - { > - is.close(); > - } catch (IOException e) > - { > - // Ignore this error > - } > - } > - } > - } > + > + return component; > + } > > - return serializationPolicy; > - } > - > - private void RemoteServiceServlet_writeResponse(HttpServletRequest request, > - HttpServletResponse response, String responsePayload) > - throws IOException > - { > - boolean gzipEncode = RPCServletUtils.acceptsGzipEncoding(request) > - && shouldCompressResponse(request, response, responsePayload); > - > - RPCServletUtils.writeResponse(getServletContext(), response, > - responsePayload, gzipEncode); > - } > - > - /** > - * Override this method to control what should happen when an exception > - * escapes the {@link #processCall(String)} method. The default > - * implementation will log the failure and send a generic failure response to > - * the client. > - *

> - * > - * An "expected failure" is an exception thrown by a service method that is > - * declared in the signature of the service method. These exceptions are > - * serialized back to the client, and are not passed to this method. This > - * method is called only for exceptions or errors that are not part of the > - * service method's signature, or that result from SecurityExceptions, > - * SerializationExceptions, or other failures within the RPC framework. > - *

> - * > - * Note that if the desired behavior is to both send the GENERIC_FAILURE_MSG > - * response AND to rethrow the exception, then this method should first send > - * the GENERIC_FAILURE_MSG response itself (using getThreadLocalResponse), > - * and then rethrow the exception. Rethrowing the exception will cause it to > - * escape into the servlet container. > - * > - * @param e > - * the exception which was thrown > - */ > - protected void RemoteServiceServlet_doUnexpectedFailure(Throwable e) > - { > - ServletContext servletContext = getServletContext(); > - RPCServletUtils.writeResponseForUnexpectedFailure(servletContext, > - getThreadLocalResponse(), e); > - } > - > - /** > - * Determines whether the response to a given servlet request should or > - * should not be GZIP compressed. This method is only called in cases where > - * the requester accepts GZIP encoding. > - *

> - * This implementation currently returns true if the response > - * string's estimated byte length is longer than 256 bytes. Subclasses can > - * override this logic. > - *

> - * > - * @param request > - * the request being served > - * @param response > - * the response that will be written into > - * @param responsePayload > - * the payload that is about to be sent to the client > - * @return true if responsePayload should be GZIP compressed, > - * otherwise false. > - */ > - protected boolean shouldCompressResponse(HttpServletRequest request, > - HttpServletResponse response, String responsePayload) > - { > - return RPCServletUtils > - .exceedsUncompressedContentLengthLimit(responsePayload); > - } > - > - private static String formatMethodNotFoundErrorMessage(Class serviceIntf, > - String serviceMethodName, Class[] parameterTypes) > - { > - StringBuffer sb = new StringBuffer(); > - > - sb.append("Could not locate requested method '"); > - sb.append(serviceMethodName); > - sb.append("("); > - for (int i = 0; i < parameterTypes.length; ++i) > - { > - if (i > 0) > - { > - sb.append(", "); > - } > - sb.append(printTypeName(parameterTypes[i])); > - } > - sb.append(")'"); > - > - sb.append(" in interface '"); > - sb.append(printTypeName(serviceIntf)); > - sb.append("'"); > - > - return sb.toString(); > - } > - > - private static String formatIllegalAccessErrorMessage(Object target, > - Method serviceMethod) > - { > - StringBuffer sb = new StringBuffer(); > - sb.append("Blocked attempt to access inaccessible method '"); > - sb.append(getSourceRepresentation(serviceMethod)); > - sb.append("'"); > - > - if (target != null) > - { > - sb.append(" on target '"); > - sb.append(printTypeName(target.getClass())); > - sb.append("'"); > - } > - > - sb.append("; this is either misconfiguration or a hack attempt"); > - > - return sb.toString(); > - } > - > - private static String formatIllegalArgumentErrorMessage(Object target, > - Method serviceMethod, Object[] args) > - { > - StringBuffer sb = new StringBuffer(); > - sb.append("Blocked attempt to invoke method '"); > - sb.append(getSourceRepresentation(serviceMethod)); > - sb.append("'"); > - > - if (target != null) > - { > - sb.append(" on target '"); > - sb.append(printTypeName(target.getClass())); > - sb.append("'"); > - } > - > - sb.append(" with invalid arguments"); > - > - if (args != null && args.length > 0) > - { > - sb.append(Arrays.asList(args)); > - } > - > - return sb.toString(); > - } > - > - /** > - * Returns the source representation for a method signature. > - * > - * @param method > - * method to get the source signature for > - * @return source representation for a method signature > - */ > - private static String getSourceRepresentation(Method method) > - { > - return method.toString().replace('$', '.'); > - } > - > - /** > - * Straight copy from > - * {@link com.google.gwt.dev.util.TypeInfo#getSourceRepresentation(Class)} to > - * avoid runtime dependency on gwt-dev. > - */ > - private static String printTypeName(Class type) > - { > - // Primitives > - // > - if (type.equals(Integer.TYPE)) > - { > - return "int"; > - } else if (type.equals(Long.TYPE)) > - { > - return "long"; > - } else if (type.equals(Short.TYPE)) > - { > - return "short"; > - } else if (type.equals(Byte.TYPE)) > - { > - return "byte"; > - } else if (type.equals(Character.TYPE)) > - { > - return "char"; > - } else if (type.equals(Boolean.TYPE)) > - { > - return "boolean"; > - } else if (type.equals(Float.TYPE)) > - { > - return "float"; > - } else if (type.equals(Double.TYPE)) > - { > - return "double"; > - } > - > - // Arrays > - // > - if (type.isArray()) > - { > - Class componentType = type.getComponentType(); > - return printTypeName(componentType) + "[]"; > - } > - > - // Everything else > - // > - return type.getName().replace('$', '.'); > - } > - > -} > + /** > + * Only allow methods annotated with @WebRemote for security reasons. > + */ > + private boolean isWebRemoteAnnotated(Method method) { > + if (method == null) > + return false; > + return method.getAnnotation(WebRemote.class) != null; > + } > + } > +} > \ No newline at end of file > Index: src/remoting/org/jboss/seam/remoting/gwt/GWTToSeamAdapter.java > =================================================================== > --- src/remoting/org/jboss/seam/remoting/gwt/GWTToSeamAdapter.java (revision 9989) > +++ src/remoting/org/jboss/seam/remoting/gwt/GWTToSeamAdapter.java (working copy) > @@ -1,210 +0,0 @@ > -package org.jboss.seam.remoting.gwt; > - > -import static org.jboss.seam.ScopeType.APPLICATION; > -import static org.jboss.seam.annotations.Install.BUILT_IN; > - > -import java.lang.reflect.InvocationTargetException; > -import java.lang.reflect.Method; > -import java.util.HashMap; > -import java.util.Map; > - > -import org.jboss.seam.Component; > -import org.jboss.seam.annotations.Install; > -import org.jboss.seam.annotations.Name; > -import org.jboss.seam.annotations.Scope; > -import org.jboss.seam.annotations.intercept.BypassInterceptors; > -import org.jboss.seam.annotations.remoting.WebRemote; > -import org.jboss.seam.util.EJB; > - > -/** > - * This class adapts GWT RPC mechanism to Seam actions. > - * > - * @author Michael Neale > - */ > - at Scope(APPLICATION) > - at Name("org.jboss.seam.remoting.gwt.gwtToSeamAdapter") > - at BypassInterceptors > - at Install(precedence=BUILT_IN) > -public class GWTToSeamAdapter { > - > - /** A very simple cache of previously looked up methods */ > - private final Map METHOD_CACHE = new HashMap(); > - > - public static GWTToSeamAdapter instance() > - { > - GWTToSeamAdapter adapter = (GWTToSeamAdapter) Component.getInstance(GWTToSeamAdapter.class); > - > - if (adapter == null) > - { > - throw new IllegalStateException("No GWTToSeamAdapter exists"); > - } > - > - return adapter; > - } > - > - /** > - * Call the service. > - * > - * @param serviceIntfName > - * The interface name - this will be the fully qualified name of > - * the remote service interface as understood by GWT. This > - * correlates to a component name in seam. > - * @param methodName > - * The method name of the service being invoked. > - * @param paramTypes > - * The types of parameters - needed for method lookup for > - * polymorphism. > - * @param args > - * The values to be passed to the service method. > - * @return A populated ReturnedObject - the returned object payload may be > - * null, but the type will not be. > - * @throws InvocationTargetException > - * @throws IllegalAccessException > - */ > - public ReturnedObject callWebRemoteMethod(String serviceIntfName, > - String methodName, Class[] paramTypes, Object[] args) > - throws InvocationTargetException, IllegalAccessException, > - SecurityException { > - > - // Find the component we're calling > - Component component = Component.forName(serviceIntfName); > - > - if (component == null) > - throw new RuntimeException("No such component: " + serviceIntfName); > - > - Object instance = getServiceComponent(serviceIntfName); > - Class clz = null; > - > - if (component.getType().isSessionBean() > - && component.getBusinessInterfaces().size() > 0) { > - for (Class c : component.getBusinessInterfaces()) { > - if (c.isAnnotationPresent(EJB.LOCAL)) { > - clz = c; > - break; > - } > - } > - > - if (clz == null) > - throw new RuntimeException( > - String > - .format( > - "Type cannot be determined for component [%s]. Please ensure that it has a local interface.", > - component)); > - } > - > - if (clz == null) > - clz = component.getBeanClass(); > - > - Method method = getMethod(serviceIntfName, methodName, clz, paramTypes); > - > - Object result = method.invoke(instance, args); > - return new ReturnedObject(method.getReturnType(), result); > - } > - > - /** > - * Get the method on the class, including walking up the class heirarchy if > - * needed. Methods have to be marked as "@WebRemote" to be allowed. > - * > - * @param methodName > - * @param clz > - * @param paramTypes > - */ > - private Method getMethod(String serviceName, String methodName, Class clz, > - Class[] paramTypes) { > - String key = getKey(serviceName, methodName, paramTypes); > - if (METHOD_CACHE.containsKey(key)) { > - return (Method) METHOD_CACHE.get(key); > - } else { > - try { > - synchronized (METHOD_CACHE) { > - Method m = findMethod(clz, methodName, paramTypes); > - if (m == null) > - throw new NoSuchMethodException(); > - METHOD_CACHE.put(key, m); > - return m; > - } > - > - } catch (NoSuchMethodException e) { > - throw new SecurityException( > - "Unable to access a service method called [" > - + methodName > - + "] on class [" > - + clz.getName() > - + "] without the @WebRemote attribute. " > - + "This may be a hack attempt, or someone simply neglected to use the @WebRemote attribute to indicate a method as" > - + " remotely accessible."); > - } > - } > - } > - > - private String getKey(String serviceName, String methodName, > - Class[] paramTypes) { > - if (paramTypes == null) { > - return serviceName + "." + methodName; > - } else { > - String pTypes = ""; > - for (int i = 0; i < paramTypes.length; i++) { > - pTypes += paramTypes[i].getName(); > - } > - return serviceName + "." + methodName + "(" + pTypes + ")"; > - } > - > - } > - > - /** > - * Recurse up the class hierarchy, looking for a compatable method that is > - * marked as "@WebRemote". If one is not found (or we hit Object.class) then > - * we barf - basically trust nothing from the client other then what we want > - * to allow them to call. > - */ > - private Method findMethod(Class clz, String methodName, Class[] paramTypes) > - throws NoSuchMethodException { > - if (clz == Object.class) { > - return null; > - } else { > - Method m = clz.getMethod(methodName, paramTypes); > - if (isWebRemoteAnnotated(m)) { > - return m; > - } else { > - return findMethod(clz.getSuperclass(), methodName, paramTypes); > - } > - } > - } > - > - /** > - * Only allow methods annotated with > - * > - * @WebRemote for security reasons. > - */ > - private boolean isWebRemoteAnnotated(Method method) { > - if (method == null) > - return false; > - return method.getAnnotation(WebRemote.class) != null; > - } > - > - /** > - * Return the service component that has been bound to the given name. > - */ > - protected Object getServiceComponent(String serviceIntfName) { > - return Component.getInstance(serviceIntfName); > - } > - > - /** > - * This is used for returning results to the GWT service endpoint. The class > - * is needed even if the result is null. a void.class responseType is > - * perfectly acceptable. > - * > - * @author Michael Neale > - */ > - static class ReturnedObject { > - public ReturnedObject(Class type, Object result) { > - this.returnType = type; > - this.returnedObject = result; > - } > - > - public Class returnType; > - > - public Object returnedObject; > - } > - > -} > Index: src/remoting/org/jboss/seam/remoting/gwt/SeamRPCRequest.java > =================================================================== > --- src/remoting/org/jboss/seam/remoting/gwt/SeamRPCRequest.java (revision 9989) > +++ src/remoting/org/jboss/seam/remoting/gwt/SeamRPCRequest.java (working copy) > @@ -1,47 +0,0 @@ > -package org.jboss.seam.remoting.gwt; > - > -import com.google.gwt.user.server.rpc.SerializationPolicy; > - > -import java.lang.reflect.Method; > - > -/** > - * @author Tomaz Cerar > - * @version $Revision$ > - * @modifiedBy $Author$ > - * @modified $Date$ > - */ > -public class SeamRPCRequest > -{ > - private final java.lang.reflect.Method method; > - private final java.lang.Object[] parameters; > - private final Class[] parameterTypes; > - private final com.google.gwt.user.server.rpc.SerializationPolicy serializationPolicy; > - > - public SeamRPCRequest(Method method, Object[] parameters, > - Class[] parameterTypes, SerializationPolicy serializationPolicy) { > - this.method = method; > - this.parameters = parameters; > - this.parameterTypes = parameterTypes; > - this.serializationPolicy = serializationPolicy; > - } > - > - public Method getMethod() > - { > - return method; > - } > - > - public Object[] getParameters() > - { > - return parameters; > - } > - > - public Class[] getParameterTypes() > - { > - return parameterTypes; > - } > - > - public SerializationPolicy getSerializationPolicy() > - { > - return serializationPolicy; > - } > -} > Index: src/remoting/org/jboss/seam/remoting/gwt/GWT14Service.java > =================================================================== > --- src/remoting/org/jboss/seam/remoting/gwt/GWT14Service.java (revision 9989) > +++ src/remoting/org/jboss/seam/remoting/gwt/GWT14Service.java (working copy) > @@ -1,113 +0,0 @@ > -package org.jboss.seam.remoting.gwt; > - > -import static org.jboss.seam.ScopeType.APPLICATION; > -import static org.jboss.seam.annotations.Install.BUILT_IN; > - > -import java.lang.reflect.Constructor; > -import java.lang.reflect.Method; > - > -import org.jboss.seam.annotations.Create; > -import org.jboss.seam.annotations.Install; > -import org.jboss.seam.annotations.Name; > -import org.jboss.seam.annotations.Scope; > -import org.jboss.seam.annotations.intercept.BypassInterceptors; > - > -import com.google.gwt.user.client.rpc.SerializationException; > -import com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader; > -import com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter; > - > -/** > - * > - * @author Shane Bryzak > - */ > - at Scope(APPLICATION) > - at Name("org.jboss.seam.remoting.gwt.gwtRemoteService") > - at Install(precedence = BUILT_IN, classDependencies = {"com.google.gwt.user.client.rpc.RemoteService"}) > - at BypassInterceptors > -public class GWT14Service extends GWTService > -{ > - private static final String SERIALIZATION_POLICY_PROVIDER_CLASS = "com.google.gwt.user.server.rpc.SerializationPolicyProvider"; > - > - private static final String SERIALIZATION_POLICY_CLASS = "com.google.gwt.user.server.rpc.SerializationPolicy"; > - private static final String LEGACY_SERIALIZATION_POLICY_CLASS = "com.google.gwt.user.server.rpc.impl.LegacySerializationPolicy"; > - > - > - private Constructor streamReaderConstructor; > - private Constructor streamWriterConstructor; > - > - private Object legacySerializationPolicy; > - > - @Create > - public void startup() throws Exception > - { > - try > - { > - log.trace("GWT14Service starting up"); > - > - Class policyProviderClass = Class.forName(SERIALIZATION_POLICY_PROVIDER_CLASS); > - Class serializationPolicyClass = Class.forName(SERIALIZATION_POLICY_CLASS); > - > - streamReaderConstructor = ServerSerializationStreamReader.class.getConstructor( > - new Class[] { ClassLoader.class, policyProviderClass } ); > - streamWriterConstructor = ServerSerializationStreamWriter.class.getConstructor( > - new Class[] { serializationPolicyClass } ); > - > - Class legacySerializationPolicyClass = Class.forName(LEGACY_SERIALIZATION_POLICY_CLASS); > - Method m = legacySerializationPolicyClass.getDeclaredMethod("getInstance"); > - legacySerializationPolicy = m.invoke(null); > - } > - catch (Exception ex) > - { > - log.error("Error initializing GWT14Service. Please ensure " + > - "the GWT 1.4 libraries are in the classpath."); > - throw ex; > - } > - } > - > - @Override > - protected String createResponse(ServerSerializationStreamWriter stream, > - Class responseType, Object responseObj, boolean isException) > - { > - stream.prepareToWrite(); > - if (responseType != void.class) > - { > - try > - { > - stream.serializeValue(responseObj, responseType); > - } catch (SerializationException e) > - { > - responseObj = e; > - isException = true; > - } > - } > - > - return (isException ? "//EX" : "//OK") + stream.toString(); > - } > - > - @Override > - public ServerSerializationStreamReader getStreamReader() > - { > - try > - { > - return (ServerSerializationStreamReader) streamReaderConstructor.newInstance( > - Thread.currentThread().getContextClassLoader(), null); > - } > - catch (Exception ex) > - { > - throw new RuntimeException("Unable to create stream reader", ex); > - } > - } > - > - @Override > - public ServerSerializationStreamWriter getStreamWriter() > - { > - try > - { > - return (ServerSerializationStreamWriter) streamWriterConstructor.newInstance(legacySerializationPolicy); > - } > - catch (Exception ex) > - { > - throw new RuntimeException("Unable to create stream writer", ex); > - } > - } > -} -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From jira-events at lists.jboss.org Fri Jan 30 22:23:54 2009 From: jira-events at lists.jboss.org (Sheng Gu (JIRA)) Date: Fri, 30 Jan 2009 22:23:54 -0500 (EST) Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3752) The possibility to kill the conversation stack with the "s:conversationPropagation" tag is missing In-Reply-To: <33326318.1227551556482.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <31571415.1233372234438.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/JBSEAM-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12450500#action_12450500 ] Sheng Gu commented on JBSEAM-3752: ---------------------------------- For and : > The possibility to kill the conversation stack with the "s:conversationPropagation" tag is missing > -------------------------------------------------------------------------------------------------- > > Key: JBSEAM-3752 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3752 > Project: Seam > Issue Type: Feature Request > Affects Versions: 2.1.1.CR1 > Reporter: Denis Forveille > Assignee: Jacob Orshalick > > The possibility to kill the conversation stack with the "s:conversationPropagation" is missing in v2.1.1.CR1. > It is possible to do that via annotation @End(root=true), the API or with pages.xml, but not with the "s:conversationPropagation" tag that may use to begin/end/join etc... a conversation > Maybe by adding another enum for "type" like "endAll" ?: -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira