geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johnny Kewl" <j...@kewlstuff.co.za>
Subject Re: Load stand alone deployment plan
Date Fri, 26 Oct 2007 14:26:35 GMT

---------------------------------------------------------------------------
HARBOR: http://coolharbor.100free.com/index.htm
Now Tomcat is also a cool pojo application server
---------------------------------------------------------------------------

Hi there, have you got the standalone application that does your (Email task 
workflow)?
If so have a look at the above link... have fun.


----- Original Message ----- 
From: "gromar" <mgrofcik@pflow.sk>
To: <user@geronimo.apache.org>
Sent: Friday, October 26, 2007 11:37 AM
Subject: Re: Load stand alone deployment plan


>
> What I am trying to do:
>
> Our company has developed Workflowclient for 3 engines but for each engine
> it is different application (it looks same for the user, but 
> implementation
> is totaly different).It is allways J2EE application.
>
> I want to develop workflow client application. It is client for connecting
> to Tasks servers of workflow engines (IBM WebSphere Process Server, Tibco
> Staffware, Oracle Process Server, jBPM etc). It is used by user for 
> managing
> his tasks. It is similar to e-mail client for handling e-mails. There are
> tasks (e-mails), queues (folders) for tasks. Each task has formular for
> viewing. Task can be completed, saved, canceled,.....
>
> Workflow client should be:
> - thin/thick application
>             - thin = web app. independent from application server
>             - thick app (for offline use) based on java., (it should be
> plug-in to e-mail client to)
> - independent from workflow engine
>
> My proposal to implement it is described on the nextfigure.
> http://www.nabble.com/file/p13423811/WFC-GBeans.png
>
> Bootstrap always depends on environment (portlet, servlet, e-mail client
> plug-in, stand alone app,...)
> User interface and form-1 n Gbeans are responsible for communication with
> user (handling tasks) and workflow connector Gbean is implemented for
> Workflow engine comunication.
>
> It is easy to hardcore this GBeans configuration into Bootstrap, but I 
> would
> liketo use "plan.xml" for configuration (in the future GBean plug-in
> repositories (it is hard to maintain formulars))
>
> As a proof of the concept, at first I would like to develop 2 different
> bootstraps (simple servlet, and standalone app). Then I will develop 2
> different GBeans for UI, formulars, and WF Engine connector.
>
>
> I hope this descripton should give you more information about my aim.
>
> Thank for in advance for your next message.
>
> regards,
> Martin
>
>
>
> djencks wrote:
>>
>>
>> On Oct 24, 2007, at 2:21 PM, gromar wrote:
>>
>>>
>>> Thank you for advice.
>>>
>>> The one way is to take LittleG cut off all other geronimo plug-ins
>>> (exept
>>> responsible for deployment) and than deploy "my" geronimo plug-in.
>> <snip>
>>
>> I'm having a very hard time understanding what you are trying to do,
>> so it's hard to offer advice.
>>
>> If you want to assemble a server that has one or more of your
>> services and possibly some javaee functionality, that is easy to do.
>>
>> 1. start with geronimo trunk
>> 2. use maven (2)
>> 3. imitate the subprojects in configs to assembly your service
>> components into one or more plugins (car files)
>> 4. imitate the assemblies of one of the servers we ship such as
>> geronimo-jetty6-javaee5 to collect the plugins you want in your
>> server into a distributable assembly.  You only need to list the
>> plugins you know you want in the pom, the ones required to make those
>> work will be automatically included as (transitive) dependencies.
>>
>> For instance if you want to construct a server that has your non-
>> javaee services (one plugin) plus a web app running on jetty, but
>> cannot deploy anything else, you'd build plugins for your services
>> and for the web app and include those in the assembly pom.
>> Everything you need for the server (such as jetty) would be included.
>>
>> If in addition you want to be able to deploy more web apps, you could
>> include the jetty deployer config in the assembly pom.
>>
>> if you need to use an earlier version of geronimo you will have to
>> work harder and write some configuration files by hand such as the
>> var/config/config.xml.
>>
>> If this does not match what you are trying to do or if you have more
>> questions please ask.
>>
>> thanks
>> david jencks
>>
>>
>
> -- 
> View this message in context: 
> http://www.nabble.com/Load-stand-alone-deployment-plan-tf4670360s134.html#a13423811
> Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
>
> 


Mime
View raw message