January 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-694) Remove need to specify external smtp server for Seam mail

by Peter Muir (JIRA)

Remove need to specify external smtp server for Seam mail --------------------------------------------------------- Key: JBSEAM-694 URL: http://jira.jboss.com/jira/browse/JBSEAM-694 Project: JBoss Seam Issue Type: Bug Reporter: Peter Muir Currently you have to setup a connection to a smtp server which is especially bad for examples -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-658) JCA ResourceAdapter for processing recieved email

by Peter Muir (JIRA)

JCA ResourceAdapter for processing recieved email ------------------------------------------------- Key: JBSEAM-658 URL: http://jira.jboss.com/jira/browse/JBSEAM-658 Project: JBoss Seam Issue Type: Sub-task Components: Core Affects Versions: 1.1.0.GA Reporter: Peter Muir This is a JCA resource adapter which delivers to an EJB3 Message Driven bean. It polls the IMAP/POP3 server at a user-defined interval, and delivers each message retrieved to the configured endpoint. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

3
16
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-725) Bug in FacesMessage Serializability workaround

by Peter Muir (JIRA)

Bug in FacesMessage Serializability workaround ---------------------------------------------- Key: JBSEAM-725 URL: http://jira.jboss.com/jira/browse/JBSEAM-725 Project: JBoss Seam Issue Type: Bug Components: JSF Reporter: Peter Muir Fix For: 1.1.5.GA The serializability workaround assumed that the FacesMessage.VALUES list was ordered by severity ordinal. In (at least) MyFaces it isn't (it is in some random order). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-693) Support attachments in Seam Mail

by Peter Muir (JIRA)

Support attachments in Seam Mail -------------------------------- Key: JBSEAM-693 URL: http://jira.jboss.com/jira/browse/JBSEAM-693 Project: JBoss Seam Issue Type: Feature Request Reporter: Peter Muir -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-713) Using FacesMessages results in stale component rendering

by Christian Bauer (JIRA)

Using FacesMessages results in stale component rendering -------------------------------------------------------- Key: JBSEAM-713 URL: http://jira.jboss.com/jira/browse/JBSEAM-713 Project: JBoss Seam Issue Type: Bug Reporter: Christian Bauer Priority: Minor Tough one... before I isolate the problem to a standalone test, these are the symptoms: A page has two <h:datatable> components, let's say tableA and tableB. There is a <h:form> around tableB with a <h:commandButton>. When this button is pressed, I execute an action method on a conversational component and update some data in the current conversation that is shown by tableA. The page is rendered again and tableA shows the updated data. However, if in the action method I use FacesMessages.instance().add("Updated object"); (or any other variation of FacesMessages), tableA is not re-rendered but shown with old state. If I click the commandButton again, tableA is rendered fine (!). Now, if I replace the call to FacesMessages with this FacesContext.getCurrentInstance().addMessage(null, new FacesMessage("Updated Object")); all works as expected and on every RenderResponse of the page, tableA is rerendered. I verified that the tableA datacomponent is not rendered again. Interestingly, the backing bean data for tableA is called during RenderResponse every time, it just displays the same old component (which, I think, it remembers somehow from the RestoreView phase). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-695) RequestContextPath for mail tags

by Peter Muir (JIRA)

RequestContextPath for mail tags -------------------------------- Key: JBSEAM-695 URL: http://jira.jboss.com/jira/browse/JBSEAM-695 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.1.5.GA Reporter: Peter Muir Currently if you include richer JSF components in an message body the path to any resource (external to the page) starts with /requestcontextpath. Would be good if it could include the host as well. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-562) Support composite keys in seam-gen templates

by Gavin King (JIRA)

Support composite keys in seam-gen templates -------------------------------------------- Key: JBSEAM-562 URL: http://jira.jboss.com/jira/browse/JBSEAM-562 Project: JBoss Seam Issue Type: Feature Request Components: Tools Reporter: Gavin King Assigned To: Norman Richards -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-698) pdf headers don't apply to first page

by Norman Richards (JIRA)

pdf headers don't apply to first page ------------------------------------- Key: JBSEAM-698 URL: http://jira.jboss.com/jira/browse/JBSEAM-698 Project: JBoss Seam Issue Type: Bug Reporter: Norman Richards Assigned To: Norman Richards Priority: Minor header/footer needs to be applied before document.open() to apply to the first page. We probably need to convert header and footer to facets to adequately support this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-647) Better error handling in seam-gen app

by Gavin King (JIRA)

Better error handling in seam-gen app ------------------------------------- Key: JBSEAM-647 URL: http://jira.jboss.com/jira/browse/JBSEAM-647 Project: JBoss Seam Issue Type: Feature Request Components: Tools Reporter: Gavin King Especially things like a "not found" page! Should probably include an exceptions.xml file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-538) Add the ability to regenerate the datasource

by gregorypierce (JIRA)

Add the ability to regenerate the datasource -------------------------------------------- Key: JBSEAM-538 URL: http://jira.jboss.com/jira/browse/JBSEAM-538 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 1.1.0.CR1 Reporter: gregorypierce Allows you to swap datasources from the current datasource to a new datasource. Why? Because many times I will develop using HSQL and then later want to move to another datasource. Note: You will also have to add overwrite="true" to the various copy tasks or else they won't overwrite the existing datasource files. <target name="new-datasource">  <condition property="database.type.default" value="${database.type}"> <isset property="database.type"/> </condition> <property name="database.type.default" value="hsql"/> <input addproperty="database.type.new" message="What kind of database are you using? [${database.type.default}] " validargs="hsql,mysql,oracle,postgres,mssql,db2,sybase,enterprisedb" defaultvalue="${database.type.default}"/>  <condition property="hibernate.dialect.default" value="${hibernate.dialect}"> <equals arg1="${database.type}" arg2="${database.type.new}"/> </condition> <condition property="hibernate.connection.url.default" value="${hibernate.connection.url}"> <equals arg1="${database.type}" arg2="${database.type.new}"/> </condition> <condition property="hibernate.connection.driver_class.default" value="${hibernate.connection.driver_class}"> <equals arg1="${database.type}" arg2="${database.type.new}"/> </condition>  <condition property="hibernate.dialect.default" value="org.hibernate.dialect.HSQLDialect"> <equals arg1="${database.type.new}" arg2="hsql"/> </condition> <condition property="hibernate.dialect.default" value="org.hibernate.dialect.MySQLDialect"> <equals arg1="${database.type.new}" arg2="mysql"/> </condition> <condition property="hibernate.dialect.default" value="org.hibernate.dialect.OracleDialect"> <equals arg1="${database.type.new}" arg2="oracle"/> </condition> <condition property="hibernate.dialect.default" value="org.hibernate.dialect.PostgreSQLDialect"> <equals arg1="${database.type.new}" arg2="postgres"/> </condition> <condition property="hibernate.dialect.default" value="org.hibernate.dialect.PostgreSQLDialect"> <equals arg1="${database.type.new}" arg2="enterprisedb"/> </condition> <condition property="hibernate.dialect.default" value="org.hibernate.dialect.SQLServerDialect"> <equals arg1="${database.type.new}" arg2="mssql"/> </condition> <condition property="hibernate.dialect.default" value="org.hibernate.dialect.DB2Dialect"> <equals arg1="${database.type.new}" arg2="db2"/> </condition> <condition property="hibernate.dialect.default" value="org.hibernate.dialect.SybaseDialect"> <equals arg1="${database.type.new}" arg2="sybase"/> </condition> <condition property="hibernate.connection.driver_class.default" value="org.hsqldb.jdbcDriver"> <equals arg1="${database.type.new}" arg2="hsql"/> </condition> <condition property="hibernate.connection.driver_class.default" value="com.mysql.jdbc.Driver"> <equals arg1="${database.type.new}" arg2="mysql"/> </condition> <condition property="hibernate.connection.driver_class.default" value="oracle.jdbc.driver.OracleDriver"> <equals arg1="${database.type.new}" arg2="oracle"/> </condition> <condition property="hibernate.connection.driver_class.default" value="org.postgresql.Driver"> <equals arg1="${database.type.new}" arg2="postgres"/> </condition> <condition property="hibernate.connection.driver_class.default" value="com.edb.Driver"> <equals arg1="${database.type.new}" arg2="enterprisedb"/> </condition> <condition property="hibernate.connection.driver_class.default" value="com.microsoft.sqlserver.jdbc.SQLServerDriver"> <equals arg1="${database.type.new}" arg2="mssql"/> </condition> <condition property="hibernate.connection.driver_class.default" value="COM.ibm.db2.jdbc.app.DB2Driver"> <equals arg1="${database.type.new}" arg2="db2"/> </condition> <condition property="hibernate.connection.driver_class.default" value="com.sybase.jdbc2.jdbc.SybDriver"> <equals arg1="${database.type.new}" arg2="sybase"/> </condition> <condition property="hibernate.connection.url.default" value="jdbc:hsqldb:."> <equals arg1="${database.type.new}" arg2="hsql"/> </condition> <condition property="hibernate.connection.url.default" value="jdbc:mysql:///test"> <equals arg1="${database.type.new}" arg2="mysql"/> </condition> <condition property="hibernate.connection.url.default" value="jdbc:oracle:thin:@localhost:1521:test"> <equals arg1="${database.type.new}" arg2="oracle"/> </condition> <condition property="hibernate.connection.url.default" value="jdbc:postgresql:template1"> <equals arg1="${database.type.new}" arg2="postgres"/> </condition> <condition property="hibernate.connection.url.default" value="jdbc:edb://localhost:5444/edb"> <equals arg1="${database.type.new}" arg2="enterprisedb"/> </condition> <condition property="hibernate.connection.url.default" value="jdbc:sqlserver://localhost"> <equals arg1="${database.type.new}" arg2="mssql"/> </condition> <condition property="hibernate.connection.url.default" value="jdbc:db2:test"> <equals arg1="${database.type.new}" arg2="db2"/> </condition> <condition property="hibernate.connection.url.default" value="jdbc:sybase:Tds:localhost:5000/test"> <equals arg1="${database.type.new}" arg2="sybase"/> </condition>  <property name="hibernate.dialect.default" value="org.hibernate.dialect.HSQLDialect"/> <property name="hibernate.connection.driver_class.default" value="org.hsqldb.jdbcDriver"/> <property name="hibernate.connection.url.default" value="jdbc:hsqldb:."/> <input addproperty="hibernate.dialect.new" message="Enter the Hibernate dialect for your database [${hibernate.dialect.default}]" defaultvalue="${hibernate.dialect.default}"/> <property name="driver.jar" value="hsqldb.jar"/> <input addproperty="driver.jar.new" message="Enter the filesystem path to the JDBC driver jar [${driver.jar}]" defaultvalue="${seamgen.home}/lib/${driver.jar}"/> <input addproperty="hibernate.connection.driver_class.new" message="Enter JDBC driver class for your database [${hibernate.connection.driver_class.default}]" defaultvalue="${hibernate.connection.driver_class.default}"/> <input addproperty="hibernate.connection.url.new" message="Enter the JDBC URL for your database [${hibernate.connection.url.default}]" defaultvalue="${hibernate.connection.url.default}"/> <property name="hibernate.connection.username" value="sa"/> <input addproperty="hibernate.connection.username.new" message="Enter database username [${hibernate.connection.username}]" defaultvalue="${hibernate.connection.username}"/> <property name="hibernate.connection.password" value=""/> <input addproperty="hibernate.connection.password.new" message="Enter database password [${hibernate.connection.password}]" defaultvalue="${hibernate.connection.password}"/> <property name="database.exists" value="n"/> <input addproperty="database.exists.new" message="Are you working with tables that already exist in the database? [${database.exists}] " validargs="y,n," defaultvalue="${database.exists}"/> <propertyfile file="${user.dir}/project.properties"> <entry key="basepackage.name" value="${basepackage.name}" /> <entry key="project.name" value="${project.name}"/> <entry key="project.home" value="${project.home}" />  <entry key="action.package" value="${action.package}"/> <entry key="model.package" value="${model.package}"/> <entry key="test.package" value="${test.package}"/>  <entry key="database.type" value="${database.type.new}"/> <entry key="database.exists" value="${database.exists.new}"/> <entry key="hibernate.dialect" value="${hibernate.dialect.new}"/> <entry key="hibernate.connection.driver_class" value="${hibernate.connection.driver_class.new}"/> <entry key="hibernate.connection.url" value="${hibernate.connection.url.new}"/> <entry key="hibernate.connection.username" value="${hibernate.connection.username.new}"/> <entry key="hibernate.connection.password" value="${hibernate.connection.password.new}"/> <entry key="driver.jar" value="${driver.jar.new}"/> <entry key="eclipse.wtp" value="${eclipse.wtp.new}"/> </propertyfile> <property file="${user.dir}/project.properties" /> <property file="${seam.home}/seam.properties" /> <property file="${user.dir}/${project.name}/project.properties" /> <condition property="wtp"> <equals arg1="${eclipse.wtp}" arg2="y"/> </condition> <antcall target="file-copy" /> <echo message="Your project has been created." /> <echo message="Add the project from inside Eclipse (or type 'seam explode') and go to http://localhost:8080/${project.name}"/> </target> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2007