December 2006 - jboss-user - Jboss List Archives

[JBoss Messaging] - Re: javax.jms.InvalidDestinationException: Destination is no

by chaituu

aboveJMS client code is correct or not?? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994233#3994233 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994233

19 years, 4 months

1
0
0 / 0

[JBoss Eclipse IDE (users)] - Re: Can't Access JBoss 4.0.2 via IP address while running in

by tpaulsz

I can access my web application when the url is: http://localhost:8080/mywebapp But I get a 'Cannot find server' error when the url is: http://10.299.99.99:8080/mywebapp I need the server to be operable with both urls. My environment is: IDE: JBossIDE for Eclipse Build id: 2.0.0.Beta2 AS: JBoss Version: 4.0.5GA(build: CVSTag=Branch_4_0 date=200610162340) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994232#3994232 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994232

19 years, 4 months

1
0
0 / 0

[JBoss Seam] - Re: Referencing global view-id variables from .jpdl.xml

by gavin.king＠jboss.com

Just especially for you, sir, I added a protected method named getViewId(Page) to org.jboss.seam.core.Pageflow, so that you can override that method and do whatever crazy thing you like in it ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994231#3994231 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994231

19 years, 4 months

1
0
0 / 0

[EJB 3.0] - ejb3-timer-service.xml with PostgreSQL

by Juergen.Zimmermann

In ejb3-timer-service.xml I made these changes:HSQLDBDelegate -> PostgreSQLDelegate | qrtz_job_details: BINARY -> oid | IS_VOLATILE VARCHAR(1) -> IS_VOLATILE boolean | qrtz_triggers: BINARY -> oid | IS_VOLATILE VARCHAR(1) -> IS_VOLATILE boolean | qrtz_blob_triggers: BINARY -> oid | qrtz_calendars: BINARY -> oid | qrtz_fired_triggers: IS_VOLATILE VARCHAR(1) -> IS_VOLATILE boolean | REQUESTS_RECOVERY VARCHAR(1) -> REQUESTS_RECOVERY boolean When starting JBossAS I get this error message and stack trace although server/default/deploy/postgres-ds.xml defines DefaultDS:2006-12-15 11:24:27,882 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Start: name=jboss.ejb:persistencePolicy=database,service=EJBTimerService state=Create mode=Manual requiredState=Installed | java.lang.IllegalStateException: Cannot find datasource meta data: jboss.jdbc:datasource=DefaultDS,service=metadata | at org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin.init(GeneralPurposeDatabasePersistencePlugin.java:101) | at org.jboss.ejb.txtimer.DatabasePersistencePolicy.startService(DatabasePersistencePolicy.java:92) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | 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:668) | at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:184) | at $Proxy0.start(Unknown Source) | at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42) | at org.jboss.system.microcontainer.ServiceControllerContextAction.install(ServiceControllerContextAction.java:46) | at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) | at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226) | at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:198) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:709) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:429) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:538) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:472) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:320) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:190) | at org.jboss.system.ServiceController.doChange(ServiceController.java:656) | at org.jboss.system.ServiceController.start(ServiceController.java:431) | at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:124) | at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:85) | at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:44) | at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:53) | at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52) | at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:145) | at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:440) | at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:451) | at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:381) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:366) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:246) | at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89) | at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:401) | at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:340) | at org.jboss.Main.boot(Main.java:210) | at org.jboss.Main$1.run(Main.java:508) | at java.lang.Thread.run(Thread.java:595) Any hint is appreciated! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994230#3994230 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994230

19 years, 4 months

1
0
0 / 0

[JBoss/Spring Integration] - Spring deployer + cluster

by viniciuscarvalho

Hi there! I just checked the new Spring deployer. One simple question. Does the applicationcontext get registred under jndi? Would it mean that using a cluster jndi I would have a single bean shared through the cluster? Regards View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994229#3994229 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994229

19 years, 4 months

1
0
0 / 0

[JBoss Seam] - Re: Event scoped component accessing Conversion scope

by quilleashm

I'll check the debug handler exception when I download the 1.1 release shortly. Cheers. Mike. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994228#3994228 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994228

19 years, 4 months

1
0
0 / 0

[JBoss Seam] - Re: Event scoped component accessing Conversion scope

by quilleashm

I think this means you can't have a conversation scoped component with UI component bindings. At the moment the setters for any binding="" get called during the restore view phase at which point the conversation scope is not valid. Is there any way round this or plans to address this in the future? Cheers. Mike. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994227#3994227 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994227

19 years, 4 months

1
0
0 / 0

[JBoss Messaging] - Re: javax.jms.InvalidDestinationException: Destination is no

by chaituu

"timfox" wrote : javax.jms.InvalidDestinationException: Destination is not an instance of SpyDestination JBossQueue[t | estQueue] | | | SpyDestination is a JBossMQ class, not JBoss Messaging. | | You are probably trying to use a JBossMQ client to talk to JBoss Messaging. | | I suspect you haven't uninstalled JBossMQ. My client is in default instance.so how to uninstalled JBossMQ.?? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994226#3994226 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994226

19 years, 4 months

1
0
0 / 0

[Security & JAAS/JBoss] - Re: Classcast exception in LoginContext.getAttributeNames()

by sohil.shah＠jboss.com

Thanks Nick View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994224#3994224 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994224

19 years, 4 months

1
0
0 / 0

[JBoss jBPM] - Re: Request didn't include a SOAP Message

by bertrand.njiipwo

I'll like to bring some precision once again. I have tried some test scenario. When i specify the service wsdl location: http://localhost.8081/creditprocess/schufa at the first time monitoring component receive a request. Hier some output: | Starting daemon thread...ok. | - Listening to port: 8081 | | 1. Incoming TCP connection from 127.0.0.1:1089 | log4j:WARN Detected problem with connection: java.net.SocketException: Software | caused connection abort: socket write error | 1. Received request | - Request URL: '/creditprocess/schufa' | - Request did not include a SOAP message. | - Searching endpoint URL with target 'portal:Schufa' | - Endpoint URL found: 'http://127.0.0.1:8080/axis/services/SchufaServiceB', | known response time is '8000' | - Calling remote service (timeout 16000ms)...done. (Call duration: 7581 ms) | 1. Sending response to client...done. | 1. Request was successfully handled. | but if i deployed the schufa service as process partner and specify the wsdl-location to http://localhost:8080/schufa/schufaWS?wsdl, i can send the message to the service endpoint: http://localhost:8080/schufa/schufaWS. In this case the jbpm-module runns perfectly and i can see the exanged Message persisted in the DB: | | Client SOAPRequest to loanapproval process: | | <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> | <SOAP-ENV:Body> | <m:apply xmlns:m="urn:samples:loanapproval"> | <loanRequestParameters> | <firstName>MyFirstName</firstName> | <lastName>MyLastName</lastName> | <amount>1000</amount> | </loanRequestParameters> | </m:apply> | </SOAP-ENV:Body> | </SOAP-ENV:Envelope> | | | loanRequestParameters: | | <?xml version="1.0" encoding="UTF-8"?> | <loanRequestParameters xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:m="urn:samples:loanapproval" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> | <firstName>MyfirstName</firstName> | <lastName>MyLastName</lastName> | <amount>1000</amount> | </loanRequestParameters> | | loanResponse: | | <?xml version="1.0" encoding="UTF-8"?> | <loanResponse><approved xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapBodyNS="urn:samples:schufa" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="1"/> | </loanResponse> | | validCustomerReturn: | | <?xml version="1.0" encoding="UTF-8"?><validCustomerReturn xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapBodyNS="urn:samples:schufa" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="1"/> | | _firstname: | | <?xml version="1.0" encoding="UTF-8"?> | <_firstname xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" | xmlns:m="urn:samples:loanapproval" xmlns:xsd="http://www.w3.org/2001/XMLSchema" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">MyFirstName | </_firstname> | | _surname: | | <?xml version="1.0" encoding="UTF-8"?> | <_surname xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" | xmlns:m="urn:samples:loanapproval" xmlns:xsd="http://www.w3.org/2001/XMLSchema" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">MyLastName | </_surname> Know when send a soap message directly to http://localhost:8081/creditprocess/schufa and specify the parameter value in the SOAP request its running fine. Some possible cause of this problem is that i'm try to integrate an non ws4ee web service with my bussiness process. The jBPM module require a java classe as service endpoint interface. With this he can access the message send and can persist this using hibernate (endpoint=http://localhost:8080/schufa/schufaWS). But if the service i'm trying to access is not a java service endpoint (endpoint=http://localhost:8081/creditprocess/schufa) then the service Handler can't access the exchanged soap messages. This may be why the request is sent to the specified endpoint but there is no soap message inside. With the first prototype the BPEL engine was BPEL4J from IBM and the services was deployed on the SOAP-Engine Axis and the monitoring component (java program) could catch the web service call inside the process execution an redirect it to the monitoring module without problem. Because of some features of jBPM by executing BPEL-Processes i'll like to substituate BPEL4J with jBPM and expect to get full access to the process execution information. I hope this can help a little bit. The serverLog is avialabe (email). Thanks once again Bertrand Njipwo View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994221#3994221 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994221

19 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user December 2006