"Edit Session Facade" in JDeveloper

Hi,
My session facade bean in TopLink project is working well. I just added a new named query and I would like to edit session facade to expose that method. Then I would need to re-create the DataControl. I did this a couple of times and that was fine. But now it doesnot show up the "Edit Session Facade" window for me to check to include the new method. Is there a way to delete the DataControl to create a new one, or any one knows any suggestion?
Thank you,
John

Make sure you added the method to the EJB interface as well.

Similar Messages

Publicar Aplicacion EJB3 Session Facade JSF

Buanas, soy nuevo en la programacion WEB, realice una aplicacion que funciona muy bien en JDeveloper modo debug, pero necesito subirla a un servidor. Tengo la limitante de que requiero que este servidor sea de distribucion libre, por tal motivo he optado por Tomcat o Jboss, el inconveniente que tengo es que la aplicacion no se me conecta con la BD.
Estoy usando un Session Facade en un proyecto y desde otro me conecto a él con un InitialContext (Como muestra el client del session facade), uso Jdeveloper 10g R3, la base de datos es Oracle 10g Express, uso JSF, con framework MyFaces.
Si alguien tiene alguna informacion de la cual me pueda basar para hacerla funcionar mi aplicacion en un servidor, se lo agradecería mucho.

Hi I don't speak english, but...
Good, I am new in the programming WEB, makes an application that works in JDeveloper way very well debug, but I need to raise it a servant. I have the limitante of which I require that this servant is of free distribution, by such reason I have decided on Tomcat or Jboss, the disadvantage that I have is that the application is not connected to me with the BD.
I am using a Session Facade in a project and from other I connect myself to him with a InitialContext (As it shows client of session facade), use Jdeveloper 10g R3, the data base is Oracle 10g Express, use JSF, with framework MyFaces.
If somebody has some information of which it can base to me to make it work my application in a servant, much would be thanked for.
Translate by Google...

(ejb 3.0) stateful session facade?

Hello,
(1) Would you consider stateful session facade (whose client is a servlet) a bad design?
(2) How to have a stateful session facade referenced in a servlet? I am using Sun Application Server Platform Edition 9.0 and trying to make an injection:
@EJB(name="ejb/KOGSessionFacade")
protected KOGSessionFacade sessionFacade;
but then I get this error in deploy-time: "A stateful session bean can not be injected into a servlet. Please refer to EJB 3.0 Persistence API Specification section #5.2 for further information."
Thanks.

Using a Stateful Session facade from a Servlet is not necessarily a bad design. In some cases, you may want to do some cleanup work on completion of a transaction. Stateful Session beans provide a convenient way (By implementing SessionSynchronization interface) to do this.
In the servlet programming model, Servlets are not designed to be single threaded. So if you inject a StatefulSessionBean (SFSB) references then multiple threads could be possibly be invoking the SFSB concurrently. In this case, the EJBContainer (as required by the specification), will throw a well defined exception.
What you may want to do is to place this SFSB reference into you Servlet session.

Error when Create Session Bean in JDeveloper

Hi All,
I followed the steps in the SRDemo tutorial to create Session bean SRPublicFacade. I used Create Session Bean wizard. Step 1 was ok. Step 2 when it's supposed to show all the POJOs and all methods (from Queries) it hang there, and skipped to Step 3 and so on... As a result I had an empty Session Bean with only class name and no methods in it. I do have correct database connection, and I have another project with similar Session Bean sucessfully. I just don't know what happened to this project or the way I created session bean this time. Any conflict when create Session Bean to the same database or something(?) Anyone has any idea please let me know.
Thank you very much,
John

Frank,
Yes, I compiled the project before building the session facade. I used JDeveloper 10.1.3.3.0
The thing is I once created successfully the session facade in another project, like SRdemo. Now I would like to repeat that in another project say SRdemo2, then it went wrong. It skipped step 2 in the wizard and look like it cannot detect the tables and named queries.
Thanks,
John

Service Locator and session facade pattern

What are differences between Service Locator and session facade pattern?
For me it seems one and the same.
Please explain me in detail. Expecting kind help.
Thanks,
Rahul
Edited by: rahulb1 on Feb 26, 2008 5:07 PM

rdoekes wrote:
The ServiceLocator Pattern is a singleton which hold a map of used DataSources. The idea is that you perform a lookup once and use the cache afterwards. The session facade is just one DataSource lookup.huh? Those J2EE patterns are not really reduced to datasources and the SessionFacade has actually nothing to do with datasources.
Session Facade
It has Facade in it and a Facade is usually used to give a simple entrypoint by providing a standartized interface. The same is now with the Session Facade. You have a Session bean that represents a high-level business component that interacts and calls lower-level business components.
Imagine having client a accessing 5 business objects with the remote calls, which is not an efficient way (network latency) or accessing the SessionFace and the session face is doing all the work through local access.
Service Locator
As J2EE components are using JDNI to lookup for ejb interfaces,DataSources, JMS components, connections etc. isntead of writing all the lookup in many code piecess across the project, you write a service locator that gives you a centralized place to handle the lookup's. It's easier to maintain and to control such a setup.
As you can see there's quite a big difference ;-)
cya,
Nail

Business Delegate and Session Facade usage.

Hi guys.
I am new to JavaEE and I recently learnt the Business Delegate and Session Facade design patterns. The tutorials from Oracle did gave me a basic idea of what they are and why they are used, but the example didn't really answer all my questions. So I decided to use a real life scenario here and put my question in to it. Any help is appreciated.
Assume I want to create a search employee page for my company, the employees are categorized by his or her department and the province he or she is in. I have in the database a look up table for department and province. (as shown in the image below)
http://oi46.tinypic.com/idvpsl.jpg
So I create three JPA entities, one for each table. Now I am stuck with what is the proper way to design the session facade design pattern. I know that I will need the to access all three entities in my page. (to get the drop down list for Provinces and Departments, and to retrieve list of Employees based on the selection) So should I create a Stateless Session Bean as session facade to access all three JPA Entities or should I create three separate Stateless Session Bean to manage one Entity each?
I came up three component diagram in the below picture.
The first one has one Stateless Session Bean as session facade and manages all three Entities.
The second one has a session facade to manage the relationship between business objects such as ProvinceManagerEJB and DepartmentManagerEJB which will manage the corresponding Entities.
The last one has three Stateless Session Beans that will manage one Entity each, all three Stateless Session Beans can be looked up via the Business Delegate pattern.
http://oi46.tinypic.com/10pqets.jpg
Please let me know if any one of them is the proper way to use business delegate and session facade. or none of them is correct. (which I assume might happen)
Again, thank you so much for your help.
Cheers
Edited by: 992005 on 05-Mar-2013 18:15
Edited by: 992005 on 05-Mar-2013 18:17

Well I can't access any of your diagrams from here so can't comment on them. For dividing the functionality into separate classes, think about
1.) Quantity - Are there many enough service calls to require splitting up or will one application service class be enough? The size of the system is important here.
2.) Are you duplicating logic in the services? e.g save person, delete person in one service and save department, delete department in another e.t.c is better factored into one service with save entity, delete entity calls because the JPA entity manager doesn't know about the type anyway and it's easier to apply common logic (e.g logging auditing) around the calls.
3.) Will each service makes sense on it's own or do you always need the other functionality to completely describe the service? Here it is important not think about entities but about the business use cases. Process1Service is better than Entity1Service, Entity2Service ... EntitynService.Think granule of reuse = granule of release. Only split out individually reusable services. A good way to understand granules of reuse in your system is to think about (or start by writing) test cases for the functionality. Testable code is reusable code.
4.) Will the services change together? At class level you would look at common closure principle (classes that change together should be packaged together). You can apply the closure to the methods as well. Make it easy for future developers to recognize dependent functionality by packaging it together.
These are just general because in enterprise development requirements are king. You can chose to follow or discard any of these rules depending on your requirements as long you understand the impact of each decision.

Session facade deligator

Hi ALL,
I used to employ BusinessDelegate pattern in ejb 2.0. My design was SFD ( session facade deligator) ---- SFIMPL - DAO.
I am wondering whether it is still being used with ejb3.0. Besides providing abstraction layer to the session facade some of the benefits of using a delegate was to cache EJBHome, or to provide client with the byteCode for the serialized ejb Handles and to abstract ejb/rmi exception from the client code.
Is this pattern still applicable to ejb3.0 since now we don't use ejbHome, ejb/rmi exceptions are not visible and you have dependency injection. In ejb3.0 is the approach of serializing ebj handle still viable?
Also with struts is it better to create intsatnce of ejb interface in base action class and avoid any session facade deliagtor and call directly ejb imp
Thanks
Edited by: j2ee_expert on Jul 8, 2008 1:13 PM

You should avoid SessioCaching now and leave the job to the dependency injection. They are much more intelligent then what was possible before EJB 3.0.
For example they will avoid RMI if both applications are running on the same JVM, and take care of all the other stuff as caching and so on.
Bottomline: You wont need it in EJB 3.0 as dependency injection will take care of all the stuff the ResouceLocator/BD was doing.

JDev 1013 BUG? EJB, CMR, DTO and session facade.

I've created two CMP Entity EJB's, CourseEJB and PupilEJB, and defined a M:N relationship between them. A course has many pupils and vice versa. Each bean has only two attributes, id (Long, part of PK) and name (String) for simplicity.
1. Generated DTO's for the two beans won't compile
I get error on:
public void addcourseEJBLocalDTO(courseEJBLocalDTO courseEJBLocalDTO)
coursesDTO.add(courseEJBLocalDTO);
courseEJBLocalDTO.setPupilsDTO(this);
and:
public void addPupilEJBLocalDTO(PupilEJBLocalDTO pupilEJBLocalDTO)
pupilsDTO.add(pupilEJBLocalDTO);
pupilEJBLocalDTO.setCoursesDTO(this);
because JDev has created definitions of the setCoursesDTO function like this:
public void setCoursesDTO(Collection<courseEJBLocalDTO> coursesDTO)
this.coursesDTO = coursesDTO;
and ditto for the setPupilsDTO method, taking a Collection as argument too.
I can fix this code manually, but next step, generating a session Facade with added methods for handling the entity beans isn't exactly any better...
One M:N relation is pretty basic, am I doing something wrong here?
Message was edited by:
jonmarti

Forgot to add, running on 1013

Depenency Injection and Session Facade in WebDynpro DCs

Hi all,
for the sake of decoupeling the business logic and persistence from the view i introduced a session facade.
I wonder how to acess the session facade bean from my webdynpro?
am i right that dependency injection inside a wd dc is not working?
does jndi work in a wd dc?
regards,
christian

Hi Christian,
First - welcome to SDN!
To your questions:
1) JNDI access to EJBs works from any client application, which means also from WD apps. <a href="http://help.sap.com/saphelp_nwce10/helpdata/en/45/e692b2cfaa5591e10000000a1553f7/frameset.htm">Here</a> you can find more information on that.
2) Dependency injection does not work within WD.
3) I would suggest you to consider the <a href="http://help.sap.com/saphelp_nwce10/helpdata/en/45/f7f744aea471fae10000000a1553f6/frameset.htm">EJB Model Importer</a> which is the easiest and recommended way for using session beans inside WD components. This is a new feature coming with <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/ce">SAP NW CE</a> aiming to increase developers productivity by reducing the need for manually written code for accessing and calling the EJB business methods.
Please do not hesitate to come back should you have any further questions.
Best regards,
Vladimir
Message was edited by:
Vladimir Pavlov

The task cannot be processed further until the current edit session is act

Dear Sir/Madam
I have installed standalone Oracle WebLogic Server 11g(10.3.6) with Sherman Update3,for I used JDeveloper 11g Release 2 (11.1.2.3.0).
I Sometimes got below message for several times and it can be repeatable when I have wanted to deploy my applications.
"[11:38:24 AM] [Deployer:149140]The task cannot be processed further until the current edit session is activated. When this occurs, task processing will continue. The user can exit the deployer tool without affecting the task."
Furthermore, I run weblogic console and I see to appear the two buttons "Activate Changes & Undo All Changes" in spite of the weblogic is in development mode, yet the state of my application is "deploy initialize". I Click "Activate Changes" button but it's not happened.
Finally, for dealing with this problem, I have to shutdown & start up the weblogic .Next, I can deploy my application.
Best Regards,
Saeed.

Hi,
That message is not an error. It means that you need to connect to the WebLogic Server Console and activate the changes.
Solution
Access the WebLogic Server Console and click on Activate Changes.
Confirm if your application shows in the WebLogic Server Console under "Deployments".
Regards,
Kal

Session Facade Question

Hi all,
I have the following scenario:
A MDB reads messages from a queue and depending on one property of the message a different stored procedure is called.
I'm thinking about 2 approaches:
1) The MDB always calls the same SSB which holds all the stored procedures calls.
2) The MDB calls different SSB depending on the stored procesure to call.
At the moment I'm implementing the 2) approach, but my main concern is if it is effective when some of the procedures are not called very frequently. Probably it will be the debate between performance or resources. Which one would be better if I have lack of resources?
TIA
Felipe

thanks but I dont get that option when I right-click my Java Service Facade. The option seems to only be there for a Session Bean Facade. Is there a way to edit the session facade for a Java Service Facade?
Also .. since we're in that topic - what's more advisable for a session facade - a Session Bean or a Java Service Facade? Pros and Cons?
Thanks again!
DF

[HOWTO] JSF + Session Facade + Entity Bean (EJB3)

I'm trying to find a tutorial that shows the advisable way to use JSF with EJB 3 entity beans using the Session Facade pattern (?), but the only tutorials around show very basic usage of JSF (validation, conversions etc.).
The only thing that is close is this: http://forum.java.sun.com/thread.jspa?threadID=5122284 but still not what I'm looking for.
Is there any documentation available out there..?
Message was edited by:
HakelRausd

Hi,
I updated the online doc in blueprints solutions catalog with a small explanation of using JSF with EJB Session Bean at https://blueprints.dev.java.net/bpcatalog/ee5/persistence/ejbfacade.html
I will add an image soon too. The basic idea for JSF and EJB3 programming model is
JSF Page --> JSF Managed Bean(backing bean) --> Session Bean --> Java Persistence Object.
In general, ther would be several JSF pages,and several JSF Managed Beans, and several Java Persistence Objects, but fewer Session Beans. The Session Bean would be expected to be shared and accessed by several managed beans with with Session Bean serving as a facade to the Java Persistence Objects, so there would be few Session Beans.
The Session Bean would usually be a local Session bean and would only be remote if-and-only-if you wanted RMI-IIOP access. Usually web components like Servlets and JSF Managed Beans use local access to the Session Beans and the access is within the same VM, no remoteness.
Most of the time, the Session Bean would be a Stateless Session Bean, and would not be a Stateful Session Bean.
hth,
Sean

Blog post : "Bug in Create/Edit View Criteria Wizard (JDeveloper 11g)"

hi
Using steps 1 to 13 from the blog post "Bug in Create/Edit View Criteria Wizard (JDeveloper 11g)" by Andrejus Baranovskis, I have been able to reproduce the issue he describes.
see http://andrejusb.blogspot.com/2008/12/bug-in-createedit-view-criteria-wizard.html
I the blog post comments he writes "... there was no time for me to fill bug in Metalink ...".
Maybe someone from Oracle can pick it up from this forum post and file it as a bug if it is one (and if possible post the bug number here).
many thanks
Jan Vervecken

The mechanism is to create a reproduceable test case, create a Service Request in metalink.oracle.com, post the test case, and convince the analyst to file it as a bug.
It may be not efficient at some time, but this the way it is handled.
--olaf

Error while calling local session bean from session facade

Hi Everybody,
I was to execute example of session facade pattern. All the files compile properly, but when ejbc command is run, i get the following error:
ERROR: Error from ejbc:
     In EJB *MANAGER, method create() exposes local interface types or local home interface types through the remote home interface of the bean. This is not allowed.
ERROR: Error from ejbc:
     In EJB *MANAGER, method remove(java.lang.Object) on the home interface does not throw java.rmi.RemoteException. This is a required exception.
     In EJB *MANAGER, method create() on the home interface does not throw java.rmi.RemoteException. This is a required exception.
ERROR: Error from ejbc: In EJB MANAGER, the home interface be.telenet.sso.servicelayer.ebiz.ManagerHome must extend the javax.ejb.EJBHome interface.
ERROR: ejbc found errors
Thanks
Amit

If you are looking a local interface up through JNDI, try using the "java:comp/env" namespace. Also, if you post these questions here about EJB, say what vendor you are using because this stuff is pretty new and there will be differences/bugs/etc.

How to create a query in your session facade.

Please help me
My code is as follows
public List<TrpSprojects> getProjectNotAssignedToUser(TrpSemployees employee) {
    List proassignements = this.findProjectAssingmentForUser(employee);
    System.out.println("Size of project assignment list :"+proassignements.size());
    List projectIdAssigned = new ArrayList();
    String queryText = "Select o from Trp_Sprojects o where o.project_id not in (";
    for(Iterator proassign = proassignements.iterator();proassign.hasNext();)
        queryText = queryText+((TrpSprojectAssignment) proassign.next()).getTrpSprojects().getProjectId().toString()+",";
    System.out.println(queryText.substring(0,queryText.length()-1)+");");
   String querytoBeExecuted = queryText.substring(0,queryText.length()-1)+")";
    System.out.println("The query to be executed: "+ queryText);
     Query q = em.createNativeQuery(querytoBeExecuted, TrpSprojects.class);
     return q.getResultList();
    }In my session facade i have to create a query that will return the projects that have not been assigned to the user.
When i display the queryText it is as follows:
Select o from Trp_Sprojects o where o.project_id not in (2,1,4,5,12,14,15,16,17,18,20,6,7,8,9,10,11,13,22,19,3,26,21,23)when am executing the query i am getting exception ...
Can anyone help me please . I have not defined this query in the TrpSprojects Class.
Part of my exception its too long am only putting a part
Feb 11, 2008 12:37:07 PM oracle.j2ee.rmi.RMIMessages EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER
WARNING: Exception returned by remote server: {0}
javax.ejb.EJBException: Exception [TOPLINK-4002] (Oracle TopLink Essentials - 2006.8 (Build 060829)): oracle.toplink.essentials.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: ORA-00904: "O": invalid identifier
Error Code: 904
Call:Select o from Trp_Sprojects o where o.project_id not in (2,1,4,5,12,14,15,16,17,18,20,6,7,8,9,10,11,13,22,19,3,26,21,23)
Query:ReadAllQuery(org.trp.model.TrpSprojects); nested exception is:
     Exception [TOPLINK-4002] (Oracle TopLink Essentials - 2006.8 (Build 060829)): oracle.toplink.essentials.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: ORA-00904: "O": invalid identifier
Error Code: 904
Call:Select o from Trp_Sprojects o where o.project_id not in (2,1,4,5,12,14,15,16,17,18,20,6,7,8,9,10,11,13,22,19,3,26,21,23)
Query:ReadAllQuery(org.trp.model.TrpSprojects); nested exception is: oracle.oc4j.rmi.OracleRemoteException: Exception [TOPLINK-4002] (Oracle TopLink Essentials - 2006.8 (Build 060829)): oracle.toplink.essentials.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: ORA-00904: "O": invalid identifier
Error Code: 904
Call:Select o from Trp_Sprojects o where o.project_id not in (2,1,4,5,12,14,15,16,17,18,20,6,7,8,9,10,11,13,22,19,3,26,21,23)
Query:ReadAllQuery(org.trp.model.TrpSprojects); nested exception is:
     Exception [TOPLINK-4002] (Oracle TopLink Essentials - 2006.8 (Build 060829)): oracle.toplink.essentials.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: ORA-00904: "O": invalid identifier
Error Code: 904
oracle.oc4j.rmi.OracleRemoteException: Exception [TOPLINK-4002] (Oracle TopLink Essentials - 2006.8 (Build 060829)): oracle.toplink.essentials.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: ORA-00904: "O": invalid identifier
Error Code: 904
Call:Select o from Trp_Sprojects o where o.project_id not in (2,1,4,5,12,14,15,16,17,18,20,6,7,8,9,10,11,13,22,19,3,26,21,23)
Query:ReadAllQuery(org.trp.model.TrpSprojects)
     at com.evermind.server.ejb.EJBUtils.getUserException(EJBUtils.java:346)
     at com.evermind.server.ejb.interceptor.system.AbstractTxInterceptor.convertAndHandleMethodException(AbstractTxInterceptor.java:69)
     at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
     at SCTimeReport_RemoteProxy_4p6ko7e.getProjectIdAssignedToUser(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.rmi.RmiMethodCall.run(RmiMethodCall.java:53)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)Regards
Lutchumaya

Thanks for your help Frank.
But when i display my query to be executed by the entityManager it is like that
Select o from Trp_Sprojects o where o.project_id not in (2,1,4,5,12,14,15,16,17,18,20,6,7,8,9,10,11,13,22,19,3,26,21,23)
Regards
Lutchumaya

"Edit Session Facade" in JDeveloper

Similar Messages

Maybe you are looking for