June 2013 - seam-issues - Jboss List Archives

[JBoss JIRA] (JBSEAM-3879) e:cell formatting of date or number colum fails, if first value is a null value

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-3879?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-3879. --------------------------------- Fix Version/s: 2.2.0.GA Resolution: Done closing due latest comments about fixed status in 2.2.0.GA > e:cell formatting of date or number colum fails, if first value is a null value > ------------------------------------------------------------------------------- > > Key: JBSEAM-3879 > URL: https://issues.jboss.org/browse/JBSEAM-3879 > Project: Seam 2 > Issue Type: Sub-task > Components: Excel > Affects Versions: 2.1.1.GA > Environment: Seam 2.1.1.GA, Windows, Jetty > Reporter: Alexander Schwartz > Assignee: Nicklas Karlsson > Labels: excel, null > Fix For: 2.2.0.GA > > 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, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-3955) Problem extending JpaIdentityStore

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-3955?page=com.atlassian.jira.plugi... ] Marek Novotny updated JBSEAM-3955: ---------------------------------- Issue Type: Bug (was: Release) Workflow: GIT Pull Request workflow (was: jira) > Problem extending JpaIdentityStore > ---------------------------------- > > Key: JBSEAM-3955 > URL: https://issues.jboss.org/browse/JBSEAM-3955 > Project: Seam 2 > Issue Type: Bug > Components: Framework > Affects Versions: 2.1.1.GA > Environment: Windows running JBoss Developer Studio > Reporter: Alejandro Barrero > Priority: Minor > > I am using > <security:jpa-identity-store class="la.netco.sim.security.MiJpaSecurity" user-class="la.netco.gestorprocesos.model.Usuario" role-class="la.netco.gestorprocesos.model.Rol"/> > in components.xml > I getting the error > Class "MiJpaSecurity" of component "org.jboss.seam.security.jpaIdentityStore" does not have a setter or a field for the property "startupDepends" components.xml netcoPM/WebContent/WEB-INF line 43 Seam Problem > Works fine if I specify org.jboss.seam.security.management.JpaIdentityStore but fails with la.netco.sim.security.MiJpaSecurity which extends it. > Your help would be greatly appreciated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-4374) GWT Example does not work with GWT 2.0.0 Milestone 1.

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-4374?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-4374. --------------------------------- Resolution: Won't Fix GWT in seam is deprecated, Errai is recommended to use > GWT Example does not work with GWT 2.0.0 Milestone 1. > ----------------------------------------------------- > > Key: JBSEAM-4374 > URL: https://issues.jboss.org/browse/JBSEAM-4374 > Project: Seam 2 > Issue Type: Component Upgrade > Components: Remoting > Affects Versions: 2.2.0.GA, 2.2.1.CR1 > Environment: linux, jboss 4.2.3, seam 2.2.1-SNAPSHOT, GWT 2.0.0 Milestone 1 > Reporter: Sand Lee > Assignee: Pete Muir > Labels: GWT, RPC, Remoting > Attachments: GWT20Service.java, GWTService.java.diff > > > way to reproduce: > cd /tmp > svn co http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_2 seam > wget http://google-web-toolkit.googlecode.com/files/gwt-2.0.0-ms1.zip > unzip gwt-2.0.0-ms1.zip > cd /tmp/seam/examples/remoting/gwt > sed -i 's/C:\/java\/gwt-windows-1.5.2/\/tmp\/gwt-2.0.0-ms1\//g' build.properties > ant clean gwt-compile deploy > pressing ask on http://localhost:8080/seam-gwt/HelloWorld.html produces following output on the server side: > 12:41:55,928 INFO [EARDeployer] Started J2EE application: file:/opt/jboss-4.2.3.GA/server/default/deploy/jboss-seam-gwt.ear |@LOCATION: org.jboss.deployment.EARDeployer.start(EARDeployer.java:368) > 12:45:00,807 ERROR [[/seam-gwt]] Exception while dispatching incoming RPC call |@LOCATION: org.apache.catalina.core.ApplicationContext.log(ApplicationContext.java:660) > java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 > at java.util.ArrayList.RangeCheck(ArrayList.java:547) > at java.util.ArrayList.get(ArrayList.java:322) > at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.extract(ServerSerializationStreamReader.java:617) > at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.readInt(ServerSerializationStreamReader.java:432) > at com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.prepareToRead(AbstractSerializationStreamReader.java:38) > at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.prepareToRead(ServerSerializationStreamReader.java:383) > at org.jboss.seam.remoting.gwt.GWTService.RPC_decodeRequest(GWTService.java:376) > at org.jboss.seam.remoting.gwt.GWTService.processCall(GWTService.java:203) > at org.jboss.seam.remoting.gwt.GWTService$1.process(GWTService.java:120) > at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:53) > at org.jboss.seam.remoting.gwt.GWTService.getResource(GWTService.java:105) > at org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) > 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.LoggingFilter.doFilter(LoggingFilter.java:60) > 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.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:230) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) > 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: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:619) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-3644) Upgrade to jaxb & jaxws api 2.1

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-3644?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-3644. --------------------------------- Resolution: Out of Date we already use 2.1 > Upgrade to jaxb & jaxws api 2.1 > ------------------------------- > > Key: JBSEAM-3644 > URL: https://issues.jboss.org/browse/JBSEAM-3644 > Project: Seam 2 > Issue Type: Component Upgrade > Components: WS > Affects Versions: 2.1.0.GA > Environment: Linux, JBoss 4.2.2 GA, Java 1.5 > Reporter: toto titi > Assignee: Shane Bryzak > Priority: Minor > Labels: jaxb, jaxws, web_services > > It would be neat to have JAXB & JAX-WS API v2.1 shipped with Seam instead of 2.0, this is getting annoying as most of implementations are based on 2.1 now. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-4141) Page <restrict> tag, Ajax call and POST parameters

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-4141?page=com.atlassian.jira.plugi... ] Marek Novotny updated JBSEAM-4141: ---------------------------------- Priority: Major (was: Blocker) > Page <restrict> tag, Ajax call and POST parameters > -------------------------------------------------- > > Key: JBSEAM-4141 > URL: https://issues.jboss.org/browse/JBSEAM-4141 > Project: Seam 2 > Issue Type: Bug > Components: Security > Affects Versions: 2.1.1.GA > Reporter: Jarek Gilewski > Assignee: Shane Bryzak > Labels: restrict > > The problem is that <restrict> part is always trigered before the page parameters are properly set with Ajax/POST call on the page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-1852) Implement dynamic privilege system with assignment to roles and users

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-1852?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-1852. --------------------------------- Resolution: Won't Fix closing, wiki example is EOL > Implement dynamic privilege system with assignment to roles and users > --------------------------------------------------------------------- > > Key: JBSEAM-1852 > URL: https://issues.jboss.org/browse/JBSEAM-1852 > Project: Seam 2 > Issue Type: Task > Components: Wiki > Reporter: Christian Bauer > Priority: Blocker > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-1852) Implement dynamic privilege system with assignment to roles and users

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-1852?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-1852. --------------------------------- Resolution: Done closing, wiki example is EOL > Implement dynamic privilege system with assignment to roles and users > --------------------------------------------------------------------- > > Key: JBSEAM-1852 > URL: https://issues.jboss.org/browse/JBSEAM-1852 > Project: Seam 2 > Issue Type: Task > Components: Wiki > Reporter: Christian Bauer > Priority: Blocker > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-1852) Implement dynamic privilege system with assignment to roles and users

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-1852?page=com.atlassian.jira.plugi... ] Marek Novotny reopened JBSEAM-1852: ----------------------------------- > Implement dynamic privilege system with assignment to roles and users > --------------------------------------------------------------------- > > Key: JBSEAM-1852 > URL: https://issues.jboss.org/browse/JBSEAM-1852 > Project: Seam 2 > Issue Type: Task > Components: Wiki > Reporter: Christian Bauer > Priority: Blocker > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-2646) Wiki document templates

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-2646?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-2646. --------------------------------- Resolution: Won't Fix closing, wiki example is EOL > Wiki document templates > ----------------------- > > Key: JBSEAM-2646 > URL: https://issues.jboss.org/browse/JBSEAM-2646 > Project: Seam 2 > Issue Type: Feature Request > Components: Wiki > Reporter: Gavin King > Priority: Blocker > > Allow creation of document templates with defined header/footer, and content sections. > Then user can select a template with creating a document. Things like FAQ entries and Forum posts would then use a specific template. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-2231) Setup wizard for wiki

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-2231?page=com.atlassian.jira.plugi... ] Marek Novotny reopened JBSEAM-2231: ----------------------------------- > Setup wizard for wiki > --------------------- > > Key: JBSEAM-2231 > URL: https://issues.jboss.org/browse/JBSEAM-2231 > Project: Seam 2 > Issue Type: Feature Request > Components: Wiki > Reporter: Christian Bauer > Priority: Blocker > > Write a setup wizard that replaces the manual wiki-data.sql editing and import. We should have the following setup procedure: > - Get the recommended environment ready (JBoss AS, MySQL) > - Deploy the wiki-ddl.sql on a new database > - Deploy the wiki.war on the appserver > - Open http://server/wiki/ and go through the setup wizard > The wizard will first import the minimum dataset (guest/admin users, roles, start page) and then ask the usual setup questions (site base URL, etc.). Depending on the future of the plugin API, it could also optionally allow you to configure some plugin defaults so you don't have to go into the Admin screen to change them after the install. Also, we can offer prepackaged datasets for certain use cases that can be imported with the wizard, e.g. "Help Documents", "Blog Website", "Forum Website". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues June 2013