Raible's Wiki: RichClient

Raible's Wiki

Raible Designs
Wiki Home
News
Recent Changes

AppFuse

Homepage
  - Korean
  - Chinese
  - Italian
  - Japanese

QuickStart Guide
  - Chinese
  - French
  - German
  - Italian
  - Korean
  - Portuguese
  - Spanish
  - Japanese

User Guide
- Korean
- Chinese

Tutorials
  - Chinese
  - German
  - Italian
  - Korean
  - Portuguese
  - Spanish

FAQ
- Korean

Latest Downloads

Other Applications

Struts Resume
Security Example
Struts Menu

Set your name in UserPreferences

Referenced by
Articles
Articles_de
Articles_pt
Articles_zh

JSPWiki v2.2.33

Hide Menu

RichClient	Search Wiki:
Your trail:

This is version 14. It is not the current version, and thus it cannot be edited.
[Back to current version] [Restore this version]

Please note that this tutorial is under development and here is not yet solved some issues. If you find any solution how to solve some problem I will very appreciate your help. Email: RadimBurget [at] seznam [.] cz

[1] About Spring-rcp
[2] Configuring Appfuse - map servlet to be listening on "ws/*" url address
[3] Configuring Appfuse - create ws servlet
[4] Configuring Appfuse - add *.jar library dependicies
[5] Configuring Appfuse - add interface to allow remote clients login
[6] Configuring RichClient - TODO
[7] Unsolved issues

About Spring-rcp [#1]

The goal of the spring-richclient project

is to provide a viable option for developers that need a platform and a 'best-practices' guide forconstructing professional Swing applications quickly.

My work is based on Spring-rcp Petclinic Demo (in CVS only) is

Configuring Appfuse - map servlet to be listening on "ws/*" url address [#2]

Add this part of code to metadata/web/servlets.xml

    <!-- REMOTE ACCESS SERVELTET -->
	<servlet>
		<servlet-name>ws</servlet-name>
		<servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
		<load-on-startup>2</load-on-startup>
	</servlet>

 	<!--
	  - Dispatcher servlet mapping for HTTP web services.
	  - (see ws-servlet.xml for the controllers).
	  -->
	<servlet-mapping>
		<servlet-name>ws</servlet-name>
		<url-pattern>/ws/*</url-pattern>
	</servlet-mapping>

Configuring Appfuse - create ws servlet[#3]

Create ws servlet XML beans descriptor. While I am using Hessian

instead of Burlap

I have commented unused part of code. If you will ever want to use the burlap instead hessian uncomment this part of code.

Difference between Hessian and Burlap is that Hessian is binary and Burlap XML based.

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd">

<!--
  - $Id: ws-servlet.xml,v 1.1 2004/08/01 23:03:20 benalex Exp $
  -->
<beans>

	<!-- Hessian exporter for the Clinic -->
	<!-- Hessian is a slim binary HTTP remoting protocol -->
	<bean name="/Clinic-hessian" class="org.springframework.remoting.caucho.HessianServiceExporter">
		<property name="service"><ref bean="userManager"/></property>
		<property name="serviceInterface">
			<value>org.appfuse.service.UserManager</value>
		</property>
	</bean>

	<!-- Burlap exporter for the Clinic -->
	<!-- Burlap is a slim XML-based HTTP remoting protocol -->
	<!--bean name="/Clinic-burlap" class="org.springframework.remoting.caucho.BurlapServiceExporter">
		<property name="service"><ref bean="clinic"/></property>
		<property name="serviceInterface">
			<value>org.springframework.samples.petclinic.Clinic</value>
		</property>
	</bean-->

	<!-- Hessian exporter for the RemoteAuthenticationManager -->
	<bean name="/RemoteAuthenticationManager-hessian" class="org.springframework.remoting.caucho.HessianServiceExporter">
		<property name="service"><ref bean="remoteAuthenticationManager"/></property>
		<property name="serviceInterface">
			<value>net.sf.acegisecurity.providers.rcp.RemoteAuthenticationManager</value>
		</property>
	</bean>

	<!-- Burlap exporter for the RemoteAuthenticationManager -->
	<!--bean name="/RemoteAuthenticationManager-burlap" class="org.springframework.remoting.caucho.BurlapServiceExporter">
		<property name="service"><ref bean="remoteAuthenticationManager"/></property>
		<property name="serviceInterface">
			<value>net.sf.acegisecurity.providers.rcp.RemoteAuthenticationManager</value>
		</property>
	</bean-->

</beans>

Configuring Appfuse - add *.jar library dependicies [#4]

For more details read how to add library to appfuse here.

Copy hessian.jar to appfuse/lib/hessian/hessian.jar

To lib/lib.properties add path info:


  #
  # Hessian
  #
  hessian.version=0.1
  hessian.dir=${lib.dir}/hessian-${hessian.version}
  hessian.jar=${hessian.dir}/hessian-${hessian.version}.jar

If you will ever need burlap do the same with burlap *.jar files

And in build.xml hessian library dependency:

<target name="package-web" ......
.......
...... 
<lib file="${hessian.jar}"/> 
...... 
</target>

(properties.xml does not need any changes)

Configuring Appfuse - add interface to allow remote clients login[#5]

Add to web/WEB-INF/applicationContextSecurity.xml this bean:

<!-- Allows remote clients to check if a username/password is valid -->
<bean id="remoteAuthenticationManager" class="net.sf.acegisecurity.providers.rcp.RemoteAuthenticationManagerImpl">  
      <property name="authenticationManager"><ref bean="authenticationManager"/></property>
</bean>

Configuring RichClient[#6]

TODO:

Unsolved issues [#7]

TODO:

Attachments:

appfuse-richclient.zip		44718 bytes
lib.zip		3189999 bytes
screenshot1.jpg		45557 bytes

Go to top More info... Attach file...

This particular version was published on 06-Nov-2006 13:52:49 MST by RadimBurget.