maven-javadoc-plugin 2.6 is and other versions are giving problem while trying with Java 1.6
Reason: there is some issues with code. we have option “fix” with plugin, but it is not working. So we dont know exact problem to generate javadoc.
Solution: Try javadoc:javadoc with one profile and try by exluding com.* in another profile
>mvn -P JavaDoc_Profile javadoc:javadoc (Generate before site) (regular maven-javadoc-plugin)
>mvn -P Site_Profile site (regular maven-javadoc-plugin with exclude com.*)
dont use site-deploy
Now to test, i dont have remote site to use site:deploy.
alternative is site:stage
-o-
http://blog.vermaas.net/2005/10/maven-2-getting-sitedeploy-to-work_30.html
http://maven.apache.org/plugins/maven-site-plugin/examples/site-deploy-to-sourceforge.net.html
http://maven.apache.org/plugins/maven-site-plugin/usage.html
Class not found exception sun.*
We used to get this exception in OSGi deployments.
In Felix, we need to use this line.
felix/conf/config.properties
# The following property makes specified packages from the class path
# available to all bundles. You should avoid using this property.
org.osgi.framework.bootdelegation=sun.*,com.sun.*
Java2WSDL vs WSDL2Java its a long debate.
Theory: People say, it is better to have contract first and develop XSD. later generate code.
Reality:
1. Working on XML tools and generating XSD is painful process.
2. We never use simple data types in real projects
3. Dont have much time to do small POCs, when depending on WSDL2Java (Proof of Concepts)
4. Difficult to handle frequent changes
Reality: Do your work using Java coding. Develop all business objects, ..etc.
Once you are confident and ready to interface with other applications go with Java2WSDL.
Java2WSDL wins and saves time for developers.
Here is the Maven Java2WSDL plugin (cxf-java2ws-plugin) for your reference.
cxf-java2ws-plugin : http://cwiki.apache.org/CXF20DOC/maven-java2ws-plugin.html
WSDL Document Structure: http://www.w3schools.com/WSDL/wsdl_documents.asp
-o-
