Patrick Heinzelmann » Technologie

September 2010
M	D	M	D	F	S	S
« Aug
	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

8. Oktober 2009

LiveCycle Mosaic, Livecycle LaunchPad and LiveCycle Workspace Mobile for LiveCycle ES 2

Filed under: AIR,Adobe,Flex,LiveCycle ES,iPhone — Patrick | 19:12

The next version of Adobe LiveCycle will shipped soon and Adobe presented some of the new feature and applications at Adobe MAX in Los Angeles. Adobe presented a LiveCycle Workspace Mobile, a mobile version of Workspace for the Apple iPhone, BlackBerry RIM and Windows Mobile. The iPhone application of Adobe Workspace is now available at the Apple iTunes. The mobile clients will only work together with the upcoming version of LiveCycle ES.

LiveCycle LaunchPad is an other new client, which will be available with LiveCycle ES 2. LaunchPad is a desktop application based on Adobe AIR and enables the user to create PDF or secure documents via Drag and Drop. Developers can easly extend LauchPad with their own processes.

An other new feature of LiveCycle ES 2 is LiveCycle Mosaic. LiveCycle Mosaic is a framework, which let you build rich internet applications based on existing entreprise applications. The information of a existing application will presented as a “Tile” in Mosiac and the different tiles can interaction to exchange information and trigger actions. You can use Flex and HTML to build the tiles.

More information about all the new stuff of LiveCycle can found the Adobe website or watch the Adobe MAX keynote.

Adobe LiveCycle ES 2 LiveCycle LaunchPad LiveCycle Mosaic LiveCycle Workspace Mobile

Comments (0)

6. Oktober 2009

Flash applications for the Apple iPhone

Filed under: Adobe,Flash,iPhone — Patrick | 16:32

Adobe announced Flash applications for the iPhone at the keynote of Adobe Max 2009. With the upcoming version of Flash Professional (CS5), Adobe provides the possiblity to export Flash applications as native iPhone applications. Flash CS5 converts the ActionScript3 projects and creates ipa files, which can submitted to Apple iPhone AppStore. Six Flash based samples apps are already available at the AppStore, more details can found here. So, this solution let you build iPhone application with your existing skills and tool set, no Xcode or Objective-C needed.

Furthermore, their is no Flash Plugin for the Browser Safari available. Since yesterday, Adobe had also set up a new website, when you try to install Flash player on the iPhone. Adobe get it to the point why it’s not available Check out the link.

This is the MystHackers video from the Adobe Max Keynote with Kevin Lynch (CTO) and Johnny Loiacono (SVP Creative Suite Unit) test possiblities how to get Flash on the iPhone.

An other interesting fact about this soultion is that you need no Mac computer anymore to build iPhone applicatons.

More information about Flash apps for iPhone can founded on:

Adobe Labs
Adobe DevNet Article
Adobe TV (Video below)

Adobe Max 2009 Flash Professional CS5 iPhone

Comments (0)

16. Mai 2009

Using annotated RemoteServices with the Spring BlazeDS Integration

Filed under: Adobe,BlazeDS,Flex,Technologie — Patrick | 19:30

On Wednesday, I found the time to test the annotation based configuration of the Spring BlazeDS Integration. Because it isn’t as easy as I thought, I wrote this little guide with all necessary configurations. You can download the sample project here.

First you have to create a new Flex Project in Flex Builder, select as Application server type “J2EE” and use LiveCycle Data Service as Remoting. Click the button “Next”.

Now you have to select the BlazeDS WAR file and click the button “Finish”.

Under Project > Properties > Flex Compiler you have add -services and behind the path to the services-config.xml (Screenhot), like in all other BlazeDS oder LiveCycle DS Applications. During the compile process the compiler creates an Actionscript class with the information of this file. The services-config.xml can found under the WEB-INF/flex. This file contains the definition of the MessageBroker and references to the messaging-config.xml and the remoting-config.xml. In the remoting-config.xml, you can find the definitions of the RemoteObjects and in the messaging-config.xml all messaging configurations.

You can delete these two files because the RemoteObjects and Messaging will now defined in your Spring application. You must also delete the references to these files in the services-config.xml. The content of the services-config.xml should now look like this.

<?xml version="1.0" encoding="UTF-8"?>
<services-config>
 
    <services>
        <service-include file-path="proxy-config.xml" />
 
        <default-channels>
           <channel ref="my-amf"/>
        </default-channels>
 
    </services>
 
 
    <security>
        <login-command class="flex.messaging.security.TomcatLoginCommand" server="Tomcat"/>
        <!-- Uncomment the correct app server
        <login-command class="flex.messaging.security.TomcatLoginCommand" server="JBoss">
		<login-command class="flex.messaging.security.JRunLoginCommand" server="JRun"/>        
        <login-command class="flex.messaging.security.WeblogicLoginCommand" server="Weblogic"/>
        <login-command class="flex.messaging.security.WebSphereLoginCommand" server="WebSphere"/>
        -->
 
        <!-- 
        <security-constraint id="basic-read-access">
            <auth-method>Basic</auth-method>
            <roles>
                <role>guests</role>
                <role>accountants</role>
                <role>employees</role>
                <role>managers</role>
            </roles>
        </security-constraint>
         -->
    </security>
 
    <channels>
 
        <channel-definition id="my-amf" class="mx.messaging.channels.AMFChannel">
            <endpoint url="http://{server.name}:{server.port}/{context.root}/messagebroker/amf" class="flex.messaging.endpoints.AMFEndpoint"/>
        </channel-definition>
 
        <channel-definition id="my-secure-amf" class="mx.messaging.channels.SecureAMFChannel">
            <endpoint url="https://{server.name}:{server.port}/{context.root}/messagebroker/amfsecure" class="flex.messaging.endpoints.SecureAMFEndpoint"/>
            <properties>
                <add-no-cache-headers>false</add-no-cache-headers>
            </properties>
        </channel-definition>
 
        <channel-definition id="my-polling-amf" class="mx.messaging.channels.AMFChannel">
            <endpoint url="http://{server.name}:{server.port}/{context.root}/messagebroker/amfpolling" class="flex.messaging.endpoints.AMFEndpoint"/>
            <properties>
                <polling-enabled>true</polling-enabled>
                <polling-interval-seconds>4</polling-interval-seconds>
            </properties>
        </channel-definition>
 
	<channel-definition id="my-longpolling-amf" class="mx.messaging.channels.AMFChannel">
		<endpoint url="http://{server.name}:{server.port}/{context.root}/messagebroker/amflongpolling" class="flex.messaging.endpoints.AMFEndpoint"/>
		<properties>
			<polling-enabled>true</polling-enabled>
			<polling-interval-seconds>5</polling-interval-seconds>
			<wait-interval-millis>60000</wait-interval-millis>
			<client-wait-interval-millis>1</client-wait-interval-millis>
			<max-waiting-poll-requests>200</max-waiting-poll-requests>
                	<user-agent-settings>
				<!-- MSIE 5, 6, 7 default max number of permanent HTTP connections is 2. -->
				<user-agent match-on="MSIE" max-streaming-connections-per-session="1"/>
				<!-- MSIE 8 max number is 6. -->
				<user-agent match-on="MSIE 8" max-streaming-connections-per-session="5"/>
				<!-- Firefox 1, 2 max number is 2. --> 
				<user-agent match-on="Firefox" max-streaming-connections-per-session="1"/>
				<!-- Firefox 3 max number is 6. -->
				<user-agent match-on="Firefox/3" max-streaming-connections-per-session="5"/>
				<!-- Safari 3, 4 max number is 4. -->  
				<user-agent match-on="Safari" max-streaming-connections-per-session="3"/>
				<!-- Chrome 0, 1, 2 max number is 6. -->
				<user-agent match-on="Chrome" max-streaming-connections-per-session="5"/>
				<!-- Opera 7, 9 max number is 4.-->
				<user-agent match-on="Opera" max-streaming-connections-per-session="3"/>
				<!-- Opera 8 max number is 8. -->  
				<user-agent match-on="Opera 8" max-streaming-connections-per-session="7"/>
				<!-- Opera 10 max number is 8. -->
				<user-agent match-on="Opera 10" max-streaming-connections-per-session="7"/>
                	</user-agent-settings>
		</properties>
	</channel-definition>        
 
        <channel-definition id="my-streaming-amf" class="mx.messaging.channels.StreamingAMFChannel">
            <endpoint url="http://{server.name}:{server.port}/{context.root}/messagebroker/streamingamf" class="flex.messaging.endpoints.StreamingAMFEndpoint"/>
        </channel-definition>
 
        <!--
        <channel-definition id="my-http" class="mx.messaging.channels.HTTPChannel">
            <endpoint url="http://{server.name}:{server.port}/{context.root}/messagebroker/http" class="flex.messaging.endpoints.HTTPEndpoint"/>
        </channel-definition>
 
        <channel-definition id="my-secure-http" class="mx.messaging.channels.SecureHTTPChannel">
            <endpoint url="https://{server.name}:{server.port}/{context.root}/messagebroker/httpsecure" class="flex.messaging.endpoints.SecureHTTPEndpoint"/>
            <properties>
                <add-no-cache-headers>false</add-no-cache-headers>
            </properties>
        </channel-definition>
        -->
    </channels>
 
    <logging>
        <target class="flex.messaging.log.ConsoleTarget" level="Warn">
            <properties>
                <prefix>[BlazeDS] </prefix>
                <includeDate>false</includeDate>
                <includeTime>false</includeTime>
                <includeLevel>false</includeLevel>
                <includeCategory>false</includeCategory>
            </properties>
            <filters>
                <pattern>Endpoint.*</pattern>
                <pattern>Service.*</pattern>
                <pattern>Configuration</pattern>
            </filters>
        </target>
    </logging>
 
    <system>
        <redeploy>
            <enabled>false</enabled>
            <!-- 
            <watch-interval>20</watch-interval>
            <watch-file>{context.root}/WEB-INF/flex/services-config.xml</watch-file>
            <watch-file>{context.root}/WEB-INF/flex/proxy-config.xml</watch-file>
            <watch-file>{context.root}/WEB-INF/flex/remoting-config.xml</watch-file>
            <watch-file>{context.root}/WEB-INF/flex/messaging-config.xml</watch-file>
            <watch-file>{context.root}/WEB-INF/flex/data-management-config.xml</watch-file>
            <touch-file>{context.root}/WEB-INF/web.xml</touch-file>
             -->
        </redeploy>
    </system>
 
</services-config>

Now you have to configurate the Dispatcher Servlet, which get the information from the Flex application. Normally, you can find the definition of the MessageBroker Servlet in the web.xml. The Spring BlazeDS integration defines the MessageBroker in applicationContext.xml and uses a Dispatcher Servlet to transfer the Flex request to the MessageBroker. So, you have to replace the Flex related configuration in the web.xml. The file should now look like this:

<?xml version="1.0" encoding="UTF-8"?>
<web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
	<display-name>AnnotatedService</display-name>
 
	<context-param>
		<param-name>contextConfigLocation</param-name>
		<param-value>
			/WEB-INF/config/web-application-config.xml
		</param-value>
	</context-param>
 
 
	<listener>
		<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
	</listener>
 
	<servlet>
		<servlet-name>dispatcherServlet</servlet-name>
		<servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
		<load-on-startup>1</load-on-startup>
	</servlet>
 
	<servlet-mapping>
    	<servlet-name>dispatcherServlet</servlet-name>
    	<url-pattern>/messagebroker/*</url-pattern>
 	</servlet-mapping>
 
     <welcome-file-list>
		<welcome-file>main.html</welcome-file>
	</welcome-file-list>
</web-app>

Now, you need a configuration file for the DispatcherServlet. Because I named the DispatcherServlet instance “dispatcherServlet”, I have to create a file with the name “dispatcherServlet-servlet.xml” in the folder WEB-INF.

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd">
 
</beans>

The next step is to configurate the MessageBroker in applicationContext.xml. Till now, you can use also for not annotated configuration of Spring BlazeDS integration.

	<flex:message-broker>
		<flex:message-service default-channels="my-streaming-amf,my-longpolling-amf,my-polling-amf" />
	</flex:message-broker>

A annotated configuration needs some additional lines to scan the source for the spring annotations. The base-package specifies where Spring should start to search for annotations.

	<context:annotation-config />
	<context:component-scan base-package="org.company" />

The applicationContext.xml should look like this:

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
	xmlns:flex="http://www.springframework.org/schema/flex"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xmlns:context="http://www.springframework.org/schema/context"
	xsi:schemaLocation="
		http://www.springframework.org/schema/beans
		http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
		http://www.springframework.org/schema/flex 
		http://www.springframework.org/schema/flex/spring-flex-1.0.xsd
		http://www.springframework.org/schema/context
		http://www.springframework.org/schema/context/spring-context-2.5.xsd">
 
	<context:annotation-config />
	<context:component-scan base-package="org.company" />
 
	<flex:message-broker>
		<flex:message-service default-channels="my-streaming-amf,my-longpolling-amf,my-polling-amf" />
	</flex:message-broker>
 
</beans>

The last step is to add the annotation in the Java class. You have to add the @Services, the @RemoteDestintion and the protocol you will use for the transfer above the class definition. When a method should be accessable via BlazeDS, you have to add above this method @RemoteInclude annotation otherwhise the @RemoteExclude annotation.

package test;
 
import org.springframework.flex.remoting.RemotingDestination;
import org.springframework.flex.remoting.RemotingExclude;
import org.springframework.flex.remoting.RemotingInclude;
import org.springframework.stereotype.Service;
 
@Service
@RemotingDestination(channels={"my-amf","my-secure-amf"})
public class SampleService {
 
	// accessable via BlazeDS
	@RemotingInclude
	public String getMessage(String name){
		return "Hello "+name;
	}
 
	// not accessable via BlazeDS
	@RemotingExclude
	public String getMessage2(String name){
		return "Hello "+name;
	}
}

The name of the RemoteObject is same as Java class name but with the first letter is a lowercase. In my example the name of the RemoteObject is “sampleService”.

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute">
	<mx:RemoteObject id="service" destination="sampleService" result="onResult(event)" fault="onFault(event)"/>
	<mx:Script>
		<![CDATA[
			import mx.rpc.events.FaultEvent;
			import mx.rpc.events.ResultEvent;
			import mx.controls.Alert;
 
			private function getMessage():void
			{
				this.service.getMessage(inputName.text);
			}
 
			private function onResult(event:Object):void
			{
				Alert.show(event.result as String, "Spring says");
			}
 
			private function onFault(event:FaultEvent):void
			{
				Alert.show("Something was wrong :(","Fault");
			}
		]]>
	</mx:Script>
	<mx:Button label="go" click="getMessage()" x="100" y="56"/>
	<mx:TextInput id="inputName" x="100" y="26"/>
	<mx:Label x="21" y="28" text="Your Name:"/>
</mx:Application>

I hope this guide helps setting up a Spring BlazeDS application using annotations.

Annotations BlazeDS Remote Object Spring

Comments (1)

7. Mai 2009

Spring BlazeDS Integration 1.0.0.RC1 Released

Filed under: BlazeDS,Flex,Technologie — Patrick | 02:16

Today, Spring published the first Release Candiate of the Spring BlazeDS Integration. http://www.springsource.org/spring-flex

One of the new features is the annotation-based configuration of Remote Desitinations. You can include and exclude function, which should publish as Remote Objects. The annotation-based configuration really simplifies the configuration of BlazeDS, if you have a big and complex application. Loving it.

An other feature of this release is the full integration of the BlazeDS Message Service.

Next Thursday, Adobe and SpringSource having a Connect Session/eSemiar about the Spring BlazeDS Integration.

Registration: http://www.adobe.com/cfusion/event/i…2539&loc=en_us

Annotations Flex Java Message Service Remote Object Spring

Comments (0)

15. Februar 2009

Using JasperReports in your Flex Application

Filed under: Flex,Technologie — Patrick | 20:42

Last week, I came cross the Flash Viewer for JasperReports. JasperReports is an OpenSource Java Framework to build Reports based on different data sources. We’re using in our projects JasperReports to generate PDF reports, too.

The Flash Viewer Project is using the Flex SDK to render the JasperReports for the HTML or Web based application. All source files of the viewer are available, so that you can customize the viewer for your needs.

But you can’t replace a interactive Flex chart component with the report viewer, because the viewer only generates a static output of the report. You can also using the JFree Chart extensions of the JasperReports, but neither the Charts nor the Text Information are selectable. If you’re changing any data of the report, you have to fill the report again in your Java Backend and rerender the report with the viewer.

So, using the viewer make only sense if you using it as preview of the report or if your reports aren’t as complex and interactive. And the best thing about the viewer is that you can use the same source file for your web and print output.

Additional Infos:

To use the Flash Viewer, you have to setup a Java web server like (Tomcat…) and run the webapp of the Flash Viewer. You get the webapp, if you download the project zip of the Flash Viewer. To display a report, you have to compile the report definition (jrpxml file) and fill the the compiled report. After that, you can use the Flash Viewer to display the report. The project zip contains a sample report, which demostrates how to use the flash viewer.

Flex Jasper Reports

Comments (13)

19. Dezember 2008

SpringSource verÃ¶ffentlicht ersten Milestone der Spring BlazeDS Integration

Filed under: Adobe,BlazeDS,Flex,Technologie — Patrick | 23:32

Heute hat SpringSource den ersten Milestone der Spring BlazeDS Integration verÃ¶ffentlicht. Informationen zum Spring BlazeDS Integration finden sich jetzt auch auf der SpringSource Webseite, dort werden eine Referenz Dokumentation, eine JavaDoc und natÃ¼rlich auch den Downloads zur VerfÃ¼gung gestellt. ZusÃ¤tzlich gibt weitere Informationen in einem Blog und einem Forum zur Spring BlazeDS Integration.

Sobald ich selber mal ein Auge auf die Integration geworfen habe, folgen weitere Informationen.

Flex Spring

Comments (0)

18. Dezember 2008

Prana Framework wird zum Spring Actionscript Framework

Filed under: Adobe,Flex,Technologie — Patrick | 00:57

Das IoC Framework Prana von Christophe Herreman ist Spring Extension unter dem Projektnamen Spring Actionscript verfÃ¼gbar. Bei der Entwicklung von Prana wurde Java Spring Framework als Vorlage genommen und dessen Funktionsweise nachimplementiert. Spring ActionScript basiert auf ActionScript 3 und bietet IntegrationsmÃ¶glichkeiten fÃ¼r MVC Frameworks Cairngorm und PureMVC.

Spring ActionScript hat nichts mit Kooperation zwischen Adobe und SpringSource zur Integration von BlazeDS/LiveCycle DS und Spring zutun. WÃ¤hrend Adobe und SpringSource an einer Backendseitigen Integration arbeiten, kann man mit dem Spring ActionScript Framework die gleichen Dependency Injection Mechnismen im Flex Frontend nutzen, welche durch Spring fÃ¼r das Java Backend zur VerfÃ¼gung gestellt werden.

Link zur Bekanntmachung im Forum des Spring Frameworks.
Link zum Subversion von Spring Actionscript

Dependency Injection Flex Inversion of Control Prana Spring

Comments (0)

13. Dezember 2008

Adobe und SpringSource kooperieren bei der Integration von Flash und Spring Plattformen

Filed under: AIR,Adobe,Allgemein,BlazeDS,Diplomarbeit,Flex,Masterthesis,Technologie — Patrick | 00:38

Adobe und SpringSource haben bekanntgegeben, dass beide der Integration von der Adobe Flash Plattform und Spring Plattform kooperieren. Ziel der Kooperation ist es, die Entwicklung von RIA mittels BlazeDS oder LiveCycle DS und Spring zuvereinfachen. Eine erste Beta-Version der BlazeDS Spring Integration soll Mitte Dezember verfÃ¼bar sein.

Desweiteren soll ein SpringSource Adapter for Adobe LiveCycle Data Services ES entwicklet werden, welche wohl in einer der kommenden Versionen von den LiveCycle DS verfÃ¼gbar sein wird. Der Adapter soll den Data Push aus Spring direkt zu Flex ermÃ¶glichen.

Link zur gemeinsamen Pressemitteilung von Adobe und SpringSource.

Flex LiveCycle DS Spring

Comments (0)

Main

Kategorien

Kalender

Suchen

Upcoming Events

Twitter Updates

Meta

LiveCycle Mosaic, Livecycle LaunchPad and LiveCycle Workspace Mobile for LiveCycle ES 2

Flash applications for the Apple iPhone

Using annotated RemoteServices with the Spring BlazeDS Integration

Spring BlazeDS Integration 1.0.0.RC1 Released

Using JasperReports in your Flex Application

SpringSource verÃ¶ffentlicht ersten Milestone der Spring BlazeDS Integration

Prana Framework wird zum Spring Actionscript Framework

Adobe und SpringSource kooperieren bei der Integration von Flash und Spring Plattformen