<!–
   
    –>
    
    
   
   
   
    <!–
   
    –>           
   
    <!–
   
    –>

    <!– You should set jvmRoute to support load-balancing via AJP ie :
            
    –> 
   

     
      <!–
     
      –>        

     
      <!–
     
      –>

       
        <!–
       
        –>

       
        <!–
       
        –>

In this explain me about context tag    this one…

docBase means what we will take here and  how to set the path

The WSDL is the contract, and you should try to make it as good as possible! If you have code in your service that validate a the input and return an error when it doesn’t match your criteria, but the criteria is not explicitly written in the WSDL, then the WSDL doesn’t really specify the contract, the code does. (Ooo.. der var det mange innskutte bisetninger.. But you don’t publish your code, so how is the client supposed to know what data is valid?

I agree that using annotations and generating a WSDL is a nice way to work, and it may save you a lot of time. But I wouldn’t call it contract-first..

Regarding Bean Validation – I agree with Cyrille in this thread (http://relation.to/12855.lace); I hope we can get a tool that generates the proper JSR-303 annotations based on restrictions written in the WSDL/XSD.

@XmlRegistry
public class ObjectFactory {
 
    private final static QName _Age_QNAME = new QName("", "age");
    private final static QName _Password_QNAME = new QName("", "password");
 
    /**
     * Create a new ObjectFactory that can be used to create new instances of schema derived classes for package: no.bekk.open.jaxb
     * 
     */
    public ObjectFactory() {
    }
 
    /**
     * Create an instance of {@link JAXBElement }{@code <}{@link Integer }{@code >}}
     * 
     */
    @XmlElementDecl(namespace = "", name = "age")
    public JAXBElement<Integer> createAge(Integer value) {
        return new JAXBElement<Integer>(_Age_QNAME, Integer.class, null, value);
    }
 
    /**
     * Create an instance of {@link JAXBElement }{@code <}{@link String }{@code >}}
     * 
     */
    @XmlElementDecl(namespace = "", name = "password")
    public JAXBElement<String> createPassword(String value) {
        return new JAXBElement<String>(_Password_QNAME, String.class, null, value);
    }
 
}

As one can see, the restrictions on values are lost – I wasn’t aware of that. Also, there is no way of declaring restrictions using JAXB annotations – i.e. you can’t generate an XSD containing restrictions from JAXB annotated code. In addition, according to http://www.java-tips.org/java-ee-tips/java-architecture-for-xml-binding/what-is-new-in-jaxb-2.0.html validation is part of JAXP.

Let’s say a service provided me with the XSD from the example, I generate JAXB code from it, implement the client using “1234567890″ as a password, I’d have to actually use the validation in JAXP to make sure the message looks as expected. I know for sure that a lot of programmers would never do that, since JAXP offers such a bad API. In addition, there are lots of situations where a value cannot (as far as I know) be restricted properly using XSD anyways – e.g. prime numbers. What would you do then? I know there is some fancy new bean validation coming in JEE 6 that might help validating input, but you wouldn’t get a corresponding schema.

Is there anything a part from restrictions that cannot be represented using JAXB annotations?

Stefan: Updated your comment using

<pre lang="xml">

How can you achieve this using annotations?

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
 
	<xs:element name="age">
		<xs:simpleType>
			<xs:restriction base="xs:integer">
				<xs:minInclusive value="0"/>
				<xs:maxInclusive value="120"/>
			</xs:restriction>
		</xs:simpleType>
	</xs:element>
 
	<xs:element name="password">
		<xs:simpleType>
			<xs:restriction base="xs:string">
				<xs:pattern value="[a-zA-Z0-9]{8}"/>
			</xs:restriction>
		</xs:simpleType>
	</xs:element>
 
</xs:schema>

Or this?

I expected someone would ask about that. You define the XML data format using JAXB2 annotations instead of using XSD (or relax ng or dtd for that matter). The way I see it, defining your XML data format using JAXB2 annotations is equivalent to defining it using an XSD schema – please let me know of any shortcommings in the JAXB2 specification if there are any.
That said, it will always make sense to look through the XSD and WSDL to make sure it interoperates well.