It would depend on how you plan to handle the incompatibility.
If the app's source files are going to be updated when the domain
is upgraded to V3 then yes. If you are going to implement some
code to allow the app to run unchanged each time it it started then no.
In either case you should document on the Dashboard how these scenarios
will be handled.
Mitesh Meswani wrote:
> Hi Rebecca,
>
> I could not access the wiki page. My question was, should such changes
> fall in realm of upgrade tool or not?
>
> Thanks,
> Mitesh
>
> Rebecca Searls wrote:
>> Mitesh,
>>
>> These are exactly the types of incompatibility issues that we want
>> to avoid,
>> when making product improvements. These changes break the
>> compatibility
>> requirements agreed upon by the ARCH and articulated in this document
>>
>> http://wiki.glassfish.java.net/Wiki.jsppage=UpgradeCompatibilityRequirements
>>
>>
>>
>> Apps that are deployed in a prior product version that is being
>> upgraded to V3
>> must be able to run in the new product without requiring manual
>> edits by the user.
>> This means V3 CMP and JPA must implement some way to handle this
>> without user intervention.
>> The old style settings do not have to be supported for new apps
>> deployed into V3.
>> Those apps can be required to use the new settings.
>>
>>
>> Mitesh Meswani wrote:
>>> .... I could think of following changes that might be of interest to
>>> upgrade tool.
>>>
>>> 1. We have a backward incompatible change in CMP that I am not sure
>>> whether falls in upgrade tool's realm. We have decided to remove
>>> deprecated element persistence-manager-factory-resource from
>>> domain.xml. If a user's app was using the element from its
>>> sun-ejb-jar.xml, it needs to be changed to point to corresponding
>>> jdbc-resource element. Do you think upgrade tool could/should help
>>> such app?
>>>
>>> 2. We have also changed the default JPA provider from TopLink
>>> Essentials to EclipseLink. User's persistence.xml if referring to
>>> toplink.* properties would need to be changed to use eclipselink.*
>>> properties. Again, do you think upgrade tool could/should help such app?
>>>
>>> Apart from above changes I can not think of any backward incompatible
>>> change from persistence.
>>>
>>> Thanks,
>>> Mitesh
>>>
>>> Rebecca Searls wrote:
>>>> Attached you will find the presentation slides for today.
>>>>
>>>>
>>>> On 07/14/09 16:24, Rebecca Searls wrote:
>>>>>
>>>>> Please join me Thur Jul 16 from 12:00-1:00 PT to learn about
>>>>> the API
>>>>> each module *must* implement to support domain upgrades in V3.
>>>>>
>>>>> V3's design model requires a new way of performing domain
>>>>> upgrades.
>>>>> Modules are required to implement a new service to support
>>>>> domain
>>>>> upgrade functionality. This TOI will present the API that must
>>>>> be implemented, discuss how to test your implementations, and
>>>>> answer your questions.
>>>>>
>>>>> Slides will be available day of the TOI.
>>>>>
>>>>>
>>>>> Date: Thur Jul 16
>>>>> Time: 12:00-1:00 PT
>>>>> Toll-free ( US) 866-545-5227
>>>>> International number 215-446-3648
>>>>> Passcode: 5933769
>>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> Subject:
>>> Removing deprecated element persistence-manager-factory-resource
>>> From:
>>> Mitesh Meswani <mitesh.meswani_at_sun.com>
>>> Date:
>>> Tue, 10 Mar 2009 16:05:31 -0700
>>> To:
>>> Ian Evans <Ian.Evans_at_Sun.COM>, Sreenivas Munnangi
>>> <Sreenivas.Munnangi_at_Sun.COM>, June Parks <June.Parks_at_Sun.COM>, Sherry
>>> Shen <Sherry.Shen_at_Sun.COM>, Ming Zhang <Ming.Zhang_at_Sun.COM>, Raja
>>> Perumal <Raja.Perumal_at_Sun.COM>, Elena Asarina <Elena.Asarina_at_Sun.COM>
>>>
>>> To:
>>> Ian Evans <Ian.Evans_at_Sun.COM>, Sreenivas Munnangi
>>> <Sreenivas.Munnangi_at_Sun.COM>, June Parks <June.Parks_at_Sun.COM>, Sherry
>>> Shen <Sherry.Shen_at_Sun.COM>, Ming Zhang <Ming.Zhang_at_Sun.COM>, Raja
>>> Perumal <Raja.Perumal_at_Sun.COM>, Elena Asarina <Elena.Asarina_at_Sun.COM>
>>> CC:
>>> Jerome Dochez <Jerome.Dochez_at_Sun.COM>, Abhijit Kumar
>>> <Abhijit.Kumar_at_Sun.COM>
>>>
>>>
>>> Hi,
>>>
>>> The element persistence-manager-factory-resource was deprecated since
>>> appserver 9.0
>>> (http://docs.sun.com/app/docs/doc/819-3661/abhdz?l=en&a=view
>>> <http://docs.sun.com/app/docs/doc/819-3661/abhdz?l=en&a=view>). This
>>> element is used by cmp beans to point to jdbc-resource-jndi name. We
>>> are planning to stop supporting this element in V3. This will avoid
>>> extra work for CMP, CLI and admin GUI.
>>>
>>> *What is the impact for you? *
>>> SQE. Samples, CTS, Tutorial::
>>> If you were using this resource from your sun-ejb-jar.xml, you will
>>> need to update it to point to the jdbc-resource directly instead of
>>> indirecting through persistence-manager-factory-resource
>>>
>>> Docs, Tutorial:
>>> We will need to remove reference to it from our documentation.
>>> Possibly add to a section that lists known incompatibility with
>>> previous versions.
>>>
>>> Can you please let us know by end of day Friday March 13 if you see
>>> any issues with the decision. If you are on 'To' list of this mail,
>>> you are a stack holder. Please point to alternate person if you
>>> believe that is wrong.
>>>
>>> Thanks,
>>> Marina and Mitesh
>>>
>>