Pergunta

We were having our application deployed on Websphere Application Server ver 7.x and were using Work and Timer Manager for creating container managed threads and timer respectively.

Now we have to move our application to IBM WebSphere Application Server Community Edition 3.0. During deployment we are facing errors for Work and Time manager entries in our web.xml file. I tried to search on net how to configure these for WASCE but could not find one. I am not even sure that these exists for WASCE or not.

Please inform if there are any resources or you can guide me in correct direction.

The entries in web.xml are as below:

<resource-ref id="ResourceRefBinding_tm">
 <res-ref-name>tm/MYApp_TIMERMANAGER</res-ref-name>
 <res-type>commonj.timers.TimerManager</res-type>
 <res-auth>Container</res-auth>
 <res-sharing-scope>Unshareable</res-sharing-scope>
</resource-ref>

 <resource-ref id="ResourceRefBinding_wm">
      <res-ref-name>wm/MyApp_WORKMANAGER</res-ref-name>
       <res-type>commonj.work.WorkManager</res-type>
      <res-auth>Container</res-auth>
      <res-sharing-scope>Shareable</res-sharing-scope>
   </resource-ref>

Thanks in advance

Foi útil?

Solução

WebSphere Application Server has proprietary implementation of Timer and Work Manager API. This API is covered by JSR 237: Work Manager for Application Servers that was withdrawn and replaced by JSR 236: Concurrency Utilities for JavaTM EE (part of Java EE 7). The API is not included in WebSphere Application Server Community Edition.

For alternatives to Timer Manager please see CommonJ TimerManager versus EJB3 TimerService

Licenciado em: CC-BY-SA com atribuição
Não afiliado a StackOverflow
scroll top