Skip to main content
Jump to: navigation, search

Difference between revisions of "Riena/Getting Started with stages"

m (Getting Started with Stages)
Line 31: Line 31:
 
That looks cool. Suppose we could just write that once and use it within different environment setups aka '''stages'''.
 
That looks cool. Suppose we could just write that once and use it within different environment setups aka '''stages'''.
  
===== StringVariableManager come to the rescue =====
+
== StringVariableManager come to the rescue ==
 
Fortunately there is this great StringVariableManager within the bundle 'org.eclipse.core.variables'. One of things it can do is substituting variable expressions within strings with their definition, e.g.
 
Fortunately there is this great StringVariableManager within the bundle 'org.eclipse.core.variables'. One of things it can do is substituting variable expressions within strings with their definition, e.g.
 
<pre>
 
<pre>
Line 47: Line 47:
 
</pre>
 
</pre>
  
===== Putting the pieces together =====
+
== Putting the pieces together ==
 
Riena performs such string substitutions within
 
Riena performs such string substitutions within
 
* all definitions for remote services. See [[Riena_Getting_started_remoteservices | Getting Started with Remote Service ]]
 
* all definitions for remote services. See [[Riena_Getting_started_remoteservices | Getting Started with Remote Service ]]
Line 53: Line 53:
  
 
With that we got all for plumbing the pieces together. What is missing is a nice artifact from the Eclipse/OSGi ecosystem to package our stages.
 
With that we got all for plumbing the pieces together. What is missing is a nice artifact from the Eclipse/OSGi ecosystem to package our stages.
===== Stage fragments =====
+
== Stage fragments ==
 
Why not putting all those stage dependent ''stuff'' into fragments? Fragments are lightweight and a perfect place for data. One stage - one fragment. As mentioned at the beginning there might be various stages (client/development, client/test, client/production, ..). And of course this pattern can also be applied to the server environment setups.
 
Why not putting all those stage dependent ''stuff'' into fragments? Fragments are lightweight and a perfect place for data. One stage - one fragment. As mentioned at the beginning there might be various stages (client/development, client/test, client/production, ..). And of course this pattern can also be applied to the server environment setups.
  
Line 60: Line 60:
  
 
Depending on the required stage the appropriate stage fragment needs to be activated, e.g. added to your launch configuration.
 
Depending on the required stage the appropriate stage fragment needs to be activated, e.g. added to your launch configuration.
===== And Finally =====
+
== And Finally ==
  
 
Stages
 
Stages

Revision as of 07:43, 30 April 2009

Riena Project > Riena Getting Started with stages


Getting Started with Stages

Developing, integrating, testing, running and maintaining large client/server applications typically involve diverse setups. Stages are Riena´s approach to deal with that. Stages are a concept - not a service or a set of classes.

All the different setups of servers and clients are almost identical (and that´s what they should). However, there is a small amount of - ermm - stuff (!) that is different. Basically, this mostly boils down to strings that are different e.g. within URLs (e.g. remote service locations) or other data that gets configured with extensions.

While developing for example URLs for remote services might look like:

http://localhost:8080/hessian/HelloWorldServiceWS
http://localhost:8080/hessian/CustomerSearchWS

and so on. Within our test environment they become:

http://your.inhouse.server:80/hessian/HelloWorldServiceWS
http://your.inhouse.server:80/hessian/CustomerSearchWS

and finally within production

https://your.prodhouse.server:80/hessian/HelloWorldServiceWS
https://your.prodhouse.server:80/hessian/CustomerSearchWS

As you can see they have a lot in common. We could rewrite them with something like that

${service_host}/hessian/HelloWorldServiceWS
${service_host}/hessian/CustomerSearchWS

That looks cool. Suppose we could just write that once and use it within different environment setups aka stages.

StringVariableManager come to the rescue

Fortunately there is this great StringVariableManager within the bundle 'org.eclipse.core.variables'. One of things it can do is substituting variable expressions within strings with their definition, e.g.

"This is a ${what} bundle."  would become   "This is a great bundle."  with the definition: what := "great"

The StringVariableManager can be configured programmatically via its API but more useful in our case by extensions, i.e. we can define variables e.g. with such an expression

<extension point="org.eclipse.core.variables.valueVariables">
	<variable
		description="Name of the host to connect to"
		name="service_host"
		readOnly="true"
		initialValue="http://localhost:8080"/>
</extension>

Putting the pieces together

Riena performs such string substitutions within

With that we got all for plumbing the pieces together. What is missing is a nice artifact from the Eclipse/OSGi ecosystem to package our stages.

Stage fragments

Why not putting all those stage dependent stuff into fragments? Fragments are lightweight and a perfect place for data. One stage - one fragment. As mentioned at the beginning there might be various stages (client/development, client/test, client/production, ..). And of course this pattern can also be applied to the server environment setups.

Fragments need a host bundle that defines the context for the fragment. Typically there is a bundle that plays the role of a main bundle, e.g. within Riena´s sample client application it is the "org.eclipse.riena.sample.app.client" bundle. This main bundle can be used as the host bundle for the stage fragments.
For convenience we store the stage fragments within a special folder in the main bundle. Within our sample application client you can find a folder called "stagefragments" that contains the stages (currently just one!).

Depending on the required stage the appropriate stage fragment needs to be activated, e.g. added to your launch configuration.

And Finally

Stages

  • are just a concept or a pattern
  • extract environment specific stuff
  • keep environment specific stuff in a well known place
  • simplify handling with different setups
  • are just beautiful

Copyright © Eclipse Foundation, Inc. All Rights Reserved.