jjeong

1. If possible, the web application should be configured to use UTF-8 as the default encoding. Orion allows this to be specific in orion-web.xml, as the default-charset attribute. Weblogic requires a context parameter named weblogic.httpd.inputCharset. See your application server documentation for more details. If the application server of choice does not allow to set the default charset for all web-apps, then every page (including the decorators) will need to specify the content-type. This is done by specifying a page header tag like this:

<%@ page contentType="text/html; charset=utf-8"%>

Note that some older versions of Orion do not respect the contentType page directive in included pages, so to be on the safe side, this directive should be specified in ALL pages, not just the top level one (one could use an include).

2. The next step is to inform the browser that the page contents are of a specific character set. This is done by specifying a meta tag in the HEAD element of the html page, like this:

<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=utf-8">

3. The final step is informing SiteMesh's decorator mechanism that it should use a specific encoding other than the default. This is done by specifying an encoding attribute to the applyDecorator tag with the name of the encoding to use.

<page:applyDecorator name="form" encoding="utf-8">
    ...
</page:applyDecorator>

Decorator Tags

These tags are used to create page Decorators. A Decorator is typically built up from an HTML layout (or whatever is appropriate for the original page content-type) with these tags inserted to provide place-holders for the data from the original (undecorated) page.

For more details, see Building Decorators.

<decorator:head />

<decorator:body />

<decorator:title [ default="..." ] />

<decorator:getProperty property="..." [ default="..." ] [ writeEntireProperty="..." ]/>

<decorator:usePage id="..." />

Page Tags

The page tags, are used to apply decorators to inline or external content from within the current page.

<page:applyDecorator name="..." [ page="..." title="..." ] >
   .....
</page:applyDecorator>

<page:param name="..."> ... </page:param>

<action name="formTest" class="com.opensymphony.xwork.example.SampleAction" method="processSample">

String SUCCESS = "success";
String NONE    = "none";
String ERROR   = "error";
String INPUT   = "input";
String LOGIN   = "login";

<result name="success" type="dispatcher">
    <param name="location">/thank_you.jsp</param>
</result>

<result name="error" type="dispatcher">
    <param name="location">/error.jsp</param>
</result>

<action name="bar" class="myPackage.barAction">
  <result name="success" type="dispatcher">
    <param name="location">foo.jsp</param>
  </result>
</action>

<action name="bar" class="myPackage.barAction">
  <result name="success" type="dispatcher">foo.jsp</result>
</action>

<action name="bar" class="myPackage.barAction">
   <result>foo.jsp</result>
</action>

Result Types

Webwork provides several implementations of the com.opensymphony.xwork.Result interface to make web-based interactions with your actions simple. These result types include:

• Chain Result - used for Action Chaining
• Dispatcher Result - used for JSP integration
• FreeMarker Result - used for FreeMarker integration
• HttpHeader Result - used to control special HTTP behaviors
• JasperReports Result - used for JasperReports integration
• Redirect Result - used to redirect to another URL
• Redirect Action Result - used to redirect to another action
• Stream Result - used to stream an InputStream back to the browser (usually for file downloads)
• Velocity Result - used for Velocity integration
• XSL Result - used for XML/XSLT integration
• PlainText Result - used to display the raw content of a particular page (eg. jsp, html etc)
• Flash Result - used to store current action into http session such that it could be retrieved and push into the stack in subsequent request through FlashInterceptor.
• JSON Result - used to return back JSON response (application/json) by converting an instance of JSONObject obtained through action's property into JSON.  
  

<interceptors>
  <interceptor name="security" class="com.mycompany.security.SecurityInterceptor"/>
  <interceptor-stack name="defaultComponentStack">
    <interceptor-ref name="component"/>
    <interceptor-ref name="defaultStack"/>
  </interceptor-stack>
</interceptors>

<action name="VelocityCounter" class="com.opensymphony.xwork.example.counter.SimpleCounter">
   <result name="success">...</result>
   <interceptor-ref name="defaultComponentStack"/>
</action>

The document tree - Sibling

A sibling is an element that shares the same parent with another element. In the diagram below, the <li>'s are siblings as they all share the same parent - the <ul>.

같은 부모를 갖는 동일 level 의 node 들...

아래는 뽑아서 올려 놓은 거랍니다.. :)

REDIRECTION
       Before  a command is executed, its input and output may be redirected using a special notation inter-
       preted by the shell.  Redirection may also be used to open and close files for the current shell exe-
       cution environment.  The following redirection operators may precede or appear anywhere within a sim-
       ple command or may follow a command.  Redirections are processed in the order they appear, from  left
       to right.

       In  the  following descriptions, if the file descriptor number is omitted, and the first character of
       the redirection operator is <, the redirection refers to the standard input (file descriptor 0).   If
       the  first  character of the redirection operator is >, the redirection refers to the standard output
       (file descriptor 1).

       The word following the redirection operator in the following descriptions, unless otherwise noted, is
       subjected  to brace expansion, tilde expansion, parameter expansion, command substitution, arithmetic
       expansion, quote removal, pathname expansion, and word splitting.  If it expands  to  more  than  one
       word, bash reports an error.

       Note that the order of redirections is significant.  For example, the command

              ls > dirlist 2>&1

       directs both standard output and standard error to the file dirlist, while the command

              ls 2>&1 > dirlist

       directs  only the standard output to file dirlist, because the standard error was duplicated as stan-
       dard output before the standard output was redirected to dirlist.

       Bash handles several filenames specially when they are used in redirections, as described in the fol-
       lowing table:

              /dev/fd/fd
                     If fd is a valid integer, file descriptor fd is duplicated.
              /dev/stdin
                     File descriptor 0 is duplicated.
              /dev/stdout
                     File descriptor 1 is duplicated.
              /dev/stderr
                     File descriptor 2 is duplicated.
              /dev/tcp/host/port
                     If  host is a valid hostname or Internet address, and port is an integer port number or
                     service name, bash attempts to open a TCP connection to the corresponding socket.
              /dev/udp/host/port
                     If host is a valid hostname or Internet address, and port is an integer port number  or
                     service name, bash attempts to open a UDP connection to the corresponding socket.

       A failure to open or create a file causes the redirection to fail.

       Redirections  using  file  descriptors  greater than 9 should be used with care, as they may conflict
       with file descriptors the shell uses internally.

   Redirecting Input
       Redirection of input causes the file whose name results from the expansion of word to be  opened  for
       reading on file descriptor n, or the standard input (file descriptor 0) if n is not specified.

       The general format for redirecting input is:

              [n]<word

   Redirecting Output
       Redirection  of output causes the file whose name results from the expansion of word to be opened for
       writing on file descriptor n, or the standard output (file descriptor 1) if n is not  specified.   If
       the file does not exist it is created; if it does exist it is truncated to zero size.

       The general format for redirecting output is:
              [n]>word

       If  the  redirection operator is >, and the noclobber option to the set builtin has been enabled, the
       redirection will fail if the file whose name results from the expansion of word exists and is a regu-
       lar  file.   If  the  redirection  operator is >|, or the redirection operator is > and the noclobber
       option to the set builtin command is not enabled, the redirection is attempted even if the file named
       by word exists.

   Appending Redirected Output
       Redirection  of  output in this fashion causes the file whose name results from the expansion of word
       to be opened for appending on file descriptor n, or the standard output (file descriptor 1) if  n  is
       not specified.  If the file does not exist it is created.

       The general format for appending output is:

              [n]>>word

   Redirecting Standard Output and Standard Error
       Bash allows both the standard output (file descriptor 1) and the standard error output (file descrip-
       tor 2) to be redirected to the file whose name is the expansion of word with this construct.

       There are two formats for redirecting standard output and standard error:

              &>word
       and
              >&word

       Of the two forms, the first is preferred.  This is semantically equivalent to

              >word 2>&1

   Here Documents
       This type of redirection instructs the shell to read input from the current source until a line  con-
       taining only word (with no trailing blanks) is seen.  All of the lines read up to that point are then
       used as the standard input for a command.

       The format of here-documents is:

              <<[-]word
                      here-document
              delimiter

       No parameter expansion, command substitution, arithmetic expansion, or  pathname  expansion  is  per-
       formed  on  word.  If any characters in word are quoted, the delimiter is the result of quote removal
       on word, and the lines in the here-document are not expanded.  If word is unquoted, all lines of  the
       here-document  are  subjected to parameter expansion, command substitution, and arithmetic expansion.
       In the latter case, the character sequence \<newline> is ignored, and \ must be  used  to  quote  the
       characters \, $, and 　?

       If the redirection operator is <<-, then all leading tab characters are stripped from input lines and
       the line containing delimiter.  This allows here-documents within shell scripts to be indented  in  a
       natural fashion.

   Here Strings
       A variant of here documents, the format is:

              <<<word

       The word is expanded and supplied to the command on its standard input.

   Duplicating File Descriptors
       The redirection operator

              [n]<&word

       is  used  to  duplicate  input  file  descriptors.   If  word expands to one or more digits, the file
       descriptor denoted by n is made to be a copy of that file descriptor.  If the digits in word  do  not
       specify  a  file descriptor open for input, a redirection error occurs.  If word evaluates to -, file
       descriptor n is closed.  If n is not specified, the standard input (file descriptor 0) is used.

       The operator

              [n]>&word

       is used similarly to duplicate output file descriptors.  If n is not specified, the  standard  output
       (file descriptor 1) is used.  If the digits in word do not specify a file descriptor open for output,
       a redirection error occurs.  As a special case, if n is omitted, and word does not expand to  one  or
       more digits, the standard output and standard error are redirected as described previously.

   Moving File Descriptors
       The redirection operator

              [n]<&digit-

       moves  the file descriptor digit to file descriptor n, or the standard input (file descriptor 0) if n
       is not specified.  digit is closed after being duplicated to n.

       Similarly, the redirection operator
       [n]>&digit-

       moves the file descriptor digit to file descriptor n, or the standard output (file descriptor 1) if n
       is not specified.

   Opening File Descriptors for Reading and Writing
       The redirection operator

              [n]<>word

       causes the file whose name is the expansion of word to be opened for both reading and writing on file
       descriptor n, or on file descriptor 0 if n is not specified.  If the file does not exist, it is  cre-
       ated.

아래 글에 이어서.. 추가 입니다.

참고 URL :
http://alma.ch/perl/Mail-Sendmail-FAQ.html
http://search.cpan.org/~mivkovic/Mail-Sendmail-0.79/Sendmail.pm

sub setSendMail {
    my $message = $_[0];

    %mail = (
                To           => 'to@email.com',
                From         => 'from@email.com',
                Subject      => 'TITLE',
                'Content-type'  => 'text/html; charset="UTF-8"',
                Message      => "<span style='font-size:11px; font-family:맑은 고딕, 돋움'>$message</span>"
            );

    if ( $message ) {
        sendmail(%mail) or die $Mail::Sendmail::error;
        print "OK. Log says:\n", $Mail::Sendmail::log;
    }
}

보시는 바와 같이 빨간 부분을 추가해 주시면 됩니다.
Content-type 앞뒤로 quotation 빼먹으시면 정상적으로 적용 안되니 유의 하세요.

우선 기본적으루다.. sendmail 을 이용해서 발송 해야 하는 건 아시죠..
리눅스 기반 입니다.

일단 sendmail 이 실행 되어 있어야 겠죠.
http://www.faqs.org/docs/linux_network/x15649.html

Perl 용 sendmail 모듈을 설치 하시죠.
http://search.cpan.org/~mivkovic/Mail-Sendmail-0.79/
http://search.cpan.org/~mivkovic/Mail-Sendmail-0.79_16/Sendmail.pm
저는 매뉴얼 설치 했습니다.
별거 없죠... 기냥.. 소스 받아서 압축 풀고 /usr/sbin/perl/site_perl 에 가져다 놓으면 끝..

샘플 코드 위에 링크 보면 있죠.. ㅋ
아래 코드는 구글링 해보시면 가장 많이 나오는 예제 중 하나 입니다.
두 가지를 다 넣어서 테스트 해본 거죠..

sub setSendMail {
    my $sendmailer = '/usr/sbin/sendmail';

    %mail = (
                To          => 'your@email.com',
                From        => 'your@email.com',
                Subject     => '제목 입력',
                Message     => "메시지 입력"
            );

    sendmail(%mail) or die $Mail::Sendmail::error;

    print "OK. Log says:\n", $Mail::Sendmail::log;

    open (MAIL, "|$sendmailer -oi -t");
    print MAIL "From: your@email.com\n";
    print MAIL "To: your@email.com\n";
    print MAIL "Subject: 제목입력\n\n";
    print MAIL "메시지 입력\n";
    close(MAIL);
}

그럼 즐프 하세요.

아주 초보적인 스크립트죠.

#!/usr/bi/perl

@files = </home/계정/*>;

foreach $file (@files) {
    if ( -f $file ) {
        print "This is a file (" . $file . ")\n";
    }

    if ( -d $file ) {
        print "This is a directory (" . $file . ")\n";
    }
}

사실 제가 만들고 싶은걸 작성 하기 전에 이 기초적인 것 부터.. 기록해 두려고.. 글 등록 합니다.
내가 만들고 싶은거..

1. 특정 디렉토리를 recursive 하게 search 를 한다.
2. inode 가 변경 된 최신 파일을 대상으로 file size 가 특정 용량을 넘는지 검사를 한다.
    - daily 로 검사 하면 된다.
    - 근데 파일은 매일 매일 증가를 할 텐데 추가된 거나 inode 만 변경 된 걸로 increase 하게 검색 할 수 있을까?
    - 파일 올릴때 어디 기록을 해야 하나..ㅡ.ㅡ;
3. 특정 용량이 넘으면 alert mail 을 발송 또는 통계를 작성 하여 메일 발송 한다.

암튼.. 지금은 배도 무지 고프고 머리도 멍 하고..
대충 이정 도만 정리를 하자..
뭐.. 보니 recursive function 하나 만들어서 잘 돌리면 몇 줄 안짜고 쉽게 만들수도 있을 것 같다.
근데.. 고민은.. 2번 이다..ㅡ.ㅡ;;
파일은 무한정 늘어 날텐데... 흠..

[원본 글]
http://java.sun.com/j2se/1.5.0/docs/guide/language/annotations.html
http://java.sun.com/docs/books/tutorial/java/javaOO/annotations.html

기본적으로 알고 계셔야 하는 annotation 이지요... :)

@Deprecated

The @Deprecated annotation indicates that the marked method should no longer be used. The compiler generates a warning whenever a program uses a deprecated method, class, or variable. When an element is deprecated, it should be documented using the corresponding @deprecated tag, as shown in the preceding example. Notice that the tag starts with a lowercase "d" and the annotation starts with an uppercase "D". In general, you should avoid using deprecated methods — consult the documentation to see what to use instead.

@Override

The @Override annotation informs the compiler that the element is meant to override an element declared in a superclass. In the preceding example, the override annotation is used to indicate that the getPreferredFood method in the Horse class overrides the same method in the Animal class. If a method marked with @Override fails to override a method in one of its superclasses, the compiler generates an error.

While it's not required to use this annotation when overriding a method, it can be useful to call the fact out explicitly, especially when the method returns a subtype of the return type of the overridden method. This practice, called covariant return types, is used in the previous example: Animal.getPreferredFood returns a Food instance. Horse.getPreferredFood (Horse is a subclass of Animal) returns an instance of Hay (a subclass of Food). For more information, see Overriding and Hiding Methods.

@SuppressWarnings

The @SuppressWarnings annotation tells the compiler to suppress specific warnings that it would otherwise generate. In the previous example, the useDeprecatedMethod calls a deprecated method of Animal. Normally, the compiler generates a warning but, in this case, it is suppressed.

Every compiler warning belongs to a category. The Java Language Specification lists two categories: "deprecation" and "unchecked". The "unchecked" warning can occur when interfacing with legacy code written before the advent of generics. To suppress more than one category of warnings, use the following syntax:

@SuppressWarnings({"unchecked", "deprecation"})

위 원문에 대한 번역이 잘된 글 링크 넣습니다.
원본 글 : http://decoder.tistory.com/21