Spring-TopLink Integration Available

A preview of our integration with Spring is available now.
http://www.oracle.com/technology/products/ias/toplink/preview/spring/index.html
We are working on contributing this into Spring and hope to have it available from the Spring Framework website in the future.
As always, your feedback is appreciated via this forum,
Doug

You will not have to change any java code when you switch "transaction controller" strategies in your Spring beans.xml file.
When you talk about "the way you use the UnitOfWork in your code", you're talking about the section in the "Transactions" chapter called "External Transaction Controllers" right? In any case, the differences at the java level, are essentially that you acquire an "active" UnitOfWork (getActiveUnitOfWork) and that you no longer explicitly commit the UnitOfWork.
Neither of these two differences impacts your use of TopLink within Spring. In Spring, the transaction is always managed by a Spring PlatformTransactionManager so your TopLink code will never call commit, whether you're using an ExternalTransactionController or not. The code will be identical whether you're running in J2SE or J2EE.
Also, since we expect users to access TopLink either through a TopLinkTemplate or through a TopLinkInterceptor, the Spring container will always "inject" a TopLink Session that is aware of whether or not there is currently an ExternalTransactionController. So, there will be no difference between the behavior of acquireUnitOfWork and getActiveUnitOfWork. Both will behave identically. They will return you the UOW currently associated with the current Spring PlatformTransactionManager. So, there is no environmental dependency here either.
JIM

Similar Messages

Spring-TopLink Integration and transparent transaction controller

Hi,
I'm new to TopLink and I read the article in the "Mastering J2EE" series about the Spring TopLink integration. I never actually got into Spring before, so I went and checked out the articles and tutorials and then I went back to my exploration of TopLink.
From what I understood, Spring promises that you wouldn't need to change your code, only your configuration files, if you change your transaction controller from the OR framework transaction controller to a JTA enabled one provided by the AS. But when I read the "Transactions" chapter in the TopLink application developer's guide, it seemed that the way you use the UnitOfWork in your code differs significantly depending on whether you're using an external transaction controller.
My question is, does this void Spring's promise or is there a work around for that?
Thanks.

You will not have to change any java code when you switch "transaction controller" strategies in your Spring beans.xml file.
When you talk about "the way you use the UnitOfWork in your code", you're talking about the section in the "Transactions" chapter called "External Transaction Controllers" right? In any case, the differences at the java level, are essentially that you acquire an "active" UnitOfWork (getActiveUnitOfWork) and that you no longer explicitly commit the UnitOfWork.
Neither of these two differences impacts your use of TopLink within Spring. In Spring, the transaction is always managed by a Spring PlatformTransactionManager so your TopLink code will never call commit, whether you're using an ExternalTransactionController or not. The code will be identical whether you're running in J2SE or J2EE.
Also, since we expect users to access TopLink either through a TopLinkTemplate or through a TopLinkInterceptor, the Spring container will always "inject" a TopLink Session that is aware of whether or not there is currently an ExternalTransactionController. So, there will be no difference between the behavior of acquireUnitOfWork and getActiveUnitOfWork. Both will behave identically. They will return you the UOW currently associated with the current Spring PlatformTransactionManager. So, there is no environmental dependency here either.
JIM

When will Spring-Toplink integration be officially released in Spring

I notice from previous emails that Spring-Toplink integration will eventually be part of the Spring framework itself (similair to existing Hibernate, iBatis, JDO integration). Can you tell me when this will occur? What version of Spring is being targeted?
thankyou,
Chris

Chris,
The work is going on right now to have the work checked in and included in Spring 1.2.
Doug

Spring TopLink Integration Preview Updated

The preview of the Spring TopLink Integration support has been updated on OTN. Changes are described in the release notes.
Also check out the OTN article Of Persistence and POJOs: Bridging the Object and Relational Worlds on using TopLink with Spring by Rod Johnson and Jim Clarke.

You will not have to change any java code when you switch "transaction controller" strategies in your Spring beans.xml file.
When you talk about "the way you use the UnitOfWork in your code", you're talking about the section in the "Transactions" chapter called "External Transaction Controllers" right? In any case, the differences at the java level, are essentially that you acquire an "active" UnitOfWork (getActiveUnitOfWork) and that you no longer explicitly commit the UnitOfWork.
Neither of these two differences impacts your use of TopLink within Spring. In Spring, the transaction is always managed by a Spring PlatformTransactionManager so your TopLink code will never call commit, whether you're using an ExternalTransactionController or not. The code will be identical whether you're running in J2SE or J2EE.
Also, since we expect users to access TopLink either through a TopLinkTemplate or through a TopLinkInterceptor, the Spring container will always "inject" a TopLink Session that is aware of whether or not there is currently an ExternalTransactionController. So, there will be no difference between the behavior of acquireUnitOfWork and getActiveUnitOfWork. Both will behave identically. They will return you the UOW currently associated with the current Spring PlatformTransactionManager. So, there is no environmental dependency here either.
JIM

Spring / Toplink Transaction / Commit Issue

Hi,
Im working on a spring / toplink integration on my project.
The problem Im facing has to do with transaction / commits
Im using a TransactionProxyFactoryBean to encapsulate a BusinessProcess responsible for creating a new Company Instance and its main Office.
As the 2 entity have to be created atomicly I have setup a PROPAGATION_REQUIRED on the createCompanyAndMainOffice method of the CompanyBusinessProcess.
The problem is I want to return a session, identified company object and I cant see how to do that correctly.
I tried and create a sub internal method like internalTXCreate called by createCompanyAndMainOffice, that would be the one transactional, so I get the commit at the end of its execution, returning the working copy with the newly inserted id, and perform a load with its its ID on the session from createCompanyAndMainOffice.
But it seems that the TransactionalProxyFactoryBean only intercepts calls on the 'entry point' methods... so back to where I started ...
I check the reference petclinic implementation and the only new* method does mention it returns a non identified BusinessObject which I find a bit disturbing in my case ...
Any idea on the problem ?
Thanks for your help,
Best Regards
Olivier Cuzacq
Software Architect
Groupe Moniteur

Something like this in createCompanyAndMainOffice should work:
return (Owner)getTopLinkTemplate().registerObject(new Owner());
post-commit, the returned Object will be a reference from Toplink shared cache.

Spring BlazeDS Integration

Spring BlazeDS Integration
this is the best tutorial for Spring BlazeDS Integration go to http://codexamples.blogspot.com
1. Configuring and Using the BlazeDS
MessageBroker with Spring
MessageBroker is the heart of the Spring BlazeDS Integration.
When HTTP messages come from Flex client will be routed through the
Spring DispatcherServlet to the Spring-managed MessageBroker.
There is no need to configure the BlazeDS MessageBrokerServlet when using the
Spring-managed MessageBroker.
2. Configuring the Spring DispatcherServlet
web.xml is the heart of the j2ee web project.So we have to configure it because
each an every request is map to web.xml.
The DispatcherServlet must be configured in web.xml to bootstrap a Spring
WebApplicationContext. For example:

<servlet>
<servlet-name>Spring MVC Dispatcher Servlet</servlet-name>
<servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
<init-param>
<param-name>contextConfigLocation</param-name>
<param-value>/WEB-INF/config/web-application-config.xml</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
3. Configuring the MessageBroker in Spring
A simplified Spring XML config namespace is provided for configuring the MessageBroker in
your WebApplicationContext. To use the namespace support you must add the schema location
in your Spring XML config files. A typical config will look something like the following:
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:flex="http://www.springframework.org/schema/flex"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
http://www.springframework.org/schema/flex
http://www.springframework.org/schema/flex/spring-flex-1.0.xsd">
</beans>
Following XML config namespace tags makes the Spring BlazeDS Integration configuration tags available under the flex
namespace in your configuration files. The above setup will be assumed for the rest of the
configuration examples to follow. For the full detail of every attribute and tag available in the
config namespace, be sure to refer to the spring-flex-1.0.xsd as every element and attribute is
fully documented there. Using an XSD-aware XML editor such as the one in Eclipse should
bring up the documentation automatically as you type.
At a minimum, the MessageBrokerFactoryBean must be configured as a bean in your
Spring WebApplicationContext in order to bootstrap the MessageBroker, along with a
MessageBrokerHandlerAdapter and an appropriate HandlerMapping (usually a
SimpleUrlHandlerMapping) to route incoming requests to the Spring-managed
MessageBroker.
These beans will be registered automatically by using the provided message-broker tag in
your bean definition file. For example, in its simplest form:
<flex:message-broker/>
This will set up the MessageBroker and necessary supporting infrastructure using sensible
defaults. The defaults can be overriden using the provided attributes of the message-broker
tag and its associated child elements. For example, the default location of the BlazeDS XML
configuration file (/WEB-INF/flex/services-config.xml) can be overridden using the
services-config-path attribute. The MessageBrokerFactoryBean uses Spring's
ResourceLoader abstraction, so that typical Spring resource paths may be used. For
example, to load the configuration from the application's classpath:
<flex:message-broker services-config-path="classpath*:services-config.xml"
The equivalent MessageBrokerFactoryBean definition using vanilla Spring configuration
would be:

<bean id="_messageBroker" class="org.springframework.flex.core.MessageBrokerFactoryBean" >
<property name="servicesConfigPath" value="classpath*:services-config.xml" />
</bean>
Note especially that with the message-broker tag, it is not necessary to assign a custom id to
the MessageBroker, and it is in fact discouraged so that you won't have to continually reference
it later. The only reason you would ever need to provide a custom id is if you were bootstrapping
more than one MessageBroker in the same WebApplicationContext.

this is the best tutorial
Is it because you have made the site ??
To be frank , there is nothing special or great in that materail .
Try to make a nice and simple copy of working example like roseindia or Abhi on java and post it .People like me definately want them .

[svn:bz-trunk] 23048: Update BlazeDS trunk to use Spring BlazeDS integration 1.5.0.RELEASE build .

Revision: 23048
Revision: 23048
Author:   [email protected]
Date:     2011-10-18 08:34:43 -0700 (Tue, 18 Oct 2011)
Log Message:
Update BlazeDS trunk to use Spring BlazeDS integration 1.5.0.RELEASE build.
Added Paths:
    blazeds/trunk/apps/samples-spring/WEB-INF/src/spring-samples/src/org/springframework/flex /samples/secured/SecurityHelper.java.UNCOMMENT
    blazeds/trunk/lib/spring/spring-flex-core-1.5.0.RELEASE.jar
Removed Paths:
    blazeds/trunk/apps/samples-spring/WEB-INF/src/spring-samples/src/org/springframework/flex /samples/secured/SecurityHelper.java
    blazeds/trunk/lib/spring/org.springframework.flex-1.0.3.RELEASE.jar

The information you provided is totally useless for determining the problem.
If it helps, I think the message you are getting is related to BlazeDS not being able to find the service class you are calling. You either have a typo somewhere, or you didn't set up a secure channel in your service config (I am assuming you meant SSL and not SSH).

ANN: Spring 1.2 with TopLink Integration Released

Version 1.2 of the Spring Framework has been released. New in the 1.2 final release is support for TopLink "out of the box". Prior to 1.2, TopLink support was an "add on" that was available on OTN. Now Spring ships with the integration code required to use TopLink as a persistence provider. TopLink 10.1.2 (9.0.4) and 10.1.3 (preview) are supported.
To get started, try out the Pet Clinic sample app configured to use TopLink.
NB: Spring doesn't include TopLink; it provides the necessary integration classes. You still need to download both Spring and TopLink.
- Shaun
Spring Home page: http://www.springframework.org
Spring 1.2 Announcement: http://www.springframework.org/node/86

Version 1.2 of the Spring Framework has been released. New in the 1.2 final release is support for TopLink "out of the box". Prior to 1.2, TopLink support was an "add on" that was available on OTN. Now Spring ships with the integration code required to use TopLink as a persistence provider. TopLink 10.1.2 (9.0.4) and 10.1.3 (preview) are supported.
To get started, try out the Pet Clinic sample app configured to use TopLink.
NB: Spring doesn't include TopLink; it provides the necessary integration classes. You still need to download both Spring and TopLink.
- Shaun
Spring Home page: http://www.springframework.org
Spring 1.2 Announcement: http://www.springframework.org/node/86

Spring Facet not available in Weblogic Enterprise Pack for Eclipse?

Hi guys, just wondering if the Spring Facet will be available for the Weblogic Enterprise Pack for Eclipse? If yes, when can we expect this to be released?

Spring Facet and other integration with Spring IDE will be in the next release of Oracle Enterprise Pack for Eclipse, which will ship in the next couple of months.
- Konstantin

Spring-JMS integration with BlazeDS

I've seen a number of articles that discuss integrating Spring with BlazeDS, but these all seem to focus on integrations related to RPC-type calls via RemoteObject. Has anyone had success configuring BlazeDS to proxy messages from a JMS broker using a connection factory and a destination defined in the Spring context? I am unclear how to go about configuring a BlazeDS messaging destination in this manner. Any guidance would be appreciated. Thanks in advance.
Jim

There is a JMSAdapter in BlazeDS that you can use for JMS integration. Please check out BlazeDS documentation.

Check out TopLink integration with JDeveloper 10g

I just thought you might want to get a look at the upcoming integration of TopLink and Oracle JDeveloper 10g.
You can download the JDeveloper 10g preview now and play with it.
See demo: http://otn.oracle.com/products/jdev/viewlets/905p_adf_toplink/toplinkEditor_viewlet_swf.html
and follow the tutorial:
http://otn.oracle.com/products/jdev/collateral/prodtour10g.html

John,
"1) When I did this last step, it created a new set of 'Offline Database Objects'. It would be nice not to have to redirect the new classes at my original objects or create a new diagram from the new objects. (I would like to bae able to get rid of one set of Database Objects.)"Currently, you are running into the issue since you already have offline tables that you are using to create online tables. You then are creating Java objects from online tables. Each time you create Java Objects from online tables, offline tables are created and cached with the project; the generator is not smart to recognize whether these tables exist offline.
That's a great suggestion and we already have this under consideration for future release. What you are asking is the ability to generate Java Objects from offline tables.
�2) The Database Objects that were created when I generated the classes all have the schema name prepended. My original Database Objects have the 'package' prepended. I would like my Java classes to map to unqualified tablenames.�Another great suggestion; we have already taken this into consideration for this release.
�Also, can I model sequences for my tables and have those automatically generated along with the tables and constraints? �You can always create a SEQUENCE table offline or online (on the database; see connections tab) in Jdeveloper and then use it in the TopLink mapping editor with your data model. Let me know if you need more info on it.
�Is there a place I can modify the default datatype to java type mappings? For example, what if I would prefer my classes to be generated with BigDecimal attributes instead of Double? �Yet another great suggestion, we will keep it in mind for future release.

Spring TopLink support outside container

I'm setting up an internal workshop at our company to teach and demo TopLink. I'm aiming to focus on TopLink, so I figured I would keep it as simple as possible.
I still want to demo transaction spanning several DAO calls though, and thought I could use the TopLink support in Spring for that. Easier said than done when I'm only running from a simple class' main method...
First I try starting a transaction with Spring, as I thought it would be able to fallback/handle it with a ThreadLocal even though it's not inside a container:
TransactionDefinition transDef = new DefaultTransactionDefinition(
TransactionDefinition.PROPAGATION_REQUIRED); TransactionStatus
TransactionStatus transStatus = transManager.getTransaction(transDef);
Which gives:
java.lang.UnsupportedOperationException: SingleSessionFactory does not support managed client Sessions
So I figure, alright, fair enough. All I have to do then is initialise a UoW through spring instead of starting a transaction, and then that will be injected into the TopLinkCallback I'm using in my DAO:
SessionFactory sessionFactory = (SessionFactory) appContext.getBean("sessionFactory");
Session currentSession = SessionFactoryUtils.getSession(sessionFactory, true);
UnitOfWork uow = currentSession.getActiveUnitOfWork();
But nope. The getActiveUnitOfWork() in my TopLinkCallback just returns null. Anyone know how to do this best outside a container? How do I initialise a UoW that Spring will hold on to for me?
Anders,

Hi Anders,
SessionFactory sessionFactory = (SessionFactory)
appContext.getBean("sessionFactory");
Session currentSession =
SessionFactoryUtils.getSession(sessionFactory,
true);
UnitOfWork uow =
currentSession.getActiveUnitOfWork();
But nope. The getActiveUnitOfWork() in my
TopLinkCallback just returns null. Anyone know how to
do this best outside a container? How do I initialise
a UoW that Spring will hold on to for me?
Anders,You're getting the expected behavior. getActiveUnitOfWork returns null outside of a transaction. It won't start one for you--you're going to have to do that before you call it.
If you put your code inside a transaction callback like the following you get an active unit of work.
final ClassPathXmlApplicationContext ctx = new ClassPathXmlApplicationContext("applicationContext-toplink.xml");
PlatformTransactionManager txManager = (PlatformTransactionManager) ctx.getBean("transactionManager");
TransactionTemplate template = new TransactionTemplate(txManager);
template.setPropagationBehavior(TransactionDefinition.PROPAGATION_REQUIRED);
TransactionCallbackWithoutResult callback =     new TransactionCallbackWithoutResult() {
     protected void doInTransactionWithoutResult(TransactionStatus transactionStatus) {
          SessionFactory sessionFactory = (SessionFactory) ctx.getBean("sessionFactory");
          Session currentSession = SessionFactoryUtils.getSession(sessionFactory, true);
          UnitOfWork uow = currentSession.getActiveUnitOfWork();
          // uow is not null
          // your code goes here
// execute your code in a tx
template.execute(callback);This code runs out of container no problem. I tested it with the petclinic example. Hope this helps.
--Shaun

Rational Rose TopLink Integration

I'm about to start a new project hosted on OAS and looking for Object-Relational Mapping Tools.
I want to follow a Model Driven Architecture (MDA) methodology, using UML as the master definition of the persistent model.
The questions I need to know about Oracle TopLink is as follows :-
i) Does a project generated from Rational Rose work with Oracle TopLink
ii) Does Oracle offer an alternative modelling tool.
ii) Does Oracle TopLink provide an incremental DDL generation tool, i.e. only generating alter statements to existing schema
Many thanks
Pat

Sapna,
There was a earlier post regarding this topic - perhaps you'd like to review that?
The link is re:How to Integrate with Rational Rose 2002
or click on "search forum" and enter "Rtaional Rose".
Regards, Guus

Problems with Toplink integration with JTS and WSAD

We have a very strange problem.
Description:
     We are attempting to integrate with JTS, insuring that TopLink does its transactional activity within the scope of a JTS transaction, as described in the Foundation Library Guide.
     We have a stateless session bean, a method of which implements a simple "insert" on a database table registerObject() on a unit of work). This bean is configured to use bean-managed transactions, but with a default resolver of rollback.
     The bean is launched in the WSAD test environment.
     When the bean method is invoked from the WSAD Universal Test Client (web app that runs in the same app server allowing discovery and unit test of bean methods), the code works. A row is inserted into the table, etc.
     Same code, same method, same (stateless) bean, same instance of the WSAD test environment, if the bean method is invoked from outside the application server (via a JUnit test driver that discovers the session bean via JNDI), the code breaks. The final JTS commit catches a javax.transaction.RollbackException, apparently without any sort of stack trace tacked to the exception printStackTrace() doesn't result in anything). No row is inserted.
     We can call the bean alternately, via these two approaches, under the same instance of test environment, and get different behavior.
     We don't understand. All (hopefully) of the relevant details follow.
We are using:
     WSAD Version: 5.0.1 Build id: 20030423_1316
     TopLink - 9.0.3.3 (Build 430)
     Oracle 9i
From our sessions.xml:
     <login>
          <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
          <datasource>project</datasource>
          <platform-class>oracle.toplink.internal.databaseaccess.OraclePlatform</platform-class>
          <uses-external-connection-pool>true</uses-external-connection-pool>
          <uses-external-transaction-controller>true</uses-external-transaction-controller>
     </login>
     <external-transaction-controller-class>oracle.toplink.jts.was.JTSExternalTransactionController_5_0</external-transaction-controller-class>
From our project XML:
     <uses-external-connection-pooling>true</uses-external-connection-pooling>
     <uses-external-transaction-controller>true</uses-external-transaction-controller>
The code that breaks:
     SessionManager sm = SessionManager.getManager();
     Server ss = (Server) sm.getSession("project", TestBean.class.getClassLoader());
     ClientSession cs = ss.acquireClientSession();
     Context c = new InitialContext();
     UserTransaction t = (UserTransaction) c.lookup("java:comp/UserTransaction");
     t.begin();
     UnitOfWork u = ss.getActiveUnitOfWork();
     u.registerObject(value);
     u.commit();
     t.commit(); /* this throws javax.transaction.RollbackException */
Thanks.

Strange problem, could be a Websphere issue, or an issue with the JTSExternalTransactionController_5_0.
Try configuring TopLink to not use JTS and see if the same problem still occurs. Also turn on TopLink logging and exception logging and your Websphere server logging to see if you can get the real exception and stack that is causing the RollbackException.
This could be an issue with the JTSExternalTransactionController_5_0 as the original version of the controller did have a JTS issue. Make sure you are no the latest patch and check with support to see if they have a patch for this problem.

Lazy loading differences Toplink vs. Hibernate - plz. explain

I'm in the process of evaluating both Toplink and hibernate as potential ORM framework to use for a project I'm currently involved in.
My question is about how Toplink resolves lazily loaded associations. In hibernate I have to perform a query inside a transactional context boundary, like:
Session s = SessionFactory.getSession();
s.beginTransaction();
... your query logic here
s.getTransaction().commit();When the query involves associations which are declared as lazily loadable, trying to invoke these associations after the transaction boundary has been closed, results in an exception. This differs from Toplink (my JUnit testcase breaks for Hibernate if I set the DAOFactory to return hibernate enabled DAO's) and I'm wondering why?
I'm guessing this has something to do with how Toplink manages its clientsession, but would like to get some confirmation about this. It looks like as-long as the thread of execution is running I can resolve associations using Toplink, but not when I use Hibernate.
This brings me to yet another question - what's considered best practices in Toplink regarding session disposal. Should I do something myself, or let the garbage collector take care of it?

I'm not too sure here, but I think it's because TopLink has a "long running" ServerSession. When you do lazy initialization outside a clientsession it is for read only purposes and it will use the centrally managed ServerSession (and cache). I'm still trying to figure out the exact relationships here, som I'm not too sure. :) Hibernate does not have a centrally shared cache, and will not be able to instantiate objects if the session is closed (for each session, objects are instantiated from it's data cache).
As for handling resources and closing/opening, use the Spring/TopLink integration. It will handle it for you and give you heaps of convenience methods that uses some clever tricks to decide if it should fetch objects with Session or UnitOfWork. It will also do some good Exception handling built into Spring.

Spring-TopLink Integration Available

Similar Messages

Maybe you are looking for