EJB Versioning

Google

Mailing List

Home

Forum Home

JBoss - Java Application Server

Struts - A MVC web framework

Tomcat - JSP/Servlet container

iText - An open source PDF Java Library

JDOM - JDOM XML Parser

J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition

J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog

Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology

JSP - A mailing list about Java Server Pages specification and reference

Struts & Hibernate

Subjects

•	JSP editor plugin for eclipse ?
•	org apache jasper JasperException: Unable to compile class for JSP
•	Tomcat: Connection reset by peer: socket write error
•	Cannot retrieve definition for form bean null
•	Struts Tiles Tutorial (free Struts training)
•	Where do I download Tomcat 4 0 6?
•	Data Access Object (DAO) pattern, example DAO 's
•	Where to download Tomcat v 4 1 24 from?
•	Tomcat 5 0 16 Requested resource not available
•	Oracle Connection Pooling in 3 2 2
•	Servlet : Session invalidate
•	Servlet action is currently unavailable
•	Tomcat/Struts Unicode Encoding/Decoding problems
•	Tomcat and webapplication specific java library path
•	Running a Simple JMS Example
•	Mapping in workers2 properties
•	org apache jasper JasperException
•	Cannot find message resources under key org apache struts action MESSAGE
•	problem with html:text bean throwing exception
•	Cannot find message resources under key org apache struts action MESSAGE
•	invalid direct reference problem with solution
•	Tool for jsp debug Try Sysdeo Eclipse Plugin
•	Tomcat 5 Cannot load JDBC driver class 'null ' SQL state: null
•	weblogic ejbc
•	java properties file
•	Jboss 3 2 3 Coyote Can 't re
•	Tomcat 5, Apache2 and mod jk2 integration problem
•	JBoss example problem new to J2EE
•	url string for connecting jboss to oracle
•	Value attribute of <html:checkbox
•	javax servlet ServletException: BeanUtils populate
•	HTTP Status 404 The requested resource is not available
•	5 0 18: Windows XP Pro vs Windows 2000

EJB Versioning

EJB Versioning

2003-11-05 - By Koscho, William

Back

Reply: 1 2 3

I would like to be able to deploy multiple versions of an EJB, and have
multiple clients select the version that want to use.

For example, I would like to deploy version 1.0 of Bean1 and version 1.1 of
Bean1? Then have Client1 choose version 1.0 and Client2 choose version 1.1.

Can the container handle multiple versions of the same bean?

Assuming it cannot and we can only deploy a single version of the bean (i.e.
version 1.1 of Bean1), then I can have an env entry in the deployment
description with a "VersionNumber" variable. Then the client can check that
environment variable once it receives the interface to the bean.

Once it has the version number, I am looking for a pattern to apply that
will allow the client to behave differently based on that version. For
example, when the client sees version 1.0 it displays the default screen,
but when it sees version 1.1, it will call an additional method on the EJB
and display an extra combo-box on the UI.

Any help is greatly appreciated.

Thanks,

Bill Koscho

Technical Specialist, Customer Service Development

Medco Health Solutions

Email: william_koscho@(protected)

Pager: 1-800-759-8888 PIN: 1781595

Phone: 201-269-2219

-- ---- ---- ---- ---- ---- ---- ---- ---
This e-mail message and any attachments contain confidential information from
Medco Health Solutions, Inc. If you are not the intended recipient, you are
hereby notified that disclosure, printing, copying, distribution, or the taking
of any action in reliance on the contents of this electronic information is
strictly prohibited. If you have received this e-mail message in error, please
immediately notify the sender by reply message and then delete the electronic
message and any attachments.

====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
<html>

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">

<meta name=Generator content="Microsoft Word 10 (filtered)">

<style>

</style>

</head>

<body lang=EN-US link=blue vlink="#606420">

<div class=Section1>

I would like to be able to deploy multiple versions of an
EJB, and have multiple clients select the version that want to use.

 

For example, I would like to deploy version 1.0 of Bean1 and
version 1.1 of Bean1?  Then have Client1 choose version 1.0 and Client2
choose version 1.1.

Can the container handle multiple versions of the same bean?


 

Assuming it cannot and we can only deploy a single version
of the bean (i.e. version 1.1 of Bean1), then I can have an env entry in the
deployment description with a "VersionNumber" variable.  Then
the client can check that environment variable once it receives the interface
to the bean.  

 

Once it has the version number, I am looking for a pattern
to apply that will allow the client to behave differently based on that
version.  For example, when the client sees version 1.0 it displays the
default screen, but when it sees version 1.1, it will call an additional method
on the EJB and display an extra combo-box on the UI.

 

Any help is greatly appreciated.

 

Thanks,

 

Bill Koscho


Technical Specialist, Customer Service
Development

Medco Health Solutions

Email: william_koscho@(protected)

Pager: 1-800-759-8888 PIN: 1781595

Phone: 201-269-2219

 

</div>

</body>

</html>

<HTML><BODY><hr size=1>This e-mail message and any
attachments contain confidential information from Medco Health Solutions, Inc.
If you are not the intended recipient, you are hereby notified that disclosure,
printing, copying, distribution, or the taking of any action in reliance on the
contents of this electronic information is strictly prohibited. If you have
received this e-mail message in error, please immediately notify the sender by
reply message and then delete the electronic message and any attachments.</BODY></HTML>
====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)