[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1869) Example of Control Set for Quartz SEAM Interation
by Piergiuseppe Spinelli (JIRA)
Example of Control Set for Quartz SEAM Interation
-------------------------------------------------
Key: JBSEAM-1869
URL: http://jira.jboss.com/jira/browse/JBSEAM-1869
Project: JBoss Seam
Issue Type: Task
Components: Examples
Affects Versions: 2.0.0.BETA1
Environment: Any OS. JBoss2_0B project.
Reporter: Piergiuseppe Spinelli
Priority: Optional
The attached sample is an attept to create a control interface to SEAM asynchronous method using Quartz as scheduling engine.
I was asked to do this in the related forum thread: I am not sure it is near to the desired functionalities, but it could be used as a starting point (or possibly as a negative sample).
The sample is very raw and I have used SEAM too short to be sure I did not make to stupid things, but if the idea is useful, I am sure other people will improve it.
Notes:
- The sample use quartz integrated in SEAM as it currently is: a support to asynchronous method
- Quartz is used with its in-memory db, the persistent status is kept by the application usign custom Entities
- Since I am a newby in SEAM, I preferred to make some custom classes for supporting CRUD operations since it was difficult to me to get the SEAM framework to do more that the simple things showed in the samples
TODO:
- it could be better to use some well known components library for the interface instead that my custom controls (i.e Trinidad)
- the entities I made to keep the application status use a table schema very similar to the quartz schema: it could be a good idea in a future to be able to use some entity model over the quartz schema
- it would be usefull to add the feature to upload the classes to be scheduler directly by the web interface, mayby using a classloader chain for supporting hot versioning.
--
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, 6 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-975) constraint by inclusion on remote calls object fields
by Zalder R (JIRA)
constraint by inclusion on remote calls object fields
-----------------------------------------------------
Key: JBSEAM-975
URL: http://jira.jboss.com/jira/browse/JBSEAM-975
Project: JBoss Seam
Issue Type: Feature Request
Components: Remoting
Reporter: Zalder R
Assigned To: Shane Bryzak
Priority: Optional
I think it could be nice to define the fields of the objects returned in a "WebRemote call" with an "include" parameter (instead of the current exclude parameter).
For instance :
now you have :
@WebRemote(exclude = {"secret"})
it would be nice to be able to define :
@WebRemote(include = {"fieldIreallyNeed1", "fieldIreallyNeed2"})
The reasons for this are many :
- security : if the object structure varies over time, you would not want the new fields to be available on the client side by default
- in some cases it's a lot more lightweight (both in the code and in the volume of data sent) to define a minimum set of fields you want instead of the fields you don't want
--
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, 6 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2186) RichFaces loses skin with login-required="true" in pages.xml
by Justin C (JIRA)
RichFaces loses skin with login-required="true" in pages.xml
------------------------------------------------------------
Key: JBSEAM-2186
URL: http://jira.jboss.com/jira/browse/JBSEAM-2186
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 2.0.0.CR3
Environment: Windows XP Professional, Java 1.6_03, JBoss 4.2.1
Reporter: Justin C
Create a new project via seam-gen. Generate some GRUD screens using generate-entities. Folow the seam-gen section in the Reference manual to do this.
Edit pages.xml and set attribute login-required="true" for the <page view-id="*"> node. Do a seam explode and start the appserver.
Access the url for the app, this will direct to the login screen, to say that login is required. Login, and access the CRUD screens.
Logout. Access a CRUD List screen from the menu. This will show a cached screen, not the login screen, as is expected. Refresh the screen from the browser. This directs to the login screen, but the RichFaces CSS skin is gone permamently.
--
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, 10 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, 10 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, 10 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, 10 months