springframework-developer — Spring Framework developers list

[Springframework-developer] Oracle 8 and OracleLobHandler

[Mike Cannon-B. <mca...@gm...>]

Hey guys,

We have some users reporting problems with Spring's OracleLobHandler
combined with Oracle 8. Is this a known problem? Does it only work
with Oracle 9+? Has anyone tried it with 8?

Any quick advice before we start digging a lot deeper would be most appreciated.

Cheers,
Mike
--
ATLASSIAN - http://www.atlassian.com

RE: [Springframework-developer] WLS 7 and TX suspend/resume - continue.

[<jue...@we...>]

Eugene,
=20
We have such autodetection in a variety of places, for example =
HibernateTransactionManager and JdoPersistenceManager which autodetect =
an underlying DataSource, to be able to expose Hibernate respectively =
JDO transactions as JDBC transactions. As of 1.1 final, those =
autodetection mechanisms can be turned off too, but we've explicitly =
been asked to autodetect by default.
=20
While I do see that autodetection of the JTA TransactionManager might =
not be desirable on WebLogic 7.0, I don't think that this a big deal: =
Simply turn it off via the "autodetectTransactionManager" flag. On a =
variety servers, autodetection eases configuration, as there is no need =
for server-specific configuration in that case. Frankly, if that =
autodetection on WebLogic 7 is the biggest issue that we have to worry =
about, I'm more than happy.
=20
Regarding auto-adapting to the J2EE server version and choosing an =
appropriate lookup strategy: We don't do that in other places either, =
currently: for example, NativeJdbcExtractors for a specific connection =
pool. We do have a simple strategy that works on many connection pool =
there: SimpleNativeJdbcExtractor, fetching the native connection via =
con.getMetaData().getConnection() - but that one still has to be =
explicitly specified.
=20
So in some respect, Spring is currently not designed to autodetect =
everything for you, but rather to make it easy for you to plug in =
appropriate strategies. You can easily factor the JtaTransactionManager =
definition out into its own XML bean definition file, or define a =
variety of combinations that are all marked as lazy-init, plugging a =
specific one in via a ${...} placeholder for the target reference of =
transaction proxies. There's a variety of options, actually.
=20
Auto-adapting to the J2EE server is not that trivial because it incurs a =
check for specific server versions: On WebLogic 8.1, use a default =
WebLogicJtaTransactionManager; on WebLogic 7.0, use a =
WebLogicJtaTransactionManager with =
WebLogicServerTransactionManagerFactoryBean. It's certainly *possible*, =
but it has to be discussed whether it's *desirable* as part of Spring.
=20
As a side note, Hibernate doesn't autodetect the J2EE server either, but =
rather requires you to explicitly specify an appropriate =
TransactionManagerLookup as Hibernate property. Kodo JDO on the other =
hand autodetects, if I'm not mistaken. Don't get me wrong: We might =
introduce such auto-adaption at a later point of time. It's just not =
that crucial, IMHO; in particular, it's no reason to defer 1.1 final.
=20
Juergen
=20

________________________________

From: spr...@li... on behalf of =
Eugene Kuleshov
Sent: Sun 05/09/2004 16:24
To: spr...@li...
Subject: Re: [Springframework-developer] WLS 7 and TX suspend/resume - =
continue.



j=FCrgen h=F6ller [werk3AT] wrote:

> I agree that it might not be following the intent of every J2EE vendor =
out
> there. However, it is still not too far-fetched to consider the JTA
> TransactionManager as a kind of extension to the UserTransaction =
interface:
> If a vendor's UserTransaction object implements the TransactionManager
> interface too, it usually should be fully usable, else the vendor =
should
> just provide a facade that solely implements UserTransaction...

   That is not my point. The point is if user is passing property A, why =
it
should affect property B anyway? If he need to do something about B, why =
not
to use that B at the first place (e.g. since it is all reflection, you =
can
pass UserTransaction instance to TansactionManager setter, which will be =
more
straightforward).

> Anyway, we can't easily turn off that autodetection by default, as =
some
> Spring users might rely on it. It also works nicely for a number of
> containers, for example Resin, Orion (OC4J), JOnAS (JOTM). And you can =
turn
> off autodetection now, via the "autodetectTransactionManager" flag,
> although the only case I know of where that is appropriate is the =
default
> JtaTransactionManager on WebLogic.

   It doesn't matter where it works. It looks like ugly hack anyway. :-)

> Regarding full autodetection of the J2EE server: While that certainly =
is
> achievable, it's not as straightforward as it may seem at first =
glance.

   Why is that?

> Migration between J2EE servers shouldn't be too hard anyway, as it =
just
> affects the JtaTransactionManager definition: The rest of the =
application
> can stay exactly the same. We currently leave it to the user to =
configure
> the JtaTransactionManager appropriately, and just include support =
classes
> for all sorts of cases.

   I didn't say it is hard, it just lead to multiple spring contexts - =
one per
each application server and so far it is the only place where you have =
to do this.

   regards,
   Eugene


________________________________
>
> Von: spr...@li... im Auftrag =
von
> Eugene Kuleshov Gesendet: So 05.09.2004 05:06 An:
> spr...@li... Betreff: Re:
> [Springframework-developer] WLS 7 and TX suspend/resume - continue.
>
>
>
> j=FCrgen h=F6ller [werk3AT] wrote:
>
>
>> Thanks, Thomas - it's great to have this for 1.1 final!
>>
>> Did you have a chance to check whether WebLogic 8.1's UserTransaction
>> object found at "java:comp/UserTransaction" implements the
>> javax.transaction.TransactionManager interface too? It does so on
>> WebLogic 7.0. The benefit of such a scenario is that Spring's
>> JtaTransactionManager will autodetect the TransactionManager, without =
any
>> special setup.
>
>
> This autodetect feature looks like a half baked solution (or dirty =
hack).
> You souldn't really rely on the fact that vendor choose to implement =
both
> interfaces in publically available instance.
>
> If you want to have smart tx proxy, it should autodetect j2ee =
container
> vendor and version and then choose right way to retrieve tx proxy. Of
> course it has to be tested carefuly for each environment, but then =
users
> can really trust Spring's tx management and can use it without =
struggling
> with configuration for each environment type. That will also simplify
> moving application from one container to another (e.g. from Weblogic =
to
> Websphere).
>
>
>> I've documented the basic JTA setup options for popular J2EE servers =
in
>> JtaTransactionManager's javadoc. It would be good to verify whether =
my
>> autodetection comment just applies to WebLogic 7.0 or also to =
WebLogic
>> 8.1.
>
>
>
>
> regards, Eugene
>
>
>
>
>
>> ________________________________
>>
>> Von: spr...@li... im Auftrag =
von
>>  Thomas Risberg Gesendet: Sa 04.09.2004 17:42 An:
>> spr...@li... Betreff: Re:
>> [Springframework-developer] WLS 7 and TX suspend/resume - continue.
>>
>>
>>
>> Juergen, Eugene,  Dimitry, all WLS 70 users,
>>
>> We now have a new WebLogicServerTransactionManagerFactoryBean.  This =
bean
>>  factory looks up the ServerTransactionManagerImpl to get around the =
NPE
>> that was thrown during a "forceResume".  I based the code on the
>> WebSphere variant.  This has been tested on WebLogic 7.0 SP5 and =
checked
>> in.  Here is a snippet from the configuration I tested with:
>>
>> <!--  transaction manager --> <bean id=3D"wls7tm"
>>
>> =
class=3D"org.springframework.transaction.jta.WebLogicServerTransactionMan=
agerFactoryBean"/>
>>  <bean id=3D"transactionManager"
>>
>> =
class=3D"org.springframework.transaction.jta.WebLogicJtaTransactionManage=
r">
>>  <property name=3D"transactionManager"> <ref local=3D"wls7tm"/> =
</property>
>> </bean>
>>
>> Thomas
>>
>>
>> Thomas Risberg wrote:
>>
>>
>>
>>> Juergen,
>>>
>>> I'll try to implement and test a
>>> WebLogicServerTransactionManagerFactoryBean today.  I'll keep you
>>> posted.
>>>
>>>
>>> For WLS 8.1 the TxHelper.getTransactionManager method is marked as
>>> deprecated even though it is not documented as such in the JavaDocs.
>>> There is also a brand new method getClientTransactionManager for 8.1
>>> that is starting out marked as deprecated.  Go figure.  We are =
probably
>>> better off recommending the JNDI lookups for 8.1.
>>>
>>> Thomas
>>>
>>>
>>>
>>> j=FCrgen h=F6ller [werk3AT] wrote:
>>>
>>>
>>>
>>>> Thanks, Thomas! This means that there *is* a way to make it work on
>>>> WebLogic 7! Eugene, Dmitri, your pain finally has an end! :-)
>>>>
>>>> Regarding obtaining the TransactionManager via the TxHelper on
>>>> WebLogic 7: That can easily be factored out into a custom
>>>> FactoryBean, like we did for WebSphere (see
>>>> WebSphereTransactionManagerFactoryBean), to be passed into
>>>> JtaTransactionManager's respectively =
WebLogicJtaTransactionManager's
>>>> "transactionManager" property. So we don't need a further
>>>> JtaTransactionManager subclass for this, just a further
>>>> TransactionManager lookup strategy.
>>>>
>>>> BTW, Dmitri told me that the WebLogic UserTransaction object at
>>>> "java:comp/UserTransaction" implements the TransactionManager
>>>> interface too, but that obviously forceResume doesn't work there... =
I
>>>> assume the ClientTransactionManagerImpl is returned there, not the
>>>> ServerTransactionManagerImpl.
>>>>
>>>> If we can double-check that this works better than the
>>>> TransactionManager fetched from JNDI, I suggest to add a
>>>> WebLogicServerTransactionManagerFactoryBean (or a similar name),
>>>> clearly documenting that this is meant as an alternative to the
>>>> standard JNDI TransactionManager reference that WebLogic provides,
>>>> mainly for WebLogic 7. I wouldn't mind to do this even for the 1.1
>>>> final release tomorrow...
>>>>
>>>> Is the TxHelper lookup available on WebLogic 8.1 too? Of course, it
>>>> shouldn't be necessary there, as the standard JNDI =
TransactionManager
>>>>  reference will work too. I just wonder whether it's available and
>>>> would work in principle: People could then configure a
>>>> WebLogicServerTransactionManagerFactoryBean to be able to deploy on
>>>> both WebLogic 7 and WebLogic 8, without adapting their Spring
>>>> configuration.
>>>>
>>>> Of course, such a WebLogicServerTransactionManagerFactoryBean would
>>>> have to be coded via reflection to avoid compile-time dependencies =
on
>>>>  WebLogic, analogous to WebSphereTransactionManagerFactoryBean. Do
>>>> you have the chance to do this before tomorrow, Thomas?
>>>>
>>>> Juergen
>>>>
>>>>
>>>> ________________________________
>>>>
>>>> Von: spr...@li... im =
Auftrag
>>>>  von Thomas Risberg Gesendet: Sa 04.09.2004 14:30 An:
>>>> spr...@li... Betreff: Re:
>>>> [Springframework-developer] WLS 7 and TX suspend/resume - continue.
>>>>
>>>>
>>>>
>>>> I have done some additional testing for this issue and this is what =
I
>>>>  have found.
>>>>
>>>> WebLogic exposes a client TransactionManager implementation via =
JNDI
>>>> (weblogic.transaction.internal.ClientTransactionManagerImpl) and in
>>>> WLS 7.0 it is throwing an NPE when you call forceResume (with or
>>>> without a suspended transaction that has been marked for
>>>> RollbackOnly).
>>>>
>>>> They also have a different server implementation
>>>> (weblogic.transaction.internal.ServerTransactionManagerImpl) that =
is
>>>> returnd by a call to TxHelper.getTransactionManager().  With this =
TM
>>>> the force resume works as expected.
>>>>
>>>> So the workaround for now is to do the suspend/resume using the TM
>>>> returned by TxHelper before calling the Spring managed code.
>>>> Alternatively we could provide a WebLogic7JtaTransactionManager =
that
>>>> uses this method of obtaining the TM.
>>>>
>>>> I doubt that BEA will fix this issue in WLS 7.0.  They will =
probably
>>>> suggest to upgrade to 8.1 or use the TxHelper to obtain the TM.
>>>>
>>>> Thomas
>>>>
>>>>
>>>> j=FCrgen h=F6ller [werk3AT] wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> Ideally, WebLogic should work properly with standard JTA
>>>>> TransactionManager resume in all cases, not needing the =
proprietary
>>>>>  forceResume call. However, the least we can expect is that
>>>>> forceResume works properly: You could send a corresponding bug
>>>>> report to BEA, for WebLogic 7.0. However, they might tell you that
>>>>> they fixed the issue in WebLogic 8.1...
>>>>>
>>>>> Juergen
>>>>>
>>>>>
>>>>> ________________________________
>>>>>
>>>>> Von: spr...@li... im
>>>>> Auftrag von j=FCrgen h=F6ller [werk3AT] Gesendet: Fr 03.09.2004 =
23:31
>>>>> An: spr...@li... Betreff: Re:
>>>>> [Springframework-developer] WLS 7 and TX suspend/resume - =
continue.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> As I already wrote in my JIRA comments: Many thanks for your
>>>>> efforts, Dmitri!
>>>>>
>>>>> I assume that with JtaTransactionManager, you'll get an
>>>>> IllegalStateException ("cannot resume rollback-only transaction" =
or
>>>>>  the like), and with WebLogicJtaTransactionManager, you'll get the
>>>>> NPE in WebLogic code?
>>>>>
>>>>> This really seems to be a bug in WebLogic 7.0... At least it =
should
>>>>>  work properly as long as not suspending a transaction that has
>>>>> been marked as rollback-only.
>>>>>
>>>>> Juergen
>>>>>
>>>>>
>>>>> ________________________________
>>>>>
>>>>> Von: spr...@li... im
>>>>> Auftrag von Dmitri Maximovich Gesendet: Fr 03.09.2004 23:07 An:
>>>>> spr...@li... Betreff:
>>>>> [Springframework-developer] WLS 7 and TX suspend/resume - =
continue.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> I just tried WLS 7 with Spring 1.1rc2 and BMT transaction
>>>>> demaraction. It doesn't work with standard JtaTransactionManager =
or
>>>>>  with WeblogicJtaTransactionManager, so something fundamentally
>>>>> broken in WLS7 (same NPE as described in JIRA SPR-251). Next I'll
>>>>> try to use WLS TransactionManager (exposed in JNDI) to
>>>>> suspend/resume transaction without Spring to see it it's going to
>>>>> work.
>>>>>



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=3D5047&alloc_id=3D10808&op=3Dclick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] Spring Framework 1.1 final released

[Thomas R. <tho...@tr...>]

I just updated the website's JavaDocs and the DTD - I think that's it 
for this release.

Thomas


Colin Sampaleanu wrote:

> I've updated the web site docs, and posted announcements on the web 
> site, forums and springframework.com.
>
>
> jürgen höller [werk3AT] wrote:
>
>> Dear Spring community,
>>
>> I'm pleased to announce that Spring 1.1 final has just been released. 
>> Since 1.1 RC2, some API clarifications have happened and a number of 
>> bugs have been fixed. There is also a variety of minor new features:
>>
>> * reworked BeanWrapperImpl's property-specific custom editor handling 
>> to allow registration for uninitialized subpaths
>> * added "applyBeanPropertyValues" method to 
>> AutowireCapableBeanFactory, for populating an existing bean instance
>>
>> * added "(abstract)" marker for properties bean definitions 
>> respectively "abstract" attribute for XML bean definitions
>>
>> * added support for SqlReturnType interface which allows to return 
>> custom types from stored procedures
>> * added auto-conversion of java.util.Date and java.util.Calendar to 
>> java.sql.Date/Time/Timestamp for JDBC parameters
>> * added support for WebSphere 4 to WebSphereNativeJdbcExtractor, 
>> autodetecting WebSphere 5 and 4 now
>>
>> * added WebLogicServerTransactionManagerFactoryBean, to be used with 
>> WebLogicJtaTransactionManager on WebLogic 7.0
>> * added support for direct JTA synchronization to AbstractLobType, as 
>> alternative to Spring transaction synchronization
>> * added "flush" method to HibernateOperations/HibernateTemplate and 
>> JdoOperations/JdoTemplate, for eager flushing
>> * added "getReportQueryIteratorByQuery" method to OJB 
>> PersistenceBrokerOperations and PersistenceBrokerTemplate
>>
>> * deprecated AbstractJndiLocator base class in favor of new 
>> JndiObjectLocator base class with explicit "lookup" method
>> * added JndiObjectTargetSource which performs a fresh JNDI lookup for 
>> each call, allowing for hot redeployment in JNDI
>> * added "cache" flag to JndiDestinationResolver, to allow for turning 
>> off the caching of Destination objects from JNDI
>> * added support for ObjectMessage to SimpleMessageConverter, 
>> converting between Serializable objects and ObjectMessages
>>
>> * added RemoteConnectFailureException and 
>> RemoteLookupFailureException as RemoteAccessException subclasses
>> * added JndiRmiServiceExporter, JndiRmiClientInterceptor, 
>> JndiRmiProxyFactoryBean (for RMI-IIOP resp. CORBA)
>> * added "lookupStubOnStartup", "cacheStub" and 
>> "refreshStubOnConnectFailure" flags to RmiClientInterceptor
>> * added "lookupHomeOnStartup" and "refreshHomeOnConnectFailure" flags 
>> to AbstractRemoteSlsbInvokerInterceptor
>>
>> * added "createMimeMessage(InputStream)" method to JavaMailSender, 
>> building a MimeMessage from raw MIME content
>> * MimeMessageHelper creates "multipart/related" now, to make mails 
>> with inline images compatible with Outlook Express
>> * added "validateAddresses" property to MimeMessageHelper (off by 
>> default), delegating to JavaMail 1.3's "validate"
>>
>> * added "http10Compatible" flag to RedirectView, to be turned off for 
>> sending HTTP 1.1 status code 303 rather than 302
>> * added "buildPdfMetadata" callback to AbstractPdfView, for adding 
>> meta fields like author to the iText PDF Document
>> * added LookupDispatchActionSupport class to Struts support, 
>> analogous to ActionSupport but for LookupDispatchActions
>>
>> As usual, see the changelog for details. Note that the 1.1 code base 
>> contains minor changes in various SPIs which are not 
>> backwards-compatible. The API as typically used in applications is as 
>> close to 100% compatible as possible, though.
>>
>> Regards,
>>
>> Juergen
>>
>>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>

Re: [Springframework-developer] Spring Framework 1.1 final released

[Colin S. <col...@ex...>]

I've updated the web site docs, and posted announcements on the web 
site, forums and springframework.com.


jürgen höller [werk3AT] wrote:

>Dear Spring community,
> 
>I'm pleased to announce that Spring 1.1 final has just been released. Since 1.1 RC2, some API clarifications have happened and a number of bugs have been fixed. There is also a variety of minor new features:
> 
>* reworked BeanWrapperImpl's property-specific custom editor handling to allow registration for uninitialized subpaths
>* added "applyBeanPropertyValues" method to AutowireCapableBeanFactory, for populating an existing bean instance
>
>* added "(abstract)" marker for properties bean definitions respectively "abstract" attribute for XML bean definitions
> 
>* added support for SqlReturnType interface which allows to return custom types from stored procedures
>* added auto-conversion of java.util.Date and java.util.Calendar to java.sql.Date/Time/Timestamp for JDBC parameters
>* added support for WebSphere 4 to WebSphereNativeJdbcExtractor, autodetecting WebSphere 5 and 4 now
>
>* added WebLogicServerTransactionManagerFactoryBean, to be used with WebLogicJtaTransactionManager on WebLogic 7.0
>* added support for direct JTA synchronization to AbstractLobType, as alternative to Spring transaction synchronization
>* added "flush" method to HibernateOperations/HibernateTemplate and JdoOperations/JdoTemplate, for eager flushing
>* added "getReportQueryIteratorByQuery" method to OJB PersistenceBrokerOperations and PersistenceBrokerTemplate
>
>* deprecated AbstractJndiLocator base class in favor of new JndiObjectLocator base class with explicit "lookup" method
>* added JndiObjectTargetSource which performs a fresh JNDI lookup for each call, allowing for hot redeployment in JNDI
>* added "cache" flag to JndiDestinationResolver, to allow for turning off the caching of Destination objects from JNDI
>* added support for ObjectMessage to SimpleMessageConverter, converting between Serializable objects and ObjectMessages
>
>* added RemoteConnectFailureException and RemoteLookupFailureException as RemoteAccessException subclasses
>* added JndiRmiServiceExporter, JndiRmiClientInterceptor, JndiRmiProxyFactoryBean (for RMI-IIOP resp. CORBA)
>* added "lookupStubOnStartup", "cacheStub" and "refreshStubOnConnectFailure" flags to RmiClientInterceptor
>* added "lookupHomeOnStartup" and "refreshHomeOnConnectFailure" flags to AbstractRemoteSlsbInvokerInterceptor
>
>* added "createMimeMessage(InputStream)" method to JavaMailSender, building a MimeMessage from raw MIME content
>* MimeMessageHelper creates "multipart/related" now, to make mails with inline images compatible with Outlook Express
>* added "validateAddresses" property to MimeMessageHelper (off by default), delegating to JavaMail 1.3's "validate"
>
>* added "http10Compatible" flag to RedirectView, to be turned off for sending HTTP 1.1 status code 303 rather than 302
>* added "buildPdfMetadata" callback to AbstractPdfView, for adding meta fields like author to the iText PDF Document
>* added LookupDispatchActionSupport class to Struts support, analogous to ActionSupport but for LookupDispatchActions
>
>As usual, see the changelog for details. Note that the 1.1 code base contains minor changes in various SPIs which are not backwards-compatible. The API as typically used in applications is as close to 100% compatible as possible, though.
> 
>Regards,
> 
>Juergen
> 
>

Re: [Springframework-developer] Spring Framework 1.1 final released

[Thomas R. <tho...@tr...>]

Eugene Kuleshov wrote:

>
>   Everybody, please note that 
> WebLogicServerTransactionManagerFactoryBean and
> WebLogicJtaTransactionManager are NOT completely tested yet on 
> WebLogic 7.0.
>
>   regards,
>   Eugene
>
>
Slight correction:

WebLogicServerTransactionManagerFactoryBean and 
WebLogicJtaTransactionManager have been tested on WebLogic Server 7.0SP5 
as well as 8.1SP2.  These classes provide access to WebLogic's JTA 
implementation via published API's.  They have been fully tested and 
there are no known issues related to their functionality.

What is yet unknown is if use of these classes provides a solution for 
Eugene's specific issue with a NullPointerException being thrown while 
trying to resume a suspended transaction that was marked for 
rollbackOnly.  This specific issue is most likely due to a bug in 
WebLogic 7.0 and we are waiting for Eugene to test whether Spring's 
latest implementation provides a viable workaround for this problem.

Thomas



>> Dear Spring community,
>>
>> I'm pleased to announce that Spring 1.1 final has just been released. 
>> Since
>> 1.1 RC2, some API clarifications have happened and a number of bugs have
>> been fixed. There is also a variety of minor new features:
>>
>> * reworked BeanWrapperImpl's property-specific custom editor handling to
>> allow registration for uninitialized subpaths * added
>> "applyBeanPropertyValues" method to AutowireCapableBeanFactory, for
>> populating an existing bean instance
>>
>> * added "(abstract)" marker for properties bean definitions respectively
>> "abstract" attribute for XML bean definitions
>>
>> * added support for SqlReturnType interface which allows to return 
>> custom
>> types from stored procedures * added auto-conversion of 
>> java.util.Date and
>> java.util.Calendar to java.sql.Date/Time/Timestamp for JDBC parameters *
>> added support for WebSphere 4 to WebSphereNativeJdbcExtractor,
>> autodetecting WebSphere 5 and 4 now
>>
>> * added WebLogicServerTransactionManagerFactoryBean, to be used with
>> WebLogicJtaTransactionManager on WebLogic 7.0 * added support for direct
>> JTA synchronization to AbstractLobType, as alternative to Spring
>> transaction synchronization * added "flush" method to
>> HibernateOperations/HibernateTemplate and JdoOperations/JdoTemplate, for
>> eager flushing * added "getReportQueryIteratorByQuery" method to OJB
>> PersistenceBrokerOperations and PersistenceBrokerTemplate
>>
>> * deprecated AbstractJndiLocator base class in favor of new
>> JndiObjectLocator base class with explicit "lookup" method * added
>> JndiObjectTargetSource which performs a fresh JNDI lookup for each call,
>> allowing for hot redeployment in JNDI * added "cache" flag to
>> JndiDestinationResolver, to allow for turning off the caching of
>> Destination objects from JNDI * added support for ObjectMessage to
>> SimpleMessageConverter, converting between Serializable objects and
>> ObjectMessages
>>
>> * added RemoteConnectFailureException and 
>> RemoteLookupFailureException as
>> RemoteAccessException subclasses * added JndiRmiServiceExporter,
>> JndiRmiClientInterceptor, JndiRmiProxyFactoryBean (for RMI-IIOP resp.
>> CORBA) * added "lookupStubOnStartup", "cacheStub" and
>> "refreshStubOnConnectFailure" flags to RmiClientInterceptor * added
>> "lookupHomeOnStartup" and "refreshHomeOnConnectFailure" flags to
>> AbstractRemoteSlsbInvokerInterceptor
>>
>> * added "createMimeMessage(InputStream)" method to JavaMailSender, 
>> building
>> a MimeMessage from raw MIME content * MimeMessageHelper creates
>> "multipart/related" now, to make mails with inline images compatible 
>> with
>> Outlook Express * added "validateAddresses" property to 
>> MimeMessageHelper
>> (off by default), delegating to JavaMail 1.3's "validate"
>>
>> * added "http10Compatible" flag to RedirectView, to be turned off for
>> sending HTTP 1.1 status code 303 rather than 302 * added 
>> "buildPdfMetadata"
>> callback to AbstractPdfView, for adding meta fields like author to the
>> iText PDF Document * added LookupDispatchActionSupport class to Struts
>> support, analogous to ActionSupport but for LookupDispatchActions
>>
>> As usual, see the changelog for details. Note that the 1.1 code base
>> contains minor changes in various SPIs which are not 
>> backwards-compatible.
>> The API as typically used in applications is as close to 100% 
>> compatible as
>> possible, though.
>>
>> Regards,
>>
>> Juergen
>>
>>
>>
>> ------------------------------------------------------- This SF.Net 
>> email
>> is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE 
>> developer
>> tools! Get your free copy of BEA WebLogic Workshop 8.1 today. 
>> http://ads.osdn.com/?ad_idP47&alloc_id808&op=click 
>> _______________________________________________ 
>> Springframework-developer
>> mailing list Spr...@li... 
>> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>

Re: [Springframework-developer] Spring Framework 1.1 final released

[Eugene K. <eu...@pl...>]

jürgen höller [werk3AT] wrote:

   Everybody, please note that WebLogicServerTransactionManagerFactoryBean and
WebLogicJtaTransactionManager are NOT completely tested yet on WebLogic 7.0.

   regards,
   Eugene


> Dear Spring community,
> 
> I'm pleased to announce that Spring 1.1 final has just been released. Since
> 1.1 RC2, some API clarifications have happened and a number of bugs have
> been fixed. There is also a variety of minor new features:
> 
> * reworked BeanWrapperImpl's property-specific custom editor handling to
> allow registration for uninitialized subpaths * added
> "applyBeanPropertyValues" method to AutowireCapableBeanFactory, for
> populating an existing bean instance
> 
> * added "(abstract)" marker for properties bean definitions respectively
> "abstract" attribute for XML bean definitions
> 
> * added support for SqlReturnType interface which allows to return custom
> types from stored procedures * added auto-conversion of java.util.Date and
> java.util.Calendar to java.sql.Date/Time/Timestamp for JDBC parameters *
> added support for WebSphere 4 to WebSphereNativeJdbcExtractor,
> autodetecting WebSphere 5 and 4 now
> 
> * added WebLogicServerTransactionManagerFactoryBean, to be used with
> WebLogicJtaTransactionManager on WebLogic 7.0 * added support for direct
> JTA synchronization to AbstractLobType, as alternative to Spring
> transaction synchronization * added "flush" method to
> HibernateOperations/HibernateTemplate and JdoOperations/JdoTemplate, for
> eager flushing * added "getReportQueryIteratorByQuery" method to OJB
> PersistenceBrokerOperations and PersistenceBrokerTemplate
> 
> * deprecated AbstractJndiLocator base class in favor of new
> JndiObjectLocator base class with explicit "lookup" method * added
> JndiObjectTargetSource which performs a fresh JNDI lookup for each call,
> allowing for hot redeployment in JNDI * added "cache" flag to
> JndiDestinationResolver, to allow for turning off the caching of
> Destination objects from JNDI * added support for ObjectMessage to
> SimpleMessageConverter, converting between Serializable objects and
> ObjectMessages
> 
> * added RemoteConnectFailureException and RemoteLookupFailureException as
> RemoteAccessException subclasses * added JndiRmiServiceExporter,
> JndiRmiClientInterceptor, JndiRmiProxyFactoryBean (for RMI-IIOP resp.
> CORBA) * added "lookupStubOnStartup", "cacheStub" and
> "refreshStubOnConnectFailure" flags to RmiClientInterceptor * added
> "lookupHomeOnStartup" and "refreshHomeOnConnectFailure" flags to
> AbstractRemoteSlsbInvokerInterceptor
> 
> * added "createMimeMessage(InputStream)" method to JavaMailSender, building
> a MimeMessage from raw MIME content * MimeMessageHelper creates
> "multipart/related" now, to make mails with inline images compatible with
> Outlook Express * added "validateAddresses" property to MimeMessageHelper
> (off by default), delegating to JavaMail 1.3's "validate"
> 
> * added "http10Compatible" flag to RedirectView, to be turned off for
> sending HTTP 1.1 status code 303 rather than 302 * added "buildPdfMetadata"
> callback to AbstractPdfView, for adding meta fields like author to the
> iText PDF Document * added LookupDispatchActionSupport class to Struts
> support, analogous to ActionSupport but for LookupDispatchActions
> 
> As usual, see the changelog for details. Note that the 1.1 code base
> contains minor changes in various SPIs which are not backwards-compatible.
> The API as typically used in applications is as close to 100% compatible as
> possible, though.
> 
> Regards,
> 
> Juergen
> 
> 
> 
> ------------------------------------------------------- This SF.Net email
> is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer
> tools! Get your free copy of BEA WebLogic Workshop 8.1 today. 
> http://ads.osdn.com/?ad_idP47&alloc_id808&op=click 
> _______________________________________________ Springframework-developer
> mailing list Spr...@li... 
> https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] WLS 7 and TX suspend/resume - continue.

[Eugene K. <eu...@pl...>]

jürgen höller [werk3AT] wrote:

> I agree that it might not be following the intent of every J2EE vendor out
> there. However, it is still not too far-fetched to consider the JTA
> TransactionManager as a kind of extension to the UserTransaction interface:
> If a vendor's UserTransaction object implements the TransactionManager
> interface too, it usually should be fully usable, else the vendor should
> just provide a facade that solely implements UserTransaction...

   That is not my point. The point is if user is passing property A, why it 
should affect property B anyway? If he need to do something about B, why not 
to use that B at the first place (e.g. since it is all reflection, you can 
pass UserTransaction instance to TansactionManager setter, which will be more 
straightforward).

> Anyway, we can't easily turn off that autodetection by default, as some
> Spring users might rely on it. It also works nicely for a number of
> containers, for example Resin, Orion (OC4J), JOnAS (JOTM). And you can turn
> off autodetection now, via the "autodetectTransactionManager" flag,
> although the only case I know of where that is appropriate is the default
> JtaTransactionManager on WebLogic.

   It doesn't matter where it works. It looks like ugly hack anyway. :-)

> Regarding full autodetection of the J2EE server: While that certainly is
> achievable, it's not as straightforward as it may seem at first glance.

   Why is that?

> Migration between J2EE servers shouldn't be too hard anyway, as it just
> affects the JtaTransactionManager definition: The rest of the application
> can stay exactly the same. We currently leave it to the user to configure
> the JtaTransactionManager appropriately, and just include support classes
> for all sorts of cases.

   I didn't say it is hard, it just lead to multiple spring contexts - one per 
each application server and so far it is the only place where you have to do this.

   regards,
   Eugene


________________________________
> 
> Von: spr...@li... im Auftrag von
> Eugene Kuleshov Gesendet: So 05.09.2004 05:06 An:
> spr...@li... Betreff: Re:
> [Springframework-developer] WLS 7 and TX suspend/resume - continue.
> 
> 
> 
> jürgen höller [werk3AT] wrote:
> 
> 
>> Thanks, Thomas - it's great to have this for 1.1 final!
>> 
>> Did you have a chance to check whether WebLogic 8.1's UserTransaction 
>> object found at "java:comp/UserTransaction" implements the 
>> javax.transaction.TransactionManager interface too? It does so on
>> WebLogic 7.0. The benefit of such a scenario is that Spring's
>> JtaTransactionManager will autodetect the TransactionManager, without any
>> special setup.
> 
> 
> This autodetect feature looks like a half baked solution (or dirty hack). 
> You souldn't really rely on the fact that vendor choose to implement both 
> interfaces in publically available instance.
> 
> If you want to have smart tx proxy, it should autodetect j2ee container 
> vendor and version and then choose right way to retrieve tx proxy. Of
> course it has to be tested carefuly for each environment, but then users
> can really trust Spring's tx management and can use it without struggling
> with configuration for each environment type. That will also simplify
> moving application from one container to another (e.g. from Weblogic to
> Websphere).
> 
> 
>> I've documented the basic JTA setup options for popular J2EE servers in 
>> JtaTransactionManager's javadoc. It would be good to verify whether my 
>> autodetection comment just applies to WebLogic 7.0 or also to WebLogic
>> 8.1.
> 
> 
> 
> 
> regards, Eugene
> 
> 
> 
> 
> 
>> ________________________________
>> 
>> Von: spr...@li... im Auftrag von
>>  Thomas Risberg Gesendet: Sa 04.09.2004 17:42 An: 
>> spr...@li... Betreff: Re: 
>> [Springframework-developer] WLS 7 and TX suspend/resume - continue.
>> 
>> 
>> 
>> Juergen, Eugene,  Dimitry, all WLS 70 users,
>> 
>> We now have a new WebLogicServerTransactionManagerFactoryBean.  This bean
>>  factory looks up the ServerTransactionManagerImpl to get around the NPE 
>> that was thrown during a "forceResume".  I based the code on the
>> WebSphere variant.  This has been tested on WebLogic 7.0 SP5 and checked
>> in.  Here is a snippet from the configuration I tested with:
>> 
>> <!--  transaction manager --> <bean id="wls7tm"
>> 
>> class="org.springframework.transaction.jta.WebLogicServerTransactionManagerFactoryBean"/>
>>  <bean id="transactionManager"
>> 
>> class="org.springframework.transaction.jta.WebLogicJtaTransactionManager">
>>  <property name="transactionManager"> <ref local="wls7tm"/> </property> 
>> </bean>
>> 
>> Thomas
>> 
>> 
>> Thomas Risberg wrote:
>> 
>> 
>> 
>>> Juergen,
>>> 
>>> I'll try to implement and test a 
>>> WebLogicServerTransactionManagerFactoryBean today.  I'll keep you
>>> posted.
>>> 
>>> 
>>> For WLS 8.1 the TxHelper.getTransactionManager method is marked as 
>>> deprecated even though it is not documented as such in the JavaDocs. 
>>> There is also a brand new method getClientTransactionManager for 8.1
>>> that is starting out marked as deprecated.  Go figure.  We are probably
>>> better off recommending the JNDI lookups for 8.1.
>>> 
>>> Thomas
>>> 
>>> 
>>> 
>>> jürgen höller [werk3AT] wrote:
>>> 
>>> 
>>> 
>>>> Thanks, Thomas! This means that there *is* a way to make it work on 
>>>> WebLogic 7! Eugene, Dmitri, your pain finally has an end! :-)
>>>> 
>>>> Regarding obtaining the TransactionManager via the TxHelper on
>>>> WebLogic 7: That can easily be factored out into a custom
>>>> FactoryBean, like we did for WebSphere (see
>>>> WebSphereTransactionManagerFactoryBean), to be passed into
>>>> JtaTransactionManager's respectively WebLogicJtaTransactionManager's
>>>> "transactionManager" property. So we don't need a further
>>>> JtaTransactionManager subclass for this, just a further
>>>> TransactionManager lookup strategy.
>>>> 
>>>> BTW, Dmitri told me that the WebLogic UserTransaction object at 
>>>> "java:comp/UserTransaction" implements the TransactionManager
>>>> interface too, but that obviously forceResume doesn't work there... I
>>>> assume the ClientTransactionManagerImpl is returned there, not the 
>>>> ServerTransactionManagerImpl.
>>>> 
>>>> If we can double-check that this works better than the 
>>>> TransactionManager fetched from JNDI, I suggest to add a 
>>>> WebLogicServerTransactionManagerFactoryBean (or a similar name), 
>>>> clearly documenting that this is meant as an alternative to the 
>>>> standard JNDI TransactionManager reference that WebLogic provides, 
>>>> mainly for WebLogic 7. I wouldn't mind to do this even for the 1.1 
>>>> final release tomorrow...
>>>> 
>>>> Is the TxHelper lookup available on WebLogic 8.1 too? Of course, it 
>>>> shouldn't be necessary there, as the standard JNDI TransactionManager
>>>>  reference will work too. I just wonder whether it's available and
>>>> would work in principle: People could then configure a 
>>>> WebLogicServerTransactionManagerFactoryBean to be able to deploy on 
>>>> both WebLogic 7 and WebLogic 8, without adapting their Spring 
>>>> configuration.
>>>> 
>>>> Of course, such a WebLogicServerTransactionManagerFactoryBean would 
>>>> have to be coded via reflection to avoid compile-time dependencies on
>>>>  WebLogic, analogous to WebSphereTransactionManagerFactoryBean. Do
>>>> you have the chance to do this before tomorrow, Thomas?
>>>> 
>>>> Juergen
>>>> 
>>>> 
>>>> ________________________________
>>>> 
>>>> Von: spr...@li... im Auftrag
>>>>  von Thomas Risberg Gesendet: Sa 04.09.2004 14:30 An: 
>>>> spr...@li... Betreff: Re: 
>>>> [Springframework-developer] WLS 7 and TX suspend/resume - continue.
>>>> 
>>>> 
>>>> 
>>>> I have done some additional testing for this issue and this is what I
>>>>  have found.
>>>> 
>>>> WebLogic exposes a client TransactionManager implementation via JNDI 
>>>> (weblogic.transaction.internal.ClientTransactionManagerImpl) and in
>>>> WLS 7.0 it is throwing an NPE when you call forceResume (with or
>>>> without a suspended transaction that has been marked for
>>>> RollbackOnly).
>>>> 
>>>> They also have a different server implementation 
>>>> (weblogic.transaction.internal.ServerTransactionManagerImpl) that is 
>>>> returnd by a call to TxHelper.getTransactionManager().  With this TM 
>>>> the force resume works as expected.
>>>> 
>>>> So the workaround for now is to do the suspend/resume using the TM 
>>>> returned by TxHelper before calling the Spring managed code. 
>>>> Alternatively we could provide a WebLogic7JtaTransactionManager that 
>>>> uses this method of obtaining the TM.
>>>> 
>>>> I doubt that BEA will fix this issue in WLS 7.0.  They will probably 
>>>> suggest to upgrade to 8.1 or use the TxHelper to obtain the TM.
>>>> 
>>>> Thomas
>>>> 
>>>> 
>>>> jürgen höller [werk3AT] wrote:
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>>> Ideally, WebLogic should work properly with standard JTA 
>>>>> TransactionManager resume in all cases, not needing the proprietary
>>>>>  forceResume call. However, the least we can expect is that 
>>>>> forceResume works properly: You could send a corresponding bug
>>>>> report to BEA, for WebLogic 7.0. However, they might tell you that
>>>>> they fixed the issue in WebLogic 8.1...
>>>>> 
>>>>> Juergen
>>>>> 
>>>>> 
>>>>> ________________________________
>>>>> 
>>>>> Von: spr...@li... im
>>>>> Auftrag von jürgen höller [werk3AT] Gesendet: Fr 03.09.2004 23:31
>>>>> An: spr...@li... Betreff: Re: 
>>>>> [Springframework-developer] WLS 7 and TX suspend/resume - continue.
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> As I already wrote in my JIRA comments: Many thanks for your
>>>>> efforts, Dmitri!
>>>>> 
>>>>> I assume that with JtaTransactionManager, you'll get an 
>>>>> IllegalStateException ("cannot resume rollback-only transaction" or
>>>>>  the like), and with WebLogicJtaTransactionManager, you'll get the
>>>>> NPE in WebLogic code?
>>>>> 
>>>>> This really seems to be a bug in WebLogic 7.0... At least it should
>>>>>  work properly as long as not suspending a transaction that has
>>>>> been marked as rollback-only.
>>>>> 
>>>>> Juergen
>>>>> 
>>>>> 
>>>>> ________________________________
>>>>> 
>>>>> Von: spr...@li... im
>>>>> Auftrag von Dmitri Maximovich Gesendet: Fr 03.09.2004 23:07 An: 
>>>>> spr...@li... Betreff: 
>>>>> [Springframework-developer] WLS 7 and TX suspend/resume - continue.
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> I just tried WLS 7 with Spring 1.1rc2 and BMT transaction 
>>>>> demaraction. It doesn't work with standard JtaTransactionManager or
>>>>>  with WeblogicJtaTransactionManager, so something fundamentally
>>>>> broken in WLS7 (same NPE as described in JIRA SPR-251). Next I'll
>>>>> try to use WLS TransactionManager (exposed in JNDI) to
>>>>> suspend/resume transaction without Spring to see it it's going to
>>>>> work.
>>>>> 

[Springframework-developer] Spring Framework 1.1 final released

[<jue...@we...>]

Dear Spring community,
=20
I'm pleased to announce that Spring 1.1 final has just been released. =
Since 1.1 RC2, some API clarifications have happened and a number of =
bugs have been fixed. There is also a variety of minor new features:
=20
* reworked BeanWrapperImpl's property-specific custom editor handling to =
allow registration for uninitialized subpaths
* added "applyBeanPropertyValues" method to AutowireCapableBeanFactory, =
for populating an existing bean instance

* added "(abstract)" marker for properties bean definitions respectively =
"abstract" attribute for XML bean definitions
=20
* added support for SqlReturnType interface which allows to return =
custom types from stored procedures
* added auto-conversion of java.util.Date and java.util.Calendar to =
java.sql.Date/Time/Timestamp for JDBC parameters
* added support for WebSphere 4 to WebSphereNativeJdbcExtractor, =
autodetecting WebSphere 5 and 4 now

* added WebLogicServerTransactionManagerFactoryBean, to be used with =
WebLogicJtaTransactionManager on WebLogic 7.0
* added support for direct JTA synchronization to AbstractLobType, as =
alternative to Spring transaction synchronization
* added "flush" method to HibernateOperations/HibernateTemplate and =
JdoOperations/JdoTemplate, for eager flushing
* added "getReportQueryIteratorByQuery" method to OJB =
PersistenceBrokerOperations and PersistenceBrokerTemplate

* deprecated AbstractJndiLocator base class in favor of new =
JndiObjectLocator base class with explicit "lookup" method
* added JndiObjectTargetSource which performs a fresh JNDI lookup for =
each call, allowing for hot redeployment in JNDI
* added "cache" flag to JndiDestinationResolver, to allow for turning =
off the caching of Destination objects from JNDI
* added support for ObjectMessage to SimpleMessageConverter, converting =
between Serializable objects and ObjectMessages

* added RemoteConnectFailureException and RemoteLookupFailureException =
as RemoteAccessException subclasses
* added JndiRmiServiceExporter, JndiRmiClientInterceptor, =
JndiRmiProxyFactoryBean (for RMI-IIOP resp. CORBA)
* added "lookupStubOnStartup", "cacheStub" and =
"refreshStubOnConnectFailure" flags to RmiClientInterceptor
* added "lookupHomeOnStartup" and "refreshHomeOnConnectFailure" flags to =
AbstractRemoteSlsbInvokerInterceptor

* added "createMimeMessage(InputStream)" method to JavaMailSender, =
building a MimeMessage from raw MIME content
* MimeMessageHelper creates "multipart/related" now, to make mails with =
inline images compatible with Outlook Express
* added "validateAddresses" property to MimeMessageHelper (off by =
default), delegating to JavaMail 1.3's "validate"

* added "http10Compatible" flag to RedirectView, to be turned off for =
sending HTTP 1.1 status code 303 rather than 302
* added "buildPdfMetadata" callback to AbstractPdfView, for adding meta =
fields like author to the iText PDF Document
* added LookupDispatchActionSupport class to Struts support, analogous =
to ActionSupport but for LookupDispatchActions

As usual, see the changelog for details. Note that the 1.1 code base =
contains minor changes in various SPIs which are not =
backwards-compatible. The API as typically used in applications is as =
close to 100% compatible as possible, though.
=20
Regards,
=20
Juergen
=20

Re: [Springframework-developer] WLS 7 and TX suspend/resume - continue.

[<jue...@we...>]

I agree that it might not be following the intent of every J2EE vendor =
out there. However, it is still not too far-fetched to consider the JTA =
TransactionManager as a kind of extension to the UserTransaction =
interface: If a vendor's UserTransaction object implements the =
TransactionManager interface too, it usually should be fully usable, =
else the vendor should just provide a facade that solely implements =
UserTransaction...
=20
Anyway, we can't easily turn off that autodetection by default, as some =
Spring users might rely on it. It also works nicely for a number of =
containers, for example Resin, Orion (OC4J), JOnAS (JOTM). And you can =
turn off autodetection now, via the "autodetectTransactionManager" flag, =
although the only case I know of where that is appropriate is the =
default JtaTransactionManager on WebLogic.
=20
Regarding full autodetection of the J2EE server: While that certainly is =
achievable, it's not as straightforward as it may seem at first glance. =
Migration between J2EE servers shouldn't be too hard anyway, as it just =
affects the JtaTransactionManager definition: The rest of the =
application can stay exactly the same. We currently leave it to the user =
to configure the JtaTransactionManager appropriately, and just include =
support classes for all sorts of cases.
=20
Juergen
=20

________________________________

Von: spr...@li... im Auftrag =
von Eugene Kuleshov
Gesendet: So 05.09.2004 05:06
An: spr...@li...
Betreff: Re: [Springframework-developer] WLS 7 and TX suspend/resume - =
continue.



j=FCrgen h=F6ller [werk3AT] wrote:

> Thanks, Thomas - it's great to have this for 1.1 final!
>
> Did you have a chance to check whether WebLogic 8.1's UserTransaction
> object found at "java:comp/UserTransaction" implements the
> javax.transaction.TransactionManager interface too? It does so on =
WebLogic
> 7.0. The benefit of such a scenario is that Spring's =
JtaTransactionManager
> will autodetect the TransactionManager, without any special setup.

   This autodetect feature looks like a half baked solution (or dirty =
hack).
You souldn't really rely on the fact that vendor choose to implement =
both
interfaces in publically available instance.

   If you want to have smart tx proxy, it should autodetect j2ee =
container
vendor and version and then choose right way to retrieve tx proxy. Of =
course
it has to be tested carefuly for each environment, but then users can =
really
trust Spring's tx management and can use it without struggling with
configuration for each environment type. That will also simplify moving
application from one container to another (e.g. from Weblogic to =
Websphere).

> I've documented the basic JTA setup options for popular J2EE servers =
in
> JtaTransactionManager's javadoc. It would be good to verify whether my
> autodetection comment just applies to WebLogic 7.0 or also to WebLogic =
8.1.



   regards,
   Eugene




>  ________________________________
>
> Von: spr...@li... im Auftrag =
von
> Thomas Risberg Gesendet: Sa 04.09.2004 17:42 An:
> spr...@li... Betreff: Re:
> [Springframework-developer] WLS 7 and TX suspend/resume - continue.
>
>
>
> Juergen, Eugene,  Dimitry, all WLS 70 users,
>
> We now have a new WebLogicServerTransactionManagerFactoryBean.  This =
bean
> factory looks up the ServerTransactionManagerImpl to get around the =
NPE
> that was thrown during a "forceResume".  I based the code on the =
WebSphere
> variant.  This has been tested on WebLogic 7.0 SP5 and checked in.  =
Here is
> a snippet from the configuration I tested with:
>
> <!--  transaction manager --> <bean id=3D"wls7tm"
>
> =
class=3D"org.springframework.transaction.jta.WebLogicServerTransactionMan=
agerFactoryBean"/>
>  <bean id=3D"transactionManager"
>
> =
class=3D"org.springframework.transaction.jta.WebLogicJtaTransactionManage=
r">
> <property name=3D"transactionManager"> <ref local=3D"wls7tm"/> =
</property>
> </bean>
>
> Thomas
>
>
> Thomas Risberg wrote:
>
>
>> Juergen,
>>
>> I'll try to implement and test a
>> WebLogicServerTransactionManagerFactoryBean today.  I'll keep you =
posted.
>>
>>
>> For WLS 8.1 the TxHelper.getTransactionManager method is marked as
>> deprecated even though it is not documented as such in the JavaDocs.
>> There is also a brand new method getClientTransactionManager for 8.1 =
that
>> is starting out marked as deprecated.  Go figure.  We are probably =
better
>> off recommending the JNDI lookups for 8.1.
>>
>> Thomas
>>
>>
>>
>> j=FCrgen h=F6ller [werk3AT] wrote:
>>
>>
>>> Thanks, Thomas! This means that there *is* a way to make it work on
>>> WebLogic 7! Eugene, Dmitri, your pain finally has an end! :-)
>>>
>>> Regarding obtaining the TransactionManager via the TxHelper on =
WebLogic
>>> 7: That can easily be factored out into a custom FactoryBean, like =
we
>>> did for WebSphere (see WebSphereTransactionManagerFactoryBean), to =
be
>>> passed into JtaTransactionManager's respectively
>>> WebLogicJtaTransactionManager's "transactionManager" property. So we
>>> don't need a further JtaTransactionManager subclass for this, just a
>>> further TransactionManager lookup strategy.
>>>
>>> BTW, Dmitri told me that the WebLogic UserTransaction object at
>>> "java:comp/UserTransaction" implements the TransactionManager =
interface
>>> too, but that obviously forceResume doesn't work there... I assume =
the
>>> ClientTransactionManagerImpl is returned there, not the
>>> ServerTransactionManagerImpl.
>>>
>>> If we can double-check that this works better than the
>>> TransactionManager fetched from JNDI, I suggest to add a
>>> WebLogicServerTransactionManagerFactoryBean (or a similar name),
>>> clearly documenting that this is meant as an alternative to the
>>> standard JNDI TransactionManager reference that WebLogic provides,
>>> mainly for WebLogic 7. I wouldn't mind to do this even for the 1.1
>>> final release tomorrow...
>>>
>>> Is the TxHelper lookup available on WebLogic 8.1 too? Of course, it
>>> shouldn't be necessary there, as the standard JNDI =
TransactionManager
>>> reference will work too. I just wonder whether it's available and =
would
>>> work in principle: People could then configure a
>>> WebLogicServerTransactionManagerFactoryBean to be able to deploy on
>>> both WebLogic 7 and WebLogic 8, without adapting their Spring
>>> configuration.
>>>
>>> Of course, such a WebLogicServerTransactionManagerFactoryBean would
>>> have to be coded via reflection to avoid compile-time dependencies =
on
>>> WebLogic, analogous to WebSphereTransactionManagerFactoryBean. Do =
you
>>> have the chance to do this before tomorrow, Thomas?
>>>
>>> Juergen
>>>
>>>
>>> ________________________________
>>>
>>> Von: spr...@li... im =
Auftrag
>>> von Thomas Risberg Gesendet: Sa 04.09.2004 14:30 An:
>>> spr...@li... Betreff: Re:
>>> [Springframework-developer] WLS 7 and TX suspend/resume - continue.
>>>
>>>
>>>
>>> I have done some additional testing for this issue and this is what =
I
>>> have found.
>>>
>>> WebLogic exposes a client TransactionManager implementation via JNDI
>>> (weblogic.transaction.internal.ClientTransactionManagerImpl) and in =
WLS
>>>  7.0 it is throwing an NPE when you call forceResume (with or =
without a
>>>  suspended transaction that has been marked for RollbackOnly).
>>>
>>> They also have a different server implementation
>>> (weblogic.transaction.internal.ServerTransactionManagerImpl) that is
>>> returnd by a call to TxHelper.getTransactionManager().  With this TM
>>> the force resume works as expected.
>>>
>>> So the workaround for now is to do the suspend/resume using the TM
>>> returned by TxHelper before calling the Spring managed code.
>>> Alternatively we could provide a WebLogic7JtaTransactionManager that
>>> uses this method of obtaining the TM.
>>>
>>> I doubt that BEA will fix this issue in WLS 7.0.  They will probably
>>> suggest to upgrade to 8.1 or use the TxHelper to obtain the TM.
>>>
>>> Thomas
>>>
>>>
>>> j=FCrgen h=F6ller [werk3AT] wrote:
>>>
>>>
>>>
>>>
>>>> Ideally, WebLogic should work properly with standard JTA
>>>> TransactionManager resume in all cases, not needing the proprietary
>>>> forceResume call. However, the least we can expect is that
>>>> forceResume works properly: You could send a corresponding bug =
report
>>>> to BEA, for WebLogic 7.0. However, they might tell you that they
>>>> fixed the issue in WebLogic 8.1...
>>>>
>>>> Juergen
>>>>
>>>>
>>>> ________________________________
>>>>
>>>> Von: spr...@li... im =
Auftrag
>>>> von j=FCrgen h=F6ller [werk3AT] Gesendet: Fr 03.09.2004 23:31 An:
>>>> spr...@li... Betreff: Re:
>>>> [Springframework-developer] WLS 7 and TX suspend/resume - continue.
>>>>
>>>>
>>>>
>>>> As I already wrote in my JIRA comments: Many thanks for your =
efforts,
>>>> Dmitri!
>>>>
>>>> I assume that with JtaTransactionManager, you'll get an
>>>> IllegalStateException ("cannot resume rollback-only transaction" or
>>>> the like), and with WebLogicJtaTransactionManager, you'll get the =
NPE
>>>> in WebLogic code?
>>>>
>>>> This really seems to be a bug in WebLogic 7.0... At least it should
>>>> work properly as long as not suspending a transaction that has been
>>>> marked as rollback-only.
>>>>
>>>> Juergen
>>>>
>>>>
>>>> ________________________________
>>>>
>>>> Von: spr...@li... im =
Auftrag
>>>> von Dmitri Maximovich Gesendet: Fr 03.09.2004 23:07 An:
>>>> spr...@li... Betreff:
>>>> [Springframework-developer] WLS 7 and TX suspend/resume - continue.
>>>>
>>>>
>>>>
>>>> I just tried WLS 7 with Spring 1.1rc2 and BMT transaction
>>>> demaraction. It doesn't work with standard JtaTransactionManager or
>>>> with WeblogicJtaTransactionManager, so something fundamentally =
broken
>>>> in WLS7 (same NPE as described in JIRA SPR-251). Next I'll try to =
use
>>>> WLS TransactionManager (exposed in JNDI) to suspend/resume
>>>> transaction without Spring to see it it's going to work.
>>>>



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=3D5047&alloc_id=3D10808&op=3Dclick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] Final preparations for 1.1 final

[Eugene K. <eu...@md...>]

jürgen,

   FYI. We will not be able to test new tx features before tuesday. It is a 
holidays in Canada.

   regards,
   Eugene


> Everybody,
>  
> I plan to release 1.1 final tomorrow, right before I leave for London and Rome for 10 days. IMO it's already overdue, so I'm very keen on sticking to that deadline.
>  
> If you've got some remaining time today, feel free to polish, complete docs, write further unit tests, test the samples. However, please do no further commits tomorrow, as I'm gonna take the release snapshot tomorrow morning.
>  
> BTW, you might have noticed that I recently did some minor deprecations: A couple of "getNrOfXxx" methods have been renamed to "getXxxCount", for consistent naming throughout the framework.
>  
> I've also deprecated ThreadLocalTargetSourceStats' "getInvocations", "getHits", "getObjects" to "getInvocationCount", "getHitCount", "getObjectCount", respectively. (I hope you don't mind that, Rod.)
>  
> Let there be 1.1 final! :-)
>  
> Juergen
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_idP47&alloc_id808&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] WLS 7 and TX suspend/resume - continue.

[Eugene K. <eu...@md...>]

jürgen höller [werk3AT] wrote:

> Thanks, Thomas - it's great to have this for 1.1 final!
> 
> Did you have a chance to check whether WebLogic 8.1's UserTransaction
> object found at "java:comp/UserTransaction" implements the
> javax.transaction.TransactionManager interface too? It does so on WebLogic
> 7.0. The benefit of such a scenario is that Spring's JtaTransactionManager
> will autodetect the TransactionManager, without any special setup.

   This autodetect feature looks like a half baked solution (or dirty hack). 
You souldn't really rely on the fact that vendor choose to implement both 
interfaces in publically available instance.

   If you want to have smart tx proxy, it should autodetect j2ee container 
vendor and version and then choose right way to retrieve tx proxy. Of course 
it has to be tested carefuly for each environment, but then users can really 
trust Spring's tx management and can use it without struggling with 
configuration for each environment type. That will also simplify moving 
application from one container to another (e.g. from Weblogic to Websphere).

> I've documented the basic JTA setup options for popular J2EE servers in
> JtaTransactionManager's javadoc. It would be good to verify whether my
> autodetection comment just applies to WebLogic 7.0 or also to WebLogic 8.1.



   regards,
   Eugene




>  ________________________________
> 
> Von: spr...@li... im Auftrag von
> Thomas Risberg Gesendet: Sa 04.09.2004 17:42 An:
> spr...@li... Betreff: Re:
> [Springframework-developer] WLS 7 and TX suspend/resume - continue.
> 
> 
> 
> Juergen, Eugene,  Dimitry, all WLS 70 users,
> 
> We now have a new WebLogicServerTransactionManagerFactoryBean.  This bean
> factory looks up the ServerTransactionManagerImpl to get around the NPE
> that was thrown during a "forceResume".  I based the code on the WebSphere
> variant.  This has been tested on WebLogic 7.0 SP5 and checked in.  Here is
> a snippet from the configuration I tested with:
> 
> <!--  transaction manager --> <bean id="wls7tm"
> 
> class="org.springframework.transaction.jta.WebLogicServerTransactionManagerFactoryBean"/>
>  <bean id="transactionManager"
> 
> class="org.springframework.transaction.jta.WebLogicJtaTransactionManager"> 
> <property name="transactionManager"> <ref local="wls7tm"/> </property> 
> </bean>
> 
> Thomas
> 
> 
> Thomas Risberg wrote:
> 
> 
>> Juergen,
>> 
>> I'll try to implement and test a 
>> WebLogicServerTransactionManagerFactoryBean today.  I'll keep you posted.
>> 
>> 
>> For WLS 8.1 the TxHelper.getTransactionManager method is marked as 
>> deprecated even though it is not documented as such in the JavaDocs. 
>> There is also a brand new method getClientTransactionManager for 8.1 that
>> is starting out marked as deprecated.  Go figure.  We are probably better
>> off recommending the JNDI lookups for 8.1.
>> 
>> Thomas
>> 
>> 
>> 
>> jürgen höller [werk3AT] wrote:
>> 
>> 
>>> Thanks, Thomas! This means that there *is* a way to make it work on 
>>> WebLogic 7! Eugene, Dmitri, your pain finally has an end! :-)
>>> 
>>> Regarding obtaining the TransactionManager via the TxHelper on WebLogic
>>> 7: That can easily be factored out into a custom FactoryBean, like we
>>> did for WebSphere (see WebSphereTransactionManagerFactoryBean), to be
>>> passed into JtaTransactionManager's respectively
>>> WebLogicJtaTransactionManager's "transactionManager" property. So we
>>> don't need a further JtaTransactionManager subclass for this, just a
>>> further TransactionManager lookup strategy.
>>> 
>>> BTW, Dmitri told me that the WebLogic UserTransaction object at 
>>> "java:comp/UserTransaction" implements the TransactionManager interface
>>> too, but that obviously forceResume doesn't work there... I assume the
>>> ClientTransactionManagerImpl is returned there, not the 
>>> ServerTransactionManagerImpl.
>>> 
>>> If we can double-check that this works better than the 
>>> TransactionManager fetched from JNDI, I suggest to add a 
>>> WebLogicServerTransactionManagerFactoryBean (or a similar name), 
>>> clearly documenting that this is meant as an alternative to the 
>>> standard JNDI TransactionManager reference that WebLogic provides, 
>>> mainly for WebLogic 7. I wouldn't mind to do this even for the 1.1 
>>> final release tomorrow...
>>> 
>>> Is the TxHelper lookup available on WebLogic 8.1 too? Of course, it 
>>> shouldn't be necessary there, as the standard JNDI TransactionManager 
>>> reference will work too. I just wonder whether it's available and would
>>> work in principle: People could then configure a 
>>> WebLogicServerTransactionManagerFactoryBean to be able to deploy on 
>>> both WebLogic 7 and WebLogic 8, without adapting their Spring 
>>> configuration.
>>> 
>>> Of course, such a WebLogicServerTransactionManagerFactoryBean would 
>>> have to be coded via reflection to avoid compile-time dependencies on 
>>> WebLogic, analogous to WebSphereTransactionManagerFactoryBean. Do you 
>>> have the chance to do this before tomorrow, Thomas?
>>> 
>>> Juergen
>>> 
>>> 
>>> ________________________________
>>> 
>>> Von: spr...@li... im Auftrag 
>>> von Thomas Risberg Gesendet: Sa 04.09.2004 14:30 An:
>>> spr...@li... Betreff: Re:
>>> [Springframework-developer] WLS 7 and TX suspend/resume - continue.
>>> 
>>> 
>>> 
>>> I have done some additional testing for this issue and this is what I 
>>> have found.
>>> 
>>> WebLogic exposes a client TransactionManager implementation via JNDI 
>>> (weblogic.transaction.internal.ClientTransactionManagerImpl) and in WLS
>>>  7.0 it is throwing an NPE when you call forceResume (with or without a
>>>  suspended transaction that has been marked for RollbackOnly).
>>> 
>>> They also have a different server implementation 
>>> (weblogic.transaction.internal.ServerTransactionManagerImpl) that is 
>>> returnd by a call to TxHelper.getTransactionManager().  With this TM
>>> the force resume works as expected.
>>> 
>>> So the workaround for now is to do the suspend/resume using the TM 
>>> returned by TxHelper before calling the Spring managed code. 
>>> Alternatively we could provide a WebLogic7JtaTransactionManager that 
>>> uses this method of obtaining the TM.
>>> 
>>> I doubt that BEA will fix this issue in WLS 7.0.  They will probably 
>>> suggest to upgrade to 8.1 or use the TxHelper to obtain the TM.
>>> 
>>> Thomas
>>> 
>>> 
>>> jürgen höller [werk3AT] wrote:
>>> 
>>> 
>>> 
>>> 
>>>> Ideally, WebLogic should work properly with standard JTA 
>>>> TransactionManager resume in all cases, not needing the proprietary 
>>>> forceResume call. However, the least we can expect is that 
>>>> forceResume works properly: You could send a corresponding bug report
>>>> to BEA, for WebLogic 7.0. However, they might tell you that they
>>>> fixed the issue in WebLogic 8.1...
>>>> 
>>>> Juergen
>>>> 
>>>> 
>>>> ________________________________
>>>> 
>>>> Von: spr...@li... im Auftrag
>>>> von jürgen höller [werk3AT] Gesendet: Fr 03.09.2004 23:31 An:
>>>> spr...@li... Betreff: Re:
>>>> [Springframework-developer] WLS 7 and TX suspend/resume - continue.
>>>> 
>>>> 
>>>> 
>>>> As I already wrote in my JIRA comments: Many thanks for your efforts,
>>>> Dmitri!
>>>> 
>>>> I assume that with JtaTransactionManager, you'll get an 
>>>> IllegalStateException ("cannot resume rollback-only transaction" or 
>>>> the like), and with WebLogicJtaTransactionManager, you'll get the NPE
>>>> in WebLogic code?
>>>> 
>>>> This really seems to be a bug in WebLogic 7.0... At least it should 
>>>> work properly as long as not suspending a transaction that has been 
>>>> marked as rollback-only.
>>>> 
>>>> Juergen
>>>> 
>>>> 
>>>> ________________________________
>>>> 
>>>> Von: spr...@li... im Auftrag
>>>> von Dmitri Maximovich Gesendet: Fr 03.09.2004 23:07 An:
>>>> spr...@li... Betreff:
>>>> [Springframework-developer] WLS 7 and TX suspend/resume - continue.
>>>> 
>>>> 
>>>> 
>>>> I just tried WLS 7 with Spring 1.1rc2 and BMT transaction 
>>>> demaraction. It doesn't work with standard JtaTransactionManager or
>>>> with WeblogicJtaTransactionManager, so something fundamentally broken
>>>> in WLS7 (same NPE as described in JIRA SPR-251). Next I'll try to use
>>>> WLS TransactionManager (exposed in JNDI) to suspend/resume 
>>>> transaction without Spring to see it it's going to work.
>>>> 

Re: [Springframework-developer] WLS 7 and TX suspend/resume - continue.

[Eugene K. <eu...@pl...>]

Thomas Risberg wrote:

   That's strange. If I'm not mistaken we have tested tx manager returned by 
TxHelper in our environment and got the same error. We'll take another try 
next week.

   regards,
   Eugene



> Juergen, Eugene,  Dimitry, all WLS 70 users,
> 
> We now have a new WebLogicServerTransactionManagerFactoryBean.  This 
> bean factory looks up the ServerTransactionManagerImpl to get around the 
> NPE that was thrown during a "forceResume".  I based the code on the 
> WebSphere variant.  This has been tested on WebLogic 7.0 SP5 and checked 
> in.  Here is a snippet from the configuration I tested with:
> 
>   <!--  transaction manager -->
>     <bean id="wls7tm"
>              
> class="org.springframework.transaction.jta.WebLogicServerTransactionManagerFactoryBean"/> 
> 
>     <bean id="transactionManager"
>              
> class="org.springframework.transaction.jta.WebLogicJtaTransactionManager">
>        <property name="transactionManager">
>          <ref local="wls7tm"/>
>        </property>
>        </bean>
> 
> Thomas
> 
> 
> Thomas Risberg wrote:
> 
>> Juergen,
>>
>> I'll try to implement and test a 
>> WebLogicServerTransactionManagerFactoryBean today.  I'll keep you posted.
>>
>> For WLS 8.1 the TxHelper.getTransactionManager method is marked as 
>> deprecated even though it is not documented as such in the JavaDocs.  
>> There is also a brand new method getClientTransactionManager for 8.1 
>> that is starting out marked as deprecated.  Go figure.  We are 
>> probably better off recommending the JNDI lookups for 8.1.
>>
>> Thomas
>>
>>
>>
>> jürgen höller [werk3AT] wrote:
>>
>>> Thanks, Thomas! This means that there *is* a way to make it work on 
>>> WebLogic 7! Eugene, Dmitri, your pain finally has an end! :-)
>>>
>>> Regarding obtaining the TransactionManager via the TxHelper on 
>>> WebLogic 7: That can easily be factored out into a custom 
>>> FactoryBean, like we did for WebSphere (see 
>>> WebSphereTransactionManagerFactoryBean), to be passed into 
>>> JtaTransactionManager's respectively WebLogicJtaTransactionManager's 
>>> "transactionManager" property. So we don't need a further 
>>> JtaTransactionManager subclass for this, just a further 
>>> TransactionManager lookup strategy.
>>>
>>> BTW, Dmitri told me that the WebLogic UserTransaction object at 
>>> "java:comp/UserTransaction" implements the TransactionManager 
>>> interface too, but that obviously forceResume doesn't work there... I 
>>> assume the ClientTransactionManagerImpl is returned there, not the 
>>> ServerTransactionManagerImpl.
>>>
>>> If we can double-check that this works better than the 
>>> TransactionManager fetched from JNDI, I suggest to add a 
>>> WebLogicServerTransactionManagerFactoryBean (or a similar name), 
>>> clearly documenting that this is meant as an alternative to the 
>>> standard JNDI TransactionManager reference that WebLogic provides, 
>>> mainly for WebLogic 7. I wouldn't mind to do this even for the 1.1 
>>> final release tomorrow...
>>>
>>> Is the TxHelper lookup available on WebLogic 8.1 too? Of course, it 
>>> shouldn't be necessary there, as the standard JNDI TransactionManager 
>>> reference will work too. I just wonder whether it's available and 
>>> would work in principle: People could then configure a 
>>> WebLogicServerTransactionManagerFactoryBean to be able to deploy on 
>>> both WebLogic 7 and WebLogic 8, without adapting their Spring 
>>> configuration.
>>>
>>> Of course, such a WebLogicServerTransactionManagerFactoryBean would 
>>> have to be coded via reflection to avoid compile-time dependencies on 
>>> WebLogic, analogous to WebSphereTransactionManagerFactoryBean. Do you 
>>> have the chance to do this before tomorrow, Thomas?
>>>
>>> Juergen
>>>
>>>
>>> ________________________________
>>>
>>> Von: spr...@li... im Auftrag 
>>> von Thomas Risberg
>>> Gesendet: Sa 04.09.2004 14:30
>>> An: spr...@li...
>>> Betreff: Re: [Springframework-developer] WLS 7 and TX suspend/resume 
>>> - continue.
>>>
>>>
>>>
>>> I have done some additional testing for this issue and this is what I
>>> have found.
>>>
>>> WebLogic exposes a client TransactionManager implementation via JNDI 
>>> (weblogic.transaction.internal.ClientTransactionManagerImpl) and in WLS
>>> 7.0 it is throwing an NPE when you call forceResume (with or without a
>>> suspended transaction that has been marked for RollbackOnly).
>>>
>>> They also have a different server implementation
>>> (weblogic.transaction.internal.ServerTransactionManagerImpl) that is
>>> returnd by a call to TxHelper.getTransactionManager().  With this TM the
>>> force resume works as expected.
>>>
>>> So the workaround for now is to do the suspend/resume using the TM
>>> returned by TxHelper before calling the Spring managed code.
>>> Alternatively we could provide a WebLogic7JtaTransactionManager that
>>> uses this method of obtaining the TM.
>>>
>>> I doubt that BEA will fix this issue in WLS 7.0.  They will probably
>>> suggest to upgrade to 8.1 or use the TxHelper to obtain the TM.
>>>
>>> Thomas
>>>
>>>
>>> jürgen höller [werk3AT] wrote:
>>>
>>>  
>>>
>>>> Ideally, WebLogic should work properly with standard JTA 
>>>> TransactionManager resume in all cases, not needing the proprietary 
>>>> forceResume call. However, the least we can expect is that 
>>>> forceResume works properly: You could send a corresponding bug 
>>>> report to BEA, for WebLogic 7.0. However, they might tell you that 
>>>> they fixed the issue in WebLogic 8.1...
>>>>
>>>> Juergen
>>>>
>>>>
>>>> ________________________________
>>>>
>>>> Von: spr...@li... im 
>>>> Auftrag von jürgen höller [werk3AT]
>>>> Gesendet: Fr 03.09.2004 23:31
>>>> An: spr...@li...
>>>> Betreff: Re: [Springframework-developer] WLS 7 and TX suspend/resume 
>>>> - continue.
>>>>
>>>>
>>>>
>>>> As I already wrote in my JIRA comments: Many thanks for your 
>>>> efforts, Dmitri!
>>>>
>>>> I assume that with JtaTransactionManager, you'll get an 
>>>> IllegalStateException ("cannot resume rollback-only transaction" or 
>>>> the like), and with WebLogicJtaTransactionManager, you'll get the 
>>>> NPE in WebLogic code?
>>>>
>>>> This really seems to be a bug in WebLogic 7.0... At least it should 
>>>> work properly as long as not suspending a transaction that has been 
>>>> marked as rollback-only.
>>>>
>>>> Juergen
>>>>
>>>>
>>>> ________________________________
>>>>
>>>> Von: spr...@li... im 
>>>> Auftrag von Dmitri Maximovich
>>>> Gesendet: Fr 03.09.2004 23:07
>>>> An: spr...@li...
>>>> Betreff: [Springframework-developer] WLS 7 and TX suspend/resume - 
>>>> continue.
>>>>
>>>>
>>>>
>>>> I just tried WLS 7 with Spring 1.1rc2 and BMT transaction 
>>>> demaraction. It
>>>> doesn't work with standard JtaTransactionManager or with
>>>> WeblogicJtaTransactionManager, so something fundamentally broken in 
>>>> WLS7 (same
>>>> NPE as described in JIRA SPR-251).
>>>> Next I'll try to use WLS TransactionManager (exposed in JNDI) to 
>>>> suspend/resume
>>>> transaction without Spring to see it it's going to work.

Re: [Springframework-developer] WLS 7 and TX suspend/resume - continue.

[Thomas R. <tho...@tr...>]

Eugene,

If you could, please try the new 
WebLogicServerTransactionManagerFactoryBean.  This bean factory looks up 
the ServerTransactionManagerImpl using the TxHelper instead of the 
ClientTransactionManagerImpl via JNDI.  I'm pretty sure this will solve 
your issue.  This new bean factory will be part of 1.1 final that should 
be out tomorrow.

Here is a snippet from the configuration I tested with:

  <!--  transaction manager -->
    <bean id="wls7tm"
             
class="org.springframework.transaction.jta.WebLogicServerTransactionManagerFactoryBean"/> 

    <bean id="transactionManager"
             
class="org.springframework.transaction.jta.WebLogicJtaTransactionManager">
       <property name="transactionManager">
         <ref local="wls7tm"/>
       </property>
       </bean>

Thomas


Eugene Kuleshov wrote:

> Thomas Risberg wrote:
>
>> Thanks for the suggestion, but I have been using sp5 and it has the 
>> same issue as sp2 when it comes to calling forceResume.
>
>
>   We are on SP2 + some CRxxxx which basically include from-scratch 
> implementation of tx management. I can send an exact number next week 
> when I'll be at work.
>
>   regards,
>   Eugene
>
>
>> Stefan Kleineikenscheidt wrote:
>>
>>> Jürgen, Dimitry, Eugene,
>>>
>>> we've had problems with XA in WLS7 as well.  Unfortunately i wasn't
>>> involved in this issue, but i can remember that the XA 
>>> implementation of
>>> SP2 and SP4 differed.  Maybe you can give it a try on SP4.
>>>
>>> -Stefan
>>>
>>>
>>>  
>>>
>>>> -----Original Message-----
>>>> From: spr...@li... 
>>>> [mailto:spr...@li...]
>>>> On Behalf Of jürgen höller [werk3AT]
>>>> Sent: Saturday, September 04, 2004 1:03 PM
>>>> To: spr...@li...
>>>> Subject: Re: [Springframework-developer] WLS 7 and TX 
>>>> suspend/resume - continue.
>>>>
>>>>
>>>> Ideally, WebLogic should work properly with standard JTA 
>>>> TransactionManager resume in all cases, not needing the proprietary 
>>>> forceResume call. However, the least we can expect is that 
>>>> forceResume works properly: You could send a corresponding bug 
>>>> report to BEA, for WebLogic 7.0. However, they might tell you that 
>>>> they fixed the issue in WebLogic 8.1...
>>>>
>>>> Juergen
>>>>
>>>>
>>>> ________________________________
>>>>
>>>> Von: spr...@li... im 
>>>> Auftrag von jürgen höller [werk3AT]
>>>> Gesendet: Fr 03.09.2004 23:31
>>>> An: spr...@li...
>>>> Betreff: Re: [Springframework-developer] WLS 7 and TX 
>>>> suspend/resume - continue.
>>>>
>>>>
>>>>
>>>> As I already wrote in my JIRA comments: Many thanks for your 
>>>> efforts, Dmitri!
>>>>
>>>> I assume that with JtaTransactionManager, you'll get an 
>>>> IllegalStateException ("cannot resume rollback-only transaction" or 
>>>> the like), and with WebLogicJtaTransactionManager, you'll get the 
>>>> NPE in WebLogic code?
>>>>
>>>> This really seems to be a bug in WebLogic 7.0... At least it should 
>>>> work properly as long as not suspending a transaction that has been 
>>>> marked as rollback-only.
>>>>
>>>> Juergen
>>>>
>>>>
>>>> ________________________________
>>>>
>>>> Von: spr...@li... im 
>>>> Auftrag von Dmitri Maximovich
>>>> Gesendet: Fr 03.09.2004 23:07
>>>> An: spr...@li...
>>>> Betreff: [Springframework-developer] WLS 7 and TX suspend/resume - 
>>>> continue.
>>>>
>>>>
>>>>
>>>> I just tried WLS 7 with Spring 1.1rc2 and BMT transaction 
>>>> demaraction. It
>>>> doesn't work with standard JtaTransactionManager or with
>>>> WeblogicJtaTransactionManager, so something fundamentally broken in 
>>>> WLS7 (same
>>>> NPE as described in JIRA SPR-251).
>>>> Next I'll try to use WLS TransactionManager (exposed in JNDI) to 
>>>> suspend/resume
>>>> transaction without Spring to see it it's going to work.
>>>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>

Re: [Springframework-developer] WLS 7 and TX suspend/resume - continue.

[Eugene K. <eu...@pl...>]

Thomas Risberg wrote:

> Thanks for the suggestion, but I have been using sp5 and it has the same 
> issue as sp2 when it comes to calling forceResume.

   We are on SP2 + some CRxxxx which basically include from-scratch 
implementation of tx management. I can send an exact number next week when 
I'll be at work.

   regards,
   Eugene


> Stefan Kleineikenscheidt wrote:
> 
>> Jürgen, Dimitry, Eugene,
>>
>> we've had problems with XA in WLS7 as well.  Unfortunately i wasn't
>> involved in this issue, but i can remember that the XA implementation of
>> SP2 and SP4 differed.  Maybe you can give it a try on SP4.
>>
>> -Stefan
>>
>>
>>  
>>
>>> -----Original Message-----
>>> From: spr...@li... 
>>> [mailto:spr...@li...]
>>> On Behalf Of jürgen höller [werk3AT]
>>> Sent: Saturday, September 04, 2004 1:03 PM
>>> To: spr...@li...
>>> Subject: Re: [Springframework-developer] WLS 7 and TX suspend/resume 
>>> - continue.
>>>
>>>
>>> Ideally, WebLogic should work properly with standard JTA 
>>> TransactionManager resume in all cases, not needing the proprietary 
>>> forceResume call. However, the least we can expect is that 
>>> forceResume works properly: You could send a corresponding bug report 
>>> to BEA, for WebLogic 7.0. However, they might tell you that they 
>>> fixed the issue in WebLogic 8.1...
>>>
>>> Juergen
>>>
>>>
>>> ________________________________
>>>
>>> Von: spr...@li... im Auftrag 
>>> von jürgen höller [werk3AT]
>>> Gesendet: Fr 03.09.2004 23:31
>>> An: spr...@li...
>>> Betreff: Re: [Springframework-developer] WLS 7 and TX suspend/resume 
>>> - continue.
>>>
>>>
>>>
>>> As I already wrote in my JIRA comments: Many thanks for your efforts, 
>>> Dmitri!
>>>
>>> I assume that with JtaTransactionManager, you'll get an 
>>> IllegalStateException ("cannot resume rollback-only transaction" or 
>>> the like), and with WebLogicJtaTransactionManager, you'll get the NPE 
>>> in WebLogic code?
>>>
>>> This really seems to be a bug in WebLogic 7.0... At least it should 
>>> work properly as long as not suspending a transaction that has been 
>>> marked as rollback-only.
>>>
>>> Juergen
>>>
>>>
>>> ________________________________
>>>
>>> Von: spr...@li... im Auftrag 
>>> von Dmitri Maximovich
>>> Gesendet: Fr 03.09.2004 23:07
>>> An: spr...@li...
>>> Betreff: [Springframework-developer] WLS 7 and TX suspend/resume - 
>>> continue.
>>>
>>>
>>>
>>> I just tried WLS 7 with Spring 1.1rc2 and BMT transaction 
>>> demaraction. It
>>> doesn't work with standard JtaTransactionManager or with
>>> WeblogicJtaTransactionManager, so something fundamentally broken in 
>>> WLS7 (same
>>> NPE as described in JIRA SPR-251).
>>> Next I'll try to use WLS TransactionManager (exposed in JNDI) to 
>>> suspend/resume
>>> transaction without Spring to see it it's going to work.

Re: [Springframework-developer] WLS 7 and TX suspend/resume - continue.

[Thomas R. <tho...@tr...>]

Both the UserTransaction and TransactionManager JNDI entries for WLS 8.1 
are of type weblogic.transaction.internal.ClientTransactionManagerImpl.

Thomas


jürgen höller [werk3AT] wrote:

>Thanks, Thomas - it's great to have this for 1.1 final!
> 
>Did you have a chance to check whether WebLogic 8.1's UserTransaction object found at "java:comp/UserTransaction" implements the javax.transaction.TransactionManager interface too? It does so on WebLogic 7.0. The benefit of such a scenario is that Spring's JtaTransactionManager will autodetect the TransactionManager, without any special setup.
> 
>I've documented the basic JTA setup options for popular J2EE servers in JtaTransactionManager's javadoc. It would be good to verify whether my autodetection comment just applies to WebLogic 7.0 or also to WebLogic 8.1.
> 
>Juergen
> 
>
>________________________________
>
>Von: spr...@li... im Auftrag von Thomas Risberg
>Gesendet: Sa 04.09.2004 17:42
>An: spr...@li...
>Betreff: Re: [Springframework-developer] WLS 7 and TX suspend/resume - continue.
>
>
>
>Juergen, Eugene,  Dimitry, all WLS 70 users,
>
>We now have a new WebLogicServerTransactionManagerFactoryBean.  This
>bean factory looks up the ServerTransactionManagerImpl to get around the
>NPE that was thrown during a "forceResume".  I based the code on the
>WebSphere variant.  This has been tested on WebLogic 7.0 SP5 and checked
>in.  Here is a snippet from the configuration I tested with:
>
>   <!--  transaction manager -->
>     <bean id="wls7tm"
>             
>class="org.springframework.transaction.jta.WebLogicServerTransactionManagerFactoryBean"/>
>     <bean id="transactionManager"
>             
>class="org.springframework.transaction.jta.WebLogicJtaTransactionManager">
>        <property name="transactionManager">
>          <ref local="wls7tm"/>
>        </property>
>        </bean>
>
>Thomas
>
>
>Thomas Risberg wrote:
>
>  
>
>>Juergen,
>>
>>I'll try to implement and test a
>>WebLogicServerTransactionManagerFactoryBean today.  I'll keep you posted.
>>
>>For WLS 8.1 the TxHelper.getTransactionManager method is marked as
>>deprecated even though it is not documented as such in the JavaDocs. 
>>There is also a brand new method getClientTransactionManager for 8.1
>>that is starting out marked as deprecated.  Go figure.  We are
>>probably better off recommending the JNDI lookups for 8.1.
>>
>>Thomas
>>
>>
>>
>>jürgen höller [werk3AT] wrote:
>>
>>    
>>
>>>Thanks, Thomas! This means that there *is* a way to make it work on
>>>WebLogic 7! Eugene, Dmitri, your pain finally has an end! :-)
>>>
>>>Regarding obtaining the TransactionManager via the TxHelper on
>>>WebLogic 7: That can easily be factored out into a custom
>>>FactoryBean, like we did for WebSphere (see
>>>WebSphereTransactionManagerFactoryBean), to be passed into
>>>JtaTransactionManager's respectively WebLogicJtaTransactionManager's
>>>"transactionManager" property. So we don't need a further
>>>JtaTransactionManager subclass for this, just a further
>>>TransactionManager lookup strategy.
>>>
>>>BTW, Dmitri told me that the WebLogic UserTransaction object at
>>>"java:comp/UserTransaction" implements the TransactionManager
>>>interface too, but that obviously forceResume doesn't work there... I
>>>assume the ClientTransactionManagerImpl is returned there, not the
>>>ServerTransactionManagerImpl.
>>>
>>>If we can double-check that this works better than the
>>>TransactionManager fetched from JNDI, I suggest to add a
>>>WebLogicServerTransactionManagerFactoryBean (or a similar name),
>>>clearly documenting that this is meant as an alternative to the
>>>standard JNDI TransactionManager reference that WebLogic provides,
>>>mainly for WebLogic 7. I wouldn't mind to do this even for the 1.1
>>>final release tomorrow...
>>>
>>>Is the TxHelper lookup available on WebLogic 8.1 too? Of course, it
>>>shouldn't be necessary there, as the standard JNDI TransactionManager
>>>reference will work too. I just wonder whether it's available and
>>>would work in principle: People could then configure a
>>>WebLogicServerTransactionManagerFactoryBean to be able to deploy on
>>>both WebLogic 7 and WebLogic 8, without adapting their Spring
>>>configuration.
>>>
>>>Of course, such a WebLogicServerTransactionManagerFactoryBean would
>>>have to be coded via reflection to avoid compile-time dependencies on
>>>WebLogic, analogous to WebSphereTransactionManagerFactoryBean. Do you
>>>have the chance to do this before tomorrow, Thomas?
>>>
>>>Juergen
>>>
>>>
>>>________________________________
>>>
>>>Von: spr...@li... im Auftrag
>>>von Thomas Risberg
>>>Gesendet: Sa 04.09.2004 14:30
>>>An: spr...@li...
>>>Betreff: Re: [Springframework-developer] WLS 7 and TX suspend/resume
>>>- continue.
>>>
>>>
>>>
>>>I have done some additional testing for this issue and this is what I
>>>have found.
>>>
>>>WebLogic exposes a client TransactionManager implementation via JNDI
>>>(weblogic.transaction.internal.ClientTransactionManagerImpl) and in WLS
>>>7.0 it is throwing an NPE when you call forceResume (with or without a
>>>suspended transaction that has been marked for RollbackOnly).
>>>
>>>They also have a different server implementation
>>>(weblogic.transaction.internal.ServerTransactionManagerImpl) that is
>>>returnd by a call to TxHelper.getTransactionManager().  With this TM the
>>>force resume works as expected.
>>>
>>>So the workaround for now is to do the suspend/resume using the TM
>>>returned by TxHelper before calling the Spring managed code.
>>>Alternatively we could provide a WebLogic7JtaTransactionManager that
>>>uses this method of obtaining the TM.
>>>
>>>I doubt that BEA will fix this issue in WLS 7.0.  They will probably
>>>suggest to upgrade to 8.1 or use the TxHelper to obtain the TM.
>>>
>>>Thomas
>>>
>>>
>>>jürgen höller [werk3AT] wrote:
>>>
>>>
>>>
>>>      
>>>
>>>>Ideally, WebLogic should work properly with standard JTA
>>>>TransactionManager resume in all cases, not needing the proprietary
>>>>forceResume call. However, the least we can expect is that
>>>>forceResume works properly: You could send a corresponding bug
>>>>report to BEA, for WebLogic 7.0. However, they might tell you that
>>>>they fixed the issue in WebLogic 8.1...
>>>>
>>>>Juergen
>>>>
>>>>
>>>>________________________________
>>>>
>>>>Von: spr...@li... im
>>>>Auftrag von jürgen höller [werk3AT]
>>>>Gesendet: Fr 03.09.2004 23:31
>>>>An: spr...@li...
>>>>Betreff: Re: [Springframework-developer] WLS 7 and TX suspend/resume
>>>>- continue.
>>>>
>>>>
>>>>
>>>>As I already wrote in my JIRA comments: Many thanks for your
>>>>efforts, Dmitri!
>>>>
>>>>I assume that with JtaTransactionManager, you'll get an
>>>>IllegalStateException ("cannot resume rollback-only transaction" or
>>>>the like), and with WebLogicJtaTransactionManager, you'll get the
>>>>NPE in WebLogic code?
>>>>
>>>>This really seems to be a bug in WebLogic 7.0... At least it should
>>>>work properly as long as not suspending a transaction that has been
>>>>marked as rollback-only.
>>>>
>>>>Juergen
>>>>
>>>>
>>>>________________________________
>>>>
>>>>Von: spr...@li... im
>>>>Auftrag von Dmitri Maximovich
>>>>Gesendet: Fr 03.09.2004 23:07
>>>>An: spr...@li...
>>>>Betreff: [Springframework-developer] WLS 7 and TX suspend/resume -
>>>>continue.
>>>>
>>>>
>>>>
>>>>I just tried WLS 7 with Spring 1.1rc2 and BMT transaction
>>>>demaraction. It
>>>>doesn't work with standard JtaTransactionManager or with
>>>>WeblogicJtaTransactionManager, so something fundamentally broken in
>>>>WLS7 (same
>>>>NPE as described in JIRA SPR-251).
>>>>Next I'll try to use WLS TransactionManager (exposed in JNDI) to
>>>>suspend/resume
>>>>transaction without Spring to see it it's going to work.
>>>>
>>>>
>>>>
>>>>
>>>>-------------------------------------------------------
>>>>This SF.Net email is sponsored by BEA Weblogic Workshop
>>>>FREE Java Enterprise J2EE developer tools!
>>>>Get your free copy of BEA WebLogic Workshop 8.1 today.
>>>>http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
>>>>_______________________________________________
>>>>Springframework-developer mailing list
>>>>Spr...@li...
>>>>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>>>
>>>>
>>>>
>>>>
>>>>-------------------------------------------------------
>>>>This SF.Net email is sponsored by BEA Weblogic Workshop
>>>>FREE Java Enterprise J2EE developer tools!
>>>>Get your free copy of BEA WebLogic Workshop 8.1 today.
>>>>http://ads.osdn.com/?ad_idP47&alloc_id808&op=ick
>>>>_______________________________________________
>>>>Springframework-developer mailing list
>>>>Spr...@li...
>>>>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>>>
>>>>
>>>>
>>>>
>>>>-------------------------------------------------------
>>>>This SF.Net email is sponsored by BEA Weblogic Workshop
>>>>FREE Java Enterprise J2EE developer tools!
>>>>Get your free copy of BEA WebLogic Workshop 8.1 today.
>>>>http://ads.osdn.com/?ad_idP47&alloc_id808&op=click
>>>>_______________________________________________
>>>>Springframework-developer mailing list
>>>>Spr...@li...
>>>>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> 
>>>>        
>>>>
>>>
>>>
>>>-------------------------------------------------------
>>>This SF.Net email is sponsored by BEA Weblogic Workshop
>>>FREE Java Enterprise J2EE developer tools!
>>>Get your free copy of BEA WebLogic Workshop 8.1 today.
>>>http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
>>>_______________________________________________
>>>Springframework-developer mailing list
>>>Spr...@li...
>>>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>>
>>>
>>>
>>>
>>>-------------------------------------------------------
>>>This SF.Net email is sponsored by BEA Weblogic Workshop
>>>FREE Java Enterprise J2EE developer tools!
>>>Get your free copy of BEA WebLogic Workshop 8.1 today.
>>>http://ads.osdn.com/?ad_idP47&alloc_id808&op=click
>>>_______________________________________________
>>>Springframework-developer mailing list
>>>Spr...@li...
>>>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>>
>>>
>>>
>>>
>>>
>>>      
>>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by BEA Weblogic Workshop
>>FREE Java Enterprise J2EE developer tools!
>>Get your free copy of BEA WebLogic Workshop 8.1 today.
>>http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
>>_______________________________________________
>>Springframework-developer mailing list
>>Spr...@li...
>>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>
>>
>>
>>    
>>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by BEA Weblogic Workshop
>FREE Java Enterprise J2EE developer tools!
>Get your free copy of BEA WebLogic Workshop 8.1 today.
>http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by BEA Weblogic Workshop
>FREE Java Enterprise J2EE developer tools!
>Get your free copy of BEA WebLogic Workshop 8.1 today.
>http://ads.osdn.com/?ad_idP47&alloc_id808&op=click
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
>  
>

Re: [Springframework-developer] WLS 7 and TX suspend/resume - continue.

[<jue...@we...>]

Thanks, Thomas - it's great to have this for 1.1 final!
=20
Did you have a chance to check whether WebLogic 8.1's UserTransaction =
object found at "java:comp/UserTransaction" implements the =
javax.transaction.TransactionManager interface too? It does so on =
WebLogic 7.0. The benefit of such a scenario is that Spring's =
JtaTransactionManager will autodetect the TransactionManager, without =
any special setup.
=20
I've documented the basic JTA setup options for popular J2EE servers in =
JtaTransactionManager's javadoc. It would be good to verify whether my =
autodetection comment just applies to WebLogic 7.0 or also to WebLogic =
8.1.
=20
Juergen
=20

________________________________

Von: spr...@li... im Auftrag =
von Thomas Risberg
Gesendet: Sa 04.09.2004 17:42
An: spr...@li...
Betreff: Re: [Springframework-developer] WLS 7 and TX suspend/resume - =
continue.



Juergen, Eugene,  Dimitry, all WLS 70 users,

We now have a new WebLogicServerTransactionManagerFactoryBean.  This
bean factory looks up the ServerTransactionManagerImpl to get around the
NPE that was thrown during a "forceResume".  I based the code on the
WebSphere variant.  This has been tested on WebLogic 7.0 SP5 and checked
in.  Here is a snippet from the configuration I tested with:

   <!--  transaction manager -->
     <bean id=3D"wls7tm"
            =20
class=3D"org.springframework.transaction.jta.WebLogicServerTransactionMan=
agerFactoryBean"/>
     <bean id=3D"transactionManager"
            =20
class=3D"org.springframework.transaction.jta.WebLogicJtaTransactionManage=
r">
        <property name=3D"transactionManager">
          <ref local=3D"wls7tm"/>
        </property>
        </bean>

Thomas


Thomas Risberg wrote:

> Juergen,
>
> I'll try to implement and test a
> WebLogicServerTransactionManagerFactoryBean today.  I'll keep you =
posted.
>
> For WLS 8.1 the TxHelper.getTransactionManager method is marked as
> deprecated even though it is not documented as such in the JavaDocs.=20
> There is also a brand new method getClientTransactionManager for 8.1
> that is starting out marked as deprecated.  Go figure.  We are
> probably better off recommending the JNDI lookups for 8.1.
>
> Thomas
>
>
>
> j=FCrgen h=F6ller [werk3AT] wrote:
>
>> Thanks, Thomas! This means that there *is* a way to make it work on
>> WebLogic 7! Eugene, Dmitri, your pain finally has an end! :-)
>>
>> Regarding obtaining the TransactionManager via the TxHelper on
>> WebLogic 7: That can easily be factored out into a custom
>> FactoryBean, like we did for WebSphere (see
>> WebSphereTransactionManagerFactoryBean), to be passed into
>> JtaTransactionManager's respectively WebLogicJtaTransactionManager's
>> "transactionManager" property. So we don't need a further
>> JtaTransactionManager subclass for this, just a further
>> TransactionManager lookup strategy.
>>
>> BTW, Dmitri told me that the WebLogic UserTransaction object at
>> "java:comp/UserTransaction" implements the TransactionManager
>> interface too, but that obviously forceResume doesn't work there... I
>> assume the ClientTransactionManagerImpl is returned there, not the
>> ServerTransactionManagerImpl.
>>
>> If we can double-check that this works better than the
>> TransactionManager fetched from JNDI, I suggest to add a
>> WebLogicServerTransactionManagerFactoryBean (or a similar name),
>> clearly documenting that this is meant as an alternative to the
>> standard JNDI TransactionManager reference that WebLogic provides,
>> mainly for WebLogic 7. I wouldn't mind to do this even for the 1.1
>> final release tomorrow...
>>
>> Is the TxHelper lookup available on WebLogic 8.1 too? Of course, it
>> shouldn't be necessary there, as the standard JNDI TransactionManager
>> reference will work too. I just wonder whether it's available and
>> would work in principle: People could then configure a
>> WebLogicServerTransactionManagerFactoryBean to be able to deploy on
>> both WebLogic 7 and WebLogic 8, without adapting their Spring
>> configuration.
>>
>> Of course, such a WebLogicServerTransactionManagerFactoryBean would
>> have to be coded via reflection to avoid compile-time dependencies on
>> WebLogic, analogous to WebSphereTransactionManagerFactoryBean. Do you
>> have the chance to do this before tomorrow, Thomas?
>>
>> Juergen
>>
>>
>> ________________________________
>>
>> Von: spr...@li... im Auftrag
>> von Thomas Risberg
>> Gesendet: Sa 04.09.2004 14:30
>> An: spr...@li...
>> Betreff: Re: [Springframework-developer] WLS 7 and TX suspend/resume
>> - continue.
>>
>>
>>
>> I have done some additional testing for this issue and this is what I
>> have found.
>>
>> WebLogic exposes a client TransactionManager implementation via JNDI
>> (weblogic.transaction.internal.ClientTransactionManagerImpl) and in =
WLS
>> 7.0 it is throwing an NPE when you call forceResume (with or without =
a
>> suspended transaction that has been marked for RollbackOnly).
>>
>> They also have a different server implementation
>> (weblogic.transaction.internal.ServerTransactionManagerImpl) that is
>> returnd by a call to TxHelper.getTransactionManager().  With this TM =
the
>> force resume works as expected.
>>
>> So the workaround for now is to do the suspend/resume using the TM
>> returned by TxHelper before calling the Spring managed code.
>> Alternatively we could provide a WebLogic7JtaTransactionManager that
>> uses this method of obtaining the TM.
>>
>> I doubt that BEA will fix this issue in WLS 7.0.  They will probably
>> suggest to upgrade to 8.1 or use the TxHelper to obtain the TM.
>>
>> Thomas
>>
>>
>> j=FCrgen h=F6ller [werk3AT] wrote:
>>
>>=20
>>
>>> Ideally, WebLogic should work properly with standard JTA
>>> TransactionManager resume in all cases, not needing the proprietary
>>> forceResume call. However, the least we can expect is that
>>> forceResume works properly: You could send a corresponding bug
>>> report to BEA, for WebLogic 7.0. However, they might tell you that
>>> they fixed the issue in WebLogic 8.1...
>>>
>>> Juergen
>>>
>>>
>>> ________________________________
>>>
>>> Von: spr...@li... im
>>> Auftrag von j=FCrgen h=F6ller [werk3AT]
>>> Gesendet: Fr 03.09.2004 23:31
>>> An: spr...@li...
>>> Betreff: Re: [Springframework-developer] WLS 7 and TX suspend/resume
>>> - continue.
>>>
>>>
>>>
>>> As I already wrote in my JIRA comments: Many thanks for your
>>> efforts, Dmitri!
>>>
>>> I assume that with JtaTransactionManager, you'll get an
>>> IllegalStateException ("cannot resume rollback-only transaction" or
>>> the like), and with WebLogicJtaTransactionManager, you'll get the
>>> NPE in WebLogic code?
>>>
>>> This really seems to be a bug in WebLogic 7.0... At least it should
>>> work properly as long as not suspending a transaction that has been
>>> marked as rollback-only.
>>>
>>> Juergen
>>>
>>>
>>> ________________________________
>>>
>>> Von: spr...@li... im
>>> Auftrag von Dmitri Maximovich
>>> Gesendet: Fr 03.09.2004 23:07
>>> An: spr...@li...
>>> Betreff: [Springframework-developer] WLS 7 and TX suspend/resume -
>>> continue.
>>>
>>>
>>>
>>> I just tried WLS 7 with Spring 1.1rc2 and BMT transaction
>>> demaraction. It
>>> doesn't work with standard JtaTransactionManager or with
>>> WeblogicJtaTransactionManager, so something fundamentally broken in
>>> WLS7 (same
>>> NPE as described in JIRA SPR-251).
>>> Next I'll try to use WLS TransactionManager (exposed in JNDI) to
>>> suspend/resume
>>> transaction without Spring to see it it's going to work.
>>>
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> This SF.Net email is sponsored by BEA Weblogic Workshop
>>> FREE Java Enterprise J2EE developer tools!
>>> Get your free copy of BEA WebLogic Workshop 8.1 today.
>>> http://ads.osdn.com/?ad_id=3D5047&alloc_id=3D10808&op=3Dclick
>>> _______________________________________________
>>> Springframework-developer mailing list
>>> Spr...@li...
>>> =
https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>>
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> This SF.Net email is sponsored by BEA Weblogic Workshop
>>> FREE Java Enterprise J2EE developer tools!
>>> Get your free copy of BEA WebLogic Workshop 8.1 today.
>>> http://ads.osdn.com/?ad_idP47&alloc_id=10808&op=3Dick
>>> _______________________________________________
>>> Springframework-developer mailing list
>>> Spr...@li...
>>> =
https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>>
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> This SF.Net email is sponsored by BEA Weblogic Workshop
>>> FREE Java Enterprise J2EE developer tools!
>>> Get your free copy of BEA WebLogic Workshop 8.1 today.
>>> http://ads.osdn.com/?ad_idP47&alloc_id=10808&op=3Dclick
>>> _______________________________________________
>>> Springframework-developer mailing list
>>> Spr...@li...
>>> =
https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>>
>>>
>>>
>>>
>>>
>>> =20
>>
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by BEA Weblogic Workshop
>> FREE Java Enterprise J2EE developer tools!
>> Get your free copy of BEA WebLogic Workshop 8.1 today.
>> http://ads.osdn.com/?ad_id=3D5047&alloc_id=3D10808&op=3Dclick
>> _______________________________________________
>> Springframework-developer mailing list
>> Spr...@li...
>> =
https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by BEA Weblogic Workshop
>> FREE Java Enterprise J2EE developer tools!
>> Get your free copy of BEA WebLogic Workshop 8.1 today.
>> http://ads.osdn.com/?ad_idP47&alloc_id=10808&op=3Dclick
>> _______________________________________________
>> Springframework-developer mailing list
>> Spr...@li...
>> =
https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>
>>
>>
>>=20
>>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=3D5047&alloc_id=3D10808&op=3Dclick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=3D5047&alloc_id=3D10808&op=3Dclick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] WLS 7 and TX suspend/resume - continue.

[Thomas R. <tho...@tr...>]

Juergen, Eugene,  Dimitry, all WLS 70 users,

We now have a new WebLogicServerTransactionManagerFactoryBean.  This 
bean factory looks up the ServerTransactionManagerImpl to get around the 
NPE that was thrown during a "forceResume".  I based the code on the 
WebSphere variant.  This has been tested on WebLogic 7.0 SP5 and checked 
in.  Here is a snippet from the configuration I tested with:

   <!--  transaction manager -->
     <bean id="wls7tm"
              
class="org.springframework.transaction.jta.WebLogicServerTransactionManagerFactoryBean"/>
     <bean id="transactionManager"
              
class="org.springframework.transaction.jta.WebLogicJtaTransactionManager">
        <property name="transactionManager">
          <ref local="wls7tm"/>
        </property>
        </bean>

Thomas


Thomas Risberg wrote:

> Juergen,
>
> I'll try to implement and test a 
> WebLogicServerTransactionManagerFactoryBean today.  I'll keep you posted.
>
> For WLS 8.1 the TxHelper.getTransactionManager method is marked as 
> deprecated even though it is not documented as such in the JavaDocs.  
> There is also a brand new method getClientTransactionManager for 8.1 
> that is starting out marked as deprecated.  Go figure.  We are 
> probably better off recommending the JNDI lookups for 8.1.
>
> Thomas
>
>
>
> jürgen höller [werk3AT] wrote:
>
>> Thanks, Thomas! This means that there *is* a way to make it work on 
>> WebLogic 7! Eugene, Dmitri, your pain finally has an end! :-)
>>
>> Regarding obtaining the TransactionManager via the TxHelper on 
>> WebLogic 7: That can easily be factored out into a custom 
>> FactoryBean, like we did for WebSphere (see 
>> WebSphereTransactionManagerFactoryBean), to be passed into 
>> JtaTransactionManager's respectively WebLogicJtaTransactionManager's 
>> "transactionManager" property. So we don't need a further 
>> JtaTransactionManager subclass for this, just a further 
>> TransactionManager lookup strategy.
>>
>> BTW, Dmitri told me that the WebLogic UserTransaction object at 
>> "java:comp/UserTransaction" implements the TransactionManager 
>> interface too, but that obviously forceResume doesn't work there... I 
>> assume the ClientTransactionManagerImpl is returned there, not the 
>> ServerTransactionManagerImpl.
>>
>> If we can double-check that this works better than the 
>> TransactionManager fetched from JNDI, I suggest to add a 
>> WebLogicServerTransactionManagerFactoryBean (or a similar name), 
>> clearly documenting that this is meant as an alternative to the 
>> standard JNDI TransactionManager reference that WebLogic provides, 
>> mainly for WebLogic 7. I wouldn't mind to do this even for the 1.1 
>> final release tomorrow...
>>
>> Is the TxHelper lookup available on WebLogic 8.1 too? Of course, it 
>> shouldn't be necessary there, as the standard JNDI TransactionManager 
>> reference will work too. I just wonder whether it's available and 
>> would work in principle: People could then configure a 
>> WebLogicServerTransactionManagerFactoryBean to be able to deploy on 
>> both WebLogic 7 and WebLogic 8, without adapting their Spring 
>> configuration.
>>
>> Of course, such a WebLogicServerTransactionManagerFactoryBean would 
>> have to be coded via reflection to avoid compile-time dependencies on 
>> WebLogic, analogous to WebSphereTransactionManagerFactoryBean. Do you 
>> have the chance to do this before tomorrow, Thomas?
>>
>> Juergen
>>
>>
>> ________________________________
>>
>> Von: spr...@li... im Auftrag 
>> von Thomas Risberg
>> Gesendet: Sa 04.09.2004 14:30
>> An: spr...@li...
>> Betreff: Re: [Springframework-developer] WLS 7 and TX suspend/resume 
>> - continue.
>>
>>
>>
>> I have done some additional testing for this issue and this is what I
>> have found.
>>
>> WebLogic exposes a client TransactionManager implementation via JNDI 
>> (weblogic.transaction.internal.ClientTransactionManagerImpl) and in WLS
>> 7.0 it is throwing an NPE when you call forceResume (with or without a
>> suspended transaction that has been marked for RollbackOnly).
>>
>> They also have a different server implementation
>> (weblogic.transaction.internal.ServerTransactionManagerImpl) that is
>> returnd by a call to TxHelper.getTransactionManager().  With this TM the
>> force resume works as expected.
>>
>> So the workaround for now is to do the suspend/resume using the TM
>> returned by TxHelper before calling the Spring managed code.
>> Alternatively we could provide a WebLogic7JtaTransactionManager that
>> uses this method of obtaining the TM.
>>
>> I doubt that BEA will fix this issue in WLS 7.0.  They will probably
>> suggest to upgrade to 8.1 or use the TxHelper to obtain the TM.
>>
>> Thomas
>>
>>
>> jürgen höller [werk3AT] wrote:
>>
>>  
>>
>>> Ideally, WebLogic should work properly with standard JTA 
>>> TransactionManager resume in all cases, not needing the proprietary 
>>> forceResume call. However, the least we can expect is that 
>>> forceResume works properly: You could send a corresponding bug 
>>> report to BEA, for WebLogic 7.0. However, they might tell you that 
>>> they fixed the issue in WebLogic 8.1...
>>>
>>> Juergen
>>>
>>>
>>> ________________________________
>>>
>>> Von: spr...@li... im 
>>> Auftrag von jürgen höller [werk3AT]
>>> Gesendet: Fr 03.09.2004 23:31
>>> An: spr...@li...
>>> Betreff: Re: [Springframework-developer] WLS 7 and TX suspend/resume 
>>> - continue.
>>>
>>>
>>>
>>> As I already wrote in my JIRA comments: Many thanks for your 
>>> efforts, Dmitri!
>>>
>>> I assume that with JtaTransactionManager, you'll get an 
>>> IllegalStateException ("cannot resume rollback-only transaction" or 
>>> the like), and with WebLogicJtaTransactionManager, you'll get the 
>>> NPE in WebLogic code?
>>>
>>> This really seems to be a bug in WebLogic 7.0... At least it should 
>>> work properly as long as not suspending a transaction that has been 
>>> marked as rollback-only.
>>>
>>> Juergen
>>>
>>>
>>> ________________________________
>>>
>>> Von: spr...@li... im 
>>> Auftrag von Dmitri Maximovich
>>> Gesendet: Fr 03.09.2004 23:07
>>> An: spr...@li...
>>> Betreff: [Springframework-developer] WLS 7 and TX suspend/resume - 
>>> continue.
>>>
>>>
>>>
>>> I just tried WLS 7 with Spring 1.1rc2 and BMT transaction 
>>> demaraction. It
>>> doesn't work with standard JtaTransactionManager or with
>>> WeblogicJtaTransactionManager, so something fundamentally broken in 
>>> WLS7 (same
>>> NPE as described in JIRA SPR-251).
>>> Next I'll try to use WLS TransactionManager (exposed in JNDI) to 
>>> suspend/resume
>>> transaction without Spring to see it it's going to work.
>>>
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> This SF.Net email is sponsored by BEA Weblogic Workshop
>>> FREE Java Enterprise J2EE developer tools!
>>> Get your free copy of BEA WebLogic Workshop 8.1 today.
>>> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
>>> _______________________________________________
>>> Springframework-developer mailing list
>>> Spr...@li...
>>> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>>
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> This SF.Net email is sponsored by BEA Weblogic Workshop
>>> FREE Java Enterprise J2EE developer tools!
>>> Get your free copy of BEA WebLogic Workshop 8.1 today.
>>> http://ads.osdn.com/?ad_idP47&alloc_id808&op=ick
>>> _______________________________________________
>>> Springframework-developer mailing list
>>> Spr...@li...
>>> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>>
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> This SF.Net email is sponsored by BEA Weblogic Workshop
>>> FREE Java Enterprise J2EE developer tools!
>>> Get your free copy of BEA WebLogic Workshop 8.1 today.
>>> http://ads.osdn.com/?ad_idP47&alloc_id808&op=click
>>> _______________________________________________
>>> Springframework-developer mailing list
>>> Spr...@li...
>>> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>>
>>>
>>>
>>>
>>>
>>>   
>>
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by BEA Weblogic Workshop
>> FREE Java Enterprise J2EE developer tools!
>> Get your free copy of BEA WebLogic Workshop 8.1 today.
>> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
>> _______________________________________________
>> Springframework-developer mailing list
>> Spr...@li...
>> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by BEA Weblogic Workshop
>> FREE Java Enterprise J2EE developer tools!
>> Get your free copy of BEA WebLogic Workshop 8.1 today.
>> http://ads.osdn.com/?ad_idP47&alloc_id808&op=click
>> _______________________________________________
>> Springframework-developer mailing list
>> Spr...@li...
>> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>
>>
>>
>>  
>>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>

Re: [Springframework-developer] Form simplification tags for JSP

[Daniel M. <mi...@pa...>]

I just submitted the tags I wrote for Spring <http://opensource.atlassian=
.com/projects/spring/browse/SPR-310>. They are not exactly like the FreeM=
arker/Velocity tags written by Darren, but I think they are pretty powerf=
ul.

The only one I'm not sold on is the forEachError tag--it may be a better =
idea to let this one up to the developer writing the pages, as the markup=
 surrounding error messages probably varies quite a bit from project to p=
roject. For example, I like to mark up my error messages like this:

<ul class=3D"error">
  <li class=3D"error">Error Message 1</li>
  <li class=3D"error">Error Message 2</li>
</ul>

As it is, the forEachError tag allows this kind of markup.

Daniel Miller

j=FCrgen h=F6ller [werk3AT] wrote:
> Seth, Daniel, everybody,
>=20
> I've created a new JIRA issues for JSP form tags. The former "form simp=
lification macros" issues has been closed for 1.1, as the Velocity and Fr=
eeMarker macros are ready now.
>=20
> http://opensource.atlassian.com/projects/spring/browse/SPR-310
>=20
> I've specified 1.1.1 as target, alongside a couple of other enhancement=
s that we've deferred beyond 1.1 final. It would be great if we managed t=
o get JSP form tags ready by then (in about 4-6 weeks)!
> =20
> Juergen
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_idP47&alloc_id=10808&op=3Dclick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>=20
>=20

Re: [Springframework-developer] WLS 7 and TX suspend/resume - continue.

[Thomas R. <tho...@tr...>]

Juergen,

I'll try to implement and test a 
WebLogicServerTransactionManagerFactoryBean today.  I'll keep you posted.

For WLS 8.1 the TxHelper.getTransactionManager method is marked as 
deprecated even though it is not documented as such in the JavaDocs.  
There is also a brand new method getClientTransactionManager for 8.1 
that is starting out marked as deprecated.  Go figure.  We are probably 
better off recommending the JNDI lookups for 8.1.

Thomas



jürgen höller [werk3AT] wrote:

>Thanks, Thomas! This means that there *is* a way to make it work on WebLogic 7! Eugene, Dmitri, your pain finally has an end! :-)
> 
>Regarding obtaining the TransactionManager via the TxHelper on WebLogic 7: That can easily be factored out into a custom FactoryBean, like we did for WebSphere (see WebSphereTransactionManagerFactoryBean), to be passed into JtaTransactionManager's respectively WebLogicJtaTransactionManager's "transactionManager" property. So we don't need a further JtaTransactionManager subclass for this, just a further TransactionManager lookup strategy.
> 
>BTW, Dmitri told me that the WebLogic UserTransaction object at "java:comp/UserTransaction" implements the TransactionManager interface too, but that obviously forceResume doesn't work there... I assume the ClientTransactionManagerImpl is returned there, not the ServerTransactionManagerImpl.
> 
>If we can double-check that this works better than the TransactionManager fetched from JNDI, I suggest to add a WebLogicServerTransactionManagerFactoryBean (or a similar name), clearly documenting that this is meant as an alternative to the standard JNDI TransactionManager reference that WebLogic provides, mainly for WebLogic 7. I wouldn't mind to do this even for the 1.1 final release tomorrow...
> 
>Is the TxHelper lookup available on WebLogic 8.1 too? Of course, it shouldn't be necessary there, as the standard JNDI TransactionManager reference will work too. I just wonder whether it's available and would work in principle: People could then configure a WebLogicServerTransactionManagerFactoryBean to be able to deploy on both WebLogic 7 and WebLogic 8, without adapting their Spring configuration.
> 
>Of course, such a WebLogicServerTransactionManagerFactoryBean would have to be coded via reflection to avoid compile-time dependencies on WebLogic, analogous to WebSphereTransactionManagerFactoryBean. Do you have the chance to do this before tomorrow, Thomas?
> 
>Juergen
> 
>
>________________________________
>
>Von: spr...@li... im Auftrag von Thomas Risberg
>Gesendet: Sa 04.09.2004 14:30
>An: spr...@li...
>Betreff: Re: [Springframework-developer] WLS 7 and TX suspend/resume - continue.
>
>
>
>I have done some additional testing for this issue and this is what I
>have found.
>
>WebLogic exposes a client TransactionManager implementation via JNDI 
>(weblogic.transaction.internal.ClientTransactionManagerImpl) and in WLS
>7.0 it is throwing an NPE when you call forceResume (with or without a
>suspended transaction that has been marked for RollbackOnly).
>
>They also have a different server implementation
>(weblogic.transaction.internal.ServerTransactionManagerImpl) that is
>returnd by a call to TxHelper.getTransactionManager().  With this TM the
>force resume works as expected.
>
>So the workaround for now is to do the suspend/resume using the TM
>returned by TxHelper before calling the Spring managed code.
>Alternatively we could provide a WebLogic7JtaTransactionManager that
>uses this method of obtaining the TM.
>
>I doubt that BEA will fix this issue in WLS 7.0.  They will probably
>suggest to upgrade to 8.1 or use the TxHelper to obtain the TM.
>
>Thomas
>
>
>jürgen höller [werk3AT] wrote:
>
>  
>
>>Ideally, WebLogic should work properly with standard JTA TransactionManager resume in all cases, not needing the proprietary forceResume call. However, the least we can expect is that forceResume works properly: You could send a corresponding bug report to BEA, for WebLogic 7.0. However, they might tell you that they fixed the issue in WebLogic 8.1...
>>
>>Juergen
>>
>>
>>________________________________
>>
>>Von: spr...@li... im Auftrag von jürgen höller [werk3AT]
>>Gesendet: Fr 03.09.2004 23:31
>>An: spr...@li...
>>Betreff: Re: [Springframework-developer] WLS 7 and TX suspend/resume - continue.
>>
>>
>>
>>As I already wrote in my JIRA comments: Many thanks for your efforts, Dmitri!
>>
>>I assume that with JtaTransactionManager, you'll get an IllegalStateException ("cannot resume rollback-only transaction" or the like), and with WebLogicJtaTransactionManager, you'll get the NPE in WebLogic code?
>>
>>This really seems to be a bug in WebLogic 7.0... At least it should work properly as long as not suspending a transaction that has been marked as rollback-only.
>>
>>Juergen
>>
>>
>>________________________________
>>
>>Von: spr...@li... im Auftrag von Dmitri Maximovich
>>Gesendet: Fr 03.09.2004 23:07
>>An: spr...@li...
>>Betreff: [Springframework-developer] WLS 7 and TX suspend/resume - continue.
>>
>>
>>
>>I just tried WLS 7 with Spring 1.1rc2 and BMT transaction demaraction. It
>>doesn't work with standard JtaTransactionManager or with
>>WeblogicJtaTransactionManager, so something fundamentally broken in WLS7 (same
>>NPE as described in JIRA SPR-251).
>>Next I'll try to use WLS TransactionManager (exposed in JNDI) to suspend/resume
>>transaction without Spring to see it it's going to work.
>>
>>
>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by BEA Weblogic Workshop
>>FREE Java Enterprise J2EE developer tools!
>>Get your free copy of BEA WebLogic Workshop 8.1 today.
>>http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
>>_______________________________________________
>>Springframework-developer mailing list
>>Spr...@li...
>>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>
>>
>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by BEA Weblogic Workshop
>>FREE Java Enterprise J2EE developer tools!
>>Get your free copy of BEA WebLogic Workshop 8.1 today.
>>http://ads.osdn.com/?ad_idP47&alloc_id808&op=ick
>>_______________________________________________
>>Springframework-developer mailing list
>>Spr...@li...
>>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>
>>
>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by BEA Weblogic Workshop
>>FREE Java Enterprise J2EE developer tools!
>>Get your free copy of BEA WebLogic Workshop 8.1 today.
>>http://ads.osdn.com/?ad_idP47&alloc_id808&op=click
>>_______________________________________________
>>Springframework-developer mailing list
>>Spr...@li...
>>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>
>>
>>
>>
>>
>>    
>>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by BEA Weblogic Workshop
>FREE Java Enterprise J2EE developer tools!
>Get your free copy of BEA WebLogic Workshop 8.1 today.
>http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by BEA Weblogic Workshop
>FREE Java Enterprise J2EE developer tools!
>Get your free copy of BEA WebLogic Workshop 8.1 today.
>http://ads.osdn.com/?ad_idP47&alloc_id808&op=click
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
>  
>

[Springframework-developer] Re: Cannot proxy classes lacking no-arg constructor using CGLIB

[katentim @hotmail.c. <kat...@ho...>]

Is it possible to get the CGLIB guys to address it or look at CGLIB source 
and submit a fix to that project?

That would be great for all projects using CGLIB and for mock testing too.

_________________________________________________________________
Smart Saving with ING Direct – earn 5.25% p.a. variable rate:  
http://ad.au.doubleclick.net/clk;7249209;8842331;n?http://www.ingdirect.com.au/burst6offer.asp?id=8

Re: [Springframework-developer] WLS 7 and TX suspend/resume - continue.

[Thomas R. <tho...@tr...>]

Stefan,

Thanks for the suggestion, but I have been using sp5 and it has the same 
issue as sp2 when it comes to calling forceResume.

Thomas


Stefan Kleineikenscheidt wrote:

>Jürgen, Dimitry, Eugene,
>
>we've had problems with XA in WLS7 as well.  Unfortunately i wasn't
>involved in this issue, but i can remember that the XA implementation of
>SP2 and SP4 differed.  Maybe you can give it a try on SP4.
>
>-Stefan
>
>
>  
>
>>-----Original Message-----
>>From: spr...@li... 
>>[mailto:spr...@li...]
>> On Behalf Of jürgen höller [werk3AT]
>>Sent: Saturday, September 04, 2004 1:03 PM
>>To: spr...@li...
>>Subject: Re: [Springframework-developer] WLS 7 and TX 
>>suspend/resume - continue.
>>
>>
>>Ideally, WebLogic should work properly with standard JTA 
>>TransactionManager resume in all cases, not needing the 
>>proprietary forceResume call. However, the least we can 
>>expect is that forceResume works properly: You could send a 
>>corresponding bug report to BEA, for WebLogic 7.0. However, 
>>they might tell you that they fixed the issue in WebLogic 8.1...
>> 
>>Juergen
>> 
>>
>>________________________________
>>
>>Von: spr...@li... im 
>>Auftrag von jürgen höller [werk3AT]
>>Gesendet: Fr 03.09.2004 23:31
>>An: spr...@li...
>>Betreff: Re: [Springframework-developer] WLS 7 and TX 
>>suspend/resume - continue.
>>
>>
>>
>>As I already wrote in my JIRA comments: Many thanks for your 
>>efforts, Dmitri!
>>
>>I assume that with JtaTransactionManager, you'll get an 
>>IllegalStateException ("cannot resume rollback-only 
>>transaction" or the like), and with 
>>WebLogicJtaTransactionManager, you'll get the NPE in WebLogic code?
>>
>>This really seems to be a bug in WebLogic 7.0... At least it 
>>should work properly as long as not suspending a transaction 
>>that has been marked as rollback-only.
>>
>>Juergen
>>
>>
>>________________________________
>>
>>Von: spr...@li... im 
>>Auftrag von Dmitri Maximovich
>>Gesendet: Fr 03.09.2004 23:07
>>An: spr...@li...
>>Betreff: [Springframework-developer] WLS 7 and TX 
>>suspend/resume - continue.
>>
>>
>>
>>I just tried WLS 7 with Spring 1.1rc2 and BMT transaction 
>>demaraction. It
>>doesn't work with standard JtaTransactionManager or with
>>WeblogicJtaTransactionManager, so something fundamentally 
>>broken in WLS7 (same
>>NPE as described in JIRA SPR-251).
>>Next I'll try to use WLS TransactionManager (exposed in JNDI) 
>>to suspend/resume
>>transaction without Spring to see it it's going to work.
>>
>>
>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by BEA Weblogic Workshop
>>FREE Java Enterprise J2EE developer tools!
>>Get your free copy of BEA WebLogic Workshop 8.1 today.
>>http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
>>_______________________________________________
>>Springframework-developer mailing list
>>Spr...@li...
>>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>
>>
>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by BEA Weblogic Workshop
>>FREE Java Enterprise J2EE developer tools!
>>Get your free copy of BEA WebLogic Workshop 8.1 today.
>>http://ads.osdn.com/?ad_idP47&alloc_id808&op=ick
>>_______________________________________________
>>Springframework-developer mailing list
>>Spr...@li...
>>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>
>>
>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by BEA Weblogic Workshop
>>FREE Java Enterprise J2EE developer tools!
>>Get your free copy of BEA WebLogic Workshop 8.1 today.
>>http://ads.osdn.com/?ad_idP47&alloc_id808&op=ick
>>_______________________________________________
>>Springframework-developer mailing list
>>Spr...@li...
>>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>
>>    
>>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by BEA Weblogic Workshop
>FREE Java Enterprise J2EE developer tools!
>Get your free copy of BEA WebLogic Workshop 8.1 today.
>http://ads.osdn.com/?ad_idP47&alloc_id808&op=click
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
>  
>

Re: [Springframework-developer] WLS 7 and TX suspend/resume - continue.

[<jue...@we...>]

Thanks, Thomas! This means that there *is* a way to make it work on =
WebLogic 7! Eugene, Dmitri, your pain finally has an end! :-)
=20
Regarding obtaining the TransactionManager via the TxHelper on WebLogic =
7: That can easily be factored out into a custom FactoryBean, like we =
did for WebSphere (see WebSphereTransactionManagerFactoryBean), to be =
passed into JtaTransactionManager's respectively =
WebLogicJtaTransactionManager's "transactionManager" property. So we =
don't need a further JtaTransactionManager subclass for this, just a =
further TransactionManager lookup strategy.
=20
BTW, Dmitri told me that the WebLogic UserTransaction object at =
"java:comp/UserTransaction" implements the TransactionManager interface =
too, but that obviously forceResume doesn't work there... I assume the =
ClientTransactionManagerImpl is returned there, not the =
ServerTransactionManagerImpl.
=20
If we can double-check that this works better than the =
TransactionManager fetched from JNDI, I suggest to add a =
WebLogicServerTransactionManagerFactoryBean (or a similar name), clearly =
documenting that this is meant as an alternative to the standard JNDI =
TransactionManager reference that WebLogic provides, mainly for WebLogic =
7. I wouldn't mind to do this even for the 1.1 final release tomorrow...
=20
Is the TxHelper lookup available on WebLogic 8.1 too? Of course, it =
shouldn't be necessary there, as the standard JNDI TransactionManager =
reference will work too. I just wonder whether it's available and would =
work in principle: People could then configure a =
WebLogicServerTransactionManagerFactoryBean to be able to deploy on both =
WebLogic 7 and WebLogic 8, without adapting their Spring configuration.
=20
Of course, such a WebLogicServerTransactionManagerFactoryBean would have =
to be coded via reflection to avoid compile-time dependencies on =
WebLogic, analogous to WebSphereTransactionManagerFactoryBean. Do you =
have the chance to do this before tomorrow, Thomas?
=20
Juergen
=20

________________________________

Von: spr...@li... im Auftrag =
von Thomas Risberg
Gesendet: Sa 04.09.2004 14:30
An: spr...@li...
Betreff: Re: [Springframework-developer] WLS 7 and TX suspend/resume - =
continue.



I have done some additional testing for this issue and this is what I
have found.

WebLogic exposes a client TransactionManager implementation via JNDI=20
(weblogic.transaction.internal.ClientTransactionManagerImpl) and in WLS
7.0 it is throwing an NPE when you call forceResume (with or without a
suspended transaction that has been marked for RollbackOnly).

They also have a different server implementation
(weblogic.transaction.internal.ServerTransactionManagerImpl) that is
returnd by a call to TxHelper.getTransactionManager().  With this TM the
force resume works as expected.

So the workaround for now is to do the suspend/resume using the TM
returned by TxHelper before calling the Spring managed code.
Alternatively we could provide a WebLogic7JtaTransactionManager that
uses this method of obtaining the TM.

I doubt that BEA will fix this issue in WLS 7.0.  They will probably
suggest to upgrade to 8.1 or use the TxHelper to obtain the TM.

Thomas


j=FCrgen h=F6ller [werk3AT] wrote:

>Ideally, WebLogic should work properly with standard JTA =
TransactionManager resume in all cases, not needing the proprietary =
forceResume call. However, the least we can expect is that forceResume =
works properly: You could send a corresponding bug report to BEA, for =
WebLogic 7.0. However, they might tell you that they fixed the issue in =
WebLogic 8.1...
>
>Juergen
>
>
>________________________________
>
>Von: spr...@li... im Auftrag =
von j=FCrgen h=F6ller [werk3AT]
>Gesendet: Fr 03.09.2004 23:31
>An: spr...@li...
>Betreff: Re: [Springframework-developer] WLS 7 and TX suspend/resume - =
continue.
>
>
>
>As I already wrote in my JIRA comments: Many thanks for your efforts, =
Dmitri!
>
>I assume that with JtaTransactionManager, you'll get an =
IllegalStateException ("cannot resume rollback-only transaction" or the =
like), and with WebLogicJtaTransactionManager, you'll get the NPE in =
WebLogic code?
>
>This really seems to be a bug in WebLogic 7.0... At least it should =
work properly as long as not suspending a transaction that has been =
marked as rollback-only.
>
>Juergen
>
>
>________________________________
>
>Von: spr...@li... im Auftrag =
von Dmitri Maximovich
>Gesendet: Fr 03.09.2004 23:07
>An: spr...@li...
>Betreff: [Springframework-developer] WLS 7 and TX suspend/resume - =
continue.
>
>
>
>I just tried WLS 7 with Spring 1.1rc2 and BMT transaction demaraction. =
It
>doesn't work with standard JtaTransactionManager or with
>WeblogicJtaTransactionManager, so something fundamentally broken in =
WLS7 (same
>NPE as described in JIRA SPR-251).
>Next I'll try to use WLS TransactionManager (exposed in JNDI) to =
suspend/resume
>transaction without Spring to see it it's going to work.
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by BEA Weblogic Workshop
>FREE Java Enterprise J2EE developer tools!
>Get your free copy of BEA WebLogic Workshop 8.1 today.
>http://ads.osdn.com/?ad_id=3D5047&alloc_id=3D10808&op=3Dclick
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by BEA Weblogic Workshop
>FREE Java Enterprise J2EE developer tools!
>Get your free copy of BEA WebLogic Workshop 8.1 today.
>http://ads.osdn.com/?ad_idP47&alloc_id=10808&op=3Dick
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by BEA Weblogic Workshop
>FREE Java Enterprise J2EE developer tools!
>Get your free copy of BEA WebLogic Workshop 8.1 today.
>http://ads.osdn.com/?ad_idP47&alloc_id=10808&op=3Dclick
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
>=20
>



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=3D5047&alloc_id=3D10808&op=3Dclick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

RE: [Springframework-developer] WLS 7 and TX suspend/resume - continue.

[Stefan K. <ste...@kl...>]

J=FCrgen, Dimitry, Eugene,

we've had problems with XA in WLS7 as well.  Unfortunately i wasn't
involved in this issue, but i can remember that the XA implementation of
SP2 and SP4 differed.  Maybe you can give it a try on SP4.

-Stefan


> -----Original Message-----
> From: spr...@li...=20
> [mailto:spr...@li...]
>  On Behalf Of j=FCrgen h=F6ller [werk3AT]
> Sent: Saturday, September 04, 2004 1:03 PM
> To: spr...@li...
> Subject: Re: [Springframework-developer] WLS 7 and TX=20
> suspend/resume - continue.
>=20
>=20
> Ideally, WebLogic should work properly with standard JTA=20
> TransactionManager resume in all cases, not needing the=20
> proprietary forceResume call. However, the least we can=20
> expect is that forceResume works properly: You could send a=20
> corresponding bug report to BEA, for WebLogic 7.0. However,=20
> they might tell you that they fixed the issue in WebLogic 8.1...
> =20
> Juergen
> =20
>=20
> ________________________________
>=20
> Von: spr...@li... im=20
> Auftrag von j=FCrgen h=F6ller [werk3AT]
> Gesendet: Fr 03.09.2004 23:31
> An: spr...@li...
> Betreff: Re: [Springframework-developer] WLS 7 and TX=20
> suspend/resume - continue.
>=20
>=20
>=20
> As I already wrote in my JIRA comments: Many thanks for your=20
> efforts, Dmitri!
>=20
> I assume that with JtaTransactionManager, you'll get an=20
> IllegalStateException ("cannot resume rollback-only=20
> transaction" or the like), and with=20
> WebLogicJtaTransactionManager, you'll get the NPE in WebLogic code?
>=20
> This really seems to be a bug in WebLogic 7.0... At least it=20
> should work properly as long as not suspending a transaction=20
> that has been marked as rollback-only.
>=20
> Juergen
>=20
>=20
> ________________________________
>=20
> Von: spr...@li... im=20
> Auftrag von Dmitri Maximovich
> Gesendet: Fr 03.09.2004 23:07
> An: spr...@li...
> Betreff: [Springframework-developer] WLS 7 and TX=20
> suspend/resume - continue.
>=20
>=20
>=20
> I just tried WLS 7 with Spring 1.1rc2 and BMT transaction=20
> demaraction. It
> doesn't work with standard JtaTransactionManager or with
> WeblogicJtaTransactionManager, so something fundamentally=20
> broken in WLS7 (same
> NPE as described in JIRA SPR-251).
> Next I'll try to use WLS TransactionManager (exposed in JNDI)=20
> to suspend/resume
> transaction without Spring to see it it's going to work.
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=3D5047&alloc_id=3D10808&op=3Dclick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_idP47&alloc_id=10808&op=3Dick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_idP47&alloc_id=10808&op=3Dick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>=20

Re: [Springframework-developer] WLS 7 and TX suspend/resume - continue.

[Thomas R. <tho...@tr...>]

I have done some additional testing for this issue and this is what I 
have found.

WebLogic exposes a client TransactionManager implementation via JNDI  
(weblogic.transaction.internal.ClientTransactionManagerImpl) and in WLS 
7.0 it is throwing an NPE when you call forceResume (with or without a 
suspended transaction that has been marked for RollbackOnly).

They also have a different server implementation 
(weblogic.transaction.internal.ServerTransactionManagerImpl) that is 
returnd by a call to TxHelper.getTransactionManager().  With this TM the 
force resume works as expected.

So the workaround for now is to do the suspend/resume using the TM 
returned by TxHelper before calling the Spring managed code. 
Alternatively we could provide a WebLogic7JtaTransactionManager that 
uses this method of obtaining the TM.

I doubt that BEA will fix this issue in WLS 7.0.  They will probably 
suggest to upgrade to 8.1 or use the TxHelper to obtain the TM.

Thomas


jürgen höller [werk3AT] wrote:

>Ideally, WebLogic should work properly with standard JTA TransactionManager resume in all cases, not needing the proprietary forceResume call. However, the least we can expect is that forceResume works properly: You could send a corresponding bug report to BEA, for WebLogic 7.0. However, they might tell you that they fixed the issue in WebLogic 8.1...
> 
>Juergen
> 
>
>________________________________
>
>Von: spr...@li... im Auftrag von jürgen höller [werk3AT]
>Gesendet: Fr 03.09.2004 23:31
>An: spr...@li...
>Betreff: Re: [Springframework-developer] WLS 7 and TX suspend/resume - continue.
>
>
>
>As I already wrote in my JIRA comments: Many thanks for your efforts, Dmitri!
>
>I assume that with JtaTransactionManager, you'll get an IllegalStateException ("cannot resume rollback-only transaction" or the like), and with WebLogicJtaTransactionManager, you'll get the NPE in WebLogic code?
>
>This really seems to be a bug in WebLogic 7.0... At least it should work properly as long as not suspending a transaction that has been marked as rollback-only.
>
>Juergen
>
>
>________________________________
>
>Von: spr...@li... im Auftrag von Dmitri Maximovich
>Gesendet: Fr 03.09.2004 23:07
>An: spr...@li...
>Betreff: [Springframework-developer] WLS 7 and TX suspend/resume - continue.
>
>
>
>I just tried WLS 7 with Spring 1.1rc2 and BMT transaction demaraction. It
>doesn't work with standard JtaTransactionManager or with
>WeblogicJtaTransactionManager, so something fundamentally broken in WLS7 (same
>NPE as described in JIRA SPR-251).
>Next I'll try to use WLS TransactionManager (exposed in JNDI) to suspend/resume
>transaction without Spring to see it it's going to work.
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by BEA Weblogic Workshop
>FREE Java Enterprise J2EE developer tools!
>Get your free copy of BEA WebLogic Workshop 8.1 today.
>http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by BEA Weblogic Workshop
>FREE Java Enterprise J2EE developer tools!
>Get your free copy of BEA WebLogic Workshop 8.1 today.
>http://ads.osdn.com/?ad_idP47&alloc_id808&op=ick
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by BEA Weblogic Workshop
>FREE Java Enterprise J2EE developer tools!
>Get your free copy of BEA WebLogic Workshop 8.1 today.
>http://ads.osdn.com/?ad_idP47&alloc_id808&op=click
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
>  
>

[Springframework-developer] Form simplification tags for JSP

[<jue...@we...>]

Seth, Daniel, everybody,

I've created a new JIRA issues for JSP form tags. The former "form =
simplification macros" issues has been closed for 1.1, as the Velocity =
and FreeMarker macros are ready now.

http://opensource.atlassian.com/projects/spring/browse/SPR-310

I've specified 1.1.1 as target, alongside a couple of other enhancements =
that we've deferred beyond 1.1 final. It would be great if we managed to =
get JSP form tags ready by then (in about 4-6 weeks)!
=20
Juergen