[jboss-user] [JBoss Cache: Core Edition] - Re: org.jboss.cache.GlobalTransaction never released
Manik, Yes, that's it. Thanks. I would certainly like to upgrade to a more recent version of the Cache. I need to check out what my customer will accept (pay for), and how much I need to touch my code. Otherwise I will use REPL_SYNC. Best Regards, Angus View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218785#4218785 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218785 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Cache: Core Edition] - Problems deploying Cache via MicroContainer following UserGu
I hit one or two little problems following the UserGuide to deploy the Cache. So for the benefit of anyone who follows I am using JBC 3.0.3 with JBossAS 5.0.1. (I copied the jbosscache-core.jar from the release to the server/all/lib directory.) First, contrary to what is stated in the UserGuide, the name of deployment file must end with "-jboss-beans.xml", not "-beans.xml". The annotation entry for CacheJmsWrapper must be all on one line. After that I hit a 'UnsupportedOperationException: Not supported in UnversionedNode' which looked suspiciously like https://jira.jboss.org/jira/browse/JBCACHE-1478. But this is reported as corrected in 3.0.3. I got round it by setting the DefaultCacheFactory boolean parameter to true. My final "example-jboss-beans.xml" file is below. | | | | | | | | | | | | | | | | | udp | Example-EntityCache | REPEATABLE_READ | REPL_SYNC | 15000 | 2 | 15000 | true | | | | | | | | | | | | | true | | | | | | | @org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.cache:service=ExampleTreeCache", exposedInterface=org.jboss.cache.jmx.CacheJmxWrapperMBean.class, registerDirectly=true) | | | | | | | [/url] View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219821#4219821 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219821 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Cache: Core Edition] - Re: LRUPolicy eviction policy
Mircea (or other), Is it possible to configure implicitly created nodes so they are evicted? I have a cache (JBC 303) which will have 100,000 entries, and a depth of 5. So that is, potentially, 400,000 implicitly created nodes hanging around indefinitely (if I have correctly understood). Thanks, Angus View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220641#4220641 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220641 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Cache: Core Edition] - CommandAwareRpcDispatcher called, then nothing.
JBossAS 501. JBC 303, also 302.
JBC clustered. I put something in the cache on one side of the cluster. On the
other side you see it arrive in the trace, CommandAwareRpcDispatcher is called;
then no more sign of it.
Extract from trace below, also the configuation which is closely modeled on
that for EJB3 SFSB.
As ever, any hints, pointers or suggestions greatly appreciated.
| 2009-03-25 18:23:23,204 TRACE [org.jboss.cache.eviction.LRUQueue]
(EvictionTimer-0) LRUQUeue.size() = 0
| 2009-03-25 18:23:23,245 TRACE [org.jgroups.protocols.UDP] (UDP
mcast,129.227.81.159:32829) received (mcast) 652 bytes from 129.227.81.158:45688
| 2009-03-25 18:23:23,245 TRACE [org.jgroups.protocols.UDP]
(Incoming-7,129.227.81.159:32829) message is [dst: , src:
129.227.81.158:32979 (3 headers), size=478 bytes], headers are
MessageDispatcher: [Header: name=MessageDispatcher, type=REQ, id=1238001803363,
rsp_expected=false], dest_mbrs=[129.227.81.159:32829], NAKACK: [MSG, seqno=11],
UDP: [channel_name=SipNotifCache]
| 2009-03-25 18:23:23,246 TRACE [org.jgroups.protocols.FD]
(Incoming-7,129.227.81.159:32829) received msg from 129.227.81.158:32979
(counts as ack)
| 2009-03-25 18:23:23,246 TRACE [org.jgroups.protocols.pbcast.NAKACK]
(Incoming-7,129.227.81.159:32829) [129.227.81.159:32829: received
129.227.81.158:32979#11
| 2009-03-25 18:23:23,246 TRACE [org.jgroups.protocols.FC]
(Incoming-7,129.227.81.159:32829) sender 129.227.81.158:32979 minus 478
credits, 1983138 remaining
| 2009-03-25 18:23:23,246 TRACE [org.jgroups.protocols.FC]
(Incoming-7,129.227.81.159:32829) sender 129.227.81.158:32979 minus 478
credits, 1983138 remaining
| 2009-03-25 18:23:23,246 TRACE [org.jgroups.blocks.RequestCorrelator]
(Incoming-7,129.227.81.159:32829) calling
(org.jboss.cache.marshall.CommandAwareRpcDispatcher) with request 1238001803363
| 2009-03-25 18:23:28,164 TRACE [org.jgroups.protocols.pbcast.STABLE]
(Timer-1,129.227.81.159:32829) setting latest_local_digest from NAKACK:
[129.227.81.158:32979#11, 129.227.81.159:32829#4]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| udp
| SipNotifCache
| true
| PESSIMISTIC
| REPEATABLE_READ
| REPL_ASYNC
| 6
| 2
| 15000
| true
| false
|
| false
|
|
| 0
|
| 0
|
| true
|
|
|
|
|false
|false
|
|
|
|
|
|${jboss.server.data.dir}${/}sipnotifcache
|
|false
|false
|false
|false
|false
|
|
|
|
|
|
|
|
|5000
|
|
|
| /
|
|
|
|1
|
|30
|
|2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| true
|
|
|
|
|
|
|
@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.cache:service=SipNotifCache",
exposedInterface=org.jboss.cache.jmx.CacheJmxWrapperMBean.class,
registerDirectly=true)
|
|
|
|
|
|
|
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221024#4221024
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221024
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Cache: Core Edition] - Re: CommandAwareRpcDispatcher called, then nothing.
Manik, Thanks. Actually I have made progress since. I did not have a jar with the classes to be instantiated in the lib directory. You might say it was a bit impolite of the system to swallow an error like that, without saying anything (there again, you might say it was pretty stupid of me not to make the classes available to the system in the first place). However one thing I have discovered is that it is not a good idea to dynamically set tracing with the cache, as a number of classes set a trace boolean when they initialise, and then stick with that. Hence, I suppose the black hole into which I fell. I had it working with the above config. I am now struggling to get it working with MVCC. I imagine that if I get irrevocably stuck I will be back. Again thank you. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221293#4221293 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221293 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Cache: Core Edition] - Hello World for Dummies
Having struggled for some time to get JBC 30 running in a cluster on JBossAS 50, I have put together a small Hello World type program to show how it is done. It may be accessed here: http://www.opendoors.fr/dummies/dummies.zip. The UserGuide does a very good job of explaining the general principals of the cache, but it does not give detailed code examples. The Unit Tests are just that: they exhaustively tests every imaginable feature, but in an isolated way, so they are not a basis to start developping on the server. So hopefully this program might fill a gap. (If anyone wants to put it somewhere else they are welcome, as the present site is not ideal). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221841#4221841 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221841 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: TestSuite in Eclipse problem
I had the same problem. I tried with a 1.6 jre and got this stack trace: | java.lang.NoClassDefFoundError: Testsuite/output | Caused by: java.lang.ClassNotFoundException: Testsuite.output | at java.net.URLClassLoader$1.run(URLClassLoader.java:200) | at java.security.AccessController.doPrivileged(Native Method) | at java.net.URLClassLoader.findClass(URLClassLoader.java:188) | at java.lang.ClassLoader.loadClass(ClassLoader.java:307) | at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) | at java.lang.ClassLoader.loadClass(ClassLoader.java:252) | at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) | Exception in thread "main" | I then downloaded a new Eclipse, as described above, and it was OK. However I had to go back to jre 1.5 because I hit the problem described here: https://jira.jboss.org/jira/browse/JBWS-2418. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4198762#4198762 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4198762 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: TestSuite in Eclipse problem
I have had this problem again. it happens when you tick 'Copy projects into workspace'. So for the JBossWS samples testsuite in Eclipse I recommend: Do NOT tick 'Copy projects into workspace'. DO use a jre 1.5. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4198779#4198779 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4198779 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Hibernate second level cache with manytomany relationships
I want to use the Hibernate Second level cache for Entity beans. It works fine with simple Entitys, but in the case of many to many relations (for example the 'Relationships' tutorial) it does not work. I think that, at a Hibernate level, there is an explanation here: http://www.javalobby.org/java/forums/t48846.html But I can not see how to implement his suggestion at EJB3 level. I suppose that what I am looking for is an annotation equivalent of | | | | | | Specifically the bit. Can anyone help? Thanks? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4245582#4245582 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4245582 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Persistence, JBoss/CMP, Hibernate, Database] - EJB3 and Hibernate second level cache with manytomany relati
I want to use the Hibernate Second level cache for EJB3 Entity beans. It works fine with simple Entitys, but in the case of many to many relations (for example the 'Relationships' tutorial) it does not work. I think that, at a Hibernate level, there is an explanation here: http://www.javalobby.org/java/forums/t48846.html But I can not see how to implement his suggestion at EJB3 level. I suppose that what I am looking for is an annotation equivalent of | | | | | | Specifically the bit. Can anyone help? Thanks? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4246124#4246124 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4246124 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Hibernate second level cache with manytomany relationshi
I guess maybe I put this in the wrong forum. I have moved it to http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4246124#4246124. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4246126#4246126 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4246126 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Cache: Core Edition] - Re: JBoss Cache (PojoCache) with Hibernate Collections (Pers
I too am trying to persist Hibernate objects in the JBoss Cache, and I hit the same problem: java.lang.VerifyError: class AOPClassProxy$2 overrides final method I do not want to recompile Hibernate; I had originally tries Mark's suggestion of using JBC as the second level cache of Hibernate, but I hit the problem described here:http://www.jboss.org/index.html?module=bb&op=viewtopic&t=159042. Any suggrestions? TVMIA View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4246963#4246963 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4246963 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Cache: Core Edition] - Failure to deploy JdbmCacheLoader with MicroContainer
When I try to deploy JdbmCacheLoader with the MicroContainer, it fails. Same
syntax in my xx-jboss-beans.xml file as for FileCacheLoader (which works). Its
also fails for the JDBCCacheLoader. It's very odd, as I can not see any
difference, from a deployment point of view, between the FileCacheLoader, and
the others. (I have tried various other combinations and permutations for the
config, but they all fail in different ways)
Extract from xx-jboss-beans.xml:
|
|
|
|false
|false
|
|
|
|
|
|${jboss.server.data.dir}${/}sipnotifcache
|
|false
|false
|false
|false
|
|
|
|
|
|
Trace (with Cache tracing enabled):
| 2009-04-01 16:29:16,864 INFO [org.jboss.deployment.MainDeployer] (RMI TCP
Connection(5)-127.0.0.1) deploy,
url=file:/C:/Other/eclipseall/ws/hsi/sipnotif20/releasePackage/sipnotif-jboss-beans.xml
| 2009-04-01 16:29:16,943 ERROR
[org.jboss.kernel.plugins.dependency.AbstractKernelController] (RMI TCP
Connection(5)-127.0.0.1) Error installing to Configured:
name=SipNotifCacheConfig#1 state=Instantiated
| java.lang.RuntimeException: Error configuring property: ignoreModifications
for SipNotifCacheConfig#1
| at
org.jboss.kernel.plugins.dependency.ConfigureAction.dispatchSetProperty(ConfigureAction.java:112)
| at
org.jboss.kernel.plugins.dependency.ConfigureAction.setAttributes(ConfigureAction.java:85)
| at
org.jboss.kernel.plugins.dependency.ConfigureAction.installActionInternal(ConfigureAction.java:44)
| at
org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)
| at
org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42)
| at
org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
| at
org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
| at
org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
| at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
| at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
| at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
| at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
| at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
| at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:774)
| at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540)
| at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:121)
| at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:51)
| at
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
| at
org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
| at
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
| at
org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
| at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
| at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)
| at
org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
| at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
| at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
| at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
| at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
| at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
| at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
| at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
| at
org.jboss
[jboss-user] [JBossWS] - Obscure 'SAXParseException: Content is not allowed in prolog
I have a 'Content is not allowed in prolog' problem. But I am pretty sure that it is not any of the usual culprits (spaces or invalid characters where they should not be). I have a WSDL (below). This is for a document type WS, and the schema is at http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4.xsd . I have verified that the WSDL is WSI Basic Profile 1.1 with soapUI and the WS-I Testing Tools V1.1. It is correctly parsed and treated by wsconsume. The server application is correctly deployed. But when I try to run the client I get (full stack trace below) WSDLException (at /definitions/types/xs:schema/xs:schema): faultCode=PARSER_ERROR: Problem parsing 'http://schemas.xmlsoap.orgsoap/envelope/'.: org.xml.sax.SAXParseException: Content is not allowed in prolog. It seems to get stuck parsing the soap envelope schema, which is imported into the 3GPP schema. (I have validated the 3GPP schema with http://www.w3.org/2001/03/webdata/xsv). JBossWS : version.id=3.0.1-native-2.0.4.GA. As ever, any suggestions ideas infinitely appreciated. WSDL: (I changed the WSDL soap NS to soapx as I thought there might be conficts with the 3GPP NS soap, but it did not make any difference) | http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4"; xmlns:tns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:soapx="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns="http://schemas.xmlsoap.org/wsdl/";> | | http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4"; xmlns:tns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4"; xmlns:xs="http://www.w3.org/2001/XMLSchema"; xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"; elementFormDefault="qualified" attributeFormDefault="unqualified"> | http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4.xsd"/> | | | | | | | | | | | | | | | | | | | | http://schemas.xmlsoap.org/soap/http"/> | | | | | | | | | | | | | | | | | Stack Trace: 09:44:35,338 TRACE [JBossEntityResolver] Mapped systemId to filename: | 09:44:35,338 TRACE [JBossEntityResolver] maps to URL: file:/C:/Other/eclipseall/ws/hsi/mm7-client2/bin/ | [Fatal Error] :1:1: Content is not allowed in prolog. | Exception in thread "main" org.jboss.ws.metadata.wsdl.WSDLException: javax.wsdl.WSDLException: WSDLException (at /definitions/types/xs:schema/xs:schema): faultCode=PARSER_ERROR: Problem parsing 'http://schemas.xmlsoap.org/soap/envelope/'.: org.xml.sax.SAXParseException: Content is not allowed in prolog. | at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:152) | at org.jboss.ws.metadata.umdm.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:293) | at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.buildMetaData(JAXWSClientMetaDataBuilder.java:84) | at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.(ServiceDelegateImpl.java:136) | at org.jboss.ws.core.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:63) | at javax.xml.ws.Service.(Service.java:79) | at org._3gpp.ftp.specs.archive._23_series._23_140.schema.rel_6_mm7_1_4.MM7Service.(MM7Service.java:41) | at test.client.MM7ClientTest2.main(MM7ClientTest2.java:25) | Caused by: javax.wsdl.WSDLException: WSDLException (at /definitions/types/xs:schema/xs:schema): faultCode=PARSER_ERROR: Problem parsing 'http://schemas.xmlsoap.org/soap/envelope/'.: org.xml.sax.SAXParseException: Content is not allowed in prolog. | at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.getDocument(JBossWSDLReaderImpl.java:2136) | at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.parseSchema(JBossWSDLReaderImpl.java:832) | at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.parseSchema(JBossWSDLReaderImpl.java:866) | at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.parseSchema(JBossWSDLReaderImpl.java:656) | at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.parseTypes(JBossWSDLReaderImpl.java:617) | at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.parseDefinitions(JBossWSDLReaderImpl.java:329) | at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.readWSDL(JBossWSDLReaderImpl.java:2290) | at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.readWSDL(JBossWSDLReaderImpl.java:2254) | at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.readWSDL(JBossWSDLReaderImpl.java:2307) | at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.readWSDL(JBossWSDLReaderImpl.java:2328) | at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.readWSDL(JBossWSDLReaderImpl.java:2360) | a
[jboss-user] [JBossWS] - Re: Obscure 'SAXParseException: Content is not allowed in pr
Looking further at this, I think the trace before it blows up is relevent. it is definitely parsing the soap envelope schema: | 2009-05-05 18:03:59,380 DEBUG [org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory] parse: http://frpar-morisona1:8080/mm7/MM7Bean?wsdl | 2009-05-05 18:03:59,568 TRACE [org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory] getBaseInputSource [wsdlUrl=http://frpar-morisona1:8080/mm7/MM7Bean?wsdl] | 2009-05-05 18:03:59,677 TRACE [org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory] getImportInputSource [parent=http://frpar-morisona1:8080/mm7/MM7Bean?wsdl,resource=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4.xsd] | 2009-05-05 18:03:59,677 TRACE [org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory] Trying to resolve: http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4.xsd | 2009-05-05 18:03:59,677 DEBUG [org.jboss.ws.core.utils.JBossWSEntityResolver] resolveEntity: [pub=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4.xsd,sysid=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4.xsd] | 2009-05-05 18:03:59,677 TRACE [org.jboss.util.xml.JBossEntityResolver] resolvePublicID, publicId=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4.xsd | 2009-05-05 18:03:59,677 TRACE [org.jboss.util.xml.JBossEntityResolver] resolveSystemID, systemId=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4.xsd | 2009-05-05 18:03:59,677 TRACE [org.jboss.util.xml.JBossEntityResolver] resolveClasspathName, systemId=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4.xsd | 2009-05-05 18:03:59,677 TRACE [org.jboss.util.xml.JBossEntityResolver] Mapped systemId to filename: REL-6-MM7-1-4.xsd | 2009-05-05 18:03:59,677 TRACE [org.jboss.util.xml.JBossEntityResolver] resolveSystemIDasURL, systemId=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4.xsd | 2009-05-05 18:03:59,677 TRACE [org.jboss.util.xml.JBossEntityResolver] Trying to resolve systemId as a URL | 2009-05-05 18:04:00,115 TRACE [org.jboss.util.xml.JBossEntityResolver] Resolved systemId as a URL | 2009-05-05 18:04:00,287 TRACE [org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory] getImportInputSource [parent=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4.xsd,resource=http://schemas.xmlsoap.org/soap/envelope/] | 2009-05-05 18:04:00,287 TRACE [org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory] Trying to resolve: http://schemas.xmlsoap.org/soap/envelope/ | 2009-05-05 18:04:00,287 DEBUG [org.jboss.ws.core.utils.JBossWSEntityResolver] resolveEntity: [pub=http://schemas.xmlsoap.org/soap/envelope/,sysid=http://schemas.xmlsoap.org/soap/envelope/] | 2009-05-05 18:04:00,287 TRACE [org.jboss.util.xml.JBossEntityResolver] resolvePublicID, publicId=http://schemas.xmlsoap.org/soap/envelope/ | 2009-05-05 18:04:00,287 TRACE [org.jboss.util.xml.JBossEntityResolver] resolveSystemID, systemId=http://schemas.xmlsoap.org/soap/envelope/ | 2009-05-05 18:04:00,302 TRACE [org.jboss.util.xml.JBossEntityResolver] resolveClasspathName, systemId=http://schemas.xmlsoap.org/soap/envelope/ | 2009-05-05 18:04:00,302 TRACE [org.jboss.util.xml.JBossEntityResolver] Mapped systemId to filename: | 2009-05-05 18:04:00,302 TRACE [org.jboss.util.xml.JBossEntityResolver] maps to URL: file:/C:/Other/eclipseall/ws/hsi/mm7-client2/bin/ | | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228712#4228712 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228712 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Tracing wsconsume
Can anybody kindly tell me how to turn on tracing in wsconsume? wsconsume.bat runs WSConsume with -Dlog4j.configuration=wstools-log4j.xml According to the Jamae / Johnson book wstools-log4j.xm is now obsolete. But I have tried replacing it with a reference to another log4j.xml file. To no effect. TIA. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4229311#4229311 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4229311 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: Tracing wsconsume
Peter, Contents of myconsume.bat: | @echo off | | @if not "%ECHO%" == "" echo %ECHO% | @if "%OS%" == "Windows_NT" setlocal | | set DIRNAME=.\ | if "%OS%" == "Windows_NT" set DIRNAME=%~dp0% | set PROGNAME=run.bat | if "%OS%" == "Windows_NT" set PROGNAME=%~nx0% | | set JAVA=%JAVA_HOME%\bin\java | set JBOSS_HOME=C:/jboss/jboss-4.2.2.GA | | rem Setup the java endorsed dirs | set JBOSS_ENDORSED_DIRS=%JBOSS_HOME%\lib\endorsed | | rem Shared libs | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;C:/Other/eclipseall/ws/hsi/mm7-client2/work | | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JAVA_HOME%/lib/tools.jar | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/activation.jar | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/getopt.jar | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/wstx.jar | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jbossall-client.jar | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/log4j.jar | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/mail.jar | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jbossws-spi.jar | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jbossws-common.jar | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jbossws-framework.jar | | rem Shared jaxws libs | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jaxws-tools.jar | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jaxws-rt.jar | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/stax-api.jar | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jaxb-api.jar | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jaxb-impl.jar | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jaxb-xjc.jar | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/streambuffer.jar | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/stax-ex.jar | | rem Stack specific dependencies | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/javassist.jar | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jboss-xml-binding.jar | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jbossws-native-client.jar | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jbossws-native-core.jar | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jbossws-native-jaxws.jar | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jbossws-native-jaxws-ext.jar | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jbossws-native-jaxrpc.jar | set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jbossws-native-saaj.jar | | rem Execute the JVM | "%JAVA%" %JAVA_OPTS% -Djava.endorsed.dirs="%JBOSS_ENDORSED_DIRS%" -Dlog4j.configuration=mylog4j.xml -classpath "%WSCONSUME_CLASSPATH%" org.jboss.wsf.spi.tools.cmd.WSConsume %* | Contents of myrun.bat: | myconsume -k -s ../src -o tmp mm7.wsdl All relevant files (mylog4j.xml, mm7,wsdl ..) are in the folder anonymous wrote : C:\Other\eclipseall\ws\hsi\mm7-client2\work That's kind of you, Angus View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4229963#4229963 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4229963 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: Tracing wsconsume
Peter: (this is going to be a little long :-)) | C:\Other\eclipseall\ws\hsi\mm7-client2\work>myrun | | C:\Other\eclipseall\ws\hsi\mm7-client2\work>myconsume -k -s ../src -o tmp mm7.wsdl | "C:\Sun\AppServer\jdk\bin\java" -Djava.endorsed.dirs="C:/jboss/jboss-4.2.2.GA\lib\endorsed" -Dlog4j.configura | tion=mylog4j.xml -classpath ";C:/Other/eclipseall/ws/hsi/mm7-client2/work;C:\Sun\AppServer\jdk/lib/tools.jar;C | :/jboss/jboss-4.2.2.GA/client/activation.jar;C:/jboss/jboss-4.2.2.GA/client/getopt.jar;C:/jboss/jboss-4.2.2.GA | /client/wstx.jar;C:/jboss/jboss-4.2.2.GA/client/jbossall-client.jar;C:/jboss/jboss-4.2.2.GA/client/log4j.jar;C | :/jboss/jboss-4.2.2.GA/client/mail.jar;C:/jboss/jboss-4.2.2.GA/client/jbossws-spi.jar;C:/jboss/jboss-4.2.2.GA/ | client/jbossws-common.jar;C:/jboss/jboss-4.2.2.GA/client/jbossws-framework.jar;C:/jboss/jboss-4.2.2.GA/client/ | jaxws-tools.jar;C:/jboss/jboss-4.2.2.GA/client/jaxws-rt.jar;C:/jboss/jboss-4.2.2.GA/client/stax-api.jar;C:/jbo | ss/jboss-4.2.2.GA/client/jaxb-api.jar;C:/jboss/jboss-4.2.2.GA/client/jaxb-impl.jar;C:/jboss/jboss-4.2.2.GA/cli | ent/jaxb-xjc.jar;C:/jboss/jboss-4.2.2.GA/client/streambuffer.jar;C:/jboss/jboss-4.2.2.GA/client/stax-ex.jar;C: | /jboss/jboss-4.2.2.GA/client/javassist.jar;C:/jboss/jboss-4.2.2.GA/client/jboss-xml-binding.jar;C:/jboss/jboss | -4.2.2.GA/client/jbossws-native-client.jar;C:/jboss/jboss-4.2.2.GA/client/jbossws-native-core.jar;C:/jboss/jbo | ss-4.2.2.GA/client/jbossws-native-jaxws.jar;C:/jboss/jboss-4.2.2.GA/client/jbossws-native-jaxws-ext.jar;C:/jbo | ss/jboss-4.2.2.GA/client/jbossws-native-jaxrpc.jar;C:/jboss/jboss-4.2.2.GA/client/jbossws-native-saaj.jar" org | .jboss.wsf.spi.tools.cmd.WSConsume -k -s ../src -o tmp mm7.wsdl | parsing WSDL... | | | generating code... | | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\AddressCodingType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\AddressType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\AnyDataType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\CancelReqType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\CapabilitiesType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ChargedPartyType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ContentClassType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ContentReferenceType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\DeliverReqType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\DeliverRspType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\DeliveryConditionType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\DeliveryReportReqType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ExtendedcancelReqType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ExtendedcancelRspType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ExtendedcancelresponseStatusType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ExtendedreplaceReqType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ExtendedreplaceRspType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\GenericRSReqType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\GenericResponseType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\GenericVASPRequestType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\MM7.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\MM7Service.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\MMStatusExtensionType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\MessageClassType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\MmDeliveryStatusType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\MmReadStatusType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\MultiAddressType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ObjectFactory.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\PreviouslySentByDateTime.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\PreviouslySentByType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\PriorityType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\ReadReplyReqType.java | org\_3gpp\ftp\specs\archive\_23_series\_23_140\schema\rel_6_mm7_1_4\RecipientsType.j
