Non EJB JTA possible?

Hi,
I am building a web service that will need to access 3 databases.
Therefore, I need to use JTA to manage the transaction.
I am trying to apply JTA without using EJB, Is that possible?
My code is like this:
UserTransaction userTransaction = (UserTransaction)inititalContext.lookup("java:comp/UserTransaction");
try
userTransaction.begin();
someDAOMethod();
userTransaction.commit();
catch(Exception ex)
Exception was encountered with at the userTransaction.commit() line, and the exception message is:
Caused by: javax.transaction.xa.XAException: JDBC driver does not support XA, hence cannot be a participant in two-phase commit. To force this participation, set the GlobalTransactionsProtocol attribute to LoggingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source = myDS
I have tried to change the transaction setting to EmulateTwoPhaseCommit, the same error happens after the restart.
When I try to change it to LoggingLastResource, WebLogic cannot start at all.
How can I do and is there anything I have done wrongly?
Thanks in advance.

Hi Joe,
Yes, I have 3 data sources through JNDI.
My DBMSes are all oracle, but of different versions, they are 8i, 10g and 11g.
Driver: oracle.jdbc.OracleDriver
I have tried to change the 11g's driver to oracle.jdbc.xa.client.OracleXADataSource, but the same error still appear.
By the way, I am using hibernate, so I have added the following properties into my 3 hibernate.cfg.xml files:
 <property name="transaction.factory_class">org.hibernate.transaction.JTATransactionFactory</property>
 <property name="transaction.manager_lookup_class">org.hibernate.transaction.WeblogicTransactionManagerLookup</property>
 <property name="current_session_context_class">jta</property>
Appreciate your help.
Let me know if you need me to provide more information.
Thanks!

Similar Messages

JTA/JTS for non-EJB & non-J2EE server used

I have a standalone java program which calls methods on 2 java classes (c1, c2) These are Non-EJB/non-RMI/non-CORBA plain java classes.
the method in c1 updates table t1 in database db1
the method in c2 updates table t2 in database db2
I would like to use JTA for conducting a 2PC based transaction. I know this can be done in an application/server or a J2EE container environment because they have built-in Transaction Managers (TM). and one just has to use JNDI to look up the UserTransaction object and then define the transaction boundaries. However, how do I all the above if I don't have access to a J2EE server and an EJB server?
It seems like I would have to use a standalone Transaction Manager (not bundled with the app-server).

Hi,
My company has just released a (beta!) version of a generic java transaction manager. Although it offers some lightweight beans as standard development model, this does not have to be the case: the core idea is an extensible and very advanced transaction kernel. JTA comptable.
This software is server-oriented: the transactional kernel (which also does recovery) startup and shutdown events trigger the start (initialization) and shutdown of your 'extension' classes. This is necessary because otherwise your resources will not be recoverable: if the transaction manager starts up, then it will first do recovery, and therefore your resources need to be available.
You can ask for a beta version through our website:
http://www.atomikos.com
Note, however: we did not yet implement the XA DataSources. Rather, we have a kind of 'external' stored procedures that allow distributed transactions over regular JDBC connections. You would have to implement your solution along this line, or wait for the XA datasources.
If there proves to be a lot of demand,
we can of course speed up development on XA. It is not a very big effort.
Best regards,
Guy
Guy Pardon ( [email protected] )
Atomikos Software Technology: Transactioning the Net
http://www.atomikos.com/

How to define your own context in an EJB environment - possibly distributed

I would like to setup a context (an object accissible per logical thread) in an EJB environment, but I am too unfamiliar with the options I may have.
My objective is to create a context in which I may set a value, then invoke a method on an object (which in turn invokes a method on another object and so forth) and eventually get back the value from the context. In other words I am trying to pass a value without passing it as a parameter. More specifically, I have written a JDBC Driver wrapper in which I want to intercept a number of method calls and based on the context settings perform one or the other JDBC preprocessing. The reason for not passing the values as parameters is to interfere as little as possible with any environment in which this code is to be integrated. I simply want to set the context and get the context (in my JDBC wrapper) without the surrounding code needing to change.
I have succeded partially by using a ThreadLocal object to hold my context. I can set and get the values to and from the context and actually pass values to my Driver wrapper without explicitly passing them as parameters. This works well in a non-EJB environment. My concern arises when I switch to the EJB environment.
If my context is set in a session bean, which invokes an entity bean, am I then guaranteed that these will execute in the same physical thread?
If the session and the entity beans are hosted on seperate machines then the answer would certainly be NO. Is there any way to have the container manage the context and propagate it accross containers when needed?
Any thoughts or suggestions on this topic are wellcome, even if they don't solve the issue entirely.
Looking forward to hear from you all!
/poul

In an EJB environment, you have absolutely no control over threading issues. (It was purposefully designed that way.) However, you do have your own little "sandbox" in the EJB ClassLoader - which is why there is a lot of use of the Singleton pattern for factories and (very carefully!) as small caching mechanisms. You might want to look into that avenue - but you have to know how your EJB vendor's ClassLoader scheme works (there does appear to be a convergence in this area) and you must be very sensitive to potential thread-blocking operations that may take a while to complete.

Calling non ejb from ejb using jndi lookup

Is it possible to call a non ejb java object from an ejb using a jndi lookup?
For example, we have a java class where main registers itself with our application server (JBoss 3.0.1). We have a test client that can use jndi to look up the object, but we can't get an ejb inside the application server to use the object.
Are we trying to do the impossible? If my question is not clear, please let me know so I can try to clarify.
Thanks

JNDI uses factories to create objects.
It's possible that JBoss has a Bean Factory which you can use to create your instance.
Tomcat has a Bean factory in its JNDI implementation. I use it just as you have indicated.
The JBoss documenation may help?
Dave

Can't access non ejb classes from JSP - NoClassDefFound error

 Hi,
 I have one session ejb which has a method returning a collection of non ejb class objects (say of Class 'Foo').
 The method signature is like :
 "Collection getFinacialData() throws RemoteException"
 It is working fine with normal java clients. Now when I run this from a JSP it gives a "NoClassDefFoundError". I kept class 'Foo' and the remote interface of the session bean in the same package and also in the same ejb jar file. Also I am running JSP and ejb in same WL server(ver 5.1, SP8 on solaris). What I have done is only deployed the bean jar file. Do I need to do anything more?
 thanks in advance.


I ran into a similar problem. I solved it by putting the client classes for
 accessing my EJB in the WebLogic POST_CLASSPATH in the startWebLogic script
 file:
 set POST_CLASSPATH=d:\weblogic\myserver\myClient.jar
 For more information on class visibility between the JSP and EJB class
 loaders, check out
 http://www.weblogic.com/docs51/classdocs/API_ejb/EJB_deployover.html#1056256
 Rick
 "niroja" <[email protected]> wrote in message
 news:3a6ed903$[email protected]..
 >
 > Hi,
 >
 > I have one session ejb which has a method returning a collection of non
 ejb class objects (say of Class 'Foo').
 > The method signature is like :
 > "Collection getFinacialData() throws RemoteException"
 > It is working fine with normal java clients. Now when I run this from a
 JSP it gives a "NoClassDefFoundError". I kept class 'Foo' and the remote
 interface of the session bean in the same package and also in the same ejb
 jar file. Also I am running JSP and ejb in same WL server(ver 5.1, SP8 on
 solaris). What I have done is only deployed the bean jar file. Do I need to
 do anything more?
 >
 > thanks in advance.
 >

NON-SERVLET, NON-EJB DYNAMIC CLASS RELOAD

hi,
          In weblogic 5.1, is there a way to reload a class from the clientclasses directory without restarting the server? it's just a class in the clientclasses used by the JSPs. a kind of hotdeploy for NON-EJB, NON-SERVLET CLASS. SPECIFIC guidance will be immensely appreciated..
          Thanks in advance
          Vijay


please show us the full error message.
it sounds like a classpath problem...

Interceptors for non EJB

Hi,
does the jee standard covers interceptors for non EJB classes? I'm using Glassfish and it worked for a plain java classes e.g.:
@Interceptors(TraceInterceptor.class)
public class PlainClass {
     public String doSomething() {
          return "somthing";
Hoever when I use the intercepter with a DAO class that's depending an an EntityManager e.g.:
@Interceptors(TraceInterceptor.class)
public class PersonDao implements IPersonDao {
     @PersistenceContext
     private EntityManager em;
     @Override
     public Person getById(Integer id) {
          return em.find(Person.class, id);
I get a NullPointer exeption because the Entity Manger is not injected.
so my question is: does the jee standard covers interceptors for non EJB classes?
Regards
Sebastian

Hi,
thanks for your response.
When I remove the @Interceptors annotation from the PersonDao everything works fine including the injection of the entity manager. When I add the @Interceptors annotation I get a null pointer at em.find(Person.class, id).
I’m new to JEE6 because I have worked with Spring the last 6 years. Accidently I never used the @Named annotation. Surprisingly that is no problem (at least in Glassfish).
Anyhow I added the @Named annotation to the DAO but that not changed anything, I still got a null pointer. What’s wrong?
@Interceptors(TraceInterceptor.class)
@Named
public class PersonDao implements IPersonDao {
     @PersistenceContext
     private EntityManager em;
     @Override
     public Person getById(Integer id) {
          return em.find(Person.class, id);
@Stateless
@Interceptors(TraceInterceptor.class)
public class TestSrv implements ITestSrv {
     @Inject
     private IPersonDao personDao;
     @Override
     public Person getPerson(Integer id) {
          return personDao.getById(id);
Best regards
Sebastian

Previous unanswered Hot deploy of non EJB, non JSP classes

 Subject to my last post I've since seen my questions has appeared twice on this
 newsgroup, March 2001, and Nov 2000 and no responses to it those times. Aren't
 there BEA engineers reading this newsgroup who would know the answer to that question?
 http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jsp&item=3776&utag=
 http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jsp&item=5171&utag=


 Firstly I already did call BEA support before coming here, this is my last resort.
 I can't get a definitive answer from support. They were the ones that actually
 suggested to me that I post here in the first place. I did search the BEA edocs
 and couldn't find anything on it.
 Secondly, I am using WL 6.1 SP1, and in the thread just beneath this one, which
 I referred to directly in my opening post on this thread, I do mention this in
 the opening paragraph, in fact I give considerable detail.
 Thirdly, I never implied there was an onus on any BEA engineer to answer anything
 here. What I did mean was that given that they do read these posts and they do
 answer posts, I was merely a bit concerned that as I'm third person to ask, it
 would be strange to still get no response given that they answer other questions.
 I mean if they don't know, then who does? It's a real simple yes/no answer, it
 would take 5 seconds.
 Paul
 Robert Patrick <[email protected]> wrote:
 >
 >
 >The answer is simple -- move to WLS 6.x and use enterprise applications
 >(or web applications or an EJB jar file)
 >to package everything up into a single deployment unit and hot deploy
 >the whole deployment unit. WLS 5.1 and
 >earlier do not support hot deployment of non-servlet/non-JSP/non-EJB
 >classes.
 >
 >Mike Reiche wrote:
 >
 >> You can always call BEA Support - 1.888.232.7878 to get the help you
 >need. This
 >> newsgroup is not official BEA Support. It is out of the goodness of
 >their hearts
 >> that BEA engineers help people out here.
 >>
 >> I don't really think you wanted everyone that read your email and didn't
 >know
 >> if such a feature was available, to send you an email saying 'No, I
 >don't know
 >> if such a feature is available'. That's why there were zero responses.
 >>
 >> None of the posts you listed mention what version of WL. That makes
 >a difference.
 >> Also read the online documentation at edocs.bea.com, search for 'hot
 >deploy'.
 >>
 >> Mike Reiche
 >>
 >> "Paul H" <[email protected]> wrote:
 >> >
 >> >Subject to my last post I've since seen my questions has appeared
 >twice
 >> >on this
 >> >newsgroup, March 2001, and Nov 2000 and no responses to it those times.
 >> >Aren't
 >> >there BEA engineers reading this newsgroup who would know the answer
 >> >to that question?
 >> >
 >> >http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jsp&item=3776&utag=
 >> >
 >> >http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jsp&item=5171&utag=
 >
 >
 ><!doctype html public "-//w3c//dtd html 4.0 transitional//en">
 ><html>
 >The answer is simple -- move to WLS 6.x and use enterprise applications
 >(or web applications or an EJB jar file) to package everything up into
 >a single deployment unit and hot deploy the whole deployment unit.
 >WLS 5.1 and earlier do not support hot deployment of non-servlet/non-JSP/non-EJB
 >classes.
 >Mike Reiche wrote:
 ><blockquote TYPE=CITE>You can always call BEA Support - 1.888.232.7878
 >to get the help you need. This
 > newsgroup is not official BEA Support. It is out of the goodness
 >of
 >their hearts
 > that BEA engineers help people out here.
 >I don't really think you wanted everyone that read your email and
 >didn't
 >know
 > if such a feature was available, to send you an email saying 'No,
 >I
 >don't know
 > if such a feature is available'. That's why there were zero responses.
 >None of the posts you listed mention what version of WL. That makes
 >a difference.
 > Also read the online documentation at edocs.bea.com, search
 >for
 >'hot deploy'.
 >Mike Reiche
 >"Paul H" <[email protected]> wrote:
 > >
 > >Subject to my last post I've since seen my questions has appeared
 >twice
 > >on this
 > >newsgroup, March 2001, and Nov 2000 and no responses to it those
 >times.
 > >Aren't
 > >there BEA engineers reading this newsgroup who would know the answer
 > >to that question?
 > >
 > >http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jsp&item=3776&utag=
 > >
 > >http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jsp&item=5171&utag=</blockquote>
 ></html>
 >
 >

How to inject EntityManager in non-EJB based WebService?

Hi,
I want to know how we can inject EntityManager in non-EJB based WebService?
Regards,
imran

I think the way to go would be to actually do use an EJB for the persistence stuff and use that EJB in your webservice. Use the right tool for the job and all that.

Transaction & non-EJB objects (helper)

hi i have a question about transactional behavior of non-EJB objects. i'm
 using
 weblogic 6.0 sp1 with ejb 2.0.
 say i have a session bean which starts a container managed transaction. and
 it calls
 out to helper class A(non-EJB), and that helper class A get a connection and
 update
 some tables. after A returns, session bean calls helper class B(non-EJB) in
 the
 same transaction. B is supposed to update some other tables but it throw an
 user
 exception. would the transaction in the session bean be rolled back? would
 it
 also roll back the changes made by helper class A?
 thanks for any help,
 z


Thanks Rob!
 "Rob Woollen" <[email protected]> wrote in message
 news:[email protected]...
 > Ziqiang Xu wrote:
 >
 > > hi i have a question about transactional behavior of non-EJB objects.
 i'm
 > > using
 > > weblogic 6.0 sp1 with ejb 2.0.
 > >
 > > say i have a session bean which starts a container managed transaction.
 and
 > > it calls
 > > out to helper class A(non-EJB), and that helper class A get a connection
 and
 > > update
 > > some tables.
 >
 > You must get the JDBC connection from a TxDataSource.
 >
 > > after A returns, session bean calls helper class B(non-EJB) in
 > > the
 > > same transaction. B is supposed to update some other tables but it
 throw an
 > > user
 > > exception. would the transaction in the session bean be rolled back?
 >
 > Merely throwing an exception from a helper class will not rollback the
 > transaction.
 >
 > Within an EJB, the best way to rollback a tx is to use the
 > EJBContext.setRollbackOnly method.
 >
 > So you could do something like this:
 >
 > session_bean_method() {
 >
 > try {
 > B.foo();
 > } catch (MyException e) {
 > ctx.setRollbackOnly();
 > throw e;
 > }
 >
 > }
 >
 > > would
 > > it
 > > also roll back the changes made by helper class A?
 > >
 >
 > If they are all within a single transaction, then yes. As I mentioned
 before,
 > make sure that you use a TxDataSource for all of your JDBC Connections.
 >
 > -- Rob
 >
 > >
 > > thanks for any help,
 > >
 > > z
 >

Custom Object Persistance (non-EJB)

Hello friends.
Could you please give examples, or links to resources, on implementing object persistance where database is the store. EJB is not considered.
It would be great if you could share your experience.
So far I found out two desing patterns for implementing object persistance, that can be found on www.javaworld.com (under Persistance).
The idea expressed in the articles is that every Business Object has a corresponding Data Access Object, that handles all persistance tasks (namely writing, reading from database).
Has anyone implemented it? What are the alternatives?
Hope to hear everyone.

It seems that managing connection is a difficult
issue. Don't you think that factory has to accomplish
connection management, and DAOs have to have a
reference to factory, and call factory's
getConnection() and closeConnection() methods, and
factory will either open and close them, or return
them to pool.You've got a point. Managing connections in a non-EJB environment is the difficult issue. (With EJBs and DataSources this is piece of cake.)
When performance is not the issue, opening and closing a new connection for each db-operation should suffice. But when performance is the issue, things get a little more complex.
A naive way of increasing performance is to have DAOs cache connection objects. The only problem with this is that you would then require one database connection for one DAO. For some applications this would not be a problem, but as a generic solution this is really, really bad.
As for letting the DAOFactory handle connections I am not convinced. I would rather design and implement a separate connection pool (or find an open source / commercial one) than complicate my factories. After all, as the class name states, a UserDAOFactory is a user data access object factory, not a connection pool or a connection manager. Low coupling, high cohesion, eh? ;)
One way of implementing a connection pool I thought of is to write a ConnectionPool class and a PoolableConnection class (or something like that) that implements java.sql.Connection and acts as a wrapper for the real connection. Closing one of these connection would not actually close the connection, but would just return it to the pool.
What is cool about this approach is that you do not have to have your clients call some weird getConnectionFromPool() and returnConnectionToPool(...) methods, they would simply call ConnectionPool.getConnection() and when they are done with the connection they close it, just like a normal java.sql.Connection.
I am oversimplyfying things, of course. But in principle this is precisely what is done in J2EE, just use a "DataSource" for a "ConnectionPool".
Writing code for getting and closing connections in every dao seems a
bit of overhead.It definetely is. With EJBs I used an abstract DAO class to implement connection retrieval (and to hide JNDI-code and cache DataSources) and had all my DAOs extended this class.
Also, from your experience, you never used the generic
CRUD methods? It seems that all your daos have
specific methods, such as loadByUsername.
The article in javaworld get away from this by using
complicating mapping techniques. Have you ever used
generic CRUD, or you found it usefull to have specific
methods?Yep, I have never done anything with CRUD. And all this generic framework stuff and mapping things seems a bit complicated. Perhaps I will have a closer look.

Where to put jar file containing non ejb beans

 Hi everyone,
 i would appreciate a lot if someone could tell me where i could place my jar file
 which contains non ejb beans
 thanks


 Hi,
 I´n not sure what you mean. But if you mean a JAR containing utility classes for
 your EJBs or Servlets you should put it for EJBs into the META-INF/lib directory
 of your EJB JAR or for Servlets/Webapps into the WEB-INF/lib directory.
 So the JAR file will be automatically loaded from the right classloader and can
 be used.
 Christian Plenagl
 Developer Relations Engineer
 BEA Support
 "Mirza Khodabaccus" <[email protected]> wrote:
 >
 >Hi everyone,
 >
 >i would appreciate a lot if someone could tell me where i could place
 >my jar file
 >which contains non ejb beans
 >
 >thanks

JDBC, JMS and EJB transactions - possible problem?

Hello,
          I am using Oracle 9, Weblogic 8.1 SP 4, MyEclipse and
          XDoclet.
          In my current project I have the following piece of code
          in one of my message driven beans (code cited as pseudocode
          without unnecessary details):
          * @ejb.bean name="MyMessageProcessor"
          * display-name="Display name for a MyMessageProcessor"
          * jndi-name="ejb/MyMessageProcessor"
          * description="Bean MyMessageProcessor"
          * destination-type="javax.jms.Queue"
          * transaction-type="Container"
          * acknowledge-mode="Auto-acknowledge"
          * subscription-durability="Durable"
          * generate="false"
          * @ejb.transaction type="Required"
          public class MyMessageProcessor implements MessageDrivenBean, MessageListener {
          public void onMessage(Message msg) {
               try {
                    //obtaining connections to two different databases via JNDi
                    java.sql.Connection connOne =
                    ((DataSource)ctx.lookup("DataSourceOne")).getConnection();
                    java.sql.Connection connTwo =
                         ((DataSource)ctx.lookup("DataSourceTwo")).getConnection();
                    // performing some UPDATEs and INSERTs on connOne and connTwo
                    // calling some other methods of this bean
                    //creating the reply JMS message and sending it to another JMS queue
                    Message msgTwo = this.createReplyMessage(msg)
                    this.queueSender.send(msgTwo);
                    //commiting everything
                    this.queueSession.commit();
               } catch (Exception ex) {
               try {
                    if (this.queueSession!=null) this.queueSession.rollback();
               } catch (JMSException JMSEx) {};
               this.context.setRollbackOnly();
          Some days ago (before the final remarks from my client) there used to be only one DataSource configurated on the basis of the
          connection pool with non-XA jdbc driver. Everything worked fine
          including the transactions (if anything wrong happend not only wasn't the replymessage sent, but also no changes were written
          to database and the incomming message was thrown back to the my bean's
          queue).
          When I deployed the second DataSource I was informed by an error message, that only one non-transactional resource may
          participate in a global transaction. When I changed both datasources
          to depend on underlying datasources with transatcional (XA) jdbc drivers, everything stopped working. Even if
          EJB transaction was theoretically successfully rolledbacked, the changed were written to the database
          and the JMS message wasn't resent to the JMS queue.
          So here are my questions:
               1. How to configure connection pools to work in such situations? What JDBC drivers should I choose?
               Are there any global server configurations, which may influence this situation?
               2. Which jdbc drivers should I choose so that the container was able to rollback the database transactions
               (of course, if necessary)?
               3. Are there any JMS Queue settings, which would disable the container to send message back to the
               queue in case of setRollbackOnly()? How should be the Queue configurated?
          As I am new to the topic and the deadline for the project seems to be too close I would be grateful
          for any help.
          This message was sent to EJB list and JDBC list.
          Sincerely yours,
          Marcin Zakidalski

Hi,
          I found these information extremely useful and helpful.
          The seperate transaction for sending messages was, of course, unintentional. Thanks a lot.
          Anyway, I still have some problems. I have made some changes to the
          code cited in my previous mail. These changes included changing QueueSessions
          to non-transactional. I also set the "Honorate global transactions" to true.
          I am using XA JDBC driver. After setting "Enable local transactions" to false
          (I did it, because I assume that JDBC transactions should be part on the global
          EJB transaction) I got the following error:
          java.sql.SQLException: SQL operations are not allowed with no global transaction by default for XA drivers. If the XA
          driver supports performing SQL operations with no global transaction, explicitly allow it by setting
          "SupportsLocalTransaction" JDBC connection pool property to true. In this case, also remember to complete the local
          transaction before using the connection again for global transaction, else a XAER_OUTSIDE XAException may result. To
          complete a local transaction, you can either set auto commit to true or call Connection.commit() or Connection.rollback().
          I have also inspected the calls of methods of bean inside of onMessage() method just to check, whether
          the transactions are correctly initialized (using the weblogic.transaction.Transaction class).
          My questions are as follows:
          1. Any suggestions how to solve it? I have gone through the google answers on that problem and only
          thing I managed to realize that JDBC must start its own transaction. Is there any way to prohibit it
          from doing that? Can using setAutocommit(true/false) change the situation for better?
          2. How to encourage the JDBC driver to be a part of EJB transaction?
          3. As I have noticed each of ejb method has its own transactions (transactions have different
          Xid). Each method of the bean has "required" transaction attribute. Shouldn't it work in such
          way that if already started transaction exists it is used by the called method?
          4. The DataSources are obtained in my application via JNDI and in the destination environment I will have slight
          impact on the configuration of WebLogic. What is least problematic and most common WebLogic configuration which would
          enable JDBC driver to participate in the EJB transaction? Is it the WebLogic configuration problem or can it be
          solved programmically?
          Currently my module works quite fine when "enable local transactions" for DataSources is set to true, but this way
          I am loosing the ability to perform all actions in one transaction.
          Any suggestions / hints are more than welcomed. This message was posted to jdbc list and ejb list.
          Marcin

Home Page Search Is Non-Functional / Not Possible to Restore Previous Session

After the latest update (to version 29), Firefox's default home page search bar has been completely non-functional. Whether I type enter or press Search, nothing happens. Another (possibly related) problem is that the "Restore Previous Session" button is never present. I also cannot restore the previous session by clicking on the History option (it is always greyed out).

I had this and other problems with v29. But after a while everything was working
again, I hope. BTW; 
I found that after Firefox v29, a LOT of my settings and add-ons were changed /
reset. Try this;
'''''[https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode Start Firefox in Safe Mode]'''''
 While you are in safe mode; 
'''''Firefox Options > Advanced > General'''''. 
Look for and turn off '''Use Hardware Acceleration'''.
Check ALL of your setting. Then restart.

Is outside-in without EJB's possible?

Is it possible to create a web service from a wsdl (outside-in approach) without EJB's involved. in CE7.1
Regards
ABS

Yes, you can but manually. There is no such easy tool as for EJBs in NetWever Developer Studio(NWDS).
Using the the NWDS you can generate automaticaly Outside-In web service sceletons but only with EJB endpoints.
Maybe you have already read that page:
http://help.sap.com/saphelp_nwce10/helpdata/en/46/7f2fef88190ad3e10000000a11466f/content.htm
But if you need a servlet-based web service and you want to start from the WSDL, you can do it manually by creating a pure java class in web project and than adding the annotations with values corresponding to the one from the WSDL. In this case you will need some more knowlage in web services area.
I hope that explainations help you.
Regards,
Yulie.

Non EJB JTA possible?

Similar Messages

Maybe you are looking for