You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Daire Quinlan (JIRA)" <ji...@activemq.org> on 2006/03/16 17:40:26 UTC
[jira] Created: (SM-350) The servicemix JBI component shouldn't
need both the service information and binding information in the WSDL to
form a valid endpoint for a PXE process.
The servicemix JBI component shouldn't need both the service information and binding information in the WSDL to form a valid endpoint for a PXE process.
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: SM-350
URL: http://jira.activemq.org/jira//browse/SM-350
Project: ServiceMix
Type: Improvement
Components: servicemix-bpe
Versions: 3.0-M1
Reporter: Daire Quinlan
Priority: Minor
Fix For: 3.0
see comment by Guillame Nodet on the servicemix_users list 16th march "Re: PXE->JBI endpoint questions."
> On 3/16/06, Quinlan, Daire (Daire) <***********.com> wrote:
> On a related note though, surely on a NMS bus neither the service nor
> the bindings should actually be necessary in the WSDL at all ?
You're right, only the PortType should be necessary. However, it would only work if there is only one PortType
defined in the wsdl, which may be not always the case.
That's the reason why ServiceMix looks for the endpoint definition to retrieve the interface name. We could
also check that if there is only one PortType in the wsdl this one is taken for the interface of the endpoint.
Guillaume Nodet
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.activemq.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (SM-350) The servicemix JBI component shouldn't
need both the service information and binding information in the WSDL to
form a valid endpoint for a PXE process.
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-350?page=all ]
Guillaume Nodet resolved SM-350:
--------------------------------
Resolution: Won't Fix
PXE jbi component is not maintained by the ServiceMix team.
> The servicemix JBI component shouldn't need both the service information and binding information in the WSDL to form a valid endpoint for a PXE process.
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-350
> URL: https://issues.apache.org/activemq/browse/SM-350
> Project: ServiceMix
> Type: Improvement
> Versions: 3.0-M1
> Reporter: Daire Quinlan
> Priority: Minor
> Fix For: 3.0
>
>
> see comment by Guillame Nodet on the servicemix_users list 16th march "Re: PXE->JBI endpoint questions."
> > On 3/16/06, Quinlan, Daire (Daire) <***********.com> wrote:
> > On a related note though, surely on a NMS bus neither the service nor
> > the bindings should actually be necessary in the WSDL at all ?
> You're right, only the PortType should be necessary. However, it would only work if there is only one PortType
> defined in the wsdl, which may be not always the case.
> That's the reason why ServiceMix looks for the endpoint definition to retrieve the interface name. We could
> also check that if there is only one PortType in the wsdl this one is taken for the interface of the endpoint.
> Guillaume Nodet
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (SM-350) The servicemix JBI component shouldn't
need both the service information and binding information in the WSDL to
form a valid endpoint for a PXE process.
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-350?page=all ]
Guillaume Nodet updated SM-350:
-------------------------------
Component: (was: servicemix-bpe)
> The servicemix JBI component shouldn't need both the service information and binding information in the WSDL to form a valid endpoint for a PXE process.
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-350
> URL: https://issues.apache.org/activemq/browse/SM-350
> Project: ServiceMix
> Type: Improvement
> Versions: 3.0-M1
> Reporter: Daire Quinlan
> Priority: Minor
> Fix For: 3.0
>
>
> see comment by Guillame Nodet on the servicemix_users list 16th march "Re: PXE->JBI endpoint questions."
> > On 3/16/06, Quinlan, Daire (Daire) <***********.com> wrote:
> > On a related note though, surely on a NMS bus neither the service nor
> > the bindings should actually be necessary in the WSDL at all ?
> You're right, only the PortType should be necessary. However, it would only work if there is only one PortType
> defined in the wsdl, which may be not always the case.
> That's the reason why ServiceMix looks for the endpoint definition to retrieve the interface name. We could
> also check that if there is only one PortType in the wsdl this one is taken for the interface of the endpoint.
> Guillaume Nodet
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira