[JBossWS] - Service endpoint and client generation problem
by joestevens
Hi,
I'm working on a small ws project to get my feet wet. Things were moving along, but got complicated enough that it was time to add some automation to the build. I'm using the bottom-up approach for my endpoint as outlined in the JAX-WS Tools section of the wiki. I wrote the implementation, added the annotations, and the wsdl got generated. Worked great.
Next, I decided to use the wsdl to generate client support code. I set up an ant task using wsconsume, and everything generated fine. So, I created a little test client using the generated code, ran it, and everything worked. Sweet. Writing software is easy.
As soon as that thought crossed my mind, the software gods decided to punish me for my hubris. If I clean out the build and recompile and regenerate, the build breaks. In order to generate the client support classes, wsconsume needs the wsdl. In order to generate the wsdl, wsprovide needs the endpoint class file. In order to compile the endpoint the client support classes are needed because the client depends on them and they are in the same source tree. So, I have a chicken and egg problem.
The only way that jumps to mind to fix this is to have separate source trees for the endpoint and the client code. That feels kind of clunky. It seems reasonable to have an endpoint implementation, client support classes, and a client in the same source tree. Do most people separate client and server or are there other solutions I'm not thinking of?
If you're still reading, thanks. Any ideas are appreciated.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152498#4152498
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4152498
17 years, 11 months
[Installation, Configuration & DEPLOYMENT] - I am getting error message when calling the Data Source
by BhupeshJ
Posted: Wed May 21, 2008 17:44 PM Post subject: Error while getting data source connection
--------------------------------------------------------------------------------
I am getting error message when calling the Data Source
Config file:
<local-tx-datasource>
<jndi-name>SQLServerDS</jndi-name>
<connection-url>dbc:jtds:sqlserver://192.168.3.202:1433</connection-url>
<driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>
<user-name>qwe</user-name>
1278
</local-tx-datasource>
Client code :
InitialContext ctx = new InitialContext();
DataSource ds = (DataSource)ctx.lookup("java:/SQLServerDS");
JNDI:
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
And I am getting following error Message.
avax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]
at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1465)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1594)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:634)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
Plz help me with the solution
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152496#4152496
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4152496
17 years, 11 months
[Installation, Configuration & DEPLOYMENT] - Error while getting data source connection
by BhupeshJ
I am getting error message when calling the Data Source
Config file:
<local-tx-datasource>
<jndi-name>SQLServerDS</jndi-name>
<connection-url>dbc:jtds:sqlserver://192.168.3.202:1433</connection-url>
<driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>
<user-name>qwe</user-name>
1278
</local-tx-datasource>
Client code :
InitialContext ctx = new InitialContext();
DataSource ds = (DataSource)ctx.lookup("java:/SQLServerDS");
And I am getting following error Message.
avax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]
at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1465)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1594)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:634)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
Plz help me with the solution
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152495#4152495
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4152495
17 years, 11 months
[Microcontainer] - SchemaResolverDeployer is parsing but not deploying
by david.lloyd＠jboss.com
It seems to parse my file OK:
| 2008-05-21 16:06:24,230 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] (HDScanner) Deploying vfsfile:/home/david/src/java/jboss-5.0.0.CR1-r73551/server/default/deploy/jboss-io.xml
| 2008-05-21 16:06:24,230 DEBUG [org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer] (HDScanner) Parsing file: FileHandler(a)91501340[path=jboss-io.xml context=file:/home/david/src/java/jboss-5.0.0.CR1-r73551/server/default/deploy/ real=file:/home/david/src/java/jboss-5.0.0.CR1-r73551/server/default/deploy/jboss-io.xml] for deploymentType: class org.jboss.cx.io.metadata.DeploymentMetaData
| 2008-05-21 16:06:24,231 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (HDScanner) Created parser: org.apache.xerces.jaxp.SAXParserImpl@4dec5ecc, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
| 2008-05-21 16:06:24,231 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (HDScanner) http://xml.org/sax/features/validation set to: true
| 2008-05-21 16:06:24,231 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (HDScanner) http://xml.org/sax/features/namespaces set to: true
| 2008-05-21 16:06:24,231 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (HDScanner) http://apache.org/xml/features/validation/dynamic set to: true
| 2008-05-21 16:06:24,231 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (HDScanner) http://apache.org/xml/features/validation/schema set to: true
| 2008-05-21 16:06:24,231 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (HDScanner) http://xml.org/sax/features/validation set to: true
| 2008-05-21 16:06:24,232 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (HDScanner) Created parser: org.apache.xerces.jaxp.SAXParserImpl@4dec5ecc, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
| 2008-05-21 16:06:24,234 DEBUG [org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer] (HDScanner) Parsed file: FileHandler(a)91501340[path=jboss-io.xml context=file:/home/david/src/java/jboss-5.0.0.CR1-r73551/server/default/deploy/ real=file:/home/david/src/java/jboss-5.0.0.CR1-r73551/server/default/deploy/jboss-io.xml] to: org.jboss.cx.io.metadata.DeploymentMetaData@5bc2832e
| 2008-05-21 16:06:24,235 DEBUG [org.jboss.deployers.vfs.plugins.classloader.InMemoryClassesDeployer] (HDScanner) Dynamic class root for vfsfile:/home/david/src/java/jboss-5.0.0.CR1-r73551/server/default/deploy/jboss-io.xml is vfsmemory://3j001-fb7hzw-fgibuklu-1-fgienkh6-1q
| 2008-05-21 16:06:24,235 DEBUG [org.jboss.classloader.spi.base.BaseClassLoader] (HDScanner) Created BaseClassLoader@3f327012{vfsfile:/home/david/src/java/jboss-5.0.0.CR1-r73551/server/default/deploy/jboss-io.xml} with policy VFSClassLoaderPolicy@85bce28{name=vfsfile:/home/david/src/java/jboss-5.0.0.CR1-r73551/server/default/deploy/jboss-io.xml domain=null roots=[MemoryContextHandler@1127983201[path=classes context=vfsmemory://3j001-fb7hzw-fgibuklu-1-fgienkh6-1q real=vfsmemory://3j001-fb7hzw-fgibuklu-1-fgienkh6-1q/classes]] delegates=null exported=[] <IMPORT-ALL>NON_EMPTY}
| 2008-05-21 16:06:24,235 DEBUG [org.jboss.classloader.spi.base.BaseClassLoaderDomain] (HDScanner) ClassLoaderDomain@7c33788d{<DEFAULT>} registerClassLoader BaseClassLoader@3f327012{vfsfile:/home/david/src/java/jboss-5.0.0.CR1-r73551/server/default/deploy/jboss-io.xml}
| 2008-05-21 16:06:24,238 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] (HDScanner) Fully Deployed vfsfile:/home/david/src/java/jboss-5.0.0.CR1-r73551/server/default/deploy/jboss-io.xml
|
However, the getBeans() method of my root metadata object isn't called (it implements org.jboss.beans.metadata.spi.BeanMetaDataFactory). Is there some other special steps I have to follow?
The metadata class is here: http://anonsvn.jboss.org/repos/sandbox/david.lloyd/networking/deployer/sr...
My jboss-beans.xml contains:
| <bean:deployment xmlns:bean="urn:jboss:bean-deployer:2.0">
| <bean:bean name="XnioDeployer" class="org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer">
| <bean:constructor>
| <bean:parameter>org.jboss.cx.io.metadata.DeploymentMetaData</bean:parameter>
| </bean:constructor>
| <bean:property name="name">jboss-io.xml</bean:property>
| <bean:property name="registerWithJBossXB">true</bean:property>
| </bean:bean>
| </bean:deployment>
|
I'm using JBossAS trunk as my testbed.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152492#4152492
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4152492
17 years, 11 months