You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by Jared Hanson <ja...@gmail.com> on 2007/02/17 00:36:04 UTC
Code for Axis2/C Static Deployment Engine
All,
I've uploaded the code for the Axis2/C static deployment engine that I've
been referring to. It can be downloaded from:
http://www.asperasoft.com/developer/axis2c/axis2-static-deploy.tar.gz
Included in the archive is the code, complete with modifications, as well as
a sample application that shows how to initialize and configure the static
engine. I had wanted to do some clean up before release, but in the
interest of getting feedback, I'm providing the code in its raw state.
There is an readme that has a brief overview.
I wish I had a nice patch to submit, but unfortunately that is not the
case. However, I have documented the relevant changes. Grep'ing through
the code for "jared@" will highlight the important differences.
What is in the package was built against 0.95. As mentioned, there are some
issues when building against the trunk. I intend to fix those.
If there is any interest in incorporating this into the project, that would
be welcome. Please ask if you have any questions. Any suggestions are
appreciated.
Thanks,
Jared Hanson
Re: Code for Axis2/C Static Deployment Engine
Posted by Nandika Jayawardana <ja...@gmail.com>.
I am +1 for using #ifdef s in the module directly.
- Nandika
On 2/19/07, Jared Hanson <ja...@gmail.com> wrote:
>
> Glad to hear you're interested in the code.
>
> It's one of my top priorities to get this building against svn head this
> week. I'll be submitting patches as I complete tasks.
>
> One question I did have:
>
> Right now I split out the static deployment engine code, so it is
> completely outside of the axis2c code base. However, it turns out that
> about 95% of the code is a copy of what is in axis2c (configuration parsing,
> etc).
>
> As I work off head, I'd like to avoid this duplication. One option that
> is available is just using a #ifdef directly in the code, usually in the
> deployment module.
>
> For example:
>
> #ifdef AXIS2_STATIC_DEPLOY
> /* Do static deployment step */
> #else
> /* Do normal dynamic deployment step */
> #endif
>
> Another option is to make a separate static deployment module. This
> option avoids the #ifdef pragmas, but would require more refactoring in
> order to move the common code to a place that can be shared by both the
> static and dynamic deployment modules.
>
> If anyone has any opinions on this, please make them known.
>
> Also, as you get a chance to review the code I uploaded, let me know any
> changes you would like made.
>
> - Jared
>
>
> On 2/17/07, Dinesh Premalal <xy...@gmail.com> wrote:
> >
> > Hi Jared,
> >
> > "Jared Hanson" <ja...@gmail.com> writes:
> > > I've uploaded the code for the Axis2/C static deployment engine that
> > > I've been referring to. It can be downloaded from:
> > > http://www.asperasoft.com/developer/axis2c/axis2-static-deploy.tar.gz
> > Downloaded sources, Give us some time look through it.
> > > What is in the package was built against 0.95. As mentioned, there
> > are some
> > > issues when building against the trunk. I intend to fix those.
> > As your previous mail mentioned, there is some refactoring going on the
> > code base. We removed some of the ops because there was some
> > performance hiccups.
> >
> > Lets try to get it build against the trunk, and put it in the code
> > base. After that you will be able to do your further development
> > easily. If we could include, static deployment engine for Axis2/C 1.0
> > release that would be great.
> > > If there is any interest in incorporating this into the project,
> > > that would be welcome.
> > Definitely !, we are open to embrace any constructive ideas or
> > contributions.
> > >Please ask if you have any questions. Any suggestions are
> > > appreciated.
> > Appreciate your effort on Static Deployment Engine. Lets try to get it
> > on svn head soon.
> >
> > thanks,
> > Dinesh
> > --
> > Dinesh Premalal
> > dinesh@wso2.com
> > WSO2, Inc.; http://www.wso2.com/
> > GPG Key ID : A255955C
> > GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255
> > 955C
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-c-dev-help@ws.apache.org
> >
> >
>
--
nandika@wso2.com
Re: Code for Axis2/C Static Deployment Engine
Posted by Jared Hanson <ja...@gmail.com>.
Glad to hear you're interested in the code.
It's one of my top priorities to get this building against svn head this
week. I'll be submitting patches as I complete tasks.
One question I did have:
Right now I split out the static deployment engine code, so it is completely
outside of the axis2c code base. However, it turns out that about 95% of
the code is a copy of what is in axis2c (configuration parsing, etc).
As I work off head, I'd like to avoid this duplication. One option that is
available is just using a #ifdef directly in the code, usually in the
deployment module.
For example:
#ifdef AXIS2_STATIC_DEPLOY
/* Do static deployment step */
#else
/* Do normal dynamic deployment step */
#endif
Another option is to make a separate static deployment module. This option
avoids the #ifdef pragmas, but would require more refactoring in order to
move the common code to a place that can be shared by both the static and
dynamic deployment modules.
If anyone has any opinions on this, please make them known.
Also, as you get a chance to review the code I uploaded, let me know any
changes you would like made.
- Jared
On 2/17/07, Dinesh Premalal <xy...@gmail.com> wrote:
>
> Hi Jared,
>
> "Jared Hanson" <ja...@gmail.com> writes:
> > I've uploaded the code for the Axis2/C static deployment engine that
> > I've been referring to. It can be downloaded from:
> > http://www.asperasoft.com/developer/axis2c/axis2-static-deploy.tar.gz
> Downloaded sources, Give us some time look through it.
> > What is in the package was built against 0.95. As mentioned, there are
> some
> > issues when building against the trunk. I intend to fix those.
> As your previous mail mentioned, there is some refactoring going on the
> code base. We removed some of the ops because there was some
> performance hiccups.
>
> Lets try to get it build against the trunk, and put it in the code
> base. After that you will be able to do your further development
> easily. If we could include, static deployment engine for Axis2/C 1.0
> release that would be great.
> > If there is any interest in incorporating this into the project,
> > that would be welcome.
> Definitely !, we are open to embrace any constructive ideas or
> contributions.
> >Please ask if you have any questions. Any suggestions are
> > appreciated.
> Appreciate your effort on Static Deployment Engine. Lets try to get it
> on svn head soon.
>
> thanks,
> Dinesh
> --
> Dinesh Premalal
> dinesh@wso2.com
> WSO2, Inc.; http://www.wso2.com/
> GPG Key ID : A255955C
> GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255 955C
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>
>
Re: Code for Axis2/C Static Deployment Engine
Posted by Dinesh Premalal <xy...@gmail.com>.
Hi Jared,
"Jared Hanson" <ja...@gmail.com> writes:
> I've uploaded the code for the Axis2/C static deployment engine that
> I've been referring to. It can be downloaded from:
> http://www.asperasoft.com/developer/axis2c/axis2-static-deploy.tar.gz
Downloaded sources, Give us some time look through it.
> What is in the package was built against 0.95. As mentioned, there are some
> issues when building against the trunk. I intend to fix those.
As your previous mail mentioned, there is some refactoring going on the
code base. We removed some of the ops because there was some
performance hiccups.
Lets try to get it build against the trunk, and put it in the code
base. After that you will be able to do your further development
easily. If we could include, static deployment engine for Axis2/C 1.0
release that would be great.
> If there is any interest in incorporating this into the project,
> that would be welcome.
Definitely !, we are open to embrace any constructive ideas or
contributions.
>Please ask if you have any questions. Any suggestions are
> appreciated.
Appreciate your effort on Static Deployment Engine. Lets try to get it
on svn head soon.
thanks,
Dinesh
--
Dinesh Premalal
dinesh@wso2.com
WSO2, Inc.; http://www.wso2.com/
GPG Key ID : A255955C
GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255 955C
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: [Axis2] Code for Axis2/C Static Deployment Engine
Posted by Nabeel Yoosuf <na...@gmail.com>.
Hi Jared,
I encourage you to raise a JIRA [1] issue under new feature so that team
members can better track this.
Nabeel.
[1] https://issues.apache.org/jira/browse/AXIS2C
On 2/16/07, Jared Hanson <ja...@gmail.com> wrote:
>
> All,
>
> I've uploaded the code for the Axis2/C static deployment engine that I've
> been referring to. It can be downloaded from:
> http://www.asperasoft.com/developer/axis2c/axis2-static-deploy.tar.gz
>
> Included in the archive is the code, complete with modifications, as well
> as a sample application that shows how to initialize and configure the
> static engine. I had wanted to do some clean up before release, but in the
> interest of getting feedback, I'm providing the code in its raw state.
> There is an readme that has a brief overview.
>
> I wish I had a nice patch to submit, but unfortunately that is not the
> case. However, I have documented the relevant changes. Grep'ing through
> the code for "jared@" will highlight the important differences.
>
> What is in the package was built against 0.95. As mentioned, there are
> some issues when building against the trunk. I intend to fix those.
>
> If there is any interest in incorporating this into the project, that
> would be welcome. Please ask if you have any questions. Any suggestions
> are appreciated.
>
> Thanks,
> Jared Hanson
>
--
http://www.cs.purdue.edu
http://mohamednabeel.blogspot.com