A non-trivial log4cxx tutorial
Here we only discuss how to change the log4cxx properties on the fly.

1. Traverse current loggers list

    LoggerList curLoggerList;
    curLoggerList =  Logger::getRootLogger()->getLoggerRepository()->getCurrentLoggers();
    LoggerList::iterator i;
    i = curLoggerList.begin();
    while (i!=curLoggerList.end())
    {
        i->p->setLevel(log4cxx::Level::DEBUG); //i->p is the LoggerPtr
        i++;
    }                                     
    Logger::getRootLogger()->setLevel(log4cxx::Level::DEBUG);

2. create Layout, Appender and change conversion pattern on the fly

    static const char patternOne[] = "%r [%t] %-5p %c- %m%n %x%n";
    //create PatternLayout with pattern patternOne

    PatternLayoutPtr myLayoutPtr;
    ConsoleAppenderPtr myConsoleAppenderPtr;

    ACE_NEW_RETURN(myLayoutPtr, PatternLayout, -1);
    myLayoutPtr->setConversionPattern(patternOne); 

    //create ConsoleAppender with layout myLayoutPtr
    ACE_NEW_RETURN(myConsoleAppenderPtr, ConsoleAppender, -1);
    myConsoleAppenderPtr->setLayout(myLayoutPtr);

3. Create FileAppender on the fly

    typedef log4cxx::helpers::ObjectPtrT 
       RollingFileAppenderPtr;

    RollingFileAppenderPtr myRollingFileAppenderPtr;

    LoggerPtr rootLogger = Logger::getRootLogger();
    
    ACE_NEW_RETURN(myRollingFileAppenderPtr, RollingFileAppender, -1); 
    
    myRollingFileAppenderPtr->setFile("myLogFile_server.log");
    myRollingFileAppenderPtr->setMaxBackupIndex( 10 );
    myRollingFileAppenderPtr->setMaxFileSize( "10MB" );
    myRollingFileAppenderPtr->setLayout(myFileLayoutPtr);
    myRollingFileAppenderPtr->activateOptions();
    rootLogger->addAppender( myRollingFileAppenderPtr );

4. Use NDC

    char hostname [MAXHOSTNAMELEN+1];
    ACE_OS::hostname (hostname, sizeof (hostname));
    int port = 8888;

    { //since we need to clean the content in oss, we set it as local
       log4cxx::StringBuffer oss;
       oss << "[" << hostname << ":" << port << "]" << 
           __FILE__ <<  ":" << __LINE__ << "\n"; 
       log4cxx::NDC::push(oss.str());
    }
    LOG4CXX_DEBUG(rootLogger, _T("starting blocking connect"));
    log4cxx::NDC::pop();

- posted by Pop @ 5:31 PM

 
UML learning

- posted by Pop @ 4:56 PM

 
Auto completion in windows Command Line

- posted by Pop @ 6:29 PM

 
An ACE online tutorial

- posted by Pop @ 11:09 PM

 
Tricks in Resource Compiler or Compatible preprocessor

- posted by Pop @ 4:10 PM

 
CVS branch or date

cvs co -r TUNDRA_DROP1 soam

Check out by date: for example 2006-01-18

cvs co -D20060118 soam

cvs up -D20060118 soam

- posted by Pop @ 4:34 PM

 
HLD document creation and adding
For HLD, add to
/design/symphony/tundra/soa/design

cvs add -kb

-kb for binary format

1. find correspondent FS
2. finish HLD
3. start up implementation
4. testing/debugging

- posted by Pop @ 12:22 PM

 
XSharp Schema Draft

- posted by Pop @ 7:36 PM

 
XML Schema Design and XSharp

- posted by Pop @ 11:04 PM

 
Sed in MKS is weird

- posted by Pop @ 11:22 PM

 
How to create Web Service in Sun App Server
1. File list
Under the project directory, you prepare
build.xml -----> makefile for asant
build.properties ----> customized properties
targets.xml ----> common targets for j2ee web services
src/${interface}.java ----> definition of the interface
src/${implementation}.java ----> implementation of the interface
conf/config-interface.xml ---> used by wscompile
conf/admin-password.txt ---> for asadmin command
lib/ ---> put any library you need
build/ ---> store the compiled class files

2. In build.properties fileSet the following properties
j2ee.home=C:/Sun/AppServer note:using slash "/" for path
project.home=project-path
project.name=project-name

3. run "asant build-service


4. start Sun App Server by running "asadmin start-domain domain1"


5. To deploy by GUI tool by running "deploytool"

• choose "new"-->"web component"
  
• create module file project-directory/project-name.war
• edit contents: select your project directory, click Add
• in Context root field, enter your context root; the URI for the service will look like http://localhost:8080/context-root/alias
• use the default values for the following steps
• add alias for implementation: select implementation component then Tab "Aliases", add alias; then select Tab "endpoint address", choose alias
• save and deploy

6. For asant (command line)

• extract from the generated WAR file \WEB-INF\webservice.xml, \WEB-INF\sun-web.xml, \WEB-INF\web.xml to project-directory/conf


• then run “asant create-war” to update the WAR by asant


• run “asant deploy-war” to deploy the WAR file

A sample template zip file
http://rommel.cs.binghamton.edu/~pliu/Template-SunContainer.zip
- posted by Pop @ 11:50 AM

 
C++ source
C++ columns
http://www.artima.com/cppsource/index.html

C++ library cross reference
http://www.cplusplus.com/ref/

IBM C++ standard Library reference
ftp://ftp.software.ibm.com/software/os390/czos/standlib_1017.pdf
- posted by Pop @ 10:13 AM

 
Document-based Web Services, My comment
Quoted from
http://java.sun.com/developer/technicalArticles/xml/jaxrpcpatterns2/

The strategies associated with the Document-Based Web Services pattern examined here are:

1. Using XML in the SOAP Body
2. Using a String in the SOAP Body
3. Using base64Encoded or raw bytes in the SOAP body
4. Using the xsd:any Element in WSDL
5. Using the xsd:anyType in WSDL

I have tried 2,3,4,5 before in my XSharp Project.

Pattern 1 is trivial. It is just the usage of extension of WSDL, analog to the "#include" instruction in C/C++ or "import" in Java/C#.

Pattern 2 uses String to hide the fact that this is XML string on the wire. It needs end user to validate the XML string.

Pattern 3 has no significant difference from Pattern 2. The only difference is the on-the-wire String is encoded in Base64. But Base64 is originally designed to encode binary type to String.

Pattern 4 will lead to the further XML parsing automatically since it is converted to XML element. It is end user's reponsibility to parse the incoming XML element snippet.

Pattern 5 is kind of dynamic parsing. In .NET, since every class has a root class "System.object", it is "System.object" that handles the XML snippet. In practice, we can cast this "System.object" to an object with specific class type. During the casting, XML parsing runtime system will try to match the XML to that object. But in Java world, it is handled the same as Pattern 4. Notice that in "RPC/Encoded" mode, Java will map the XML element to "Java.lang.object" at first, and try the type casting just like .NET.
- posted by Pop @ 7:44 AM