Wise 1.1

Operating systemsOS : Windows / Linux / Mac OS / BSD / Solaris
Program licensingScript Licensing : LGPL - GNU Lesser General Public License
CreatedCreated : Aug 28, 2010
Size downloadDownloads : 3
Program licensing
Thank you for voting...

Wise can be used as a total and effective client ...

Wise by Red Hat Middleware LLC can be used as a total and effective client decoupler from the server using ws to inter operate.
Most important functions of Wise 1.1:
Components:
• Wise [wise1.1.exe]-core - It is a library to simplify web service invocation from a client point of view: it aims at providing a near zero-code solution to find and parse wsdls, select service and endpoint and call operations mapping user defined object model to JAX-WS objects required to perform the call.
• Wise - 0MB-webgui - In a nutshell this is a web application designed to call a generic web-service given the wsdl only. Wise 1.1 parses the wsdl and dynamically generates a web interface to call the service and read the result. It is designed to be used by non-programmer people (for example QA testers), but it is very useful also for developer since it is easy to use for rapid tests.
• LMS - Lms is an acronym for Logging Meta Service. Lms' goal and use are very similar to the axis' tcp monitor ones: it logs any tcp communication and gives developers the opportunity to review any request-response communications. Lms is a JBoss deployable application (an ear) and have a jmx mbean as application core and a web user interface to make its use easy.
News in the current Wise version:
Bugs:
• JBossws client Port isn't 3ad safe. Remove synchronization work around when and if jbossws changes
• Addition classpath for compilation is needed during integration
• WSKernelLocator bean name conflicts with jbossws one
• WSMethod map have to use soapAction as key and not method name.
• WSImportImpl has a concurrency issue
• WSImportImpl have potential concurrency issue
• setSecurityConfigMap in ReflectionEnablerDelegate don't work with MK config
• Fix cobertura maven plugin issue
smooks suffer of classloading issue when using smooks cache
• keepSource and verbose configs are ignored in our JBossWSNative consumer implementation
• Using of Maps in WSDynamicClientImpl and WSServiceImpl expose to potential cocurrency issues
• ReflectionBasedWSDynamicClientBuilder. transferWSDL We would have problems with relative urls external references
• Wise clients targeting the same wsdl and using the same config (temp dir) clean the temp dir "concurrently"
• Write more stress tests
• Review javadoc
• Review our documentation
• Removed jboss-service from the project
• Verify needeJars in WSImportImpl
• Smooks 1. 2 needs correct classloader also during config validation
Feature Requests:
• Mavenize the project
• Add a JAXBEleement smooks' decoder
• Provide a wise's sample running as web application
• WSSE Enabler have to attach WSSE as first handlar in chain
• JBossws client Port isn't 3ad safe. Create Thread pool solution
• Remove MK dependencies using exteral config
• Transform all samples into integration tests
• Adding maven-source-plugin
• Create stress tests using multiple threads
• WSDynamicClientImpl. getWSMethod launch an error if doesn't find serviceName or portname
• Totally remove MK dependencies and caches
• Use BeanRepository instead of BeanAccessor in SmooksHandler
• LoggingHandler should support Log4J
• Upgrade smooks to 1. 2
Tasks:
• General review of jcip annotations
• Modify the version number for mavenized wise
• Provide huson configuration
• WSDynamicClientBuilder. getCatelogFile typo
• The message stream for the WSContractConsumer is hardcoded to be System. out. Make it configurable
• SmooksMapper. applyMapping() use wrong smooks api
• Publish wise snapshot distribution to jboss. org snapshot repository
• Include required classes only when creating test endpoint wars
• Verify samples
• Review smooks tests
• Workaround for primitive type parameters
• Move all smooks config file to 1. 2 format
Sub-tasks:
• Sample-> test conversion of WSA+WSSE
• Sample-> test conversion of MTOM
• Sample-> test conversion of usingSmooks
• Sample-> test conversion of Groovy sample
• Sample-> test conversion of Ruby sample
• Add shouldRunWithoutMK to all integration tests
• Create maven profile to run stress tests
• Manage a life cycle for WSDynamicClient
• Provide an SPI approach to keep Wise flexible
• WiseMapper should use smooks profiles
• Review smookshandler to totally remove smooksCache

Wise 1.1 scripting tags: web, java framework, smooks, network, relationship, conversion, tests, server management, development tool. What is new in Wise 1.1 software script? - Unable to find Wise 1.1 news. What is improvements are expecting? Newly-made Wise 1.2 will be downloaded from here. You may download directly. Please write the reviews of the Wise. License limitations are unspecified.