S
Stephen
We have a number of web applications that are currently sharing code
through a file-inclusion process whereby each application delivers to
the same client its own copy of common code.
like this:
com.some.app1.*
com.some.shared.*
com.some.app2.*
com.some.shared.*
As you can imagine, this is causing problems.
We want to move the com.some.shared.* package into a single service
which the other applications use. The purpose of the com.shared package
is to present query forms and perform searches on behalf of its
containing application.
The com.some.shared.* package in its current implementation communicates
with the other applications through a SearchRequest/SearchResponse
interface. com.some.shared.* includes JSPs which we want to use.
Not sure what is the best way to approach. A web service? Can we use the
com.shared JSPs or do the applications need to keep their own versions
of the query form JSPs?
Is web service feasible in this problem? Is there a better solution?
through a file-inclusion process whereby each application delivers to
the same client its own copy of common code.
like this:
com.some.app1.*
com.some.shared.*
com.some.app2.*
com.some.shared.*
As you can imagine, this is causing problems.
We want to move the com.some.shared.* package into a single service
which the other applications use. The purpose of the com.shared package
is to present query forms and perform searches on behalf of its
containing application.
The com.some.shared.* package in its current implementation communicates
with the other applications through a SearchRequest/SearchResponse
interface. com.some.shared.* includes JSPs which we want to use.
Not sure what is the best way to approach. A web service? Can we use the
com.shared JSPs or do the applications need to keep their own versions
of the query form JSPs?
Is web service feasible in this problem? Is there a better solution?