Thank you!
I will do it that way in the future.
Christian
Am 20.02.2009 um 16:58 schrieb Martin Feller:
To my knowledge this is the only surprise.
If you don't like surprise parties, I'd recommend the following
(assuming
you did changes in code in the tree wsrf/java/core/source):
Don't call "ant deploy" in wsrf/java/core/source after you changed
code, but call "ant jar" and copy build/lib/wsrf_core.jar to
$GLOBUS_LOCATION/lib
afterwards.
By that you make sure that only your code changes show up, and no
configuration
or packaging specific issues.
Martin
Christian Szongott wrote:
Thank you for your very fast response!
Am 20.02.2009 um 16:01 schrieb Charles Bacon:
On Feb 20, 2009, at 8:46 AM, Christian Szongott wrote:
Hi all!
I built and installed GT 4.0.8 as described in the quickstart
(http://globus.org/toolkit/docs/4.0/admin/docbook/quickstart.html).
Everything worked fine. The globus container started and i was able
to execute jobs.
Today I built and deployed wsrf-core using the build.xml
(gt4.0.8-all-source-installer/source-trees/wsrf/java/core/source/
build.xml).
If I want to start the globus-container I get the following error:
Out of curiosity, why did you perform this step?
I just added some outputs to one of the java classes to see what is
going on there. It wasn't the best idea, but when I noticed it, it
was
too late! I'm searching for the point in GT where the delegated
credentials from the delegation service are used for authentication.
Failed to start container: Container failed to initialize [Caused
by:
Secure container requires valid credentials. No container
descriptor
file configured and default proxy not found. Run grid-proxy-init to
create default proxy credential.]
Was it wrong to build and deploy it that way?
What's wrong with it? Or what files do I have to edit to make it
work
again?
When you rebuilt core by hand, it did not build the same way it
builds
out of the installer. Look at the pkgdata/pkg_data_src.gpt file in
the wsrf/java/core directory and see the Build_Steps at the end.
One
of them enables the container security descriptor that's the default
in full builds of GT; you'll want to pass that option also when you
build by hand. Alternatively, if you look at the java ws core admin
docs, you'll find a reference to the container security descriptor
that you can add to the globalOptions section of the
server-config.wsdd. You can do that by hand and point it at the
global_security_descriptor.xml that is installed.
I've added the containerSecDesc-parameter to my server-config.wsdd as
you mentioned. It seems that everything is working again. Was it the
only difference or do I have to expect some more "surprises"?
Christian
