You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@beehive.apache.org by James Black <jb...@ieee.org> on 2005/07/18 17:27:17 UTC
re: using controls, path flow and webservices in one project
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I am using all aspects of beehive in one webapp, and I realized that I
don't think I am doing a great job of building the webapp.
I am using an ant file from the controls-blank, and it doesn't
specifically deal with webservices.
Is there an example of a build.xml file that will allow me to use .java
for my webservices, and for controls and path flow, so I can stop using
.jpf and .jws for example.
Or, do I just heavily edit my build.xml file?
I don't like this idea as it will make it harder to handle new upgrades.
Thanx for any suggestions.
- --
"Love is mutual self-giving that ends in self-recovery." Fulton Sheen
James Black james@usf.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFC28pVikQgpVn8xrARAs6UAJ480KXbEJv4+ZQXbuLoy6rN83yrqQCfQ9JR
89l44gGZraQdtzTNIGltIW4=
=8EQV
-----END PGP SIGNATURE-----
Re: using controls, path flow and webservices in one project
Posted by Eddie O'Neil <ek...@bea.com>.
Yeah -- I've gotten lazy about nightlies. :)
But, the samples/petstoreWeb/build.xml file for the most recent one
you've got should be fine. It worked this way for the v1m1 release.
You may need to split some of your source files up in order to
resolve build issues with them -- just depends on how your dependencies
work.
I often structure projects as:
src/
controls/
page-flows/
web-services/
so that the dependencies can run from the top-to-bottom in that order.
Eddie
James Black wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Eddie O'Neil wrote:
>
>> Take a look at the samples/petstoreWeb/build.xml Ant file which builds
>>all of those source artifacts (web services, controls, and page flows)
>>using *only* the .java file extensions.
>>
>> I tend to encourage breaking your web services up from the rest of the
>>Beehive source artifacts since they often end up running in separate
>>webapps, though the build should work either way.
>>
>> You may need to tweak the source paths depending on how you have your
>>webapp structured and what your dependencies are, but it should be a
>>good start.
>
>
> I am d/l the latest code from subversion now, as the latest nightly is
> a bit dated, it appears.
>
> I will look at the petstore example and see though.
>
> Since there is a great deal of similar classes between my webservices
> and the rest of my webapp I found it easier to just keep them together,
> as they form one webapp with more than one entry point.
>
> - --
> "Love is mutual self-giving that ends in self-recovery." Fulton Sheen
> James Black james@usf.edu
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFC286qikQgpVn8xrARAofUAJ9lm/fKbR4zGvrGPMVJegOnqBD4GQCeJ6gq
> NlYaDrjvBwTnjaRLs28X6vY=
> =LK4D
> -----END PGP SIGNATURE-----
>
Re: using controls, path flow and webservices in one project
Posted by James Black <jb...@ieee.org>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Eddie O'Neil wrote:
> Take a look at the samples/petstoreWeb/build.xml Ant file which builds
> all of those source artifacts (web services, controls, and page flows)
> using *only* the .java file extensions.
>
> I tend to encourage breaking your web services up from the rest of the
> Beehive source artifacts since they often end up running in separate
> webapps, though the build should work either way.
>
> You may need to tweak the source paths depending on how you have your
> webapp structured and what your dependencies are, but it should be a
> good start.
I am d/l the latest code from subversion now, as the latest nightly is
a bit dated, it appears.
I will look at the petstore example and see though.
Since there is a great deal of similar classes between my webservices
and the rest of my webapp I found it easier to just keep them together,
as they form one webapp with more than one entry point.
- --
"Love is mutual self-giving that ends in self-recovery." Fulton Sheen
James Black james@usf.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFC286qikQgpVn8xrARAofUAJ9lm/fKbR4zGvrGPMVJegOnqBD4GQCeJ6gq
NlYaDrjvBwTnjaRLs28X6vY=
=LK4D
-----END PGP SIGNATURE-----
Re: using controls, path flow and webservices in one project
Posted by Eddie O'Neil <ek...@bea.com>.
James--
Take a look at the samples/petstoreWeb/build.xml Ant file which
builds all of those source artifacts (web services, controls, and page
flows) using *only* the .java file extensions.
I tend to encourage breaking your web services up from the rest of
the Beehive source artifacts since they often end up running in separate
webapps, though the build should work either way.
You may need to tweak the source paths depending on how you have your
webapp structured and what your dependencies are, but it should be a
good start.
Hope that helps.
Eddie
James Black wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I am using all aspects of beehive in one webapp, and I realized that I
> don't think I am doing a great job of building the webapp.
>
> I am using an ant file from the controls-blank, and it doesn't
> specifically deal with webservices.
>
> Is there an example of a build.xml file that will allow me to use .java
> for my webservices, and for controls and path flow, so I can stop using
> .jpf and .jws for example.
>
> Or, do I just heavily edit my build.xml file?
>
> I don't like this idea as it will make it harder to handle new upgrades.
>
> Thanx for any suggestions.
>
> - --
> "Love is mutual self-giving that ends in self-recovery." Fulton Sheen
> James Black james@usf.edu
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFC28pVikQgpVn8xrARAs6UAJ480KXbEJv4+ZQXbuLoy6rN83yrqQCfQ9JR
> 89l44gGZraQdtzTNIGltIW4=
> =8EQV
> -----END PGP SIGNATURE-----
>