"load data infile * append into table "usermonth....."

And I received the following error message

"SQL*Loader-941: Error during describe of table "usermonth"
ORA-04043: object "usermonth" does not exist"

After one hour of despair and I realized by pure luck that you need to provide the name of the table with upper case, otherwise the utility is not able to find it. Quite strange, but at least I’m happy that now it works.

The link for the survey is here.

dispatcher : EventDispatcher
notifiers : Object
object : Object
propertyList : Array
proxyClass : Class
type : QName
uid:String

For the “type” property a fix was provided in Livecycle Data Services 3, but not for the others. So if you design your domain object and you plan to use Livecycle Data Services it’s a good idea to not use this reserved keywords as names for your properties.

The problem appears only if you like to use the proxy approach (not having the corresponding AS class included in the client SWF).

]]> http://cornelcreanga.com/2009/09/adobe-max-online/feed/ 1 http://cornelcreanga.com/2009/09/logging-everything-in-blazeds/ http://cornelcreanga.com/2009/09/logging-everything-in-blazeds/#comments Mon, 07 Sep 2009 11:57:12 +0000 cornel http://cornelcreanga.com/?p=129 When you create a Flex/Java project in Flex Builder the logging tag in the services-config.xml file looks like that:

    <logging>
        <target class="flex.messaging.log.ConsoleTarget" level="Error">
            <properties>
                <prefix>[BlazeDS] </prefix>
                <includeDate>false</includeDate>
                <includeTime>false</includeTime>
                <includeLevel>false</includeLevel>
                <includeCategory>false</includeCategory>
            </properties>
            <filters>
                <pattern>Endpoint.*</pattern>
                <pattern>Service.*</pattern>
                <pattern>Configuration</pattern>
            </filters>
        </target>
    </logging>

Unfortunately you can lose some important error messages with this <filters> configuration. That’s why its better to edit the file after creating the project and change the filters section to *

    <filters>
        <pattern>*</pattern>
    </filters>

In order to use it you should modify services-config.xml to use the newly created class (I created my class in the package flex.messaging.log):
<target class=”flex.messaging.log.JavaUtilLogTarget” level=”Debug”>

The source code is below:

import java.util.logging.Level;

public class JavaUtilLogTarget extends AbstractTarget{
public void logEvent(LogEvent event) {

  java.util.logging.Logger log =
    java.util.logging.Logger.getLogger(event.logger.getCategory());
  Level level;

  if (event.level >= LogEvent.ERROR)
    level = Level.SEVERE;
  else if (event.level >= LogEvent.WARN)
    level = Level.WARNING;
  else if (event.level >= LogEvent.INFO)
    level = Level.INFO;
  else if (event.level >= LogEvent.DEBUG)
    level = Level.FINE;
  else
    level = Level.FINEST;

  log.log(level,event.message,event.throwable);

  }
}