You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Davanum Srinivas <da...@gmail.com> on 2008/02/01 20:05:49 UTC
PojoDeployer vs JAXWSMessageReceiver in services.xml
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sandakith, Roy,
Looks like PojoDeployer picks up only the javax.jws.WebService annotation and not the javax.xml.ws.WebServiceProvider
annotation.
Sandakith,
~From what i know, we cannot modify WAR's shipped by the TCK. Only changes allowed are removing sun specific dd's and
adding our own and maybe change the port #'s...This may have an effect on which way to lean using PojoDeployer vs
JAXWSMessageReceiver in services.xml as we cannot modify the WAR's to suit the pojo deployer. Please note that all the
existing services.xml in the modules\jaxws are handwritten :(
thanks,
dims
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFHo22NgNg6eWEDv1kRAvK8AJ9TNdoDxX+5mZW1j/U9d9lRO07C5gCdH+Is
5R1BjDLElspRZxxyt0uGCko=
=cZDJ
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: PojoDeployer vs JAXWSMessageReceiver in services.xml
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Hi Dims
> Sandakith, Roy,
> Looks like PojoDeployer picks up only the javax.jws.WebService
> annotation and not the javax.xml.ws.WebServiceProvider
Are you talking about defaultSchemaGenerator ?
> annotation.
>
> Sandakith,
> ~From what i know, we cannot modify WAR's shipped by the TCK. Only
> changes allowed are removing sun specific dd's and
> adding our own and maybe change the port #'s...This may have an effect
> on which way to lean using PojoDeployer vs
> JAXWSMessageReceiver in services.xml as we cannot modify the WAR's to
> suit the pojo deployer. Please note that all the
> existing services.xml in the modules\jaxws are handwritten :(
>
> thanks,
> dims
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: PojoDeployer vs JAXWSMessageReceiver in services.xml
Posted by Deepal jayasinghe <de...@gmail.com>.
Davanum Srinivas wrote:
> One more observation:
>
> In PojoDeployer, we can't specify a custom wsdl (yet!) When one writes
> a WebServiceProvider, typically they provide a
> wsdl and the xsd's.
Well , for simple POJO there was no such a requirement that is why
POJODeployer does not have that support. Since we have found the use
case now we can implement POJODeployer to support custom wsdl.
-Deepal
>
> -- dims
>
> Davanum Srinivas wrote:
> | Sandakith, Roy,
> | Looks like PojoDeployer picks up only the javax.jws.WebService
> | annotation and not the javax.xml.ws.WebServiceProvider
> | annotation.
> |
> | Sandakith,
> | ~From what i know, we cannot modify WAR's shipped by the TCK. Only
> | changes allowed are removing sun specific dd's and
> | adding our own and maybe change the port #'s...This may have an effect
> | on which way to lean using PojoDeployer vs
> | JAXWSMessageReceiver in services.xml as we cannot modify the WAR's to
> | suit the pojo deployer. Please note that all the
> | existing services.xml in the modules\jaxws are handwritten :(
> |
> | thanks,
> | dims
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Re: PojoDeployer vs JAXWSMessageReceiver in services.xml
Posted by Lahiru Sandakith <sa...@gmail.com>.
Hi Dims,
As I understood in the forward set of testcases of the TCK we have a set of
sun war files which we can not make any changes for that other than some
parts of the web.xml. We have to get our deployment configured in to
deploying this and pass the testcases. On the reverse set of test cases we
have set of wsdls that we have to codegenerate the services and pass the
test cases by deploying those services.
Thanks
Lahiru
On Feb 6, 2008 1:34 AM, Davanum Srinivas <da...@gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Jeff,
>
> looks like we need more information from the folks who have the TCK.
> specifically some layout hints on where the service
> classes are and where the wsdl's and xsd's are.
>
> ~From what i can tell with the information we have now. We need to be able
> to plugin the RI's wsgen to generate wsdl if
> it's absent. We need to be able to pick up wsdl/xsd for a specific service
> if they are already in the war. and we need
> to be able to pick up all the classes with webservice and
> webservicesprovider annotations from the war and turn them
> into services.
>
> thanks,
> dims
>
> Jeff Barrett wrote:
> | ims,
> |
> | My understanding of what the TCK permits is the same as yours. You can
> | remove the RI-specific DDs and can add your own vendor-specific DDs.
> | However, anything that exists in the TCK application archive (such as
> | classes, WSDL, etc) must remain as is. So, the classes couldn't be
> moved
> | from WEB-INF/classes to some POJO-deployer-specific location. Another
> | consideration is that a single TCK application archive, I believe,
> | contains multiple services AND there may be multiple TCK application
> | archive.
> |
> | Is any of that going to cause problems for the POJO deployer?
> |
> | I talked with Roy Wood about this a bit, and I got the impression that
> | having multiple archives and multiple services may be a problem that
> needs
> | to be fixed in the POJO deployer. Also, that it would be possible to
> | point the POJO deployer at a specific directory or archive, so it could
> be
> | pointed to an "installed applications" directory and be able to find the
> | services there. It seems to me that would work for the TCKs.
> |
> | Thoughts?
> |
> | Thanks,
> | Jeff
> |
> | IBM Software Group - WebSphere Web Services Development
> | Phone: 512-838-4587 or Tie Line 678-4587
> | Internet e-mail and Sametime ID: barrettj@us.ibm.com
> |
> |
> |
> | Davanum Srinivas <da...@gmail.com>
> | 02/04/2008 04:45 PM
> | Please respond to
> | axis-dev@ws.apache.org
> |
> |
> | To
> | axis-dev@ws.apache.org
> | cc
> |
> | Subject
> | [Axis2] Re: PojoDeployer vs JAXWSMessageReceiver in services.xml
> |
> |
> |
> |
> |
> |
> | Resending using [Axis2] since looks like no one looks at the emails
> | otherwise :)
> |
> | Davanum Srinivas wrote:
> | | One more observation:
> | |
> | | In PojoDeployer, we can't specify a custom wsdl (yet!) When one writes
> a
> | | WebServiceProvider, typically they provide a
> | | wsdl and the xsd's.
> | |
> | | -- dims
> | |
> | | Davanum Srinivas wrote:
> | | | Sandakith, Roy,
> | | | Looks like PojoDeployer picks up only the javax.jws.WebService
> | | | annotation and not the javax.xml.ws.WebServiceProvider
> | | | annotation.
> | | |
> | | | Sandakith,
> | | | ~From what i know, we cannot modify WAR's shipped by the TCK. Only
> | | | changes allowed are removing sun specific dd's and
> | | | adding our own and maybe change the port #'s...This may have an
> effect
> | | | on which way to lean using PojoDeployer vs
> | | | JAXWSMessageReceiver in services.xml as we cannot modify the WAR's
> to
> | | | suit the pojo deployer. Please note that all the
> | | | existing services.xml in the modules\jaxws are handwritten :(
> | | |
> | | | thanks,
> | | | dims
>
> - ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
>
>
> - ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Cygwin)
>
> iD8DBQFHqME4gNg6eWEDv1kRAisTAJ9VgDn6Iu/WWxQQmAGOf5iWW6posQCgvbVz
> NiM/pP0YGE4/+AFCCoyuwnI=
> =oDOA
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Thanks
Lahiru Sandakith
http://sandakith.wordpress.com/
GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
Re: [Axis2] Re: PojoDeployer vs JAXWSMessageReceiver in services.xml
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jeff,
looks like we need more information from the folks who have the TCK. specifically some layout hints on where the service
classes are and where the wsdl's and xsd's are.
~From what i can tell with the information we have now. We need to be able to plugin the RI's wsgen to generate wsdl if
it's absent. We need to be able to pick up wsdl/xsd for a specific service if they are already in the war. and we need
to be able to pick up all the classes with webservice and webservicesprovider annotations from the war and turn them
into services.
thanks,
dims
Jeff Barrett wrote:
| ims,
|
| My understanding of what the TCK permits is the same as yours. You can
| remove the RI-specific DDs and can add your own vendor-specific DDs.
| However, anything that exists in the TCK application archive (such as
| classes, WSDL, etc) must remain as is. So, the classes couldn't be moved
| from WEB-INF/classes to some POJO-deployer-specific location. Another
| consideration is that a single TCK application archive, I believe,
| contains multiple services AND there may be multiple TCK application
| archive.
|
| Is any of that going to cause problems for the POJO deployer?
|
| I talked with Roy Wood about this a bit, and I got the impression that
| having multiple archives and multiple services may be a problem that needs
| to be fixed in the POJO deployer. Also, that it would be possible to
| point the POJO deployer at a specific directory or archive, so it could be
| pointed to an "installed applications" directory and be able to find the
| services there. It seems to me that would work for the TCKs.
|
| Thoughts?
|
| Thanks,
| Jeff
|
| IBM Software Group - WebSphere Web Services Development
| Phone: 512-838-4587 or Tie Line 678-4587
| Internet e-mail and Sametime ID: barrettj@us.ibm.com
|
|
|
| Davanum Srinivas <da...@gmail.com>
| 02/04/2008 04:45 PM
| Please respond to
| axis-dev@ws.apache.org
|
|
| To
| axis-dev@ws.apache.org
| cc
|
| Subject
| [Axis2] Re: PojoDeployer vs JAXWSMessageReceiver in services.xml
|
|
|
|
|
|
| Resending using [Axis2] since looks like no one looks at the emails
| otherwise :)
|
| Davanum Srinivas wrote:
| | One more observation:
| |
| | In PojoDeployer, we can't specify a custom wsdl (yet!) When one writes a
| | WebServiceProvider, typically they provide a
| | wsdl and the xsd's.
| |
| | -- dims
| |
| | Davanum Srinivas wrote:
| | | Sandakith, Roy,
| | | Looks like PojoDeployer picks up only the javax.jws.WebService
| | | annotation and not the javax.xml.ws.WebServiceProvider
| | | annotation.
| | |
| | | Sandakith,
| | | ~From what i know, we cannot modify WAR's shipped by the TCK. Only
| | | changes allowed are removing sun specific dd's and
| | | adding our own and maybe change the port #'s...This may have an effect
| | | on which way to lean using PojoDeployer vs
| | | JAXWSMessageReceiver in services.xml as we cannot modify the WAR's to
| | | suit the pojo deployer. Please note that all the
| | | existing services.xml in the modules\jaxws are handwritten :(
| | |
| | | thanks,
| | | dims
- ---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
- ---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFHqME4gNg6eWEDv1kRAisTAJ9VgDn6Iu/WWxQQmAGOf5iWW6posQCgvbVz
NiM/pP0YGE4/+AFCCoyuwnI=
=oDOA
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Re: PojoDeployer vs JAXWSMessageReceiver in services.xml
Posted by Jeff Barrett <ba...@us.ibm.com>.
ims,
My understanding of what the TCK permits is the same as yours. You can
remove the RI-specific DDs and can add your own vendor-specific DDs.
However, anything that exists in the TCK application archive (such as
classes, WSDL, etc) must remain as is. So, the classes couldn't be moved
from WEB-INF/classes to some POJO-deployer-specific location. Another
consideration is that a single TCK application archive, I believe,
contains multiple services AND there may be multiple TCK application
archive.
Is any of that going to cause problems for the POJO deployer?
I talked with Roy Wood about this a bit, and I got the impression that
having multiple archives and multiple services may be a problem that needs
to be fixed in the POJO deployer. Also, that it would be possible to
point the POJO deployer at a specific directory or archive, so it could be
pointed to an "installed applications" directory and be able to find the
services there. It seems to me that would work for the TCKs.
Thoughts?
Thanks,
Jeff
IBM Software Group - WebSphere Web Services Development
Phone: 512-838-4587 or Tie Line 678-4587
Internet e-mail and Sametime ID: barrettj@us.ibm.com
Davanum Srinivas <da...@gmail.com>
02/04/2008 04:45 PM
Please respond to
axis-dev@ws.apache.org
To
axis-dev@ws.apache.org
cc
Subject
[Axis2] Re: PojoDeployer vs JAXWSMessageReceiver in services.xml
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Resending using [Axis2] since looks like no one looks at the emails
otherwise :)
Davanum Srinivas wrote:
| One more observation:
|
| In PojoDeployer, we can't specify a custom wsdl (yet!) When one writes a
| WebServiceProvider, typically they provide a
| wsdl and the xsd's.
|
| -- dims
|
| Davanum Srinivas wrote:
| | Sandakith, Roy,
| | Looks like PojoDeployer picks up only the javax.jws.WebService
| | annotation and not the javax.xml.ws.WebServiceProvider
| | annotation.
| |
| | Sandakith,
| | ~From what i know, we cannot modify WAR's shipped by the TCK. Only
| | changes allowed are removing sun specific dd's and
| | adding our own and maybe change the port #'s...This may have an effect
| | on which way to lean using PojoDeployer vs
| | JAXWSMessageReceiver in services.xml as we cannot modify the WAR's to
| | suit the pojo deployer. Please note that all the
| | existing services.xml in the modules\jaxws are handwritten :(
| |
| | thanks,
| | dims
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFHp5WggNg6eWEDv1kRAklNAJ9aFfhVXLfwk5VREDsYU1aZNkhEkACg8oYm
4Xqu2zBji3JEaJDbYT1cXAo=
=OCYq
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[Axis2] Re: PojoDeployer vs JAXWSMessageReceiver in services.xml
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Resending using [Axis2] since looks like no one looks at the emails otherwise :)
Davanum Srinivas wrote:
| One more observation:
|
| In PojoDeployer, we can't specify a custom wsdl (yet!) When one writes a
| WebServiceProvider, typically they provide a
| wsdl and the xsd's.
|
| -- dims
|
| Davanum Srinivas wrote:
| | Sandakith, Roy,
| | Looks like PojoDeployer picks up only the javax.jws.WebService
| | annotation and not the javax.xml.ws.WebServiceProvider
| | annotation.
| |
| | Sandakith,
| | ~From what i know, we cannot modify WAR's shipped by the TCK. Only
| | changes allowed are removing sun specific dd's and
| | adding our own and maybe change the port #'s...This may have an effect
| | on which way to lean using PojoDeployer vs
| | JAXWSMessageReceiver in services.xml as we cannot modify the WAR's to
| | suit the pojo deployer. Please note that all the
| | existing services.xml in the modules\jaxws are handwritten :(
| |
| | thanks,
| | dims
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFHp5WggNg6eWEDv1kRAklNAJ9aFfhVXLfwk5VREDsYU1aZNkhEkACg8oYm
4Xqu2zBji3JEaJDbYT1cXAo=
=OCYq
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: PojoDeployer vs JAXWSMessageReceiver in services.xml
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
One more observation:
In PojoDeployer, we can't specify a custom wsdl (yet!) When one writes a WebServiceProvider, typically they provide a
wsdl and the xsd's.
- -- dims
Davanum Srinivas wrote:
| Sandakith, Roy,
| Looks like PojoDeployer picks up only the javax.jws.WebService
| annotation and not the javax.xml.ws.WebServiceProvider
| annotation.
|
| Sandakith,
| ~From what i know, we cannot modify WAR's shipped by the TCK. Only
| changes allowed are removing sun specific dd's and
| adding our own and maybe change the port #'s...This may have an effect
| on which way to lean using PojoDeployer vs
| JAXWSMessageReceiver in services.xml as we cannot modify the WAR's to
| suit the pojo deployer. Please note that all the
| existing services.xml in the modules\jaxws are handwritten :(
|
| thanks,
| dims
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFHo4kjgNg6eWEDv1kRAgghAJ4+xTtnWfqWB0xnYCclhhDa02hphgCg9g25
5Jjm9Ux9DswEfhs7iiIzKSc=
=N6+7
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org