How do you set focus in Flash ActionScript 3 (AS3)?

Answer

Use the stage focus method:

stage.focus = object;

Source Code

import flash.text.TextField;
import flash.text.TextFieldType;
import fl.controls.Button;

var exampleTextField:TextField = new TextField();
exampleTextField.width = 100;
exampleTextField.height = 20;
exampleTextField.x = 50;
exampleTextField.y = 20;
exampleTextField.type = TextFieldType.INPUT;
exampleTextField.border = true;
addChild(exampleTextField);

var focusInButton:Button = new Button();
focusInButton.label = "Focus";
focusInButton.width = 80;
focusInButton.height = 20;
focusInButton.x = 10;
focusInButton.y = 70;
addChild(focusInButton);

var focusOutButton:Button = new Button();
focusOutButton.label = "Focus Out";
focusOutButton.width = 80;
focusOutButton.height = 20;
focusOutButton.x = 110;
focusOutButton.y = 70;
addChild(focusOutButton);

focusInButton.addEventListener(MouseEvent.MOUSE_UP, function(){ 
  stage.focus = exampleTextField;
});
focusOutButton.addEventListener(MouseEvent.MOUSE_UP, function(){ 
  stage.focus = null;
});

Working with States in Flex 4
by Frank Sommers
September 16, 2009

Advertisements

Interested in Flex graphics? Check out the new book Flex 4 Fun by Chet Haase, available as a PrePrint™ from Artima Press.

Summary
Flex 4's new syntax simplifies working with application states. This article provides a tutorial introduction into UI state management with Flex 4, and includes a complete example.

Stateless Web applications aim to store as little state on the server as possible. Reducing, or even eliminating, reliance on server-side state makes it easier to implement a scalable infrastructure, at least in principle.

At the same time, only the simplest Web applications can function completely without state. Dispatching a request to an online weather reporting service may work in a purely stateless fashion, but more sophisticated applications must keep track of where a user is in a complex data entry process, possible data validation errors, and so on. Data-intensive applications may also need to cache a user's frequently accessed data in order to reduce response time.

Client-Side State

Instead of storing state data on the server, rich-client applications may choose to store such information on the client. A key benefit of rich-client frameworks is that they provide APIs and programming language constructs that make it easier to work with application state on the client. In addition to client-side collections APIs and language support for data processing, rich-client frameworks typically offer high-level constructs to manage application state related to display logic as well.

Consider, for example, a sign-in component typical of many Web applications: A user is presented with text input boxes to enter a user name and a password, as well as a button to initiate the sign-in. A login box may also provide a handy way for the user to create a new account. If the user chooses to register a new account, another view is presented with text boxes for additional information, such as first and last names, and so forth:

In a traditional, server-generated HTML user interface, the server may return an entirely newly rendered page when a user chooses to register instead of signing in. By contrast, a rich-client can affect the change in the user interface entirely on the client side, without interaction from the server.

The simplest way to code that is to write display logic that inserts and removes new labels and text boxes in the UI at runtime, for instance, by modifying the UI's DOM in the browser. More sophisticated rich-client frameworks, however, provide a much handier abstraction to accomplish the same goal: UI states.

UI States in Flex

A UI state is the set of all components and component properties in effect in a component at any given point in time. Multiple UI states can be associated with a component: Switching from one state to another causes the rich-client runtime to add, remove, or modify components based on the differences between states. The login form, for instance, could have "login" and "register" states: The register state defines additional input boxes, changes the label of the button component from "Sign in" to "Register", and also causes the button click to invoke a register() method instead of signin().

In Flex, defining and working with application states has been possible since the 2.0 version of the Flex SDK. In Flex versions 2 and 3, states were defined inside a states array in an MXML document; inside each state definition, in turn, were declarations of what should be added, removed, or modified, related to some base state. It was also possible to build one state on another.

<?xml version="1.0" encoding="utf-8"?>
<mx:VBox xmlns:mx="http://www.adobe.com/2006/mxml"> 

  <mx:Script>
      <![CDATA[
            private function signin():void {
                // Implementation of signin
            }

            private function register():void {
                // Implementation of register
            }
        ]]>
  </mx:Script>

  <mx:states>

    <mx:State name="Register">        

        <mx:AddChild relativeTo="{loginForm}" position="lastChild" creationPolicy="all">
            <mx:FormItem id="frmPasswordConfirm" label="Confirm:">
                <mx:TextInput id="passwordConfirm" displayAsPassword="true"/>
            </mx:FormItem>        
        </mx:AddChild>

        <mx:AddChild relativeTo="{loginForm}" position="lastChild">
            <mx:FormItem label="First name:" id="frmFirstName">
                <mx:TextInput id="firstName" width="220"/>
            </mx:FormItem>
        </mx:AddChild>

        <mx:AddChild relativeTo="{loginForm}" position="lastChild">            
            <mx:FormItem label="Last name:" id="frmLastName">
                <mx:TextInput id="lastName" width="220"/>
            </mx:FormItem>
        </mx:AddChild>

        <mx:AddChild relativeTo="{loginButton}" position="after">
            <mx:LinkButton label="Return to login" click="setCurrentUIState()"/>
        </mx:AddChild>            

        <mx:RemoveChild target="{registerLink}"/>            

        <mx:SetProperty target="{loginLabel}" name="text" value="Create a new account:"/>    
        <mx:SetProperty target="{loginButton}" name="enabled" value="false"/>
        <mx:SetProperty target="{loginButton}" name="label" value="Register"/>
            
     </mx:State>        

  </mx:states>
    
 <mx:Label text="Sign In:" 
            fontWeight="bold" paddingLeft="12" fontSize="14" 
            id="loginLabel" width="100%"/>
        
        <mx:Form id="loginForm" width="100%">

            <mx:FormItem label="Email:" id="frmEmail">
                <mx:TextInput id="email" width="220"/>
            </mx:FormItem>            

            <mx:FormItem label="Password:" id="frmPassword">
                <mx:TextInput id="password" displayAsPassword="true" width="220"/>
            </mx:FormItem>        
        </mx:Form>

        <mx:CheckBox id="rememberMe" label="Remember me on this computer"    
            paddingLeft="77" selected="true"/>

        <mx:ControlBar width="100%"    paddingLeft="84">
            <mx:Button label="Sign in" id="loginButton" click="signin()" enabled="false"/>            
            <mx:LinkButton label="Need to Register?" id="registerLink"
                click="currentState='Register'"/>            
        </mx:ControlBar>
</mx:VBox>

Listing 1: Login box with Flex 3

In the above Flex 3.0 implementation, AddChild and RemoveChild tags indicate that the runtime should add or remove child components, respectively, in the register state. The SetProperty tag, in turn, changes the button's label to "Register," and the SetEventHandler tag ensures that a register() method is invoked when the UI is the register state. Clicking on the LinkButton component toggles between the signin and register states.

While the Flex 2 and 3 state syntax works well, adding and removing components is rather cumbersome: For instance, you have to specify where new components are to be added apart from the new components' parents. UI components supporting a large number of states end up becoming unwieldy, with significant portions of related UI logic scattered across a large MXML file.

Flex 4's State Improvements

To simplify state definition, Flex 4 introduces a new states syntax. Although the various component states are still declared inside the states tag, the definition of each state is specified inline. To see how that works, consider the Flex 4 implementation of the login component. To make the Flex 4 implementation mirror the Flex 3 version as closely as possible, we didn't define separate component and skin files, a Flex 4 best practice:

<?xml version="1.0" encoding="utf-8"?>
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009" 
    xmlns:s="library://ns.adobe.com/flex/spark" 
    xmlns:mx="library://ns.adobe.com/flex/halo">
	
    <fx:Script>
        <![CDATA[
            private function signin(): void {
                 // Implementation of signin 
            }

            private function register(): void {
                // Implementation of register
            }
        ]]>
    </fx:Script>
	
    <s:states>
        <s:State name="signin"/>
        <s:State name="register"/>
    </s:states>
	
    <s:Group id="mainGroup">
        <s:layout>
            <s:VerticalLayout/>
        </s:layout>
		
    <mx:Label text="Sign in:" fontWeight="bold" paddingLeft="12" fontSize="14" id="loginLabel" width="100%"/>
		
    <mx:Form id="loginForm" width="100%" paddingTop="3" paddingBottom="3">

        <mx:FormItem label="First name:" includeIn="register" id="firstNameItem" alpha="0.0">
            <s:TextInput id="firstName" width="220"/>
        </mx:FormItem>

        <mx:FormItem label="Last name:" includeIn="register" id="lastNameItem" alpha="0.0">
            <s:TextInput id="lastName" width="220"/>
        </mx:FormItem>

        <mx:FormItem label="Email:" id="emailItem">
            <s:TextInput id="email" width="220"/>			
        </mx:FormItem>

        <mx:FormItem label="Password:" id="passwordItem">
            <s:TextInput id="password" displayAsPassword="true" width="220"/>
        </mx:FormItem>

        <mx:FormItem label="Confirm:" includeIn="register" id="confirmItem" alpha="0.0">
             <s:TextInput id="passwordConfirmation" displayAsPassword="true" width="220"/>			
        </mx:FormItem>
    </mx:Form>

    <s:Group>
        <s:layout>
            <s:HorizontalLayout paddingLeft="100"/>
        </s:layout>
        <s:Button label="Sign in" label.register="Register" id="loginButton" 
            enabled="true" click.signin="signin()" click.register="register()"/>
			
        <mx:LinkButton label="Need to register?" 
            click="currentState = 'register'" includeIn="signin"/>
        <mx:LinkButton label="Return to signin"
            click="currentState = 'signin'" includeIn="register"/>
     </s:Group>
		
    <mx:CheckBox id="rememberMe" label="Remember me on this computer" paddingLeft="110"/>
 </s:Group>
</s:Application>

Listing 2: Login box with Flex 4 state syntax

Instead of AddChild and RemoveChild methods, components that should be visible in the register state only are added an includeIn="register" tag. You can specify a comma-separated list of state names for the includeIn tag. Flex 4 also provides an excludeFrom tag, if you need to declare what states a component should be removed from. This new syntax allows you to declare components in place, inside the parent.

Properties can similarly be set inline using a new dot-separated syntax. For example, the Button component's label property is defined as follows:

... label="Sign in" label.register="Register" 

This tells Flex to set the button's label property to "Register" in the register state, and to "Sign in" in other states (the default). And listeners can be declared similarly: When the component is in the register state, the register() method is invoked on a button click, otherwise the signin() method is called:

click="signin()" click.register="register()"

The new component syntax makes it much easier to define sophisticated components with relatively straightforward, declarative code. The Flex 4 component states syntax also supports state groups as well as the ability to assign a new parent to a component. It is important to note that the new syntax only impacts MXML declarations—which is what the Flex compiler uses to generate ActionScript code. States can be defined in ActionScript as well, but that syntax does not change in Flex 4.

Flex gives you convenient ways not only to define component states, but also to specify transitions between states. To make the transition between the signin and register states smoother, this example includes a transition effect between those states. A forthcoming Artima article will describe Flex 4 transitions in greater detail.

Share Your Opinion

Have an opinion on Flex 4's states syntax? Discuss this article in the Articles Forum topic, Working with States in Flex 4.

Resources

Adobe's Flash Builder 4
http://labs.adobe.com/technologies/flashbuilder4

Flex 4 SDK
http://opensource.adobe.com/wiki/display/flexsdk/Flex+SDK

Gumbo Project
http://opensource.adobe.com/wiki/display/flexsdk/Gumbo

Flex.org
http://www.flex.org

About the Authors

Frank Sommers is Editor-in-Chief of Artima.

BlazeDS 와 스프링(Spring) 연동하기

출처 : http://youthgonewild.co.kr/category/FLEX

위의 내용이 springfactory를 정의한 부분입니다.
이제 이 factory를 통해서 스프링과 remote object가 연결됩니다.
그러면 flex.messaging.factory.SpringFactory 는 원래 flex package에 존재하는 클래스일까요?
그렇지 않습니다. 스프링과의 연동을 위해 따로 제작된 클래스죠. 저도 외국 사이트에서 다운로드 했습니다.
첨부파일로 올리니 다운 받아서 lib에 등록해서 사용하시면 됩니다..

 blazeds-spring-beta1.jar

출처 : http://softworld.tistory.com/entry/Flex-4Blazeds-Spring-%EC%84%A4%EC%A0%95-%EC%99%84%EB%A3%8C%EB%90%9C-war

blazeds-spring.war

blazeds.war

Adobe가 제공 다운로드에다가 장난질을 쳐놨넹..

Turnkey안에 spring 설정된 war가 있었는데 지워놓은듯... spring설정시 의존성때문에 잘 되지도 않더만 이걸 지워 놓으면 고생할 사람많겠구만...

LiveCycle Data Services살릴려고 Blazeds는 개발 완전 중단되있고 그나마 남은 Freamwork는 graniteds

우선 제공되는 blazeds + spring 연동 war file을 남겨 본다. Test 결과는 잘 돌아감!!!

blazeds-spring.war

Blazeds Ver.4 + Spring Ver.3.0.1

spring ver.을 최신으로 올려봤지만 의존성때문에 잘 안됨..

blazeds.war

기본 Blazeds ver.4 도 올려 놓는다!

출처 : http://lahuman.tistory.com/55

주요 몇가지 소스를 간단히 소개 하면,

1. /WEB-INF/web.xml

2. /WEB-INF/flex/services-config.xml

3. application-context.xml

위 예제를 보면 Spring MVC를 이용해서 flex BlazeDS를 호출 한다.

아래 파일을 찬찬히 봐라!

시스템 환경

BlazeDS 4.0.x

Spring 3.0.x

SBI 1.3 or 1.5

Webapplicationcontext.xml에서 <flex-remoting> 태그 사용시 발생하는 오류

예)

    <bean id="SimpleExampleService2" class="com.mydomain.data.SimpleExample">

        <flex:remoting-destination/>

    </bean>

오류메시지

SEVERE: Context initialization failed

org.springframework.beans.factory.CannotLoadBeanClassException: Error loading class [org.springframework.flex.core.MessageInterceptionAdvice] for bean with name 'org.springframework.flex.core.MessageInterceptionAdvice#0' defined in null: problem with class file or dependent class; nested exception is java.lang.NoClassDefFoundError: org/aopalliance/intercept/MethodInterceptor

    at org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1211)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.predictBeanType(AbstractAutowireCapableBeanFactory.java:568)

    at org.springframework.beans.factory.support.AbstractBeanFactory.getType(AbstractBeanFactory.java:523)

    at org.springframework.flex.config.RemotingAnnotationPostProcessor.findRemotingDestinations(RemotingAnnotationPostProcessor.java:148)

    at org.springframework.flex.config.RemotingAnnotationPostProcessor.postProcessBeanFactory(RemotingAnnotationPostProcessor.java:79)

    at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:624)

    at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:614)

    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:398)

    at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:443)

    at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:459)

    at org.springframework.web.servlet.FrameworkServlet.initWebApplicationContext(FrameworkServlet.java:340)

    at org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:307)

    at org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:127)

    at javax.servlet.GenericServlet.init(GenericServlet.java:211)

    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1164)

    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:984)

    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4043)

    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4349)

    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)

    at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)

    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)

    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)

    at org.apache.catalina.core.StandardService.start(StandardService.java:450)

    at org.apache.catalina.core.StandardServer.start(StandardServer.java:709)

    at org.apache.catalina.startup.Catalina.start(Catalina.java:551)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

    at java.lang.reflect.Method.invoke(Method.java:597)

    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287)

    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:412)

Caused by: java.lang.NoClassDefFoundError: org/aopalliance/intercept/MethodInterceptor

    at java.lang.ClassLoader.defineClass1(Native Method)

    at java.lang.ClassLoader.defineClass(ClassLoader.java:620)

    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)

    at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1814)

    at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:868)

    at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1321)

    at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1200)

    at org.springframework.util.ClassUtils.forName(ClassUtils.java:258)

    at org.springframework.beans.factory.support.AbstractBeanDefinition.resolveBeanClass(AbstractBeanDefinition.java:408)

    at org.springframework.beans.factory.support.AbstractBeanFactory.doResolveBeanClass(AbstractBeanFactory.java:1229)

    at org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1200)

    ... 30 more

Feb 20, 2012 5:19:32 PM org.apache.catalina.core.ApplicationContext log

SEVERE: StandardWrapper.Throwable

org.springframework.beans.factory.CannotLoadBeanClassException: Error loading class [org.springframework.flex.core.MessageInterceptionAdvice] for bean with name 'org.springframework.flex.core.MessageInterceptionAdvice#0' defined in null: problem with class file or dependent class; nested exception is java.lang.NoClassDefFoundError: org/aopalliance/intercept/MethodInterceptor

    at org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1211)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.predictBeanType(AbstractAutowireCapableBeanFactory.java:568)

    at org.springframework.beans.factory.support.AbstractBeanFactory.getType(AbstractBeanFactory.java:523)

    at org.springframework.flex.config.RemotingAnnotationPostProcessor.findRemotingDestinations(RemotingAnnotationPostProcessor.java:148)

    at org.springframework.flex.config.RemotingAnnotationPostProcessor.postProcessBeanFactory(RemotingAnnotationPostProcessor.java:79)

    at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:624)

    at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:614)

    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:398)

    at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:443)

    at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:459)

    at org.springframework.web.servlet.FrameworkServlet.initWebApplicationContext(FrameworkServlet.java:340)

    at org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:307)

    at org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:127)

    at javax.servlet.GenericServlet.init(GenericServlet.java:211)

    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1164)

    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:984)

    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4043)

    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4349)

    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)

    at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)

    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)

    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)

    at org.apache.catalina.core.StandardService.start(StandardService.java:450)

    at org.apache.catalina.core.StandardServer.start(StandardServer.java:709)

    at org.apache.catalina.startup.Catalina.start(Catalina.java:551)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

    at java.lang.reflect.Method.invoke(Method.java:597)

    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287)

    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:412)

Caused by: java.lang.NoClassDefFoundError: org/aopalliance/intercept/MethodInterceptor

    at java.lang.ClassLoader.defineClass1(Native Method)

    at java.lang.ClassLoader.defineClass(ClassLoader.java:620)

    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)

    at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1814)

    at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:868)

    at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1321)

    at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1200)

    at org.springframework.util.ClassUtils.forName(ClassUtils.java:258)

    at org.springframework.beans.factory.support.AbstractBeanDefinition.resolveBeanClass(AbstractBeanDefinition.java:408)

    at org.springframework.beans.factory.support.AbstractBeanFactory.doResolveBeanClass(AbstractBeanFactory.java:1229)

    at org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1200)

    ... 30 more

Feb 20, 2012 5:19:32 PM org.apache.catalina.core.StandardContext loadOnStartup

SEVERE: Servlet /web1 threw load() exception

java.lang.NoClassDefFoundError: org/aopalliance/intercept/MethodInterceptor

    at java.lang.ClassLoader.defineClass1(Native Method)

    at java.lang.ClassLoader.defineClass(ClassLoader.java:620)

    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)

    at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1814)

    at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:868)

    at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1321)

    at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1200)

    at org.springframework.util.ClassUtils.forName(ClassUtils.java:258)

    at org.springframework.beans.factory.support.AbstractBeanDefinition.resolveBeanClass(AbstractBeanDefinition.java:408)

    at org.springframework.beans.factory.support.AbstractBeanFactory.doResolveBeanClass(AbstractBeanFactory.java:1229)

    at org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1200)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.predictBeanType(AbstractAutowireCapableBeanFactory.java:568)

    at org.springframework.beans.factory.support.AbstractBeanFactory.getType(AbstractBeanFactory.java:523)

    at org.springframework.flex.config.RemotingAnnotationPostProcessor.findRemotingDestinations(RemotingAnnotationPostProcessor.java:148)

    at org.springframework.flex.config.RemotingAnnotationPostProcessor.postProcessBeanFactory(RemotingAnnotationPostProcessor.java:79)

    at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:624)

    at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:614)

    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:398)

    at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:443)

    at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:459)

    at org.springframework.web.servlet.FrameworkServlet.initWebApplicationContext(FrameworkServlet.java:340)

    at org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:307)

    at org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:127)

    at javax.servlet.GenericServlet.init(GenericServlet.java:211)

    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1164)

    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:984)

    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4043)

    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4349)

    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)

    at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)

    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)

    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)

    at org.apache.catalina.core.StandardService.start(StandardService.java:450)

    at org.apache.catalina.core.StandardServer.start(StandardServer.java:709)

    at org.apache.catalina.startup.Catalina.start(Catalina.java:551)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

    at java.lang.reflect.Method.invoke(Method.java:597)

    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287)

    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:412)

해결방법

Aopalliance-1.0.jar lib폴더에 추가

오류메시지

SEVERE: Context initialization failed

org.springframework.beans.factory.BeanCreationException: Error creating bean with name '_messageBrokerDefaultHandlerMapping': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '_messageBroker': Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanInitializationException: MessageBroker initialization failed; nested exception is org.springframework.aop.framework.AopConfigException: Cannot proxy target class because CGLIB2 is not available. Add CGLIB to the class path or specify proxy interfaces.

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:450)

    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:290)

    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)

    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:287)

    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:189)

    at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:557)

    at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:842)

    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:416)

    at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:443)

    at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:459)

    at org.springframework.web.servlet.FrameworkServlet.initWebApplicationContext(FrameworkServlet.java:340)

    at org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:307)

    at org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:127)

    at javax.servlet.GenericServlet.init(GenericServlet.java:211)

    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1164)

    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:984)

    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4043)

    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4349)

    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)

    at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)

    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)

    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)

    at org.apache.catalina.core.StandardService.start(StandardService.java:450)

    at org.apache.catalina.core.StandardServer.start(StandardServer.java:709)

    at org.apache.catalina.startup.Catalina.start(Catalina.java:551)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

    at java.lang.reflect.Method.invoke(Method.java:597)

    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287)

    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:412)

Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name '_messageBroker': Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanInitializationException: MessageBroker initialization failed; nested exception is org.springframework.aop.framework.AopConfigException: Cannot proxy target class because CGLIB2 is not available. Add CGLIB to the class path or specify proxy interfaces.

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1401)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:512)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:450)

    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:290)

    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)

    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:287)

    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:189)

    at org.springframework.beans.factory.support.AbstractBeanFactory.isSingleton(AbstractBeanFactory.java:392)

    at org.springframework.context.support.AbstractApplicationContext.isSingleton(AbstractApplicationContext.java:1024)

    at org.springframework.web.servlet.handler.AbstractUrlHandlerMapping.registerHandler(AbstractUrlHandlerMapping.java:370)

    at org.springframework.web.servlet.handler.SimpleUrlHandlerMapping.registerHandlers(SimpleUrlHandlerMapping.java:129)

    at org.springframework.web.servlet.handler.SimpleUrlHandlerMapping.initApplicationContext(SimpleUrlHandlerMapping.java:104)

    at org.springframework.context.support.ApplicationObjectSupport.initApplicationContext(ApplicationObjectSupport.java:119)

    at org.springframework.web.context.support.WebApplicationObjectSupport.initApplicationContext(WebApplicationObjectSupport.java:71)

    at org.springframework.context.support.ApplicationObjectSupport.setApplicationContext(ApplicationObjectSupport.java:73)

    at org.springframework.context.support.ApplicationContextAwareProcessor.doProcess(ApplicationContextAwareProcessor.java:116)

    at org.springframework.context.support.ApplicationContextAwareProcessor.postProcessBeforeInitialization(ApplicationContextAwareProcessor.java:99)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:394)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1394)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:512)

    ... 31 more

Caused by: org.springframework.beans.factory.BeanInitializationException: MessageBroker initialization failed; nested exception is org.springframework.aop.framework.AopConfigException: Cannot proxy target class because CGLIB2 is not available. Add CGLIB to the class path or specify proxy interfaces.

    at org.springframework.flex.core.MessageBrokerFactoryBean.afterPropertiesSet(MessageBrokerFactoryBean.java:185)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1460)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1398)

    ... 50 more

Caused by: org.springframework.aop.framework.AopConfigException: Cannot proxy target class because CGLIB2 is not available. Add CGLIB to the class path or specify proxy interfaces.

    at org.springframework.aop.framework.DefaultAopProxyFactory.createAopProxy(DefaultAopProxyFactory.java:67)

    at org.springframework.aop.framework.ProxyCreatorSupport.createAopProxy(ProxyCreatorSupport.java:104)

    at org.springframework.aop.framework.ProxyFactory.getProxy(ProxyFactory.java:112)

    at org.springframework.flex.core.EndpointConfigProcessor.processAfterStartup(EndpointConfigProcessor.java:69)

    at org.springframework.flex.core.MessageBrokerFactoryBean.processAfterStart(MessageBrokerFactoryBean.java:294)

    at org.springframework.flex.core.MessageBrokerFactoryBean.afterPropertiesSet(MessageBrokerFactoryBean.java:168)

    ... 52 more

Feb 20, 2012 5:21:11 PM org.apache.catalina.core.ApplicationContext log

SEVERE: StandardWrapper.Throwable

org.springframework.beans.factory.BeanCreationException: Error creating bean with name '_messageBrokerDefaultHandlerMapping': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '_messageBroker': Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanInitializationException: MessageBroker initialization failed; nested exception is org.springframework.aop.framework.AopConfigException: Cannot proxy target class because CGLIB2 is not available. Add CGLIB to the class path or specify proxy interfaces.

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:450)

    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:290)

    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)

    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:287)

    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:189)

    at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:557)

    at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:842)

    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:416)

    at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:443)

    at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:459)

    at org.springframework.web.servlet.FrameworkServlet.initWebApplicationContext(FrameworkServlet.java:340)

    at org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:307)

    at org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:127)

    at javax.servlet.GenericServlet.init(GenericServlet.java:211)

    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1164)

    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:984)

    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4043)

    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4349)

    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)

    at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)

    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)

    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)

    at org.apache.catalina.core.StandardService.start(StandardService.java:450)

    at org.apache.catalina.core.StandardServer.start(StandardServer.java:709)

    at org.apache.catalina.startup.Catalina.start(Catalina.java:551)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

    at java.lang.reflect.Method.invoke(Method.java:597)

    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287)

    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:412)

Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name '_messageBroker': Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanInitializationException: MessageBroker initialization failed; nested exception is org.springframework.aop.framework.AopConfigException: Cannot proxy target class because CGLIB2 is not available. Add CGLIB to the class path or specify proxy interfaces.

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1401)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:512)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:450)

    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:290)

    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)

    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:287)

    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:189)

    at org.springframework.beans.factory.support.AbstractBeanFactory.isSingleton(AbstractBeanFactory.java:392)

    at org.springframework.context.support.AbstractApplicationContext.isSingleton(AbstractApplicationContext.java:1024)

    at org.springframework.web.servlet.handler.AbstractUrlHandlerMapping.registerHandler(AbstractUrlHandlerMapping.java:370)

    at org.springframework.web.servlet.handler.SimpleUrlHandlerMapping.registerHandlers(SimpleUrlHandlerMapping.java:129)

    at org.springframework.web.servlet.handler.SimpleUrlHandlerMapping.initApplicationContext(SimpleUrlHandlerMapping.java:104)

    at org.springframework.context.support.ApplicationObjectSupport.initApplicationContext(ApplicationObjectSupport.java:119)

    at org.springframework.web.context.support.WebApplicationObjectSupport.initApplicationContext(WebApplicationObjectSupport.java:71)

    at org.springframework.context.support.ApplicationObjectSupport.setApplicationContext(ApplicationObjectSupport.java:73)

    at org.springframework.context.support.ApplicationContextAwareProcessor.doProcess(ApplicationContextAwareProcessor.java:116)

    at org.springframework.context.support.ApplicationContextAwareProcessor.postProcessBeforeInitialization(ApplicationContextAwareProcessor.java:99)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:394)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1394)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:512)

    ... 31 more

Caused by: org.springframework.beans.factory.BeanInitializationException: MessageBroker initialization failed; nested exception is org.springframework.aop.framework.AopConfigException: Cannot proxy target class because CGLIB2 is not available. Add CGLIB to the class path or specify proxy interfaces.

    at org.springframework.flex.core.MessageBrokerFactoryBean.afterPropertiesSet(MessageBrokerFactoryBean.java:185)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1460)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1398)

    ... 50 more

Caused by: org.springframework.aop.framework.AopConfigException: Cannot proxy target class because CGLIB2 is not available. Add CGLIB to the class path or specify proxy interfaces.

    at org.springframework.aop.framework.DefaultAopProxyFactory.createAopProxy(DefaultAopProxyFactory.java:67)

    at org.springframework.aop.framework.ProxyCreatorSupport.createAopProxy(ProxyCreatorSupport.java:104)

    at org.springframework.aop.framework.ProxyFactory.getProxy(ProxyFactory.java:112)

    at org.springframework.flex.core.EndpointConfigProcessor.processAfterStartup(EndpointConfigProcessor.java:69)

    at org.springframework.flex.core.MessageBrokerFactoryBean.processAfterStart(MessageBrokerFactoryBean.java:294)

    at org.springframework.flex.core.MessageBrokerFactoryBean.afterPropertiesSet(MessageBrokerFactoryBean.java:168)

    ... 52 more

Feb 20, 2012 5:21:11 PM org.apache.catalina.core.StandardContext loadOnStartup

SEVERE: Servlet /web1 threw load() exception

org.springframework.aop.framework.AopConfigException: Cannot proxy target class because CGLIB2 is not available. Add CGLIB to the class path or specify proxy interfaces.

    at org.springframework.aop.framework.DefaultAopProxyFactory.createAopProxy(DefaultAopProxyFactory.java:67)

    at org.springframework.aop.framework.ProxyCreatorSupport.createAopProxy(ProxyCreatorSupport.java:104)

    at org.springframework.aop.framework.ProxyFactory.getProxy(ProxyFactory.java:112)

    at org.springframework.flex.core.EndpointConfigProcessor.processAfterStartup(EndpointConfigProcessor.java:69)

    at org.springframework.flex.core.MessageBrokerFactoryBean.processAfterStart(MessageBrokerFactoryBean.java:294)

    at org.springframework.flex.core.MessageBrokerFactoryBean.afterPropertiesSet(MessageBrokerFactoryBean.java:168)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1460)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1398)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:512)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:450)

    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:290)

    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)

    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:287)

    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:189)

    at org.springframework.beans.factory.support.AbstractBeanFactory.isSingleton(AbstractBeanFactory.java:392)

    at org.springframework.context.support.AbstractApplicationContext.isSingleton(AbstractApplicationContext.java:1024)

    at org.springframework.web.servlet.handler.AbstractUrlHandlerMapping.registerHandler(AbstractUrlHandlerMapping.java:370)

    at org.springframework.web.servlet.handler.SimpleUrlHandlerMapping.registerHandlers(SimpleUrlHandlerMapping.java:129)

    at org.springframework.web.servlet.handler.SimpleUrlHandlerMapping.initApplicationContext(SimpleUrlHandlerMapping.java:104)

    at org.springframework.context.support.ApplicationObjectSupport.initApplicationContext(ApplicationObjectSupport.java:119)

    at org.springframework.web.context.support.WebApplicationObjectSupport.initApplicationContext(WebApplicationObjectSupport.java:71)

    at org.springframework.context.support.ApplicationObjectSupport.setApplicationContext(ApplicationObjectSupport.java:73)

    at org.springframework.context.support.ApplicationContextAwareProcessor.doProcess(ApplicationContextAwareProcessor.java:116)

    at org.springframework.context.support.ApplicationContextAwareProcessor.postProcessBeforeInitialization(ApplicationContextAwareProcessor.java:99)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:394)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1394)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:512)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:450)

    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:290)

    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)

    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:287)

    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:189)

    at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:557)

    at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:842)

    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:416)

    at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:443)

    at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:459)

    at org.springframework.web.servlet.FrameworkServlet.initWebApplicationContext(FrameworkServlet.java:340)

    at org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:307)

    at org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:127)

    at javax.servlet.GenericServlet.init(GenericServlet.java:211)

    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1164)

    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:984)

    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4043)

    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4349)

    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)

    at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)

    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)

    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)

    at org.apache.catalina.core.StandardService.start(StandardService.java:450)

    at org.apache.catalina.core.StandardServer.start(StandardServer.java:709)

    at org.apache.catalina.startup.Catalina.start(Catalina.java:551)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

    at java.lang.reflect.Method.invoke(Method.java:597)

    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287)

    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:412)

해결방법

cglib-nodep-2.2.jar 라이브러리 추가

참조

http://develop.sunshiny.co.kr/80 (스프링 라이브러리 의존성)

출처 : http://blog.naver.com/PostView.nhn?blogId=thunder1119&logNo=100091204490

올해초 Srping BlazeDS Integration 1.0.0 M1 으로 스프링과 BlazeDS를 적용해 보았는데

( 머드초보님의 M1 사용기 : http://mudchobo.tomeii.com/tt/371 )

한학기 마치고 다시 접하려고 했더니 정식버전이 나왔더군요!

그래서 반가운 마음에 적용해보려고 Spring 홈페이지( http://www.springsource.org )에서 다운로드후

문서를 보았는데. M1에 비해서 문서의 양이 늘어나있고 영어 잼병인 저에겐 소스코드만이 유일한

해독가능한 언어인데 상황에 따라 다르게 적용해야되는 코드들이라 영 도움이 안되 몇일간 삽질을 시켜주었습니다ㅜㅜ

우선 설명하기에 앞서 플렉스 컴퍼넌트 카페( http://cafe.naver.com/flexcomponent.cafe ) 에 서기님이 올려주신

Flex3+eclipse europa + BlazeDS 셋팅 게시물의 첨부된 문서의 세팅방법을 모두 완료했다는 가정하에 설명하도록

하겠습니다. ( http://cafe.naver.com/flexcomponent.cafe?iframe_url=/ArticleRead.nhn%3Farticleid=10906

서기님이 작성하신 셋팅문서 첨부해 두겠습니다.)

blazeds_hello(blazeds).zip

blazeds_setting.doc

자 이제 위 과정으로 BlazeDS_Hello.mxml을 실행하였을 경우 "Welcome BlazeDS 성공!" 이란 문구를 보았다고 치고

이제 Srping BlazeDS Integration을 적용해 보도록 하겠습니다.

우선 Srping BlazeDS Integration에 필요한 환경(Java 5 or higher, Spring 2.5.6 or higher ,Adobe BlazeDS 3.2 or higher)

을 구성해주어야 되는데 http://www.springsource.org/download 에서 우선 Srping BlazeDS Integration과 Spring 2.5.6

을 받아서 lib안에 넣어줍니다.

그리고 web.xml을 수정해보겠습니다.

우선 spring을 사용하면서 필요없어진 리스너를 삭제합니다.

그리고 스프링을 사용하기 위한 ContextLoaderListener를 삽입합니다.

<servlet-mapping>태그는 그대로 두고 <servlet> 태그만 스프링을 사용하기 위해 아래와 같이 수정합니다.

여기 까지가 web.xml 수정사항입니다.

그 후 spring을 사용하려면 기본적으로 WEB-INF밑에 applicationContext.xml 파일이 있어야 하기에 만들어 줍니다.

이제 web.xml에서 <servlet>태그밑에 <param-value>에 선언해 두었던 web-application-config.xml을 만들어줍니다.

안의 내용은 뒤에 설명하도록 하겠습니다.

이제 WEB-INF밑에 flex폴더에 들어있는 BlazeDS관련 xml들을 수정하겠습니다.

우선 remoting-config.xml에 선언해둔 blaze id에 destination 태그를 삭제합니다. 이태그는 이제 spring 관리하에

web-application-config.xml에서 새로운 인생(?)을 살게 될 것입니다.

그리고 services-config.xml <services> 태그밑에  아래와 같이 default-channels 태그를 추가해 줍니다.

자 이제 주역인 web-application-config.xml에 내용을 넣도록 하겠습니다.

우선 설명하기에 앞서 전체코드 나갑니다.

얼핏 복잡해보이기도 하지만 사실 그렇게 어렵지 않습니다.

우선 네임스페이스 부분을 보면 xmlns:flex="http://www.springframework.org/schema/flex 추가됬고

스키마부분을 보면

http://www.springframework.org/schema/flex
http://www.springframework.org/schema/flex/spring-flex-1.0.xsd

기존 스프링에서 이두개가 추가되었고

web.xml에서 들어오는 MessageBroker를 아래 태그가 담당합니다.

id는 편하신데로 주시면 되고 사실 이부분을 doc에 보면 여러가지 방법으로 표현할 수 있는데 <flex:message-broker/>등

짧게 표현이 가능하지만 doc이 부실한지 제가 못찾는지 이대로 실행하면 오류가나서 실행이안됩니다.

그래서 전 그냥 기존 spring 방식으로 bean으로 처리했습니다.

다음으로 스프링에 SimpleUrlHandlerMapping 으로 MassageBroker와 연결합니다.

저는 편의상 p 네임스페이스로 축약해서 사용했습니다.

그리고 이부분은 저도 잘 모르겠는데 messageBroker와 관련된 adapter인듯 합니다.

<bean class="org.springframework.flex.servlet.MessageBrokerHandlerAdapter" />

그리고 저를 가장 고생시킨.. remoting 부분인데 1.0.0 정식이 나오면서 <flex:remoting-service>태그가

<flex:remoting-destination>으로 바겼는지 국내와 국외문서 모두에 <flex:remoting-service>으로 되어있어서

상당히 고생했습니다. 이부분도 다양한 사용방법이 있는데 자세한것은 레퍼런스를 참조하시고 우선 성공한 방법만

소개하겠습니다.

<bean id="test" class="test.Test">
               <flex:remoting-destination destination-id="blaze" message-broker="mySpringManagedMessageBroker"/>
</bean>

또는

<bean id="test" class="test.Test"/>
      
<flex:remoting-destination ref="test" destination-id="blaze" message-broker="mySpringManagedMessageBroker"/>

또는

<bean id="test" class="test.Test"/>

<bean id="product" class="org.springframework.flex.remoting.RemotingDestinationExporter"
             p:messageBroker-ref="mySpringManagedMessageBroker" p:service-ref="test"
             p:destinationId="blaze" />

레퍼런스문서에 ref 외에는 나와있질 않아서 계속 메시지브로커를 찾지못한다는 에러를 보았는데

결국 flex스키마 문서를 죄 뒤져서 속성을 찾아냈습니다 ㅡㅠ

message-broker="mySpringManagedMessageBroker" 부분은 꼭 넣어주시고

remoting-config.xml에서 destination id로 사용되는 부분과 같은 속성이 destination-id 입니다.

사실 이외에도 채널등 여러 속성이 있는데 불필요하다고 판단해서 다 제외했습니다.

자이제 여기까지 설정을 하시고 BlazeDS_Hello.mxml을 실행해보시면 다음과 같은 아름다운 화면을 보실 수 있습니다!

반갑다 친구야!!

[출처] Spring BlazeDS Integration 1.0.0 Release(정식) 적용하기(1) - 세팅 및 Remoting적용|작성자 황금비율

Spring Projects

Spring Flex

Spring BlazeDS Integration is a top-level Spring project, and a component of the complete Spring Web stack.  This project's purpose is to make it easier to build Spring-powered Rich Internet Applications using Adobe Flex as the front-end client.  It aims to achieve this purpose by providing first-class support for using the open source Adobe BlazeDS project and its powerful remoting and messaging facilities in combination with the familiar Spring programming model.

The Flex Addon for Spring Roo is a new component that raises the bar for productivity in building Flex clients backed by Spring BlazeDS Integration on the server-side. By utilizing the next-generation code-generation and management facilities of Spring Roo, it provides the fastest way to get up and running with a new Spring-based Flex project by letting developers focus on doing what they do best - write code.

in

• Spring Flex

Spring BlazeDS Integration is a top-level Spring project, and a component of the complete Spring Web stack.  This project's purpose is to make it easier to build Spring-powered Rich Internet Applications using Adobe Flex as the front-end client.  It aims to achieve this purpose by providing first-class support for using the open source Adobe BlazeDS project and its powerful remoting and messaging facilities in combination with the familiar Spring programming model.

The Flex Addon for Spring Roo is a new component that raises the bar for productivity in building Flex clients backed by Spring BlazeDS Integration on the server-side. By utilizing the next-generation code-generation and management facilities of Spring Roo, it provides the fastest way to get up and running with a new Spring-based Flex project by letting developers focus on doing what they do best - write code.

http://www.springsource.com/download/community?project=Spring%20BlazeDS%20Integration

#maven

Latest News

• The latest production release, Spring BlazeDS Integration 1.5.0 is now available! View the Official Announcement.
• Be sure to check out the 1.0.0.M1 release of the Flex Addon for Spring Roo. See this 15 minute screencast for an introduction to the Flex Addon.

(For compatibility with Spring Roo 1.1.0 and above, please get in touch with us on the forums for guidance on how to get up and running with the nightly snapshots of the Flex Addon.)

• Check out Using Spring BlazeDS Integration 1.0 for an introduction to the project. Also, for a nice step-by-step tutorial, check out the Flex 4 and Spring 3 Integration Refcard. Though this material is focused on Spring BlazeDS Integration 1.0.x, it can easily be adapted to work with the latest release.
• The Spring BlazeDS Integration Test Drive samples are available as an integrated part of the distribution. Many thanks to Christophe Coenraets from Adobe for his contributions!

Spring Flex Resources

• Downloads
• 1.5.2 Reference Documentation
• 1.5.2 JavaDoc
• 1.0.3 Reference Documentation
• 1.0.3 JavaDoc
• Spring BlazeDS Integration Forum
• Version Control: Subversion
• Change Log: Fisheye
• Issue Tracking: Spring BlazeDS Integration Jira
• Issue Tracking: Flex Addon for Spring Roo Jira
• Build Status: Bamboo

Spring Flex Presentations

• Adobe Developer Week 2010: Adobe Flex and BlazeDS Integration with SpringSource (This version includes a preview of upcoming features such as Hibernate serialization support and the Flex addon for Spring Roo.)
• JavaHispano Webinar (en Español): Webinar Spring + Flex con Sergi Almar e Iván Álvarez
• Adobe MAX 2009: Integrating Spring with BlazeDS and LiveCycle Data Services
• Adobe eSeminar: Spring and the Adobe Flash Platform

Spring Flex Articles and Tutorials

• Christophe Coenraets: Flex / Spring Mobile Test Drive
• blog.springsource.com: Introducing the Flex Addon for Spring Roo
• InfoQ: Virtual Panel: State of the Art in Enterprise Flex Frameworks
• DZone Refcardz: Flex 4 and Spring 3 Integration Refcard
• Adobe Developer Connection: An introduction to Spring BlazeDS integration
• Christophe Coenraets: New Spring / BlazeDS Test Drive Available: Flex 4, BlazeDS 4, and Spring / BlazeDS Integration 1.0.3
• James Ward: Flash Builder 4 Data Wizards with Java / Spring
• blog.springsource.com: Using Spring BlazeDS Integration 1.0
• Spring by Example: Simple Flex Webapp
• Jettro Coenradie: Integrate flex security in Mate using the spring BlazeDS integration project

 

Maven Artifacts

Here is the Spring External Repository needed for BlazeDS dependencies:

<repository>
    <id>spring-external</id>
    <name>Spring External Repository</name>
    <url>http://maven.springframework.org/external</url>
</repository>

Here is the Spring Flex dependency definition:

<dependency>
 <groupId>org.springframework.flex</groupId>
 <artifactId>spring-flex-core</artifactId>
 <version>1.5.2.RELEASE</version>
</dependency> 

fxstyleexplorer.air

첨부한 파일을 다운 받아서 프로젝트에 넣어주시구요.

(출처 : http://flexology.wordpress.com/2008/09/30/loadinganimated_gif_in_flex/ )

AnimatedGIFImage.as 파일을 추가합니다.
소스는 아래와 같습니다.

package gif
{
 import flash.net.URLRequest;

 import mx.controls.Image;
 import mx.core.UIComponent;

 import org.gif.player.GIFPlayer;

 public class AnimatedGIFImage extends Image
 {
  private var _gifImage:UIComponent;

  public function AnimatedGIFImage()
  {
   super();
   this._gifImage=new UIComponent();
  }

  override public function set source(value:Object):void
  {
   if (!value is String)
   {
    throw new ArgumentError("Source must be of type String");
   }

   super.source=value;
  }

  override protected function createChildren():void
  {
   super.createChildren();
   var player:GIFPlayer=new GIFPlayer();
   player.load(new URLRequest(this.source as String));
   this._gifImage.addChild(player);
  }

  override protected function updateDisplayList(unscaledWidth:Number, unscaledHeight:Number):void
  {
   this.addChild(this._gifImage);
   super.updateDisplayList(unscaledWidth, unscaledHeight);
  }
 }
}

그리고 사용하실땐
<gif:AnimatedGIFImage source="test.gif" width="100" height="100"/> 와 같이 사용하시면 됩니다.

Datagrid avec ItemRenderer avec CheckBox, ComboBox, ColorPicker

Updated for Flex 3

Voici un exemple d'utilisation du composant DataGrid en Flex 2 Flex 3 avec des ItemRenderer.

Chaque champ peut-être édité. Cet exemple montre l'utilisation de CheckBox, de ComboBox, de NumericStepper et de ColorPicker comme Renderer.

Voir la démo - See the demo

Voir les sources - View the sources

dgRendererSimple.zip

Explication

Tout est dans le code.

Les ItemRenderer de chaque colonne sont programmés en MXML.

Progressbar in Datagrid Example

출처 : http://www.flex-blog.com/progressbar-in-datagrid-example/

Line Break

Author: Roelof (13 Articles) - Author Website

Roelof is a SAP Consultant specialized in Front-End development. In his spare free time he is either developing on the web, playing basketball, watching soccer or traveling. He is also the co-owner of Flex-Blog.com.

In the comments of our previous post about using the ProgressBar, one of our readers asked if a ProgressBar could be used inside a DataGrid.

This is, ofcourse, possible. So we decided to write an example about this.

There are a couple of things you need to know before we start:

1. Use an ItemRenderer to show the ProgressBar inside the DataGrid instead of text.
2. Create a DataProvider for the DataGrid (in our case we use an ArrayCollection).
3. Create an action to start the ProgressBar (in our case we simulate a download).
4. Make sure the ArrayCollection is updated on every progress of the ProgressBar.

First we create an ItemRenderer in a seperate ActionScript file (myProgressBar.as):

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34

package {     import mx.containers.HBox;     import mx.controls.ProgressBar;     import mx.controls.dataGridClasses.*;     public class myProgressBar extends HBox     //This should normally be extends ProgressBar, we are using HBox to have more control over the layout.     {         private var pb:ProgressBar;                 public function myProgressBar():void {             //Create new ProgressBar Instance             pb = new ProgressBar();             //Set some layout things             pb.mode = "manual";             pb.percentWidth = 100;                      pb.labelPlacement = "center";             this.setStyle("verticalAlign","middle");             //Add ProgressBar as child             addChild(pb);         }                 override public function set data(value:Object):void         {             super.data = value;         }                   override protected function updateDisplayList(unscaledWidth:Number, unscaledHeight:Number) : void{             super.updateDisplayList(unscaledWidth, unscaledHeight);             pb.setProgress(data.loaded, data.total);         }     } }

Then we will use this ItemRenderer inside the DataGrid column.

1	<mx:DataGridColumn itemRenderer="myProgressBar" dataField="progress" headerText="Progress" width="180" paddingLeft="5"/>

To start the ‘fake’ ProgressBar download progress, we are using an Image as a Button inside the DataGrid.

1 2 3 4 5 6 7 8 9 10

<mx:DataGridColumn width="112" headerText="Download">                 <mx:itemRenderer>                     <fx:Component>                         <mx:HBox horizontalAlign="center" verticalAlign="middle">                                 <s:Label text="{data.file}"/>                             <mx:Image buttonMode="true" toolTip="'Download'" click="outerDocument.downloadFile()" source="@Embed(source='images/down_alt.png')"/>                         </mx:HBox>                     </fx:Component>                 </mx:itemRenderer>                          </mx:DataGridColumn>

Why use outerDocument?
Since the itemRenderer is within another Component, we need to use outerDocument to call a method inside your ‘main’ Component.

Next step was to implement the method downloadFile():

1 2 3 4 5 6 7

public function downloadFile():void{                 //start timer                 var timer:Timer = new Timer(500);                 // add event listener                 timer.addEventListener(TimerEvent.TIMER, updateProgressBar);                 timer.start();                          }

Next, implement the eventListener. Inside the eventListener we need to make sure the DataGrid / ArrayCollection gets updated.

1 2 3 4 5 6 7

private function updateProgressBar(event:TimerEvent):void{                 var myItem:Object;                  // Add a 'random' number to loaded. To fake the progress..                 myDataGrid.selectedItem.loaded += Math.ceil(Math.random() * 5);                 //refesh arraycollection to refresh the datagrid                 myArrayCollection.refresh();                            }

Then you are done. Below you will find a working example. For the full source code either use Right Mouse Click -> View Source or scroll down.

Full Source Code:
ProgressBarInsideDatagridExample.mxml

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72

<?xml version="1.0" encoding="utf-8"?> <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"                xmlns:s="library://ns.adobe.com/flex/spark"                xmlns:mx="library://ns.adobe.com/flex/halo" width="500"  height="200" initialize="init();" viewSourceURL="srcview/index.html">     <fx:Script>         <![CDATA[             import mx.collections.ArrayCollection;                         [Bindable]private var myArrayCollection:ArrayCollection;                         private function init():void {                 // Create instance of myArrayCollection                 myArrayCollection = new ArrayCollection;                 // Create new Object                 var obj:Object = new Object;                                 obj.file = "File 1";                 obj.total = 100;                 obj.loaded = 0;                 // Add object to myArrayCollection                 myArrayCollection.addItem(obj);                 obj = new Object;                 obj.file = "File 2";                 obj.total = 100;                 obj.loaded = 0;                 // Add object to myArrayCollection                 myArrayCollection.addItem(obj);             }             public function downloadFile():void{                 //start timer                 var timer:Timer = new Timer(500);                 // add event listener                 timer.addEventListener(TimerEvent.TIMER, updateProgressBar);                 timer.start();                          }             private function updateProgressBar(event:TimerEvent):void{                 var myItem:Object;                  // Add a 'random' number to loaded. To fake the progress..                 myDataGrid.selectedItem.loaded += Math.ceil(Math.random() * 5);                 //refesh arraycollection to refresh the datagrid                 myArrayCollection.refresh();                            }                                 ]]>     </fx:Script>         <fx:Declarations>         <!-- Place non-visual elements (e.g., services, value objects) here -->         </fx:Declarations>         <mx:DataGrid id="myDataGrid" height="200" width="500" dataProvider="{myArrayCollection}">         <mx:columns>             <mx:DataGridColumn width="112" headerText="Download">                 <mx:itemRenderer>                     <fx:Component>                         <mx:HBox horizontalAlign="center" verticalAlign="middle">                                 <s:Label text="{data.file}"/>                             <mx:Image buttonMode="true" toolTip="'Download'" click="outerDocument.downloadFile()" source="@Embed(source='images/down_alt.png')"/>                         </mx:HBox>                     </fx:Component>                 </mx:itemRenderer>                          </mx:DataGridColumn>                         <mx:DataGridColumn itemRenderer="myProgressBar" dataField="progress" headerText="Progress" width="180" paddingLeft="5"/>         </mx:columns>               </mx:DataGrid>     </s:Application>

myProgressBar.as

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34

package {     import mx.containers.HBox;     import mx.controls.ProgressBar;     import mx.controls.dataGridClasses.*;     public class myProgressBar extends HBox     //This should normally be extends ProgressBar, we are using HBox to have more control over the layout.     {         private var pb:ProgressBar;                 public function myProgressBar():void {             //Create new ProgressBar Instance             pb = new ProgressBar();             //Set some layout things             pb.mode = "manual";             pb.percentWidth = 100;                      pb.labelPlacement = "center";             this.setStyle("verticalAlign","middle");             //Add ProgressBar as child             addChild(pb);         }                 override public function set data(value:Object):void         {             super.data = value;         }                   override protected function updateDisplayList(unscaledWidth:Number, unscaledHeight:Number) : void{             super.updateDisplayList(unscaledWidth, unscaledHeight);             pb.setProgress(data.loaded, data.total);         }     } }

TabNavigator와 ModuleLoader 사용시 문제

TabNavigator 가 포함된 상위 노드에 creationPolicy="all" 로 해주면 어느정도 문제는 해결됨

Copy Flex UIComponent

flex DataGrid Border remove

화면 전환시 데이터그리드 외곽선이 지워지는 현상

variableRowHeight="true"

Package	flash.printing
Class	public final class PaperSize
Inheritance	PaperSize Object

The following table shows the approximate size for each paper type. The size is approximate because there is some variation among printer drivers. For example, the width of A4 paper can be 595.0, 595.2, 595.22 or 595.28 points depending on the driver.

Related API Elements

Public Properties

Hide Inherited Public Properties

Show Inherited Public Properties

	Property		Defined By
		constructor : Object A reference to the class object or constructor function for a given object instance.	Object
		prototype : Object [static] A reference to the prototype object of a class or function object.	Object

Public Methods

Hide Inherited Public Methods

Show Inherited Public Methods

	Method		Defined By
		hasOwnProperty(name:String):Boolean Indicates whether an object has a specified property defined.	Object
		isPrototypeOf(theClass:Object):Boolean Indicates whether an instance of the Object class is in the prototype chain of the object specified as the parameter.	Object
		propertyIsEnumerable(name:String):Boolean Indicates whether the specified property exists and is enumerable.	Object
		setPropertyIsEnumerable(name:String, isEnum:Boolean = true):void Sets the availability of a dynamic property for loop operations.	Object
		toLocaleString():String Returns the string representation of this object, formatted according to locale-specific conventions.	Object
		toString():String Returns the string representation of the specified object.	Object
		valueOf():Object Returns the primitive value of the specified object.	Object

In the first article of this series, I discussed how to prevent users from printing directly from Flash’s default context menu. In the second article, I wrote about using the AlivePDF library to create PDFs from your application for printing or saving. Today I will be covering how to print application data from Flex.

The Flex framework comes with several classes to assist you in printing; however, they don’t tend to produce the greatest results. The PrintDataGrid class is probably your best option when it comes to printing data, but whenever I’ve worked with it in the past I’ve always ended up disappointed. Even after formatting, there are always issues; like rows getting cut off and pages breaks in weird places.

There have been talks about AlivePDF offering a Grid class to the library, which may be interesting, but it hasn’t been released and would probably only handle DataGrid data. So the best option I’ve found for printing data is to allow a server to generate a PDF, which can then be sent back to Flex and output however you want.

A great benefit of this option is the ability to easily format the print results. You can use simple HTML and CSS to customize the printout much easier than you could using ActionScript. You can also add custom styles, letterheads, and footers to fit your needs.

Here is an example, you can view the source here.

This will work with any server-side script that can generate PDF content. In this demo I am using a ColdFusion script which simply generates an HTML table and returns it in PDF format. You can view the ColdFusion code along with the rest of the source code here.

The data from the server is returned to Flex as a ByteArray. You can take that ByteArray and output it to the user in several different ways:

Using the Browser

Similar to the last article in this series, you can send the results to a server-side script to either display the PDF in the browser or prompt the user to open or save the document. This time, however, the AlivePDF library is no longer necessary since the PDF binary has already been created.

Save locally from Flash

Thanks to new capabilities in Flash Player 10, you can also provide users the option to save the PDF directly from Flash. This eliminates the need for the second server-side script.

If you plan to use the save functionality you’ll need to set the “Required Flash Player version” in your project preferences to 10.0.0 or higher or else Flex Builder will complain. You have to remember that only users with Flash Player 10 or above will be able to use this functionality, so some type of version validation is a necessity.

Another caveat is that the save method must be triggered by some type of user interaction, that’s why the sample application prompts for system access before saving. Although the user has clicked the “Print Data” button, that event is lost when the server call is made, so we need another interaction from the user.

출처 : http://storyjava.tistory.com/52

1. 기본이 되는 인쇄 예제

*source : http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf65381-7ffc.html

*source code :  DGPrint.fxp

2. screen layout이랑 print layout 설정하기

*source : http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7c80.html

*source code : DGPrintCustomComp.fxp

3. 자동으로 페이지 나누기

*source : http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7c7e.html

*source code : MultiPagePrint.fxp

4. Advance Datagrid Print

*source : http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7c7e.html

*source code : ADGPrint.fxp

Using the FlexPrintJob class

printJob.addObject(myDataGrid);
printJob.addObject(myButton);

<?xml version="1.0"?>
<!-- printing\DGPrint.mxml -->
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml">

    <mx:Script>
        <![CDATA[
            import mx.printing.*;

            // Create a PrintJob instance.
            private function doPrint():void {
                // Create an instance of the FlexPrintJob class.
                var printJob:FlexPrintJob = new FlexPrintJob();

                // Start the print job.
                if (printJob.start() != true) return;

                // Add the object to print. Do not scale it.
                printJob.addObject(myDataGrid, FlexPrintJobScaleType.NONE);

                // Send the job to the printer.
                printJob.send();
            }
        ]]>
    </mx:Script>

    <mx:VBox id="myVBox">
        <mx:DataGrid id="myDataGrid" width="300">
            <mx:dataProvider>
                <mx:Object Product="Flash" Code="1000"/>
                <mx:Object Product="Flex" Code="2000"/>
                <mx:Object Product="ColdFusion" Code="3000"/>
                <mx:Object Product="JRun" Code="4000"/>
            </mx:dataProvider>
        </mx:DataGrid>
        <mx:Button id="myButton" 
            label="Print" 
            click="doPrint();"/>
    </mx:VBox>
</mx:Application>
The executing SWF file for the previous example is shown below:
 

Flex printing breakthrough! And more!

AlivePDF

출처 : http://flystone.tistory.com/61

SpriteVisualElement (Spark) | Flex Examples 

SpriteVisualElement 는 Flex 의 UIComponent 같은 역활을 한다.
Flex 에 Sprite 객체를 넣을 수 있는 Element 이다.

클래스명에서 보는것과 같이 Elemet 이므로 다른 컴포넌트에 넣을때에는
addChild() 가 아닌 addElement() 로  해야만 정상 작동 한다.

또한 이 엘리멘트를 사용할 때 주의해야 할 것은
아무리 addChild() 로 Sprite 객체든 다른 것들을 넣고 transform 작업을 하여도
실질적으로 이 엘리멘트에 width, height 값은 변하지 않는다.

따라서 직접적으로 width, height 를 변환해 주어야 다른 컴포넌트들과의 위치 정렬및 스크롤러 생성 등의
좌표 관련 설정이 원하는데로 나올 것 이다. 

Printing with Flex: Chapter 11 - Enterprise Development with Flex

This excerpt is from Enterprise Development with Flex. If you want to use Adobe Flex to build production-quality Rich Internet Applications for the enterprise, this groundbreaking book shows you exactly what's required. You'll learn efficient techniques and best practices, and compare several frameworks and tools available for RIA development -- well beyond anything you'll find in Flex tutorials and product documentation. Through many practical examples, the authors impart their considerable experience to help you overcome challenges during your project's life cycle.

Measuring programming progress by lines of code is like measuring aircraft building progress by weight.
--Bill Gates

In general, the process of printing from web applications works a little differently compared to printing from the desktop. Web applications have good reason for not allowing direct access to a user’s printer: malicious websites could immediately start printing their fliers on your home or corporate printer, offering you anything from pizza delivery to adult entertainment. That’s why you can’t write a program in JavaScript that would automatically detect all available printers and send them print jobs. That’s why the user is forced to manually select the printer via the web browser’s pop-up dialog window.

Existing Flash Player bugs add more issues for Flex developers; for example, the Print dialog might not report all features of the available printer, and setting such parameters as tray selection or paper size might not be possible. To put it simply, you may not have complete control over the user’s printer from an application running in Flash Player. You may need to adjust your reports to standard printer settings.

The process of printing from Flash Player consists of starting a single-threaded print job and adding dynamically created pages to it (i.e., the data that comes from a database). Unfortunately, Flash Player’s virtual machine AVM2 ActionScript timeout is 15 seconds. Accordingly, for both Flex and AIR, the interval between the following commands shouldn’t be more than 15 seconds:

If, at each of these commands, printing the specified page always completed in 15 seconds or less, your application will be able to print a multipage document, although somewhat slowly. If any of the intervals spans more than 15 seconds, however, your print job will receive a runtime exception, which turns direct printing from Flash Player into an unpleasant experience, if application developers don’t handle exceptions properly. Plus, if the internal thread that started the print job failed, it may be automatically closed and unable to be recovered properly.

You may think that setTimeout() can help break the 15-second barrier for printing, but it can’t. Printing has to be handled by the same internal AVM2 thread (apparently a bug), and with setTimeout(), you are in fact spawning a new one. The issue with printing long documents is demonstrated in Example 11.1, “PrintTimeout.mxml—an illustration of printing failure”. The PrintJob starts and the method finishPrinting() is called in the same thread and works fine. If you instead comment out the call to finishPrinting() and uncomment the method setTimeout(), this printing job will fail: the addPage() will throw an exception, because it runs in a thread different than PrintJob.

Imagine that a timeout was initiated not by calling the function setTimeout(), but rather by Flash Player during printing of a multipage document because one of the addPage() calls took longer than 15 seconds. In this case, addPage() would be called on a different internal thread than PrintJob.start() and the addPage() operation would fail, even though Flash Player should’ve known how to process a such situation properly.

<?xml version="1.0" encoding="utf-8"?>
<mx:WindowedApplication xmlns:mx="http://www.adobe.com/2006/mxml"
layout="vertical">
   <mx:Button label="Print Me" click="printMe()"/>
   <mx:Script>
      <![CDATA[

         private function printMe() :void {
            var pj:PrintJob = new PrintJob();
            pj.start();

   //           setTimeout(function() :void { finishPrinting(pj);}, 1);

                   finishPrinting(pj);
         }

         private function finishPrinting(pj:PrintJob): void {
            pj.addPage(this);
            pj.send();
         }
      ]]>
   </mx:Script>
</mx:WindowedApplication>

Example 11.1, “PrintTimeout.mxml—an illustration of printing failure” just prints itself, addPage(this), but if it had to print, say, a slow-rendered DataGrid with a couple of thousand rows, the chances are high that such a program would time out before the printing job was finished.

There is a bigger problem than the technical restrictions mentioned so far, and it is in the very approach to printing via the PrintJob API. The process of programming reports in ActionScript comes down to creating snapshots of components displayed on the users’ monitors and sending them to the printer. Because screen resolution differs from printer resolution, however, application developers pursing this method need to create separate layouts just for printing, which is time-consuming and challenging.

That’s why you should consider creating and printing your reports as PDF files. Besides, it neatly reinforces this book’s philosophy: minimize the amount of code that business application developers have to write. In this chapter, you’ll learn how to create XDP-enabled Flex components that will allow application developers to generate PDF documents on the client side with minimal coding.

import flash.net.*;
import flash.utils.ByteArray;

public class FormRenderer {
 public static function openPdf(xdp:String, target:String="_blank"):void{
   var req:URLRequest = new URLRequest("/createPDF.jsp");
   req.method = URLRequestMethod.POST;

   var ba :ByteArray = new ByteArray();;
   ba.writeMultiByte(xdp, "iso-8859-1");
   ba.compress();
   ba.position = 0;
   req.data = ba;
   navigateToURL(req, target);
 }
}

public class PanelXdp extends Panel implements IXdpObject{
    public function get xmlContent():Object{
       // The code to return representation of the panel
       // in the XDP format goes here
    }
}

<%@ page language="java"
   import="java.io.*,
   java.util.*,
   javax.xml.parsers.*,
   org.w3c.dom.Document,
   flex.messaging.*,
   flex.acrobat.pdf.XDPXFAHelper,
   flex.messaging.util.UUIDUtils,
   org.w3c.dom.Document
   "
%><%!
private static void _log(Object o){
   System.out.println(""+o);
}
private String getParam(HttpServletRequest request, String name, String defVal)
throws Exception{
       String val = request.getParameter(name);
     return (val!=null && val.length()>0)?val:defVal;
}
private String getParam(HttpServletRequest request, String name) throws Exception{
   return getParam(request, name, null);
}
private void processRenderRequest(HttpServletRequest request,
                        HttpServletResponse response) throws Exception{

   String data      = getParam(request, "document");
   String template = getParam(request, "template"); // Security hole, check path
   _log("template="+template);
   _log("data="+data);
   template = FlexContext.getServletContext().getRealPath(template);
   _log("template real="+template);

       // You must have LCDS license to use XDPXFAHelper
   XDPXFAHelper helper = new XDPXFAHelper();
   helper.open(template);
   // Import XFA dataset
   if( data!=null ){
      _log("data.length="+data.length());
      ByteArrayInputStream bais = new
                        ByteArrayInputStream(data.getBytes("UTF-8"));
      DocumentBuilderFactory builderFactory =
                                    DocumentBuilderFactory.newInstance();
      DocumentBuilder builder =
                                    builderFactory.newDocumentBuilder();
      Document dataset = builder.parse(bais);
      helper.importDataset(dataset);
   } else
      _log("data="+null);

   byte[] content = helper.saveToByteArray();
   _log("content="+content);
   helper.close();
   ServletOutputStream out3 = response.getOutputStream();
   response.setContentType("application/pdf");
   response.setContentLength(content.length);
   out3.write(content);
}
%><%
_log("");
_log("--------------------------------------------");
_log("render.jsp");
processRenderRequest(request, response);
%>

PDF Generation on the Client

AlivePDF is an open source library for generating PDFs in ActionScript on the client side. It’s offered under the MIT license at http://alivepdf.org; download AlivePDF.swc and link it to your Flex Builder project. One of the classes included in AlivePDF.swc is called PDF.

Note

Unless you are developing an AIR application or deploying it for Flash Player 10 (see the next note), even client-generated PDF content has to be sent to a server that will just bounce it back (see Example 11.20, “PDFServlet.java”) to have the web browser open the Acrobat Reader plug-in.

Basic Printing with AlivePDF

The process of generating PDFs in AlivePDF starts with instantiation of the PDF class, specifying the print orientation, units of measurement, and the paper size. Then you create and add pages to the instance of the PDF object, and finally you call the function savePdf() to turn these pages into a ByteArray and save them to the PDF file on your filesystem if you use Adobe AIR. If this is a web application written in Flex, the same savePdf() function sends the ByteArray to the server with the deployed script create.php (supplied by alivepdf.org), which will return this array of bytes to your web browser as a PDF document.

Note

Starting from Flash Player 10, the FileReference class allows you to save files locally. Its function save() opens the pop-up window, allowing the user to specify the filename for saving the data. In our example, this eliminates the need for a round trip to the server that does nothing but bounce this array of bytes. Keep in mind, though, that after saving the PDF this way, the user will need to complete an extra step to open the file with Acrobat Reader or any other program.

Example 11.4, “Basic printing with AlivePDF: test1.mxml” shows the process of preparing and saving a PDF file with AlivePDF.

Example 11.4. Basic printing with AlivePDF: test1.mxml

<?xml version="1.0" encoding="utf-8"?>
    <mx:WindowedApplication xmlns:mx="http://www.adobe.com/2006/mxml"
   layout="vertical" horizontalAlign="center" verticalAlign="middle">

   <mx:Button label="Hello World!!!" click="hw()"/>

 <mx:Script><![CDATA[

   import org.alivepdf.fonts.Style;
   import org.alivepdf.fonts.FontFamily;
    import org.alivepdf.saving.Method;
    import org.alivepdf.layout.Size;
    import org.alivepdf.layout.Unit;
        import org.alivepdf.layout.Orientation;
    import org.alivepdf.pdf.PDF;

  private function hw():void{

   var p:PDF = new PDF(Orientation.PORTRAIT, Unit.MM, Size.A4);
   p.addPage();
   p.setFont(FontFamily.ARIAL, Style.NORMAL, 12);
   p.addText("10x10", 10, 10);
   p.addText("100x100", 100, 100);
   p.addMultiCell(50, 8, "Hello World2");

   savePdf(p, "hw.pdf");
 }

 private function savePdf(p:PDF, fileName:String):void{

   var ba:ByteArray = p.save(Method.LOCAL);
   var fs:FileStream = new FileStream();
   var f:File = File.desktopDirectory.resolvePath(fileName);
   fs.open(f, FileMode.WRITE);

   try{
      fs.writeBytes(ba);
   } catch (e:*){}

     fs.close();
 }
]]></mx:Script>

</mx:WindowedApplication>

After you click the button Hello World!!! (see the example code), a file called hw.pdf is created in the AIR desktop directory (see Chapter 9, Working with Adobe AIR for details). For example, Figure 11.1, “Sample output of the AlivePDF program” shows our hw.pdf file, which was saved in the directory C:\Documents and Settings\Administrator\Desktop.

Figure 11.1. Sample output of the AlivePDF program

The goal here was to give you a taste of the process of preparing the document with AlivePDF. To investigate the complete set of AlivePDF’s APIs, visit http://AlivePDF.org.

AlivePDF does a good job of creating objects and assembling them into pages, which are then converted into a PDF format. But it still requires you to prepare (in addition to the screen version) a second copy of the UI to be printed. It’s not what-you-see-is-what-you-get (WYSIWYG) programming. This process requires manual allocation and measurements of each object in the PDF-to-be.

Note

The blog http://alivepdf.bytearray.org is yet another good source of up-to-date information regarding AlivePDF.

Enhancing AlivePDF

What can be done to improve this process? We still want to use AlivePDF’s printing engine, but we don’t want to manually write the code specifying styles and measurements as we did in Example 11.4, “Basic printing with AlivePDF: test1.mxml”. In this section, you’ll see how to create components and containers that are smart enough to present themselves as PDF or XDP objects.

Note

All examples from this section are located in the Flex Builder project called clientPdfAir (which comes with this chapter; see the Preface for information on obtaining the sample code) and are self-contained AIR applications. alivePDF.swc has to be present in the build path of the project.

The program test2.mxml in Example 11.5, “Printing with AlivePDF from an AIR application” illustrates Flex-to-PDF-object conversion, a big difference compared to test1.mxml. It uses the ActionScript class AlivePdfPrinter, which is included with the code samples of this chapter. Its addObject() method converts a given Flex object to corresponding PDF snippets, one at a time. You don’t need to worry about the sizes, locations, fonts, or styles of these objects. This is WYSIWYG. Flash Player is a rendering engine here.

Example 11.5. Printing with AlivePDF from an AIR application

<?xml version="1.0" encoding="utf-8"?>
    <mx:WindowedApplication xmlns:mx="http://www.adobe.com/2006/mxml"
     xmlns:printer="com.farata.printing.pdf.client.*"
   layout="vertical" >
   <mx:Style source="main.css"/>
   <mx:Canvas width="100%" height="100%" backgroundColor="white">
     <mx:Label id="lbl1" text="Hello" x="10" y="10"/>
     <mx:Label id="lbl2" text="World" x="50" y="30" fontWeight="bold"/>
          <mx:Label id="lbl3" text="And" x="150" y="60" fontStyle="italic"
                                                        enabled="false"/>
     <mx:Label id="lbl4" text="Happy" x="70" y="90" fontSize="16"
                                         textDecoration="underline"/>
         <mx:Label id="lbl5" text="New Year" x="50" y="140" fontSize="24"
                                        fontWeight="bold" color="green"/>
     <mx:Button id="btn1" label="Button1" x="70" y="240"/>
   </mx:Canvas>

 <mx:ApplicationControlBar width="100%">
   <mx:Label text="File name:"/>
   <mx:TextInput id="txtFileName" text="hw2.pdf"/>
   <mx:Button label="Save PDF" click="printPdf()"/>
     </mx:ApplicationControlBar>

   <printer:AlivePdfPrinter id="prn" printComplete="viewPdf()"/>
<mx:Script><![CDATA[

  import flash.net.URLRequest;

  private var file:File;

  private function printPDF():void{

   prn.addObject(lbl1);
   prn.addObject(lbl2);
   prn.addObject(lbl3);
   prn.addObject(lbl4);
   prn.addObject(lbl5);
   prn.addObject(btn1);

   file = prn.printToFile (txtFileName.text);
 }

 private function viewPdf():void{
   var req:URLRequest = new URLRequest(file.url);
   navigateToURL(req, "_blank");
}

]]></mx:Script>

</mx:WindowedApplication>

The code in Example 11.5, “Printing with AlivePDF from an AIR application” produces the screen as it’s shown in the AIR runtime, on the left in Figure 11.2, “The results of printing with enhanced AlivePDF”. On the right side, you can see the hw2.swf file produced by this program and shown in Adobe Acrobat. The fonts in the Acrobat Reader image look smaller because of the small zoom percentage.

Figure 11.2. The results of printing with enhanced AlivePDF

The listings that follow do not include the entire source code of the class AlivePdfPrinter; that comes with the source code of this chapter’s samples. The idea is to have a set of components that can expose their information in a form suitable for printing. The method AlivePdfPrinter.addObject(o) calls locateExtension(), which instantiates the appropriate object that can present itself in a form suitable for AlivePDF (Example 11.6, “The method AlivePdfPrinter.locateExtension()”).

Example 11.6. The method AlivePdfPrinter.locateExtension()

private static function locateExtension(o:*):IPdfPrinterExtension{
  if( o is Label )
   return new LabelPdfExtension(/*o*/);
  if( o is PdfPrintDataGrid )
   return new PdfPrintDataGridPdfExtension(/*o*/);
  if( o is DataGrid )
   return new DataGridPdfExtension(/*o*/);
  if( o is Container )
   return new ContainerPdfExtension(/*o*/);
  if( o is UIComponent )
   return new UIComponentPdfExtension(/*o*/);
 return null;
}

After identifying the type of the object to be printed, the object exposes its font and style information that’s being passed to the AlivePDF’s PDF object for printing. Example 11.7, “The addObject() method in the LabelPdfExtension class” shows the function addObject() from the ActionScript class com.farata.printing.pdf.client.extensions.LabelPdfExtension.

Example 11.7. The addObject() method in the LabelPdfExtension class

public function addObject(o:*, printer:IAlivePdfPrinter):void{
 var pdf:PDF = printer.pdf;
   var c:Label = Label(o);
   if( c==null ) return;
   if( !c.visible )
      return;

   var fontFamily:String = c.getStyle("fontFamily");
   if( fontFamily==null )
      fontFamily = FontFamily.ARIAL;

   var style:String = "";

   if( c.getStyle("fontWeight")=="bold" )
       style += "B";

   if( c.getStyle("fontStyle")=="italic" )
      style += "I";
   if( c.getStyle("textDecoration")=="underline" )
        style += "U";

   var size:int = c.getStyle("fontSize");
   var color:Color = new RGBColor(c.getStyle(c.enabled?"color":"disabledColor"));

   allocateSpace(c, printer);

   pdf.textStyle(color/*, alpha*/);
   pdf.setFont(fontFamily, style, pxToPt(size));

   var ptText:PPoint = mapPoint(c, printer);
   ptText.y.px += c.height;

   pdf.addText(c.text, ptText.x.pt, ptText.y.pt);

 }

Example 11.7, “The addObject() method in the LabelPdfExtension class”’s code gets the styles, font, and text from the Flex Label object and initializes appropriate properties of the PDF object per the requirements of the AlivePDF library.

The sample code of this chapter as well as the clear.swc library has several similar extensions for a number of Flex components (see com.farata.printing.swc), and you can keep adding more objects to your own business framework of PDF-ready components.

These extensions are not subclasses of corresponding Flex components, but rather utility classes that know how to present the content of components to AlivePDF.

Note

While writing the method addObjects() for your components, keep in mind that measurements in Flash Player are in pixels and you may need to convert them into other units required by the AlivePDF API.

If you’d like to see what’s inside the generated hw2.pdf file, just open it with any text editor; you’ll see something like Example 11.8, “A fragment of the h2.pdf content” (which is just a fragment of the file).

Example 11.8. A fragment of the h2.pdf content

%PDF-1.4
1 0 obj
<</Type /Pages
/Kids [3 0 R
]
/Count 1
>>
endobj
3 0 obj
<</Type /Page
/Parent 1 0 R
/MediaBox [0 0 595.28 841.89]
/Resources 2 0 R
/Rotate 0
/Dur 3
/Contents 4 0 R>>
endobj
4 0 obj
<</Length 780>>
stream
2 J
0.57 w
0 Tr
/GS0 gs
0 Tw 0 Tc 100 Tz 0 TL
BT /F1 7.00 Tf ET
q 0.043137254901960784 0.2 0.23529411764705882 rg BT 25.50 802.14 Td (Hello) Tj ET
Q
0 Tr
/GS1 gs
0 Tw 0 Tc 100 Tz 0 TL
BT /F2 7.00 Tf ET
q 0.043137254901960784 0.2 0.23529411764705882 rg BT 55.50 787.89 Td (World) Tj ET
Q
0 Tr
/GS2 gs
0 Tw 0 Tc 100 Tz 0 TL
BT /F3 7.00 Tf ET
q 0.6666666666666666 0.7019607843137254 0.7019607843137254 rg BT 130.50 764.64 Td
(And) Tj ET Q
0 Tr
/GS3 gs
0 Tw 0 Tc 100 Tz 0 TL
BT /F1 12.00 Tf ET
q 0.043137254901960784 0.2 0.23529411764705882 rg BT 70.50 738.39 Td (Happy) Tj ET
70.50 737.19 34.68 0.60 re f Q
0 Tr
/GS4 gs
0 Tw 0 Tc 100 Tz 0 TL
BT /F2 18.00 Tf ET
q 0 0.5019607843137255 0 rg BT 55.50 692.64 Td (New Year) Tj ET Q
/GS5 gs
q 47.25 0 0 16.50 52.50 645.39 cm
/I1 Do Q
endstream
endobj
5 0 obj
<</Type /ExtGState
/SA true
/CA 1
/n 5
/BM /Normal
/ca 1
>>
endobj
...
15 0 obj
<<
/Producer (Alive PDF 0.1.4.6)
/CreationDate (D:200905152226)
>>
endobj
16 0 obj
<<
/Type /Catalog
/Pages 1 0 R
/OpenAction [3 0 R /FitH null]
/PageLayout /SinglePage
>>
endobj
xref
...
trailer
<<
/Size 17
/Root 16 0 R
/Info 15 0 R
>>
startxref
2467
%%EOF

Note

After this chapter was written, a new open source library called purePDF became available. It's an ActionScript port of a popular Java library called iText. You can download purePDF at http://code.google.com/p/purepdf/.

Printing Flex Containers

All these extensions for Flex controls are great, but there is another issue to tackle: Flex views often use containers. For example, you need to be able to generate a PDF for a DataGrid in two formats. This object should be similar to mx.printing.PrintDataGrid, but it should support PDF printing rather than working with PrintJob. It should support pagination, headers, and footers; this is a must for printing multipage documents.

Or imagine a TabNavigator container from which you need to print the content of each tab as a separate multipage PDF. The goal is to have a container that can iterate its children and tell each of them, “Hey, kiddo, print yourself.” When this mission is accomplished, just implement the same behavior to allow containers (and components) to expose themselves in the XDP format, too.

Sample extensions for the most complex Flex components, such as DataGrid, DataGridItemRenderer, and Canvas, are supplied as code samples for this chapter. Use them as a guide for the creation of your own printing extensions.

For example, the application test4.mxml includes the PdfPrintDataGrid component from clear.swc and outputs the data grid to the file hw4.pdf, as shown in Figure 11.3, “Running test4.mxml (left) generates PDF hw4 (right)” and Example 11.9, “An AIR application to print a data grid to a PDF file”.

Figure 11.3. Running test4.mxml (left) generates PDF hw4 (right)

Example 11.9. An AIR application to print a data grid to a PDF file

<?xml version="1.0" encoding="utf-8"?>
<mx:WindowedApplication xmlns:mx="http://www.adobe.com/2006/mxml"
  xmlns:printer="com.farata.printing.pdf.client.*"
  layout="vertical"
  creationComplete="onCreationComplete(event)" >

   <mx:DataGrid id="dg" x="0" y="0"
   width="100%" height="100%" >

    <mx:columns>
      <mx:DataGridColumn dataField="name" headerText="Name"/>
      <mx:DataGridColumn dataField="phone" headerText="Phone"/>
      <mx:DataGridColumn dataField="email" headerText="E-mail"/>
    </mx:columns>
   </mx:DataGrid>

   <mx:ApplicationControlBar width="100%">
    <mx:Label text="File name:"/>
    <mx:TextInput id="txtFileName" text="hw4.pdf"/>
     <mx:Button label="Save PDF" click="doSavePdf()"/>
   </mx:ApplicationControlBar>

   <printer:AlivePdfPrinter id="prn" printComplete="viewPdf()"/>

<mx:Script><![CDATA[

import flash.net.URLRequest;
private var file:File;

private function onCreationComplete(evt:*):void{

   var array:Array = [];

   for(var i:int=1; i<=30; i++){
       var obj:Object = new Object();
      obj.name   = "User " +i;
      obj.phone  = "555-219-227"+i;
      obj.email  = "user"+i+"@hello.world";
      obj.active = (i % 2 ) == 1;
      array.push(obj);

   }
   dg.dataProvider = array;
}
private function printPdf():void{

   prn.addObject(dg);
   file = prn.printToFile(txtFileName.text);
}

private function viewPdf():void{
   var req:URLRequest = new URLRequest(file.url);
   navigateToURL(req, "_blank");
}

]]></mx:Script>
</mx:WindowedApplication>

The line:

prn.addObject(dg);

results in invoking the code from Example 11.6, “The method AlivePdfPrinter.locateExtension()”, and the DataGridPdfExtension class shown in Example 11.10, “Class DataGridPdfExtension” is engaged.

Example 11.10. Class DataGridPdfExtension

package com.farata.printing.pdf.client.extensions{

   import com.farata.printing.PdfPrintDataGrid;

   import com.farata.printing.pdf.client.IAlivePdfPrinter;
   import mx.controls.DataGrid;

   public class DataGridPdfExtension extends BasePdfExtension{

    override public function addObject(o:*, printer:IAlivePdfPrinter):void{

     var c:DataGrid = o as DataGrid;
      var p:PdfPrintDataGrid = new PdfPrintDataGrid();
      p.x = c.x;
       p.y = c.y;
     p.width = c.width;
     p.height = c.height;
     p.columns = c.columns;
     p.dataProvider = c.dataProvider;

      c.parent.addChild(p);
     printer.addObject(p);
     c.parent.removeChild(p);
   }

 }
}

If in Example 11.6, “The method AlivePdfPrinter.locateExtension()” all components were located inside, say, Canvas, and the printing extensions for this container were ready, this code sample would become even shorter—something like this:

prn.addObject(myCanvas);

The myCanvas component would’ve taken care of its kids.

The good news is that you don’t have to write printing extensions to all components. The code in Example 11.6, “The method AlivePdfPrinter.locateExtension()” checks to see whether the component is an instance of Label, DataGrid, or Container.

Part of the sample code in the test3.mxml application has a canvas:

<mx:Canvas id="canvas" width="100%" height="100%"
      backgroundColor="white">

   <mx:Label id="lbl1" text="Hello" x="100" y="10"/>
    <mx:Label id="lbl2" text="World" x="50" y="30" fontWeight="bold"/>
    <mx:Label id="lbl3" text="And" x="150" y="60" fontStyle="italic"
              enabled="false"/>
    <mx:Label id="lbl4" text="Happy" x="90" y="90" fontSize="16"
                                      textDecoration="underline"/>
   <mx:Label id="lbl5" text="New Year" x="80" y="140" fontSize="24"
     fontWeight="bold" color="green"/>
   <mx:Button id="btn1" label="Button1" x="1" y="1"/>
    <mx:Button id="btn2" label="Button2" x="10" y="100"/>

    <mx:HBox x="250" y="130" borderThickness="3" borderColor="blue"
       borderStyle="solid"   backgroundColor="yellow">
      <mx:Label text="Inside HBox" color="gray"/>
   </mx:HBox>
</mx:Canvas>

The code to print this Canvas is pretty simple: just pass a reference to the class AlivePdfPrinter, and it’ll figure out how to print its child components:

private function printPdf():void{
   prn.addObject(canvas);
   file = prn.printToFile(txtFileName.text);
}

The function addObject() tries to locate an extension class for Canvas as shown in Example 11.6, “The method AlivePdfPrinter.locateExtension()”, and will use the ContainerPdfExtension, because Canvas is a Container. Should you want to provide some functionality specific to Canvas, you need to create CanvasPdfExtension and modify the code in Example 11.6, “The method AlivePdfPrinter.locateExtension()” accordingly.

A fragment of ContainerPdfExtension is shown in Example 11.11, “The main part of ContainerPdfExtension”.

Example 11.11. The main part of ContainerPdfExtension

package com.farata.printing.pdf.client.extensions{
 public class ContainerPdfExtension extends BasePdfExtension{

   private static var s_offsetLock:int = 0;

   override public function addObject(o:*, printer:IAlivePdfPrinter):void{

    s_offsetLock++;
    var c:Container = Container(o);
    setOffset(c, printer);
    allocateSpace(c, printer);
    drawBackgroundAndBorder(c, printer);

     var len:int = c.numChildren;
    for(var i:int=0; i<len; i++){
      var ch:DisplayObject = c.getChildAt(i);
      printer.addObject(ch);
    }

    s_offsetLock--;
    }

   private  function setOffset(o:Container, printer:IAlivePdfPrinter):void{
     if( s_offsetLock==1 ) {
      var ptLocal:Point = new Point(o.x, o.y);
        var ptGlobal:Point = o.parent.localToGlobal(ptLocal);
        printer.lastOffset.x.px = ptGlobal.x;
        printer.lastOffset.y.px = ptGlobal.y;
     }
    }
 }

}

All other components that the code in Example 11.6, “The method AlivePdfPrinter.locateExtension()” won’t recognize will be printed as prescribed in the UIComponentPdfExtension as a snapshot of an image (Example 11.12, “Printing a Flex object as an image”).

Example 11.12. Printing a Flex object as an image

public function addObject(o:*, printer:IAlivePdfPrinter):void{

   if( !o.visible ) return;
   var c:UIComponent = o;
   var pdf:PDF = printer.pdf;
   var rc:PRectangle = new PRectangle();
   rc.left.px = c.x;

   rc.top.px = c.y;
   rc.right.px = rc.left.px+c.width;
   rc.bottom.px = rc.top.px+c.height;

   printer.allocateSpace(rc);
   pdf.addImage(c, rc.left.pt, rc.top.pt, rc.right.pt-rc.left.pt,
   rc.bottom.pt-rc.top.pt);
}

Of course, it’s better not to use a bitmap but instead a PDF representation specific to a component, which will allow Acrobat Reader to recognize its text content and generate searchable documents rather than bitmaps.