"Yes I edited the topology file after entering the service definitions and
then I restarted the server."

I interpret the above as:

1. added service definition to data directory
2. edited topology (which would deploy the new webapp without knowing about
the service def)
3. restart server (which would make server aware of new service def for new
topology deployments but the webapp still not)

NOTE: webapps are not recreated on restart

If the above is correct then you need to touch the topology so that it gets
redeployed.
If you haven't done that already then just do it and see if it works.

On Wed, Jan 3, 2018 at 9:20 AM, Gareth Williams <[email protected]>
wrote:

> Yes I edited the topology file after entering the service definitions and
> then I restarted the server.
>
> Any other suggestions?
>
> -----Original Message-----
> From: larry mccay [mailto:[email protected]]
> Sent: 03 January 2018 13:15
> To: [email protected]
> Subject: Re: Add Apache Knox Services
>
> It all looks okay to me.
> You may need to touch the sandbox.xml file.
>
> If you happen to have had it configured in the topology before you added
> the service definition AND restarted then the generated webapp wouldn't
> have known about the service and it wouldn't have been added to the
> gateway.xml file in the webapp.
>
> You can check that file - if you like or just touch the topology and see
> if the new deployment works.
>
> On Wed, Jan 3, 2018 at 5:47 AM, Gareth Williams <[email protected]>
> wrote:
>
> > I am unable to add new services to my Apache Knox installation. For
> > example, I have created a tomcat site which hosts a static html file.
> > I have added it to Knox as a service called ‘Simple’.
> >
> > When I attempt to visit a page within one of the new services, I
> > receive =
> > 404 page from jetty (not tomcat).
> >
> > I have attached my topology and services xml files and my log files.
> >
> > Thanks,
> >
> > Gareth
> >
>

Reply via email to