[JBoss Web Services Users] - Consuming Web Services when WSDL access / UDDI discovery is
by vimalm
One of the Vendors that we have, expose some .net web services end points but now prohibit access to WSDL via the ?WSDL mechanism as part of a their new security policy. Suddenly the code that used to work to consume their web services no longer works with this new security policy implementation. I have generated the web services stubs using wsconsume and using those stubs to make the calls. One of the thing that Service class does (From JBOSSWS which gets invoked by the generated Stubs) is to open an InputStream to WSDL URL which is now blocked and I get a FileNotFoundException and my process terminates and not able to invoke the business method on the endPoint.
Is there a way around this problem or access to the WSDL URL is absolutely required where the web services are hosted?
We have been using Jboss 4.2.1GA and the jbossws implementation that came with it. I am hoping that suggestion does not involve upgrading the JBOSS server to 5.X as we are not prepared to do that right now!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262547#4262547
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262547
16 years, 6 months
[JBoss Microcontainer Users] - ManagementView API question/comment
by ozizka@redhat.com
Hi,
regarding ManagementView#getMatchingDeploymentName( String regex ):
1) Shouldn't the name be ...Names?
2) What's the point of throwing an exception in case of zero names found? Why not just reply with an empty set? Now when I just want to check remotely whether or not something is deployed, I have to:
| public boolean isDeployed( String name ){
| try {
| Set<String> names = currentProfileView.getMatchingDeploymentName( name );
| if( matchingNames.size() > 0 )
| return true;
| } catch( Exception ex ){
| if( ex.getCause() != null && ex.getCause().getCause() != null &&
| ex.getCause().getCause() instanceof NoSuchDeploymentException ){
| return false;
| } else {
| throw ex;
| }
| }
|
instead of
| return currentProfileView.getMatchingDeploymentName( name ).size() > 0;
|
3) The same applies to getDeployment( String name ) - why not just return null?
Perhaps there are some tech reasons to do it this ugly way, but I would like it to have the API more user-friendly.
Thanks,
Ondra
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262540#4262540
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262540
16 years, 6 months