[ANN] XINS 1.4.0 released: Web Services development framework

After 5 months of development, tuning and testing, XINS 1.4.0 has been released. XINS is an open-source Java-based Web Services framework. It offers a simple tool for the development of distributed applications.
One of the key features that differentiates XINS from other technologies is the definition-driven approach. Write simple XML definitions and XINS will generate lots for you:
* Documentation of the specifications and implementations
* Test forms, for testing your applications with a browser
* Client-side Java code, supporting load-balancing, fail-over and time-out handling
* Web application (WAR file), compatible with servlet containers
* WSDL, for SOAP-interoperability
* Unit test code, based on JUnit
* Stubs, typically used for testing
* etc.
Another key feature is protocol independence. XINS supports several communication protocols, including SOAP, XML-RPC and POX-RPC. For each incoming request XINS automatically determines which protocol to use. With XSLT the results can be transformed to HTML or other content types. Custom protocols can be added by added a single Java class.
XINS 1.4 offers various new features over release 1.3, as well as some bug fixes. The main new features are:
* Automatic communication protocol detection.
* Asynchronous requests (http://xins.sf.net/asynchronous.html)
* Generation of documentation in OpenDocument format, for use by OpenOffice.org, for example.
* Support for including files (e.g. HTML) in the WAR file
* Extensive Pet Store demo
Additionally, both the compile-time performance and the runtime performance of XINS have been tuned further.
XINS is used in production systems since the end of 2002. As a stable release, XINS 1.4.0 is backwards compatible with all previous stable releases. It has been tested extensively on various Java and OS platforms, including Solaris, Linux and Windows.
Download XINS 1.4.0, either as a Windows installer or as a platform-independent TAR GZ file:
* Windows installer: http://prdownloads.sf.net/xins/xins-1.4.0.exe?download
* TAR GZ archive: http://prdownloads.sf.net/xins/xins-1.4.0.tgz?download
More information is available here:
* XINS website: http://xins.sf.net/
* XINS 1.4.0 release notes: http://xins.sf.net/notes-1.4.0.html
* User guide: http://xins.sf.net/docs/
* XINS Primer: http://xins.sf.net/primer.html - A 15-minute introduction tutorial
* Presentation Frameworks in general and XINS in particular: http://xins.sf.net/presentation_200604_v4.pdf
* Wikipedia page: http://en.wikipedia.com/wiki/XINS

After 5 months of development, tuning and testing, XINS 1.4.0 has been released. XINS is an open-source Java-based Web Services framework. It offers a simple tool for the development of distributed applications.
One of the key features that differentiates XINS from other technologies is the definition-driven approach. Write simple XML definitions and XINS will generate lots for you:
* Documentation of the specifications and implementations
* Test forms, for testing your applications with a browser
* Client-side Java code, supporting load-balancing, fail-over and time-out handling
* Web application (WAR file), compatible with servlet containers
* WSDL, for SOAP-interoperability
* Unit test code, based on JUnit
* Stubs, typically used for testing
* etc.
Another key feature is protocol independence. XINS supports several communication protocols, including SOAP, XML-RPC and POX-RPC. For each incoming request XINS automatically determines which protocol to use. With XSLT the results can be transformed to HTML or other content types. Custom protocols can be added by added a single Java class.
XINS 1.4 offers various new features over release 1.3, as well as some bug fixes. The main new features are:
* Automatic communication protocol detection.
* Asynchronous requests (http://xins.sf.net/asynchronous.html)
* Generation of documentation in OpenDocument format, for use by OpenOffice.org, for example.
* Support for including files (e.g. HTML) in the WAR file
* Extensive Pet Store demo
Additionally, both the compile-time performance and the runtime performance of XINS have been tuned further.
XINS is used in production systems since the end of 2002. As a stable release, XINS 1.4.0 is backwards compatible with all previous stable releases. It has been tested extensively on various Java and OS platforms, including Solaris, Linux and Windows.
Download XINS 1.4.0, either as a Windows installer or as a platform-independent TAR GZ file:
* Windows installer: http://prdownloads.sf.net/xins/xins-1.4.0.exe?download
* TAR GZ archive: http://prdownloads.sf.net/xins/xins-1.4.0.tgz?download
More information is available here:
* XINS website: http://xins.sf.net/
* XINS 1.4.0 release notes: http://xins.sf.net/notes-1.4.0.html
* User guide: http://xins.sf.net/docs/
* XINS Primer: http://xins.sf.net/primer.html - A 15-minute introduction tutorial
* Presentation Frameworks in general and XINS in particular: http://xins.sf.net/presentation_200604_v4.pdf
* Wikipedia page: http://en.wikipedia.com/wiki/XINS

Similar Messages

  • [ANN] XINS 1.5.0 released: Web Services development framework

    XINS 1.5.0 has been released. XINS is an open-source Web Services framework.
    It offers a simple tool for the development of APIs.
    One of the key features that differentiates XINS from other technologies is the definition-driven approach.
    Write simple XML definitions and XINS will generate for you:
    * Documentation of the specifications in HTML
    * Test forms, for testing your applications with a browser
    * Client-side code, supporting load-balancing, fail-over and time-out handling
    * Web application, compatible with Java servlet containers
    * WSDL, for SOAP-interoperability
    * Unit test code, based on JUnit
    * Stubs, typically used for testing
    Another key feature is protocol independence. XINS supports several communication protocols, including SOAP, XML-RPC and POX-RPC.
    For each incoming request XINS automatically determines which protocol to use. With XSLT the results can be transformed to HTML or other content types. Custom protocols can be added.
    XINS 1.5 offers various new features over release 1.4, as well as some bug fixes. The main new features are:
    * Improved integration with Eclipse and NetBeans
    * JMX support
    * Tools for APIs (PMD, FindBugs, java2html, test coverage, ...)
    * Ant tasks to call an API and to call a XINS target
    * Integration of the front-end framework in the core
    XINS is used in production systems since the end of 2002. As a stable release, XINS 1.5.0 is backwards compatible with all previous stable releases.
    It has been tested extensively on various platforms, including Solaris, Linux and Windows.
    Download XINS 1.5.0:
    Windows installer: http://prdownloads.sf.net/xins/xins-1.5.0.exe?download
    TAR GZ archive: http://prdownloads.sf.net/xins/xins-1.5.0.tgz?download
    Resources:
    Web site: http://xins.sourceforge.net/
    Release notes: http://xins.sourceforge.net/notes-1.5.0.html
    XINS demos: http://xins.sourceforge.net/demo.html
    Documentation: http://xins.sourceforge.net/documentation.html
    User guide: http://xins.sourceforge.net/docs/index.html
    101 new features in XINS 1.5 presentation: http://xins.sourceforge.net/xins1.5-features.ppt

    Int my ant task I have the following:
    <mxmlc services="${SERVICE_CONFIG_PATH}" ... >
    Where SERVICE_CONFIG_PATH is the absolute path of the services config file.
    I didn't see anything like this in your ant task.

  • [ANN] XINS 2.1 open source Web Services framework release

    XINS 2.1 Web Services Framework has been released.
    XINS is an open source Web Services Framework based on simple specifications of the Web Service in XML and
    generation of code and documentation from the specification.
    The generation includes Client JAR with its Javadoc, Server side template with its Javadoc, documentation in OpenDocument Format,
    documentation in HTML including the test forms, WSDL file, unit tests (JUnit) and stubs.
    The Web Services accept several protocols including REST, SOAP, XML-RPC, XML, JSON Yahoo! and JSON-RPC.
    What's new:
    * Start the API with java -jar <api name>.war
    * Improved generated specification in OpenDocument Format
    * Include/exclude calling convention with ACLs
    * New calling convention that maps SOAP request and response as the wsdl2api command mapping.
    * Smaller generated build.xml
    * Added possibility to include other runtime properties files
    * The runtime property location can be a URL
    * Swing Graphical User Interface
    * New tools: emma, glean, webstart
    * New target: javadoc-test-<api name>, javadoc-apis
    * Bug fixes and small RFEs
    Download XINS 2.1:
    Windows installer: http://prdownloads.sf.net/xins/xins-2.1.exe?download
    TAR GZ archive: http://prdownloads.sf.net/xins/xins-2.1.tgz?download
    Resources:
    Web site: http://xins.sourceforge.net/
    XINS demos: http://xins.sourceforge.net/demo.html
    Documentation: http://xins.sourceforge.net/documentation.html
    User guide: http://xins.sourceforge.net/docs/index.html

    I recommend you implement your web service with JAX-WS 2.0
    Axis (both version) are good but why do you want to use something that is not included in JEE API, when Java provide same thing with better performance.
    personally try to prevent non standard technologies despite they can be better than core java implementation sometimes.
    I don't know Xfire.
    the good:
    -JAX-WS performance is better than axis,
    - you can create your web service simply with annotation.(this means write class and then make it as a service easily)
    - support every kind of service invocation(callback,Asynchronous,...)
    - architecture is nice (you can operate on SOAP level)
    the Bad:
    - It is JEE 5 or JSE 6 dependent.
    - there is seriously lack of documentation and examples for it, on java web sites and internet.

  • Java Web Services Developer Pack 1.3 now available

    All,
    The Java Web Services Developer Pack 1.3 is now available for
    download from http://java.sun.com/webservices. This release of JWSDP includes the fcs release of JAXRPC 1.1 and SAAJ 1.2 based on the WS-I basic profile 1.0 in addition to bug fixes /maintenance relases of the other components that have been in there in the previous releases. Feel free to download and send us comments at [email protected]
    - Rajiv
    :wq

    I was pumped when I saw this post, then deflated when I read what was new...
    No new JSF. I'm sooo ready for an update :-)
    TTFN,
    -bd-
    http://bill.dudney.net/roller/page/bill

  • Java Web Services Developer Pack (Java WSDP)

    Anybody tried Java Web Services Developer Pack 1.6 ?
    http://java.sun.com/webservices/jwsdp/index.jsp
    Was it simple and easy to consume external web services using this tool ?
    http://java.sun.com/webservices/jwsdp/index.jsp

    FYI,
    JWSDP 2.0 is now available.
    Also, if you want to consume web services try using JAX-WS. It will be part of the next Java SE release (mustang). You can learn more about JAX-WS at http://jax-ws.dev.java.net.

  • Web services Development

    A general question for the group (sorry if this is off-topic, if there's a better
    forum for this type of Q let me know).
    I'm a web services and web app developer who is new to BEA. In the past I've used
    toolkits like Axis for web services and I've always preferred this approach. It
    seems to me that using BEA I can develop Web Services in one of two ways. The
    'low-level' way where I could use the command line tools (or ant) to create, deploy
    and manage the code, or I could use WLW and the nice attribute driven approach.
    It strikes me (on first blush) that these techniques are not compatible, so if
    I choose one I have to stick with that, and I shouldn't (can't) mix and match
    the two.
    As a relative newcomer to this community which one should I choose?
    Which are people out there using?
    Can the approaches me mixed?
    What implications does using one or the other have in terms of deployment and
    the type of WLS I have installed?
    Again sorry if this is off topic, or an RTFM. If either of these is the case pointers
    to the FM would be appreciated.
    Thanks,
    Kevin Jones

    I think if you are looking for training in "BEA web services" then do
    it the WLW way.
    However, if you think your web service may be deployed to a non-BEA
    app server, then pick up the standards.
    This is true for regular web apps using struts vs. WLW's 'netui'
    and JSR 162 vs. WLW Portals as well.
    Kevin Jones wrote:
    Thanks Michael,
    anybody else have any comments?
    For example if you were looking for training in BEA web services would you expect
    it to be WLW or 'command line' based?
    Kevin
    "Michael Wooten" <[email protected]> wrote:
    Hi Kevin,
    The two web services development approaches are for two different audiences,
    so
    it's up to you to select which is more to your liking :-)
    Developers who are familiar with the Apache Axis Web Services Platform,
    will find
    lots of similarities in the Ant-scrpt based approach that the WLS 8.1
    Web Services
    Platform uses. This would also be the environment for those that really
    like to
    see that their code uses classes from a standard, like JAX-RPC or SAAJ.
    Workshop is really targeted at developers who are less interested in
    the mechanics
    of Web service construction, and more interested in what they want the
    web service
    to do. It offers developers with this mindset, almost complete isolation
    from
    the technologies associated with web service development (i.e. SOAP,
    WSDL, XML,
    etc.), while still producing a deployable web service that can interoperate
    with
    web services created by other Web Service stacks.
    Again, both of these approaches have healthy developer audiences, so
    I see no
    real reason to promote one over the other. Personally, I think it makes
    sense
    to become adept at both.
    All in all, I'd have to say that Workshop makes better use of the developer's
    time :-)
    Regards,
    Mike Wooten
    "Kevin Jones" <[email protected]> wrote:
    A general question for the group (sorry if this is off-topic, if there's
    a better
    forum for this type of Q let me know).
    I'm a web services and web app developer who is new to BEA. In the past
    I've used
    toolkits like Axis for web services and I've always preferred this approach.
    It
    seems to me that using BEA I can develop Web Services in one of twoways.
    The
    'low-level' way where I could use the command line tools (or ant) to
    create, deploy
    and manage the code, or I could use WLW and the nice attribute driven
    approach.
    It strikes me (on first blush) that these techniques are not compatible,
    so if
    I choose one I have to stick with that, and I shouldn't (can't) mixand
    match
    the two.
    As a relative newcomer to this community which one should I choose?
    Which are people out there using?
    Can the approaches me mixed?
    What implications does using one or the other have in terms of deployment
    and
    the type of WLS I have installed?
    Again sorry if this is off topic, or an RTFM. If either of these isthe
    case pointers
    to the FM would be appreciated.
    Thanks,
    Kevin Jones

  • Java Web Services Developer Pack, where is jwsdp.home defined?

    Hi.
    I am trying out the Web Services Developer Pack, and so far so good, a really nice package of tools, tutorials and examples.
    But there is one thing I do not understand regarding the Ant scripts for building the various examples.
    In most of the scripts, the ${jwsdp.home} is used, but where is it defined? I have looked everywhere, and the only place where I have seen it defined, is in the server.xml file that is used by Tomcat. And it seems somewhat strange that Ant should be dependant on Tomcat on this particular issue, so surely that cannot be it.
    It may seem like a unimportant question, but it is not, as I am purely beginning to use Ant, and need this information for when I'll begin writing my own scripts. Sure, I could just hardcode my app home path into the scripts, but that would be a ugly hack.
    Thanks in advance
    /Gabriel

    In the path c:\jwsdp-1.1\conf of my installation, the file server.xml includes this code:
        <!-- Absolute Pathname of the JWSDP Installation -->
        <Environment
                  name="jwsdp.home"
           description="Absolute Pathname of the JWSDP Installation"
                  type="java.lang.String"
                 value="C:\jwsdp-1.1"/>.. is that what are you looking for, is'n it?

  • Java Web Services Developer Pack 1.5 and SOAP?

    Hi all,
    I'm trying to figure out what, if any, support does Java Web Services Developer Pack 1.5 have for parsing and dealing with SOAP messages. I couldn't find any documentation or info in the tutorial about it, but founds some packages through JavaDoc that seem to deal with SOAP. Does anyone know what the deal is? Do you use this toolkit for SOAP, maybe even WS-security?
    Thanks for any pointers!
    Olia

    You can use JWSDP 1.3 but the minimum requirement form that toolkit is JDK 1.4. So you need to download the JDK 1.4 from http:/java.sun.com and install it first and after that you can install that JWSDP 1.3. Good Luck.

  • Java Web Services Developer Pack 1.3

    Does anyone know how I can remove Java Web Services Developer Pack 1.3 manually from my system? I have tried using add/remove and the system does not allow to remove the application.

    The link: Developer Survey
    on that page, doesn't work. :)
    -G

  • Java Web Services Developer Pack 1.3 and JDK 1.3.1

    Does anyone know if I can use Java Web Services Developer Pack 1.3 with JDK 1.3.1? The installation instructions only mention JDK 1.4.
    Thanks,
    Jerry

    You can use JWSDP 1.3 but the minimum requirement form that toolkit is JDK 1.4. So you need to download the JDK 1.4 from http:/java.sun.com and install it first and after that you can install that JWSDP 1.3. Good Luck.

  • Java Web Services Developer Pack v1.2

    I recently installed J2SE v1.4.2 Beta on my computer and it works fine with the platform, which is Windows XP Home Edition.
    Now, I like to learn Java Servlet Technology and had searched through the downloads pages. I found Java Web Services Developer Pack v1.2. But I have doubt about this: Is there any problem to run Java Web Services Developer Pack on Windows XP HOME Edition? I learnt that Sun engineers had it tested on Windows XP Professional Edition.
    I will appreciate any comments and opinions. Thanks in advance!

    doesn't mean it won't work on home edition. just means that they probably think anyone who might want to use J2WSDP will prob have Pro...

  • Web Service Developer Pack for production use?

    Hello,
    Can anyone tell me what the licensing is for use of the web services developer pack reference implementations? Can they be used in a production environment, or are they for development purposes only?
    Any information is appreciated.
    Holly

    The JWSDP can be used for production use. It is not just
    a reference implementation. The exception is the bundled
    UDDI registry which is just for testing development.

  • Experienced Web Services development Employee Opportunity in North Jersey

    A dynamic young firm that has developed a state-of-art solution in enterprise communication applications is expanding its organization. With a growing business they are now seeking an experienced Web services developer with the following skills.
    &bull; Work experience designing & developing Web-Services; Java/C++ programming a must
    &bull; Experience with Apache, Javascript/AJAX/HTML/Applets, XML/XSD, WSDL, PHP, Linux, MySQL required
    &bull; Computer Science degree and 5+ years work experience
    &bull; Work background with communication applications is a plus
    If you wish to be a part of this exciting team involved in cutting edge technology, please get in touch. Our long relationship with this client allows us to bring your expertise to the direct attention of their CTO.
    Please send a Word resume when you contact me! No work authorization (visa) support can be provided.
    Thanks,
    Durga Kotikalapudi
    Recruiter, CMI
    [email protected]

    Hi Raj, Wrong Initiative.
    *=================> Please don't spoil the forum. <=================*
    I am sorry if you find this a bit rude or like that, but this a technical discussion forum not a job portal where you should find candidates for your organization.
    rajhyd wrote:
    Anyone interested can respond to this message and please send me your mobile number or e mail address and I will get in touch with you.I think instead of this you should make your email address visible in your current profile, so that people can reply you on that instead of expressing their interest here.
    *All the best for your new venture,
    typurohit* (Tejas Purohit)

  • Article written on EJB 3.0 , web services develop n deploy on JBOSS AS

    Dear Friends
    I would like to announce the article written on EJB 3.0 , web services development and deployment on JBOSS AS at the following location http://jamessmithjava.100webcustomers.com/index.html , I think this would help developers to increase interest on JBoss as well as EJBs
    Regards
    James
    [email protected]
    http://tech.groups.yahoo.com/group/james_smithjava

    Dear Friends
    I would like to announce the article written on EJB 3.0 , web services development and deployment on JBOSS AS at the following location http://jamessmithjava.100webcustomers.com/index.html , I think this would help developers to increase interest on JBoss as well as EJBs
    Regards
    James
    [email protected]
    http://tech.groups.yahoo.com/group/james_smithjava

  • Difference between Web Service Developer and Web Compononent Developer?

    What's the difference between Web services Developer and Web Component Developer? What's their job description. I'm aiming to be a web application developer. Which track should I follow?

    Here is another article on J2SE vs JEE:
    http://www.velocityrevies.com/forums/t151124-what-is-j2se-vs-j2ee.html
    I believe the people who said JSE is only for desktop development are not correct, as well as their saying their are 2 kinds of developer (web service and component).
    As I understand it, web service developers provide a way to expose the data and functionality of a program written in a particular language (such as Java or C#) as XML documents to anyone subscribing to the service over the internet. The remote applications subscribing to the service therefore can be written in any other language. For example, imagine a Cobol program trying to get data from a program written in Java. Since both cobol and Java should have ways to parse XML documents, they don't have to know each other's syntax. There are many programs written in many many languages in the web and XML is a standard way for them to communicate. Web Services are an advanced topic and you shouldn't worry about it until you master web applications and/or desktop applications.
    As I understand it, a web component developer creates java widgets that produce some visual image with basic functionality associated with it. For example, an html button. These widgets are used by other developers for the presentation layer when creating a web application or desktop application. I'm not sure about this definition since I never messed with web component development. I suggest you keep way from this specialized area on concentrate on web applications and/or desktop applications.
    You can consider application development as devided into two general categories. Web development and Desktop development (there are others). Web development is further broken down into browser based applications and mobile device applications. I suspect their are more jobs in web development than desktop development. I therefore suggest you concentrate on browder based web development (just my opinion). However, each has their advantages and disadvantages over each other, depending on the task at hand(http://stackoverflow.com/questions/905365/desktop-development-versus-web-development)
    Disclaimer:
    http://myweb.accessus.net/~090/univdisc.html

Maybe you are looking for