Seam-gen places components.properties on the WAR root, which isn't on the classpath (although it should be available to the servlet context)
--------------------------------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-3499
URL: https://jira.jboss.org/jira/browse/JBSEAM-3499
Project: Seam
Issue Type: Bug
Components: Core, Tools
Reporter: Pete Muir
Fix For: 2.1.0.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
Add flush attribute to @End annotation
--------------------------------------
Key: JBSEAM-3005
URL: http://jira.jboss.com/jira/browse/JBSEAM-3005
Project: Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.1.0.A1, 2.0.2.GA
Reporter: Dan Allen
Priority: Minor
Fix For: 2.1.0.GA
The @End annotation should support the flush attribute to complement the flushMode attribute on the @Begin annotation. While there may be cases to perform bean-managed flushing, it makes sense to allow this to be specified declaratively, especially for simple cases. The flushing would need to occur in the ConversationInterceptor.
--
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
End current conversation and begin a new one
--------------------------------------------
Key: JBSEAM-3504
URL: https://jira.jboss.org/jira/browse/JBSEAM-3504
Project: Seam
Issue Type: Feature Request
Components: Core
Affects Versions: The future
Reporter: Stuart Douglas
Add a convience method to Conversation that allows a user to end and then begin a new conversation:
Conversation.instance().end();
Manager.instance().initializeTemporaryConversation();
Conversation.instance().begin();
Possibly add annotations/pages.xml to support this as well
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
chatroom example allow users not connected to post messages as user "null>"
---------------------------------------------------------------------------
Key: JBSEAM-2953
URL: http://jira.jboss.com/jira/browse/JBSEAM-2953
Project: Seam
Issue Type: Bug
Components: Examples
Affects Versions: 2.0.2.CR2
Reporter: Jay Balunas
Priority: Minor
Deploy the remoting/chatroom example. You can send a message even if not connected and it will show as user: "null>".
--
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
remoting/helloworld example still processes even if you select "cancel"
-----------------------------------------------------------------------
Key: JBSEAM-2954
URL: http://jira.jboss.com/jira/browse/JBSEAM-2954
Project: Seam
Issue Type: Bug
Components: Examples
Affects Versions: 2.0.2.CR2
Reporter: Jay Balunas
Priority: Minor
When you launch the remoting helloworld example you have the option of selecting "ok" or "cancel" on the popup box.
If you hit cancel it will still process but with "null" for a string.
--
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
New Permission annotations works only on method level
------------------------------------------------------
Key: JBSEAM-3352
URL: https://jira.jboss.org/jira/browse/JBSEAM-3352
Project: Seam
Issue Type: Bug
Components: Security
Affects Versions: 2.1.0.BETA1
Reporter: Vinicius Carvalho
Priority: Minor
The new permission annotations (@PermissionUser,@PermissionRole) are working only when methods gets annotated with them. The problem is on the AnnotatedBeanProperty class which checks for
public static AnnotatedBeanProperty scanForProperty(Class cls, Class<? extends Annotation> annotation)
{
for (Field f : cls.getFields())
{
if (f.isAnnotationPresent(annotation))
{
return new AnnotatedBeanProperty(f, f.getAnnotation(annotation));
}
}
It should be cls.getDeclaredFields() since f.getFields only returns public fields.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Specify which transaction instance to use on the @Transactional annotation
--------------------------------------------------------------------------
Key: JBSEAM-3496
URL: https://jira.jboss.org/jira/browse/JBSEAM-3496
Project: Seam
Issue Type: Feature Request
Affects Versions: 2.1.0.CR1
Environment: non JTA environment
Reporter: Scott Olcott
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
wicket example - some field values are forgotten
------------------------------------------------
Key: JBSEAM-3469
URL: https://jira.jboss.org/jira/browse/JBSEAM-3469
Project: Seam
Issue Type: Bug
Components: Examples
Affects Versions: 2.1.0.CR1
Environment: java 6, jboss 4.2.3.GA
Reporter: Marek Novotny
Assignee: Pete Muir
Priority: Minor
1. Login as registered user
2. Search any hotel
3. Book it and fill all required form fields and click on Book button
4. On confirmation page go back with clicking Revise button.
Field values for Room preference and Credit Card Expiry year are forgotten.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://jira.jboss.org/jira/browse/JBSEAM-164?page=com.atlassian.jira.plu... ]
Pete Muir updated JBSEAM-164:
-----------------------------
Fix Version/s: 2.1.1.CR1
(was: The future)
> Kill all conversations
> ----------------------
>
> Key: JBSEAM-164
> URL: https://jira.jboss.org/jira/browse/JBSEAM-164
> Project: Seam
> Issue Type: Feature Request
> Components: Core
> Reporter: Gavin King
> Fix For: 2.1.1.CR1
>
> Attachments: kill-all-other-conversations.diff, seam-endall-patch-v1.diff
>
>
> Users want an operation to kill all conversations, and they want that to happen in the same action as beginning a new conversation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
dvdstore example readme.txt needs to be updated with infor about tomcat+jboss-embedded
--------------------------------------------------------------------------------------
Key: JBSEAM-3477
URL: https://jira.jboss.org/jira/browse/JBSEAM-3477
Project: Seam
Issue Type: Task
Reporter: Marek Novotny
Priority: Minor
readme.txt says that dvdstore example runs on Jboss and tomcat, but it runs in Tomcat only with jboss-embedded installed in tomcat.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira