Hi everyone,
I have MDB annotated as follows:
@MessageDriven(activationConfig = {
@ActivationConfigProperty(propertyName = messagingType, propertyValue =
javax.jms.MessageListener),
@ActivationConfigProperty(propertyName = destinationType, propertyValue =
javax.jms.Topic),
Hi everyone,
I am trying to handle the situation when session is expired and user make an
attempt to navigate to some other page within the same application. I tried to
follow documentation and examples (defined exception in exceptions.xml, added
seam filter in web.xml,...) but apparently
Hi everyone,
I have to use topic with durable subscribers which receive messages using
selectors. My is what happens to the messages which neither of the subscribers
want? Do they expire?
Thanks
Ed
View the original post :
Hi everyone,
First of all I love Seam. So far we've built one application of the medium
complexity and experience is very positive.
We have pretty large legacy application which needs to be brought to the new
technology with certain improvements. I can see how most of it could be
implemented
The idea is that we have a set of products. Each of them has a number of
attributes. Each attribute can be marked as searchable which makes them appear
on the product search page. Operator can turn the searchable attribute on and
off at application runtime. Name of the corresponding to the
Hi everyone,
I have many-to-one unidirectional relationship between two objects as follows:
| @Entity
| @Table(name = A)
| public class A implements Serializable {
|
| private Long id;
|
| private B bObject;
|
| @Id
| public Long getId() {
| return id;
|
