[JBoss JIRA] Created: (JBSEAM-4512) BPM task does not rollback
by Jason E (JIRA)
BPM task does not rollback
--------------------------
Key: JBSEAM-4512
URL: https://jira.jboss.org/jira/browse/JBSEAM-4512
Project: Seam
Issue Type: Bug
Components: BPM
Affects Versions: 2.2.0.GA
Environment: Testing this on Windows XP. Deploying to JBoss AS 4.2.2
Reporter: Jason E
I have made a simple change to the ShipAction.java class in the dvdstore example that ships with Seam. Here is the change
//@EndTask
public String ship() {
order.ship(track);
TaskInstance ti = ManagedJbpmContext.instance().getTaskInstance(taskInstance.getId());
taskInstance.end();
if(true) throw new RuntimeException("TESTING");
return "admin";
}
I commented out the end task annotation and I am ending the task via the TaskInstance API. When I throw the Runtime exception the changes to the ORDERS entity bean (i.e. updating the tracking number) rolls back. The problem is that the task instance change (i.e. ending the task) does not rollback. It appears that jBPM is flushing its changes in another db transaction. This seems like a bug since I would expect the ending of my task to also rollback. This seems like the desired behavior.
This was the only change I made to the dvdstore example that ships with Seam 2.2.0.GA so it should be easy to reproduce.
Thanks!
Jason
--
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
12 years, 4 months
[JBoss JIRA] Created: (SEAMSECURITY-86) Scheme setting for pages in @ViewConfig
by Bill Elliot (JIRA)
Scheme setting for pages in @ViewConfig
---------------------------------------
Key: SEAMSECURITY-86
URL: https://issues.jboss.org/browse/SEAMSECURITY-86
Project: Seam Security
Issue Type: Feature Request
Affects Versions: 3.0.0.Final
Reporter: Bill Elliot
Is there a way in Seam 3 to do like in the Page definitions of Seam 2 to specify the Scheme (HTTP/HTTPS) to use for a specific page? I need to be able to place the login and password changing screens into HTTPS for increased security and best practices. This could likely be done in the Pages definition under a @ViewConfig. Possibly adding a new annotation @Scheme("HTTPS").
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (SEAMINTL-70) Document usage of BundleTemplateMessage/TemplateMessage
by Gerald Turner (Created) (JIRA)
Document usage of BundleTemplateMessage/TemplateMessage
-------------------------------------------------------
Key: SEAMINTL-70
URL: https://issues.jboss.org/browse/SEAMINTL-70
Project: Seam International
Issue Type: Feature Request
Components: Messages
Affects Versions: 3.1.0.Beta3
Reporter: Gerald Turner
Assignee: Ken Finnigan
Priority: Optional
As a user, the current documentation is sufficient for severity+text messages, however on closer inspection of the Message class, I see that detail and targets properties are available, much like FacesMessage.
I dug around the seam-international source and experimented with a bean having fields/method like the following:
@Inject
private Messages messages;
@Inject
private transient TemplateMessage message;
public void doSometing() {
messages.add(message.level(Level.WARN).text("Text {0}, {1}, {2}").textParams('a', 'b', 'c').detail("Detail {0}, {1}, {2}").detailParams(1, 2, 3).targets("message").build());
messages.add(message.level(Level.FATAL).text("Fatality!").targets("message").build());
}
This works. A few caveats:
* TemplateMessage field has to be marked transient, otherwise get WELD error during deployment about Serializable bean having non-Serializable field.
* Make sure to call add(Message) signature (invoke build()) instead of add(MessageBuilder), otherwise only the most recent message is added.
* doSomething method is not reentrant/thread-safe because of the builder.
I'd prefer to use Messages instead of the builders, perhaps have a methods like info(String text, String details, String targets, Object... args), however that gets ugly with the varargs, having to cast Object[], etc. Perhaps I should stick with FacesMessages.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] Created: (SEAMINTL-57) Select Message Interface by Locale
by Ken Finnigan (JIRA)
Select Message Interface by Locale
----------------------------------
Key: SEAMINTL-57
URL: https://issues.jboss.org/browse/SEAMINTL-57
Project: Seam International
Issue Type: Enhancement
Components: Locales, Messages
Reporter: Ken Finnigan
Assignee: Ken Finnigan
If a developer Injects a message interface and then does BlahMessages.helloWorld("Brian"); how does that become localized to either the App locale or the Client locale?
For App locale, could specify developer adds @Locale('fr') to message interface injection point
For Client locale, above approach doesn't work. Need to have a wrapper class around the various locale specific message interfaces that the developer would inject to use, and then when called would call the appropriate locale specific version.
Something like:
class MessagesWrapper<BlahMessage> {}
with a way to specify which locales are supported in that wrapper, so it knows possible locale specific interfaces it would require, and then it uses the @Client @Locale to retrieve the correct localized message
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months