[JBoss JIRA] Created: (JBSEAM-4567) Metawidget examples fail to deploy to JBoss AS 6 M2
by Jozef Hartinger (JIRA)
Metawidget examples fail to deploy to JBoss AS 6 M2
---------------------------------------------------
Key: JBSEAM-4567
URL: https://jira.jboss.org/jira/browse/JBSEAM-4567
Project: Seam
Issue Type: Bug
Components: Examples
Affects Versions: 2.2.1.CR1
Environment: java version "1.6.0_14"
JBoss AS 6 M2 with Mojarra 2.0.3-SNAPSHOT
Reporter: Jozef Hartinger
Affects all the metawidget examples we have in Seam (booking, dvdstore, groovybooking)
09:55:56,553 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Parse: name=vfszip:/home/jharting/jboss/jboss-6.0.0.20100216-M2/server/default/deploy/seam-metawidget-dvdstore.ear/ state=PreParse mode=Manual requiredState=Parse: org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/home/jharting/jboss/jboss-6.0.0.20100216-M2/server/default/deploy/seam-metawidget-dvdstore.ear/seam-metawidget-dvdstore.war/
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:362)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:322)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:294)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:234)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1660)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1378)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1431)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1319)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:378)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2029)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1050)
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1289)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1213)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1107)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:918)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:633)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:898)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:677)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:409)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Invalid value jsp for {http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd}body-contentType valid are [tagdependent, empty, scriptless, JSP]
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)
at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:229)
at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:206)
at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:137)
at org.jboss.deployment.TldParsingDeployer.parse(TldParsingDeployer.java:64)
at org.jboss.deployment.TldParsingDeployer.parse(TldParsingDeployer.java:38)
at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:121)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.handleMultipleFiles(AbstractVFSParsingDeployer.java:397)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:282)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:355)
... 30 more
Caused by: java.lang.RuntimeException: Invalid value jsp for {http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd}body-contentType valid are [tagdependent, empty, scriptless, JSP]
at org.jboss.xb.builder.runtime.EnumValueAdapter.cast(EnumValueAdapter.java:137)
at org.jboss.xb.builder.runtime.BeanHandler.setParent(BeanHandler.java:149)
at org.jboss.xb.builder.runtime.BuilderParticleHandler.setParent(BuilderParticleHandler.java:67)
at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.setParent(SundayContentHandler.java:1189)
at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endElement(SundayContentHandler.java:1103)
at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endElement(SundayContentHandler.java:238)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.endElement(SaxJBossXBParser.java:373)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLNSDTDValidator.endNamespaceScope(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
... 40 more
09:55:56,717 INFO [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=dvdstoreDatasource' to JNDI name 'java:dvdstoreDatasource'
09:55:56,719 WARN [org.jboss.system.server.profileservice.hotdeploy.HDScanner] Failed to process changes: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS IN ERROR: Name -> Error
vfszip:/home/jharting/jboss/jboss-6.0.0.20100216-M2/server/default/deploy/seam-metawidget-dvdstore.ear/ -> org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/home/jharting/jboss/jboss-6.0.0.20100216-M2/server/default/deploy/seam-metawidget-dvdstore.ear/seam-metawidget-dvdstore.war/
DEPLOYMENTS IN ERROR:
Deployment "vfszip:/home/jharting/jboss/jboss-6.0.0.20100216-M2/server/default/deploy/seam-metawidget-dvdstore.ear/" is in error due to the following reason(s): java.lang.RuntimeException: Invalid value jsp for {http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd}body-contentType valid are [tagdependent, empty, scriptless, JSP]
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1198)
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1144)
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:848)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:416)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
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
13 years, 11 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3629) Since Seam v2.1.0, httpServletRequest.getUserPrincipal() is always returning null when using plain J2EE security
by Denis Forveille (JIRA)
Since Seam v2.1.0, httpServletRequest.getUserPrincipal() is always returning null when using plain J2EE security
----------------------------------------------------------------------------------------------------------------
Key: JBSEAM-3629
URL: https://jira.jboss.org/jira/browse/JBSEAM-3629
Project: Seam
Issue Type: Bug
Components: Security
Affects Versions: 2.1.0.GA
Environment: Seam v2.1.0GA, WebSphere v6.1.0.17 (Without EJB3 FP), RF v3.2.2, facelets 1.1.14, JSF RI 1.2_09
Reporter: Denis Forveille
Priority: Critical
Since v2.1.GA, it is not possible to use plain J2EE security.
Now, httpServletRequest.getUserPrincipal() always return null and also
@In
UserPrincipal principal;
does not work
This is not working because the http request is wrapped in IdentityRequestWrapper (in IdentityFilter) and its getUserPrincipal() method is reading principal variable on Identity component.
httpServletRequest.getUserPrincipal() should work when seam security is not use, and so we should have a way to "disable" Seam 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
13 years, 11 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3999) Race condition in component initialization
by Stuart Douglas (JIRA)
Race condition in component initialization
------------------------------------------
Key: JBSEAM-3999
URL: https://jira.jboss.org/jira/browse/JBSEAM-3999
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.1.1.GA
Reporter: Stuart Douglas
When starting up application (or session) scoped component that do not have an @Startup annotation it is possible to get a race condition where two instances of the component are instantiated, as no locking is present in component initialization. I ran into this when my multi-threaded reporting process was the first component to hit the cache and jboss cache provider got instantiated twice:
`16:54:48,717 INFO [JbossCacheProvider] Starting JBoss Treecache 1.x
16:54:48,717 INFO [JbossCacheProvider] Starting JBoss Treecache 1.x`
In this case it is easy to work around, by simply adding startup="true" to the application scoped component. It is also possible to make calls on a component before the create method is called.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-977) Invoking Seam Email render from a page containing Icefaces tags creates render exception
by Karthikeyan Pattabiraman (JIRA)
Invoking Seam Email render from a page containing Icefaces tags creates render exception
----------------------------------------------------------------------------------------
Key: JBSEAM-977
URL: http://jira.jboss.com/jira/browse/JBSEAM-977
Project: JBoss Seam
Issue Type: Bug
Components: ICE Faces Integration
Environment: Windows XP, JDk 5.0, JBoss AP, JBoss Seam, Facelets, IceFaces
Reporter: Karthikeyan Pattabiraman
Assigned To: Gregory Dick
When I invoke Seam E-mail functionality from an Iceface page containing menu Items to the child level (to any level) causes the following exception:
Error send mail
java.lang.NullPointerException:
at com.icesoft.faces.component.menubar.MenuItemRenderer.renderChildrenRecursive(MenuItemRenderer.java:382)
at com.icesoft.faces.component.menubar.MenuItemRenderer.encodeBegin(MenuItemRenderer.java:185)
at javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:512)
at com.icesoft.faces.renderkit.dom_html_basic.DomBasicRenderer.encodeParentAndChildren(DomBasicRenderer.java:339)
at com.icesoft.faces.component.menubar.MenuBarRenderer.encodeChildren(MenuBarRenderer.java:94)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:524)
at com.icesoft.faces.renderkit.dom_html_basic.DomBasicRenderer.encodeParentAndChildren(DomBasicRenderer.java:341)
at com.icesoft.faces.renderkit.dom_html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:97)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:524)
at org.jboss.seam.ui.JSF.renderChild(JSF.java:174)
at org.jboss.seam.ui.JSF.renderChildren(JSF.java:162)
at org.jboss.seam.ui.JSF.renderChild(JSF.java:177)
at org.jboss.seam.ui.JSF.renderChildren(JSF.java:162)
at org.jboss.seam.ui.JSF.renderChild(JSF.java:177)
at org.jboss.seam.ui.JSF.renderChildren(JSF.java:162)
at org.jboss.seam.ui.JSF.renderChild(JSF.java:177)
at org.jboss.seam.ui.JSF.renderChildren(JSF.java:162)
at org.jboss.seam.ui.JSF.renderChild(JSF.java:177)
at org.jboss.seam.ui.JSF.renderChildren(JSF.java:162)
at org.jboss.seam.ui.JSF.renderChild(JSF.java:177)
at org.jboss.seam.ui.JSF.renderChildren(JSF.java:162)
at org.jboss.seam.ui.JSF.renderChild(JSF.java:177)
at org.jboss.seam.ui.JSF.renderChildren(JSF.java:162)
at org.jboss.seam.ui.JSF.renderChild(JSF.java:177)
at org.jboss.seam.ui.JSF.renderChildren(JSF.java:162)
at org.jboss.seam.ui.JSF.renderChild(JSF.java:177)
at org.jboss.seam.ui.JSF.renderChildren(JSF.java:162)
at org.jboss.seam.ui.JSF.renderChild(JSF.java:177)
at org.jboss.seam.ui.JSF.renderChildren(JSF.java:162)
at org.jboss.seam.ui.facelet.FaceletsRenderer.renderFacelet(FaceletsRenderer.java:106)
at org.jboss.seam.ui.facelet.FaceletsRenderer.render(FaceletsRenderer.java:54)
at org.jboss.seam.ui.facelet.FaceletsRenderer.render(FaceletsRenderer.java:38)
When I remove the child Items (the page still contains other iceFaces tags), the issue leads me staright to issue # JBSEAM-827.
Hence I am not able to use Seam E-mail with ICEFaces together.
Things I used:
============
mail Template (same as it is in Seam Examples):
<m:message xmlns="http://www.w3.org/1999/xhtml"
xmlns:m="http://jboss.com/products/seam/mail"
xmlns:h="http://java.sun.com/jsf/html">
<m:from name="Peter" address="peter(a)example.com" />
<m:to name="#{person.firstname} #{person.lastname}">#{person.address}</m:to>
<m:subject>Try out Seam!</m:subject>
<m:body>
<p><h:outputText value="Dear #{person.firstname}" />,</p>
<p>You can try out Seam by visiting <a href="http://labs.jboss.com/jbossseam">http://labs.jboss.com/jbossseam</a>.</p>
<p>Regards</p>
<p>Peter</p>
</m:body>
</m:message>
menu Items:
=============
<ice:form id="menu" xmlns="http://www.w3.org/1999/xhtml"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:s="http://jboss.com/products/seam/taglib"
xmlns:ice="http://www.icesoft.com/icefaces/component">
<ice:panelGroup id="menupanel" styleClass="formBorderHighlight">
<ice:menuBar id="menubar" orientation="horizontal">
<ice:menuItem value="Parent 1">
<ice:menuItem value="Child 1" />
</ice:menuItem>
</ice:menuBar>
</ice:panelGroup>
</ice:form>
--
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
13 years, 11 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1316) NumberFormatException when using 'noSelectionLabel="true"' on s:selectItems for a ice:selectMenuOne
by David Rogers (JIRA)
NumberFormatException when using 'noSelectionLabel="true"' on s:selectItems for a ice:selectMenuOne
---------------------------------------------------------------------------------------------------
Key: JBSEAM-1316
URL: http://jira.jboss.com/jira/browse/JBSEAM-1316
Project: JBoss Seam
Issue Type: Bug
Components: ICE Faces Integration
Affects Versions: 1.2.1.GA
Reporter: David Rogers
Assigned To: Gregory Dick
Peter Muir "Something very strange is going on when trying to use Seam selectItems with icefaces - I'm not quite sure what... If you create a JIRA issue I can try to take a look (I'm not sure when...)"
This was in response to a forum post I put up indicating that I was getting a NumberFormatException when using the 'noSelectionLabel="true"' attribute on a s:selectItems when the ice:selectMenuOne was set to required="true" and I attempted to submit the form with nothing selected (obviously the correct behaviour would be to show a validation message indicating that the field was a required value.
java.lang.NumberFormatException: For input string: "Select..."
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:447)
at java.lang.Integer.<init>(Integer.java:620)
at org.jboss.seam.ui.EntityConverter.getAsObject(EntityConverter.java:197)
at org.jboss.seam.ui.PrioritizableConverter.getAsObject(PrioritizableConverter.java:61)
at org.jboss.seam.ui.ConverterChain.getAsObject(ConverterChain.java:105)
at com.icesoft.faces.renderkit.dom_html_basic.DomBasicInputRenderer.getConvertedValue(DomBasicInput
Renderer.java:97)
at com.icesoft.faces.renderkit.dom_html_basic.MenuRenderer.getConvertedValue(MenuRenderer.java:129)
at javax.faces.component.UIInput.getConvertedValue(UIInput.java:395)
at javax.faces.component.UIInput.validate(UIInput.java:349)
at com.icesoft.faces.component.ext.HtmlSelectOneMenu.validate(HtmlSelectOneMenu.java:418)
at javax.faces.component.UIInput.processValidators(UIInput.java:183)
at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:624)
at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:624)
at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:624)
at javax.faces.component.UIForm.processValidators(UIForm.java:70)
at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:624)
at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:624)
at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:624)
at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:624)
at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:624)
at javax.faces.component.UIViewRoot.processValidators(UIViewRoot.java:146)
at org.apache.myfaces.lifecycle.LifecycleImpl.processValidations(LifecycleImpl.java:262)
at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:76)
at com.icesoft.faces.webapp.xmlhttp.BlockingServlet.renderCyclePartial(BlockingServlet.java:473)
at com.icesoft.faces.webapp.xmlhttp.BlockingServlet.receiveUpdates(BlockingServlet.java:442)
at com.icesoft.faces.webapp.xmlhttp.BlockingServlet.executeRequest(BlockingServlet.java:324)
at com.icesoft.faces.webapp.xmlhttp.BlockingServlet.service(BlockingServlet.java:186)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252
)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at twp.filter.RoleFilter.doFilter(RoleFilter.java:46)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202
)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at twp.filter.UtilFilter.doFilter(UtilFilter.java:44)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202
)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202
)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11Base
Protocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
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: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-859) Seam fileupload tag does not work with IceFaces
by Crayton OSteen (JIRA)
Seam fileupload tag does not work with IceFaces
-----------------------------------------------
Key: JBSEAM-859
URL: http://jira.jboss.com/jira/browse/JBSEAM-859
Project: JBoss Seam
Issue Type: Bug
Components: ICE Faces Integration
Affects Versions: 1.1.6.GA
Environment: JBOSS AS 4.0.5, Windows XP, Seam 1.1.6GA, IceFaces 1.5.3
Reporter: Crayton OSteen
Assigned To: Gregory Dick
Priority: Blocker
Attachments: fileupload.zip
I've been waiting to implement the IceFaces file upload component until some of the integration issues were worked out. Seam has come out with their own file upload component. So now Seam has decided that getting the IceFaces file upload component working with Seam is not a priority (see http://jira.jboss.org/jira/browse/JBSEAM-676 ).
This is great, except I can't get Seam's file upload component it to work with IceFaces.
I feel a priority should be either 1) Seam should work with the IceFaces file upload or 2) the file upload component that comes with Seam should work with IceFaces.
I'm attaching an example project that demostrate the s:fileupload tag within a IceFaces tab. The s:fileupload worked fine until I integrated IceFaces in, but now it doesn't.
--
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
13 years, 11 months