JDev 10.1.3: Reformat sources.

Hi.
When I reforamt java sources all ok. But when I reformat xml or jspx sources, jdev remove blank lines. Which settings I can use, that jdev did not remove blank lines in xml sources?

Any chance that we can get the specific problematic files for the reformatting?
You can send it to me at shay . shmeltzer@ oracle.com
(remove the spaces).
Shay

Similar Messages

Jdev 10.1.2 data-sources.xml weirdness

Hi, I am using JDeveloper 10.1.2 with all the updates.
My project is a web service. I'm getting a database connection like this:
InitialContext ic = new InitialContext();
DataSource ods = (DataSource) ic.lookup("jdbc/PeopleSoftPooledDS");
Connection conn = ods.getConnection();I find that I cannot do "Oracle" things with the connection; in debug I find out that its not an Oracle connection. Its com.evermind something. I'm trying to figure out why, and how to get an Oracle driver connection.
No data-sources.xml files under my jdeveloper install reference the evermind driver now. Yet I'm still getting an evermind connection.
I can't seem to figure out what is going on
Dennis S

The class name is defined as oracle.jdbc.pool.OracleConnectionCacheImpl. The connection driver is defined as oracle.jdbc.driver.OracleDriver.
By not being able to do "Oracle" things with the connection I mean method calls. I did a stmt.execute() and couldn't do a stmt.getCursor() because stmt wasn't an Oracle object.

How Get JDev to Omit data-sources.xml from every .war deployment

I want a global data-sources.xml file to be used for all deployments. I do not want a copy of my standard data-sources.xml file to be included in every single deployment. I want my global data-sources.xml file to reside in the standard J2EE location of:
oc4j_home/oc4j_instance_name/j2ee/config/data-sources.xml
JDeveloper, for whatever reason, includes a data-sources.xml into every .war file. How do we configure JDev to omit the data-sources.xml? How do we set up JDev to automatically configure the .xml files (orion-application.xml, application.xml, etc) to use the global data-sources.xml? I do not want to manually do this for every deployment.
I've been trying hard to find the answer in JDev online help and other OAS manuals. I read everywhere that I can have a "global" data-sources.xml, but I find no way to easily configure JDeveloper to do it this way.
I would be grateful for you insights/help.
thanks
-Paul Janda

I found the answer:
In JDeveloper, Go to Tools | Preferences
Select Deployment
Uncheck the option for "Bundle default data-sources.xml during deployment"
Upon the next generation of the .ear or .war file (including the next deployment), data-sources.xml will be omitted.
-paul janda

How to add a data-source.xml to the project to config DB connections and to be SCM'ed

I'd like to explicitly manage a data-sources.xml for my JSP + BC4J project.
Any helps on getting the released Jdev to add a data-source.xml that would then
be what the .ear deploys to OC4J?
Thanks, curt

I have a JSP + BC4J project:
So far my naive experiments to explicitely add data-sources.xml to a
project that is picked up by the deploy to .ear step and put in the
root of the .ear have failed.
Is this one of those gaps like the orion-application.xml file, that has no
solution at present?
Or is the back-door via adding an EJB component to my project, then deleting it??
Thanks, curt

Data-sources.xml

Hi All,
In the 'Connections-Navigator' I have made some database connections, when I deploy my application JDev creates a file data-sources.xml ant put it under META-INF directory of ear file. But I am not able to see this file anywhere in my source tree. Is there any way to see and edit this file? Actually I want to enter some pooling related options in this file.
Thanks,
Vinod

hi Vinod
In my "SomeApp" workspace it appears in the same directory as SomeApp.jws, named SomeApp-data-sources.xml
see also:
"JDev 10g : no control over data-sources.xml"
JDev 10g : no control over data-sources.xml
success
Jan Vervecken

How to force Jdeveloper to preserve existing sources directory structure?

Hi all,
I have JDeveloper 9.0.3.4 which I have to use.
I tried to import to project from existing sources and I tried to keep existing sources
directory structure by selection option "Scan source paths to determine project contents" which should (according to documentation) preserve existing directory structure and show it in the Navigator.
But instead I get always (Jdev default?) directory structure:
Sources
HTML Sources
Miscelaneous Files
I changed default settings for Input path in project settings and for default project settings but still I get this Jdev structure.
Is there a way to force JDeveloper to preserve the directory structure of sources it imports from?
Many thanks,
Mile

I'd like to be able to specify the default project directory structure in 10g as well. For example I would like to have under the project root:
build.xml
src\
generatedsrc\
config\
resources\
build\
deploy\
Generating an ant build.xml using the wizard should also take into account the directory structure being used by the JDeveloper project build. I don't see why I should have to modify the build.xml file at all.

Testing data sources in oc4j-ra.xml

Is there a way to test the data sources in oc4j-ra.xml from the server? I have a server sitting inside a DMZ that has access back to internal databases. The DMZ has its own set of IP addresses and it has specific openings to the internal resources it needs. that is why i would like to test the connections from the server.

Hi,
You're right. I've downloaded JDev 10.1.2.
The working version:
<data-source name="jdev-connection-myconn"
               class="com.evermind.sql.DriverManagerDataSource"
               location="jdbc/myconnCoreDS" xa-location="jdbc/xa/myconnXADS"
               ejb-location="jdbc/myconnDS"
               pooled-location="jdbc/myconnPooledDS"
               connection-driver="oracle.jdbc.driver.OracleDriver"
               username="xxx" password="yyy"
               url="jdbc:oracle:thin:@localhost:1521:mysid"
               inactivity-timeout="30"/>and:
DataSource ds = (DataSource) getInitialContext().lookup("jdbc/myconnDS");JDev generates the correct data-sources.xml, if you create the data-sources.xml with its wizard (New Galery/General/DeploymentDescriptors/data-sources.xml). Then you can see in the properties dialog, the default setting is: Auto update data-sources.xml when running or deploying to OC4J.
So when you first run the embedded OC4J, your data-sources.xml file will be updated with your connections.
I read these useful things in Olaf Heimburger's blog :) (OC4J: Configuring DataSources, 2007-05-03)
Regards,
Kati

Jdev support with PVCS Version control system

Hi,
Is there any JDev plugin available for PVCS source control system.
We have to use PVCS version control system for our SOA composites. If there is no plugin available, what is the approach commonly used for these scenarios.
Thanks for your response.

Which JDev version do you use?
AFAIK there is no extension for PVCS available for 11g (check http://www.oracle.com/ocom/groups/public/@otn/documents/webcontent/131167.xml).
Anyway if you have an external tool which lets you work with PVCS you can use it outside of jdev without a problem. Depending on the interface you might be able to do some kind of integration into jdev using the 'External Tools...' interface.
Timo

HOWTO: Using a BC4J Application Module in an Stateless EJB Session Bean

HOWTO: Using a BC4J Application Module in an Stateless EJB Session Bean
by Steve Muench
Overview
BC4J provides automatic facilities for deploying any application module as a stateful EJB session bean. If you want to leverage the features of your BC4J application module from a stateless EJB session bean, it's not automatic but it is straightforward to implement. This howto article explains the details.
For our example, we will create a stateless EJB session bean that uses a container-managed transaction. To keep things simple, let's assume the session bean has a single public method on its remote interface named createDepartment() with the following signature:
public void createDepartment(int id, String name, String loc) throws AppException
AppException is an example of an application-specific exception that our method will throw if any problems arise during its execution.The goal of this article is to illustrate how to use the BC4J application module named com.example.hr.HRApp as part of the implementation of this createDepartment method on our stateless enterprise bean. Let's assume that the HRApp application module has a view object member named Departments, based on the com.example.hr.DeptView view object, based on the familiar DEPT table and related to the com.example.hr.Dept entity object so our view can be updateable.
Creating the Stateless Session Bean
We can start by using the JDeveloper Enterprise Bean wizard to create a new stateless session bean called StatelessSampleEJB implemented by:[list][*]com.example.StatelessSampleEJBBean (Bean class)[*]com.example.StatelessSampleEJBHome (Home interface)[*]com.example.StatelessSampleEJB (Remote interface)[list]
We then use the EJB Class Editor to add the createDepartment method to the remote interface of StatelessSampleEJB with the signature above. We edit the remote interface to make sure that it also reflects that the createDepartment method thows the AppException like this:
package com.example;
import javax.ejb.EJBObject;
import java.rmi.RemoteException;
public interface StatelessSampleEJB extends EJBObject {
void createDepartment(int id, String name, String loc)
throws RemoteException,AppException;
}Before we start adding BC4J into the picture for our implementation, our StatelessSampleEJBBean class looks like this:
package com.example;
import javax.ejb.SessionBean;
import javax.ejb.SessionContext;
public class StatelessSampleEJBBean implements SessionBean {
public void ejbCreate(){}
public void ejbActivate(){}
public void ejbPassivate(){}
public void ejbRemove(){}
public void setSessionContext(SessionContext ctx){
public void createDepartment(int id, String name, String loc)
throws AppException {
    // TODO: Implement method here
}We can double-click on the ejb-jar.xml file in our project to see the XML deployment descriptor for the bean we just created:
<ejb-jar>
   <enterprise-beans>
      <session>
         <description>Session Bean ( Stateless )</description>
         <display-name>StatelessSampleEJB</display-name>
         <ejb-name>StatelessSampleEJB</ejb-name>
         <home>com.example.StatelessSampleEJBHome</home>
         <remote>com.example.StatelessSampleEJB</remote>
         <ejb-class>com.example.StatelessSampleEJBBean</ejb-class>
         <session-type>Stateless</session-type>
         <transaction-type>Container</transaction-type>
      </session>
   </enterprise-beans>
</ejb-jar>We need to add the extra <assembly-descriptor> section in this file to indicate that the createDepartment method will require a transaction. After this edit, the ejb-jar.xml file looks like this:
<ejb-jar>
   <enterprise-beans>
      <session>
         <description>Session Bean ( Stateless )</description>
         <display-name>StatelessSampleEJB</display-name>
         <ejb-name>StatelessSampleEJB</ejb-name>
         <home>com.example.StatelessSampleEJBHome</home>
         <remote>com.example.StatelessSampleEJB</remote>
         <ejb-class>com.example.StatelessSampleEJBBean</ejb-class>
         <session-type>Stateless</session-type>
         <transaction-type>Container</transaction-type>
      </session>
   </enterprise-beans>
   <assembly-descriptor>
      <container-transaction>
         <method>
            <ejb-name>StatelessSampleEJB</ejb-name>
            <method-name>createDepartment</method-name>
            <method-params>
               <method-param>int</method-param>
               <method-param>java.lang.String</method-param>
               <method-param>java.lang.String</method-param>
            </method-params>
         </method>
         <trans-attribute>Required</trans-attribute>
      </container-transaction>
   </assembly-descriptor>
</ejb-jar>
Aggregating a BC4J Application Module
With the EJB aspects of our bean setup, we can proceed to implementing the BC4J application module aggregation.
The first thing we do is add private variables to hold the EJB SessionContext and the instance of the aggregated BC4J ApplicationModule, like this:
// Place to hold onto the aggregated appmodule instance
transient private ApplicationModule _am = null;
// Remember the SessionContext that the EJB container provides us
private           SessionContext    _ctx = null;and we modify the default, empty implementation of the setSessionContext() method to remember the session context like this:
public void setSessionContext(SessionContext ctx){ _ctx = ctx; }We add additional constants that hold the names of the J2EE datasource that we want BC4J to use, as well as the fully-qualified name of the BC4J application module that we'll be aggregating:
// JNDI resource name for the J2EE datasource to use
private static final String DATASOURCE = "jdbc/OracleCoreDS";
// Fully-qualified BC4J application module name to aggregate
private static final String APPMODNAME = "com.example.hr.HRApp";We expand the now-empty ejbCreate() and ejbRemove() methods to create and destory the aggregated instance of the BC4J application module that we'll use for the lifetime of the stateless session bean. When we're done, ejbCreate() it looks like this:
public void ejbCreate() throws CreateException {
try {
    // Setup a hashtable of environment parameters for JNDI initial context
    Hashtable env = new Hashtable();
    env.put(JboContext.INITIAL_CONTEXT_FACTORY,JboContext.JBO_CONTEXT_FACTORY);
    // NOTE: we want to use the BC4J app module in local mode as a simple Java class!
    env.put(JboContext.DEPLOY_PLATFORM, JboContext.PLATFORM_LOCAL);
    env.put(PropertyConstants.INTERNAL_CONNECTION_PARAMS,DATASOURCE);
    // Create an initial context, using this hashtable of environment params
    InitialContext ic = new InitialContext(env);
    // Lookup a home interface for the application module
    ApplicationModuleHome home = (ApplicationModuleHome)ic.lookup(APPMODNAME);
    // Using the home, create the instance of the appmodule we'll use
    _am = home.create();
    // Register the BC4J factory to handle EJB container-managed transactions
    registerContainerManagedTransactionHandlerFactory();
catch(Exception ex) {
     ex.printStackTrace();
    throw new CreateException(ex.getMessage());
}and ejbRemove() looks like this:
public void ejbRemove() {
try {
    // Cleanup any appmodule resources before getting shutdown
    _am.remove();
catch(JboException ex) { /* Ignore */ }
}The helper method named reigsterContainerManagedTransactionHandlerFactory() looks like this:
private void registerContainerManagedTransactionHandlerFactory() {
SessionImpl session = (SessionImpl)_am.getSession();
session.setTransactionHandlerFactory(
    new TransactionHandlerFactory() {
      public TransactionHandler createTransactionHandler() {
        return new ContainerManagedTxnHandlerImpl();
      public JTATransactionHandler createJTATransactionHandler() {
        return new ContainerManagedTxnHandlerImpl();
}The last detail is to use the BC4J appmodule to implement the createDepartment() method. It ends up looking like this:
public void createDepartment(int id, String name, String loc)
throws AppException {
try {
    // Connect the AM to the datasource we want to use for the duration
    // of this single method call.
    _am.getTransaction().connectToDataSource(null,DATASOURCE,false);
    // Use the "Departments" view object member of this AM
    ViewObject departments = _am.findViewObject("Departments");
    // Create a new row in this view object.
    Row newDept = departments.createRow();
    // Populate the attributes from the parameter arguments.
    newDept.setAttribute("Deptno", new Number(id));
    newDept.setAttribute("Dname", name);
    newDept.setAttribute("Loc", loc);
    // Add the new row to the view object's default rowset
    departments.insertRow(newDept);
    // Post all changes in the AM, but we don't commit them. The EJB
    // container managed transaction handles the commit.
    _am.getTransaction().postChanges();
catch(JboException ex) {
    // To be good EJB Container-Managed Transaction "citizens" we have
    // to mark the transaction as needing a rollback if there are problems
    _ctx.setRollbackOnly();
    throw new AppException("Error creating dept "+ id +"\n"+ex.getMessage());
finally {
    try {
      // Disconnect the AM from the datasource we're using
      _am.getTransaction().disconnect();
    catch(Exception ex) { /* Ignore */ }
Building a Test Client
With the EJB-Tier work done, we can build a sample client program to test this new stateless EJB Session Bean by selecting the bean in the Oracle9i JDeveloper IDE and choosing "Create Sample Java Client" from the right-mouse menu.
When the "Sample EJB Client Details" dialog appears, we take the defaults of connecting to embedded OC4J container. Clicking the (OK) button generates the following test class:
import java.util.Hashtable;
import javax.naming.Context;
import javax.naming.InitialContext;
import com.example.StatelessSampleEJB;
import com.example.StatelessSampleEJBHome;
public class SampleStatelessSampleEJBClient {
public static void main(String [] args) {
    SampleStatelessSampleEJBClient sampleStatelessSampleEJBClient =
       new SampleStatelessSampleEJBClient();
    try {
      Hashtable env = new Hashtable();
      env.put(Context.INITIAL_CONTEXT_FACTORY,
              "com.evermind.server.rmi.RMIInitialContextFactory");
      env.put(Context.SECURITY_PRINCIPAL, "admin");
      env.put(Context.SECURITY_CREDENTIALS, "welcome");
      env.put(Context.PROVIDER_URL,
              "ormi://localhost:23891/current-workspace-app");
      Context ctx = new InitialContext(env);
      StatelessSampleEJBHome statelessSampleEJBHome =
           (StatelessSampleEJBHome)ctx.lookup("StatelessSampleEJB");
      StatelessSampleEJB statelessSampleEJB;
      // Use one of the create() methods below to create a new instance
      // statelessSampleEJB = statelessSampleEJBHome.create();
      // Call any of the Remote methods below to access the EJB
      // statelessSampleEJB.createDepartment( int id, java.lang.String name, java.lang.String loc );
    catch(Throwable ex) {
      ex.printStackTrace();
}We uncomment the call to the create() method and add a few calls to the createDepartment() method so that the body of the test program now looks like this:
// Use one of the create() methods below to create a new instance
statelessSampleEJB = statelessSampleEJBHome.create();
// Call any of the Remote methods below to access the EJB
statelessSampleEJB.createDepartment( 13, "Test1","Loc1");
System.out.println("Created department 13");
statelessSampleEJB.createDepartment( 14, "Test2","Loc2");
System.out.println("Created department 14");
try {
// Try setting a department id that is too large!
statelessSampleEJB.createDepartment( 23456, "Test3","Loc3");
catch (AppException ax) {
System.err.println("AppException: "+ax.getMessage());
}Before we can successfully run our SampleStatelessSampleEJBClient we need to first run the EJB bean that the client will try to connect to. Since Oracle9i JDeveloper supports local running and debugging of the EJB-Tier without doing through a full J2EE deployment step, to accomplish this prerequisite step we just need to right-mouse on the StatelessSampleEJB node in the System Navigator and select "Run". This starts up the embedded OC4J instance and runs the EJB right out of the current out path.Finally, we can run the SampleStatelessSampleEJBClient, and see the output of the test program in the JDeveloper log window:
Created department 13
Created department 14
AppException: Error creating dept 23456
JBO-27010: Attribute set with value 23456 for Deptno in Dept has invalid precision/scale
Troubleshooting
One error that might arise while running the example is that the database connection information in your data-sources.xml for the jdbc/OracleCoreDS datasource does not correspond to the database you are trying to test against. If this happens, then double-check the file .\jdev\system\oc4j-config\data-sources.xml under the JDeveloper installation home directory to make sure that the url value provided is what you expect. For example, to work against a local Oracle database running on your current machine, listening on port 1521, with SID of ORCL, you would edit this file to have an entry like this for jdbc/OracleCoreDS :
<data-source
    class="com.evermind.sql.DriverManagerDataSource"
    name="OracleDS"
    location="jdbc/OracleCoreDS"
    xa-location="jdbc/xa/OracleXADS"
    ejb-location="jdbc/OracleDS"
    connection-driver="oracle.jdbc.driver.OracleDriver"
    username="scott"
    password="tiger"
    url="jdbc:oracle:thin:@localhost:1521:ORCL"
    inactivity-timeout="30"
/>This is the data-sources.xml file that gets used by the embedded OC4J instance running in JDeveloper.
Conclusion
Hopefully this article has illustrated that it is straightforward to utilize the full power of BC4J in local mode as part of your EJB Stateless Session Beans using container-managed transaction. This example illustrated a single createDepartment method in the enterprise bean, but by replicating the application module interaction code that we've illustrated in createDepartment, any number of methods in your stateless session bean can use the aggregated application module instance created in the ejbCreate() method.
Code Listing
The full code listing for the SampleStatelessEJB bean implementation class looks like this:
* StatelessSampleEJB
* Illustrates how to use an aggregated BC4J application module
* in local mode as part of the implementation of a stateless
* EJB session bean using container-managed transaction.
* HISTORY
* smuench/dmutreja 14-FEB-2002 Created
package com.example;
import oracle.jbo.*;
import oracle.jbo.server.*;
import javax.ejb.*;
import oracle.jbo.domain.Number;
import oracle.jbo.common.PropertyConstants;
import java.util.Hashtable;
import javax.naming.InitialContext;
import oracle.jbo.server.ejb.ContainerManagedTxnHandlerImpl;
public class StatelessSampleEJBBean implements SessionBean {
// JNDI resource name for the J2EE datasource to use
private static final String DATASOURCE = "jdbc/OracleCoreDS";
// Fully-qualified BC4J application module name to aggregate
private static final String APPMODNAME = "com.example.hr.HRApp";
// Place to hold onto the aggregated appmodule instance
transient private ApplicationModule _am = null;
// Remember the SessionContext that the EJB container provides us
private           SessionContext    _ctx = null;
public void ejbCreate() throws CreateException {
    try {
      // Setup a hashtable of environment parameters for JNDI initial context
      Hashtable env = new Hashtable();
      env.put(JboContext.INITIAL_CONTEXT_FACTORY,JboContext.JBO_CONTEXT_FACTORY);
      env.put(JboContext.DEPLOY_PLATFORM, JboContext.PLATFORM_LOCAL);
      env.put(PropertyConstants.INTERNAL_CONNECTION_PARAMS,DATASOURCE);
      // Create an initial context, using this hashtable of environment params
      InitialContext ic = new InitialContext(env);
      // Lookup a home interface for the application module
      ApplicationModuleHome home = (ApplicationModuleHome)ic.lookup(APPMODNAME);
      // Using the home, create the instance of the appmodule we'll use
      _am = home.create();
      // Register the BC4J factory to handle EJB container-managed transactions
      registerContainerManagedTransactionHandlerFactory();
    catch(Exception ex) {
       ex.printStackTrace();
      throw new CreateException(ex.getMessage());
public void ejbActivate(){}
public void ejbPassivate(){}
public void ejbRemove(){}
public void setSessionContext(SessionContext ctx){ _ctx = ctx; }
public void createDepartment(int id, String name, String loc)
throws AppException {
    try {
      // Connect the AM to the datasource we want to use for the duration
      // of this single method call.
      _am.getTransaction().connectToDataSource(null,DATASOURCE,false);
      // Use the "Departments" view object member of this AM
      ViewObject departments = _am.findViewObject("Departments");
      // Create a new row in this view object.
      Row newDept = departments.createRow();
      // Populate the attributes from the parameter arguments.
      newDept.setAttribute("Deptno", new Number(id));
      newDept.setAttribute("Dname", name);
      newDept.setAttribute("Loc", loc);
      // Add the new row to the view object's default rowset
      departments.insertRow(newDept);
      // Post all changes in the AM, but we don't commit them. The EJB
      // container managed transaction handles the commit.
      _am.getTransaction().postChanges();
    catch(JboException ex) {
      // To be good EJB Container-Managed Transaction "citizens" we have
      // to mark the transaction as needing a rollback if there are problems
      _ctx.setRollbackOnly();
      throw new AppException("Error creating dept "+ id +\n"+ex.getMessage());
    finally {
      try {
        // Disconnect the AM from the datasource we're using
        _am.getTransaction().disconnect();
      catch(Exception ex) { /* Ignore */ }
private void registerContainerManagedTransactionHandlerFactory() {
    SessionImpl session = (SessionImpl)_am.getSession();
    session.setTransactionHandlerFactory(
      new TransactionHandlerFactory() {
        public TransactionHandler createTransactionHandler() {
          return new ContainerManagedTxnHandlerImpl();
        public JTATransactionHandler createJTATransactionHandler() {
          return new ContainerManagedTxnHandlerImpl();

Hi Steve, It4s me again;
About the question I made, I tried with a single assembly-descriptor tag and a single container-transaction tag in the deployment descriptor of the session bean and these were the results.
java.lang.NullPointerException
     void com.evermind.server.rmi.RMIConnection.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(java.lang.Throwable)
     java.lang.Object com.evermind.server.rmi.RMIConnection.invokeMethod(com.evermind.server.rmi.RMIContext, long, long, java.lang.reflect.Method, java.lang.Object[])
     java.lang.Object com.evermind.server.rmi.RemoteInvocationHandler.invoke(java.lang.Object, java.lang.reflect.Method, java.lang.Object[])
     java.lang.Object com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(java.lang.Object, java.lang.reflect.Method, java.lang.Object[])
     java.lang.Object com.evermind.server.ejb.StatelessSessionRemoteInvocationHandler.invoke(java.lang.Object, java.lang.reflect.Method, java.lang.Object[])
     void __Proxy1.modificaEnvoltura(java.lang.Integer, java.lang.Integer, java.lang.Integer, java.lang.Integer, java.lang.Integer, java.lang.Integer, java.lang.String)
     void SamplemdeController.envolturaControlEJBClient.main(java.lang.String[])
Then I tried with multiple assembly-descriptor tags each with a single container-transaction tag and the results were:
java.lang.NullPointerException
     void com.evermind.server.rmi.RMIConnection.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(java.lang.Throwable)
     java.lang.Object com.evermind.server.rmi.RMIConnection.invokeMethod(com.evermind.server.rmi.RMIContext, long, long, java.lang.reflect.Method, java.lang.Object[])
     java.lang.Object com.evermind.server.rmi.RemoteInvocationHandler.invoke(java.lang.Object, java.lang.reflect.Method, java.lang.Object[])
     java.lang.Object com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(java.lang.Object, java.lang.reflect.Method, java.lang.Object[])
     java.lang.Object com.evermind.server.ejb.StatelessSessionRemoteInvocationHandler.invoke(java.lang.Object, java.lang.reflect.Method, java.lang.Object[])
     void __Proxy1.modificaEnvoltura(java.lang.Integer, java.lang.Integer, java.lang.Integer, java.lang.Integer, java.lang.Integer, java.lang.Integer, java.lang.String)
     void SamplemdeController.envolturaControlEJBClient.main(java.lang.String[])
Finally I tried with a single assembly-descriptor and multiple container tags and the results were:
java.lang.NullPointerException
     void com.evermind.server.rmi.RMIConnection.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(java.lang.Throwable)
     java.lang.Object com.evermind.server.rmi.RMIConnection.invokeMethod(com.evermind.server.rmi.RMIContext, long, long, java.lang.reflect.Method, java.lang.Object[])
     java.lang.Object com.evermind.server.rmi.RemoteInvocationHandler.invoke(java.lang.Object, java.lang.reflect.Method, java.lang.Object[])
     java.lang.Object com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(java.lang.Object, java.lang.reflect.Method, java.lang.Object[])
     java.lang.Object com.evermind.server.ejb.StatelessSessionRemoteInvocationHandler.invoke(java.lang.Object, java.lang.reflect.Method, java.lang.Object[])
     void __Proxy1.modificaEnvoltura(java.lang.Integer, java.lang.Integer, java.lang.Integer, java.lang.Integer, java.lang.Integer, java.lang.Integer, java.lang.String)
     void SamplemdeController.envolturaControlEJBClient.main(java.lang.String[])
How can I make my Stateless Session bean work out?

Platform.runLater messes up my Thread.currentThread().getContextClassLoader()

Hi,
I have a plugin mechanism in my application. The plugins are defines by an interface and are loaded via URLClassLoader. A plugin can also have resources, loaded via ResourceBundle.getBundle.
Whenever a plugin's method is called, I do this, before it is called:
ClassLoader oldLoader = Thread.currentThread().getContextClassLoader();
Thread.currentThread().setContextClassLoader(pluginClassLoaders.get(pluginClass.cast(proxy)));
// Invoke plugin method
Thread.currentThread().setContextClassLoader(oldLoader);
The plugin methods are called in their own thread, that means, when I want to open a window I need to do it on the JavaFX Application Thread with Platform.runLater.
The problem is, that in the run method of the Platform.runLater, my Thread.currentThread().getContextClassLoader() is not my URLClassLoader but the Application Classloader.
Why I need this?
I don't want the plugin developer to always keep in mind, that he has to pass the correct class loader (of his classes) into the ResourceBundle.getBundle method.
Instead I thought I could rely on Thread.currentThread().getContextClassLoader(), which is set in the main application, to load the correct bundle.
It would work, but not if I load the bundle inside the JavaFX Application Thread (but which makes the most sense for UI development).
So my goal was to have a convenient method like:
String getResource(String bundle, String key)
return ResourceBundle.getBundle(bundle).getString(key), Thread.currentThread().getContextClassLoader());
To avoid passing the classloader every time.
Any ideas on this?

OK, found the problem.
In data-sources.xml, there is a connection pool and a managed-data-source settings. If I set the data source in there - it works!! Seems these XML tags take preference above the datasource tag.
This is how the data-sources.xml now looks that's been working:
<?xml version = '1.0' standalone = 'yes'?>
<data-sources xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/data-sources-10_1.xsd" schema-major-version="10" schema-minor-version="1">
<connection-pool name="jdev-connection-pool-MYDB">
<connection-factory factory-class="com.mysql.jdbc.Driver" user="henkie" password="->DataBase_User_recGxQcVfghwCszzy_gfsRgwOrxutL2l" url="jdbc:mysql://localhost/mydb"/>
</connection-pool>
<managed-data-source name="jdev-connection-managed-MYDB" jndi-name="jdbc/MYDBDS" connection-pool-name="jdev-connection-pool-MYDB"/>
</data-sources>

How to change the connection to MTP

Please advise how do I change the auto connection to MTP for Iphone 4.

Meaning you have created just the empty data-sources.xml and not configured any Connection Pool and DataSource in JDev?
In Oracle AS 10.1.3 you have two ways to do this:
1. Use JDev and configure the data-sources.xml (Context Menu -> Properties)
2. In Oracle AS: Select application -> Administration -> Services -> JDBC Resources -> Create Pool and Create DataSource
--olaf

Custom OA page (no personalization) translation from English to Spanish

Hi,
Problem Description:
I have a custom OA page with no personalizations. I need to translate it into "Latin American Spanish".
The steps I've done as of now are:
1. Ran the following command from D:\RUP6\jdevbin\jdev\bin>
XLIFFExtract D:\RUP6\jdevhome\jdev\myprojects\xx\oracle\apps\xxtmg\sl\webui\ExecutionPG.xml -includeSubpackages -mmd_dir D:\RUP6\jdevbin\jdev\lib\ext\jrad\config\mmd -root D:\RUP6\jdevhome\jdev\myprojects\ -xliff_dir D:\temp -source file -languages es-MX
2. Changed the <target></target> text to Spanish equivalent for all <trans-unit> tags
3. Ran the following command D:\RUP6\jdevbin\jdev\bin>
XLIFFImport -username apps -password apps -dbconnection "(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.139.249)(PORT=1527)))(CONNECT_DATA=(SID=CDEV35)(SERVER=DEDICATED)))" D:\RUP6\jdevhome\jdev\myprojects\xx\oracle\apps\xxtmg\sl\webui\ExecutionPG.xlf
4. Bounced the server
5. Selected "Latin American Spanish" and the bottom of the Oracle Apps Login page, and logged in.
Result:
The page shows the standard messages and prompts (like Search Region Go button etc) in Spanish, but my custom buttons, labels prompts are still in English.
I ran the following and I was able to see the translations correctly
BEGIN
jdr_utils.printtranslations ('/xx/oracle/apps/xxtmg/sl/webui/ExecutionPG', 'es-MX' );
END;
Output snippet:
<?xml version = '1.0' encoding = 'UTF-8'?>

<xliff version="1.0">
<file datatype="jdr" original="ExecutionPG" source-language="en-US" target-language="es-MX">
<body>
<trans-unit id=".xx.oracle.apps.xxtmg.sl.webui.ExecutionPG..BatchMeaning...prompt" translate="yes">
<source>Batch Status</source>
<target>Batch Estado</target>
</trans-unit>
<trans-unit id=".....
*R&D Done:*
I've gone through the following posts (some of them) in the forums, the dev guide and pretty much everything, but the translations are still not coming up on the page.
Re: How do we translate custom OAF pages to Multiple languages
Re: How do we translate custom OAF pages to Multiple languages
Re: How to devolop OAF page in Arabic
Any help is appreciated.
Thanks in advance
Regards,
Manoj

Hi Manoj,
Have you looked at the Internationlisation section of the dev guide, Ive not done transalations before but this seems to be what you are looking for.
In the Dev Guide search for Translating Personalizations Stored in MDS and click on Internationalization, then look at the language sections from there you will see a link for Translating Personalizations Stored in MDS. It seems to indicate you need to specify which OAF elements get translated, this is for personalisations but the concept should be the same.
Keith

Need to transfer data from one external hd to another hd

Hi, I need to transfer movies from one external hd to another external hd - destination hd is formatted currently as NTSC, source hd is formatted currently as Mac OSx extended (journalled).
I believe I need to transfer data across to different hd before I can reformat source hd to MSDOS - fat. Then after reformatting source hd I want to transfer data back from destination hd to source hd, to allow this to be viewed on TV & PC...
I have tried copying & dragging from one to another, doesn't work (on desktop, or in Finder).
Any help welcome, thank you.

When you reformat a drive it erases all data. You'll need to buy a second external drive.
Note: you can reformat a single partition on a drive. More info
I like the Seagate USB 3.0 Backup plus drives. Works on USB 2.0 ports. They come formatted for PC but easy to format in Disk Utility.
I don't recommend Western Digital because of the boot problem with some of their drives. LaCie makes good drives. All Mac formatted drives will cost more and it’s easy to reformat with Disk Utility. Do not use the software that comes with the drives. It’s recommended that you use Apple’s Disk Utility.
Prices vary but this gives you an idea of what you’ll find. As you notice the second and third TB is usually only $15 more per TB. It's not uncommon to find a 1T is more than the 2T
Current Amazon pricing:
Seagate Backup Plus 1 TB USB 3.0 $154.85 (used to be around $85.00)
Seagate Backup Plus 2 TB USB 3.0 $114.95 (used to be around $99.00
Seagate Backup Plus 3 TB USB 3.0 $129.90 (used to be around $115.00)
Locally, Best Buy seems to have the best prices.
Occassionally you'll find the 3T for $99 on sale.

Need a substitue for OrionPooledDataSource **ClassCastException **

Hi
we are getting a "null, java.lang.ClassCastException" when executing the following:
InitialContext ic = new InitialContext();
Object o = ic.lookup("jdbc/od_jdbc_connectionPooledDS");
OracleConnectionPoolDataSource ds = (OracleConnectionPoolDataSource) o;
even though my data-sources.xml in my
C:\JDev\jdev\mywork\DVDOrdering\DVDOrdering-data-sources.xml
contains the following
<data-source name="jdev-connection-od_jdbc_connection"
class="com.evermind.sql.DriverManagerDataSource"
location="jdbc/od_jdbc_connectionCoreDS"
xa-location="jdbc/xa/od_jdbc_connectionXADS"
ejb-location="jdbc/od_jdbc_connectionDS"
pooled-location="jdbc/od_jdbc_connectionPooledDS"
connection-driver="oracle.jdbc.driver.OracleDriver"
username="hr" password="hr"
url="jdbc:oracle:thin:@localhost:1521:Metadata" inactivity-timeout="30"/>
Thru the debugger i can see that o is of type OrionPooledDataSource
What package / class else can i cast the datasource to?
All the best
Jim

Thru the debugger i can see that o is of type OrionPooledDataSourceHm,,, this Orion thing must have faded away from oracle jdbc packages some time ago.
Anyway, you can probably cast it to javax.sql.ConnectionPoolDataSource. You can check it by reflection         Class orionDs = OrionPoolDataSource.class;
        Class[] ifs = orionDs.getInterfaces();
        for ( int i =0; i< ifs.length; i++) {
            System.out.println(ifs.getName());
System.out.println(orion.Ds.getSuperClass.getName());
What is better, if you use Jdeveloper, right click the object and choose "view Type Hierachy". You can see them all.

How to change the connection pool configuration on OC4J?

Hi everybody,
I am developing an application with JDeveloper which is running on an OC4J standalone server, we have 2 enviroments, the develop server and the server of the client, and the data base connection configurations are differents.
The problem is that if we try to deploy the application (we have deploy on the develop server) on the client server and try to change the connection pool configuration the application cannot connect to the data base, we need to re-build the project with the client connection pool configuration.
We tried to change the configuration on the enterprise manager of the OC4J, on "JDBC Resources" panel, and the test the connection is ok, but when try to access to the application we get an Exception. After that we try to do that changing the parameters from the datasources.xml file on the application, but the result is the same.
How can we change the DataBase configuration without re-build the project?
Thanks very much
Tony

Meaning you have created just the empty data-sources.xml and not configured any Connection Pool and DataSource in JDev?
In Oracle AS 10.1.3 you have two ways to do this:
1. Use JDev and configure the data-sources.xml (Context Menu -> Properties)
2. In Oracle AS: Select application -> Administration -> Services -> JDBC Resources -> Create Pool and Create DataSource
--olaf

JDev 10.1.3: Reformat sources.

Similar Messages

Maybe you are looking for