[JBossWS] - HELP! Can not deploy even the simplest web service
by a3leggeddog
Hello -
I'm very new to JBoss (done a lot of Tomcat), so please forgive the question if it is really basic. However, I am having the most frustrating time installing, configuring and deploying a WAR to JBoss. First, I'm using JBoss 4.2.2GA, WS 2.0.3GA, and Java 1.6 running on Windows.
I have tried following the instructions both on the JBoss site and postings I've found online to get everything installed, but the instructions never seem to match exactly what I have. For example, trying to compile the test suite once I think I have the JBossWS installed. Either files are missing from the package I downloaded from the JBoss site, or the Ant task fails with errors. I have copied the various JaxB JARs to the endorsed LIB, etc.
I think I have JBoss and JBossWS installed correctly, but I don't know for sure.
I then wrote a simple web service in Eclipse (Ganymede) and tried to deploy it using Eclipse's built in deploy and by dropping the WAR in the deploy directory. When I do, I get the following error:
16:51:34,796 ERROR [MainDeployer] Could not start deployment: file:/C:/jboss-4.2.2.GA/server/default/deploy/EchoService.war
|
| java.lang.StringIndexOutOfBoundsException: String index out of range: -1
|
| at java.lang.String.substring(Unknown Source)
|
| at org.jboss.wsf.common.JavaUtils.getPackageName(JavaUtils.java:535)
|
| at org.jboss.ws.metadata.wsdl.WSDLUtils.getTypeNamespace(WSDLUtils.java:700)
|
| at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.processWebService(JAXWSWebServiceMetaDataBuilder.java:304)
|
| at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:108)
|
| at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:50)
|
| at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderJSE.buildMetaData(JAXWSMetaDataBuilderJSE.java:63)
|
| at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.create(UnifiedMetaDataDeploymentAspect.java:66)
|
| at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
|
| at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97)
|
| at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:90)
|
| at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
|
| at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
|
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
|
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
|
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
|
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
|
| at $Proxy45.start(Unknown Source)
|
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
|
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
|
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
|
| at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
|
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
|
| at java.lang.reflect.Method.invoke(Unknown Source)
|
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
|
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
|
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
|
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
|
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
|
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
|
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
|
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
|
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
|
| at $Proxy9.deploy(Unknown Source)
|
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
|
| at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
|
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
|
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
|
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
I have been struggling with this for days, and I really don't know what I'm doing wrong or what state my environment is in. I would sincerely appreciate ANY help anyone can give - I am truly at the end of my rope.
Thanks,
Seth
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165533#4165533
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165533
17 years, 9 months
[JBoss Portal] - Re: Url : how to define MyPortal as the default portal.
by Antoine_h
Hello,
I don't remember exactly what I did for the class in the jira.
I surely modified it to provide it to the portal.
mine is a little bit different, for specific thing of my portal.
however, here the main part of the code of it, that must be changed.
this is working in my portal, with JBP 2.6.4.
// orginal code : Portal portal = ctx.getDefaultPortal();
| PortalObject portalObject = ctx.getChild(getDefaultPortalName());
| if (portalObject == null) {
| throw new IllegalStateException(
| "PortalObject as Default Portal is not found. Default Portal name is defined to : "
| + getDefaultPortalName());
| }
| Portal portal = null;
| if (portalObject instanceof Portal) {
| portal = (Portal) portalObject;
| } else {
| throw new IllegalStateException(
| "Can't find PortalObject with default portal name : "
| + getDefaultPortalName());
| }
| // (.... here the rest of the code of the method)
|
The whole class is quite simple.
the thing to do (modify) is to find the default portal from the name you want, and then make the same process as the original class, with that "portal" instance.
look at the code and make it work your way.
that the most simple thing I believe I can tell for helping you do it.
hope it helps.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165515#4165515
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165515
17 years, 9 months
[JBoss Cache: Core Edition] - Re: cache not flushed as often as expected
by yangju
Sorry the xml quoto was missing. It is
<region name="/_default_">
| <!--0 means no limit -->
| <attribute name="maxNodes">0</attribute>
| <attribute name="timeToLiveSeconds">1800</attribute>
| <attribute name="maxAgeSeconds">1800</attribute>
| </region>
"yangju" wrote : I am running jboss 4.2 and hibernate with jboss treecache (deployed as mbean) as hibernate cache provider. I have the following default region evict policy defined in the treecache-service.xml :
| org.jboss.cache.eviction.LRUPolicy
|
| <!--0 means no limit -->
| 0
| 1800
| 1800
|
|
| In my code I save my query cache into a region called "/myregion". However, I don't have region "/myregion" configured. I thought if myregion is not defined in treecache-service.xml, it falls back to _default_ region. So I expected that every 30 mins my cache is flushed. However, I found that the cache is flushed every 3 or 4 hours, not 30 mins as specified in the _default_ region.
|
| Do I have to define myregion? Doesn't treecache uses default cache policy if it cannot fine myregion?
|
| Thanks.
|
|
|
| <!--0 means no limit -->
| 0
| 1800
| 1800
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165513#4165513
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165513
17 years, 9 months