This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 53372 - Topic can't be deployed without changes
Summary: Topic can't be deployed without changes
Status: CLOSED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 8 (show other bugs)
Version: 4.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: Rajeshwar Patil
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-13 17:57 UTC by Petr Blaha
Modified: 2006-03-24 13:06 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Blaha 2005-01-13 17:57:04 UTC
user's feedbeack from nbj2ee:
If the MDB a durable subscriber, then the clientId
and subscriptionName 
> properties must also be specified as an
activation config property. 
> Currently these properties are missing from both
generated deployment 
> descriptor. I mean, it would be enough to find a
complet activation 
> configuration in any of the two descriptor  
(sun-ejb-jar.xml or 
> ejb-jar.xml) file, but neither have one.
> 
> The generated server resource entry for
registering a 
> javax.jms.ToppicConnectionFactory JMS resource
should also have an extra 
> property: ClientId.
> 
> It would be nice to have these items with some
proper names.
> 
> Otherwise I think that it was a wise decision to
choice durable 
> subscriber topic as a default generated topic
bean, because this seems 
> to be the most complicated one. If you know how
to set up a durable 
> subscriber topic bean, then a non durable topic
deployment will be easy 
> as pie.
> 
> I'am afraid, the easyiest way to solve the
problem of right-away 
> deployability to change the
subscriptionDurability to NonDurable.
Comment 1 Petr Blaha 2005-02-07 16:49:37 UTC
This issue should be fixed in Beta.
Comment 2 _ ludo 2005-02-17 05:12:16 UTC
need for 4.1
Comment 3 Rajeshwar Patil 2005-03-04 19:19:23 UTC
two ways to solve this, as the user suggested; On Topic bean creation
create bean with  --
   1) durable subscription  or
   2) non-durable subscription

If we choose first(which is what we are doing now), then we need
additional  entries in DDs (ClientID & Subcription Name). These
entries can be obtained by the Wizard or can be generated silently
based on bean name.

If we choose second, we need to change subscription type in ejb-jar DD.


I am not sure which type (durable or non-durable) is more commonly used ?


Comment 4 Petr Blaha 2005-03-07 09:48:31 UTC
I think that we should use durable subscription. This type is safer
for J2EE application. If an durable MDB listener goes down, that MDB
will not miss the message.
Comment 5 Rajeshwar Patil 2005-03-09 20:31:32 UTC
Modified Files:
src/org/netbeans/modules/j2ee/ejbjarproject/ejb/wizard/mdb/MessageGenerator.java 
new revision: 1.9; previous revision: 1.8
Comment 6 Petr Blaha 2005-03-15 15:06:09 UTC
Build 20050314