Until now whenever client jar is imported in OSB Jdeveloper for EJB transport, list of home and remote interfaces is populated.
However working with this client jar EJB 2.1, interface list is not
populated. I have checked the jar, it is valid and contains
interfaces. Also working fine with java code. I am getting:
Invalid Ref instance error in JDeveloper
In Eclipse OEPE, no error message. Not working here also.
What could be the issue?
This is how it looks in JDeveloper, getting Invalid Ref instance error
There seems to be some issue with the EJB Cient jar you are using.
To confirm try with some other client jar, I hope you will not get any issue with that.
Which version of Jdeveloper 12c are you using?
Thanks & Regards,
Tarun
Related
After changing the Java implementation from #WebService (javax.jws) to #Endpoint (Spring annotation) I lost testing link visible in Weblogic console inside the war application. But wsdl is available still after deployment. It is only about the link inside the WLS console.
Does anyone know if this is possible to fix to display it back in WLS console or at least maybe if you have experience with this maybe you know what are the dependencies which can lead to displaying that link (?WSDL) ?
regards
E.
Expected solution is to display testing link in Weblogic console back.
I already checked the descriptor (web.xml) if it is compatible with Weblogic 12 (it's ok). Normally with #WebService annotation it works (displayed in WLS console as a WSDL testing link).
I am using glassfish 3.1 and configure Oracle Datasource. However, I tried to Ping from glassfish admin console, but hitting an error with oracle.jdbc.pool.OracleDataSource not found. What could be the Issue?
As per http://docs.oracle.com/cd/E18930_01/html/821-2432/gkyan.html - you need to insert Oracle jdbc driver manually as it does not come bundled with Glassfish 3.1 installation. Just put the required jar into domain/lib directory.
Driver jar is downloadable from http://www.oracle.com/technetwork/database/features/jdbc/index-091264.html
I'm trying to include the SQL Server Driver in a Spring MVC project.
I'm using STS 3.6.2 which has a embedded version of Maven
How can I accomplish this? I tried to include the driver via Add External Jar but it didn't work. And I read that since I'm using an embedded version I can't use the console
I have created a sample EJB Project and a Dynamic project.
Now I have used the interface of EJBProject inside the client project so that it could use the proxy object and in turn interact with the bean to fetch the data.
However, I have created a blank EAP project and have added both the EJBProject and the DynamicWebproject. Now according to the concept I have bundled the EJB and Web inside EAp and have deployed on JBoss Server, so technically if I hit the jboss url then it should direct me to welcome page of client. However I am not getting as expected.
Am I doing any mistake in deploying it??
When you will deploy EAP then a target must be generated in that target you will have application.xml in that you will have context root now use this context root in your url foreg: localhost:yourport/yourprojectname/contextroot
this must take you to your page
The TOMCAT server is using an Oracle 9G ojdbc14 driver to its jndi connections in the /common/lib folder.
My web application uses Maven + Spring and I'm getting the dataSource using Spring jndi features.
I'm trying to bypass TOMCAT old ojdbc14 driver with a newer one (ojdbc14 10.2.0.4.0).
I've tried putting the jars in the WEB-INF/lib folder as a project dependency, but it doesn't work the application keeps using the old oracle driver that is in the TOMCAT folder.
I'm trying to bypass the TOMCAT oracle driver because I cannot update it to the newest version because there are lots of other projects using it.
Does anyone have a clue?
This won't work, Tomcat won't use the JDBC driver of your webapp to create a connection pool. In other words, you'll have to either replace the version in common/lib or to use a standalone connection pool at the application level.