April 2008 - jboss-user - Jboss List Archives

[JBossWS] - java-->wsdl/xsd query - minOccurs value of args for wsdl ope

by yogeshkb

Hi Team, I have a wsdl/xsd snippet generated for an SEI below. <xs:complexType name='addBannedUser'> <xs:sequence> <xs:element minOccurs='0' name='arg0' type='xs:string'/> <xs:element minOccurs='0' name='arg1' type='xs:string'/> </xs:sequence> The arguments for the operation are all mandatory and they cannot be null. Pls help me on how to configure the wsprovide scripts to generate the wsdl/xsd with the minOccurs=1 for all the arguments of my operation. Regards, Yogesh View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144799#4144799 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144799

18 years, 3 months

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - Re: setting up properties in the run script

by nirajsingh

Hi rob, If i am not wrong, Eclipse has their own environment for setting the JAVA_OPTS. Once you attached the jboss app to eclipse then over the start server from the right click you can set the JAVA_OPTS. Regards, Niraj Kumar Singh View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144798#4144798 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144798

18 years, 3 months

1
0
0 / 0

[JBossWS] - Re: org.jboss.ws.WSException

by maffeis

Hi. I was able to work around this issue by naming all my WSDL request parameters as "arg0", "arg1" etc (instead of "id", "name" in your example), and by naming by response parameter as "result". Probably there is a cleaner solution using JAXB annotation, which allows you to name parameters the way you like. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144797#4144797 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144797

18 years, 3 months

1
0
0 / 0

[Remoting] - Re: What are you using Remoting for?

by thejavafreak

"david.lloyd(a)jboss.com" wrote : I am currently working on the design for Remoting 3, and I'd like to hear what the end-users of Remoting are using it for, or what you'd LIKE to use it for, and what features (like transports for example) are most useful to you. Also, please share what features you think are missing, that you'd like to see in future versions. | | Please keep posts in this thread related to the main topic only - any replies to posts within this thread should be moved to a new thread. Thanks. I am using it for our IVR (Interactive Voice Response) program. I use it to get the data input stream from the socket sent by the IVR and send back the response to the IVR. Thanks for this great JBoss Remoting project, we are able to reduce boiler plate codes, although we still have some issue as we can not get the invocation handler to be deployed on JBoss AS. Until now we are using the Simple server as standalone apps to handle the streams from the IVR. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144793#4144793 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144793

18 years, 3 months

1
0
0 / 0

[JBoss Portal] - Re: IDE that supports portlet development for JBOSS Portal

by csagar

"yhqian95" wrote : I have installed the bundle package of JBOSS server and Portal server( jboss-portal-2.0-jboss-4.0.2) and deployed the helloworld portlet. It works fine. | | Now I want to code my own portlet and portal. | I am using JBOSS Eclipse IDE for the development on the JBOSS application server. The JBOSS Eclipse IDE tool dosen't support portlet development so far, how can I start? Is there an IDE that support portlet development on the JBOSS platform? | | Thanks | | hi, Hope you are still there on this forum. have you got any solution to your problem??? I am stuck at the same problem . Wanted to send you email but couldn't see ur email id in ur profile.Please reply to csagar(a)techmahindra.com if you get this mail View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144792#4144792 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144792

18 years, 3 months

1
0
0 / 0

[Security & JAAS/JBoss] - Re: How to configure

by draggy

hello people, Now I'm getting some error: | 2008-04-17 18:02:47,113 DEBUG [org.jboss.security.auth.login.XMLLoginConfig] Starting jboss.security:service=XMLLoginConfig | 2008-04-17 18:02:47,113 DEBUG [org.jboss.security.auth.login.XMLLoginConfigImpl] Try loading config as XML, url=file:/C:/jboss-portal-2.6.4/server/default/conf/login-config.xml | 2008-04-17 18:02:47,254 DEBUG [org.jboss.security.auth.login.XMLLoginConfigImpl] Failed to load config as XML | org.jboss.xb.binding.JBossXBException: Failed to parse source: The element type "authentication" must be terminated by the matching end-tag "</authentication>". @ *unknown*[166,4] | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:193) | at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:158) | at org.jboss.security.auth.login.XMLLoginConfigImpl.loadXMLConfig(XMLLoginConfigImpl.java:324) | at org.jboss.security.auth.login.XMLLoginConfigImpl.loadConfig(XMLLoginConfigImpl.java:288) | at org.jboss.security.auth.login.XMLLoginConfigImpl.loadConfig(XMLLoginConfigImpl.java:268) | at org.jboss.security.auth.login.XMLLoginConfig.startService(XMLLoginConfig.java:176) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) | at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:597) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) | at $Proxy0.start(Unknown Source) | at org.jboss.system.ServiceController.start(ServiceController.java:417) | 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:597) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | 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 $Proxy4.start(Unknown Source) | at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) | 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 org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) | 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:597) | 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 $Proxy5.deploy(Unknown Source) | at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) | at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) | at org.jboss.Main.boot(Main.java:200) | at org.jboss.Main$1.run(Main.java:508) | at java.lang.Thread.run(Thread.java:619) | Caused by: org.xml.sax.SAXException: The element type "authentication" must be terminated by the matching end-tag "</authentication>". @ *unknown*[166,4] | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.fatalError(SaxJBossXBParser.java:355) | at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source) | at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) | at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) | at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source) | at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) | at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) | at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) | at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) | at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) | at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) | at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) | at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:189) | ... 53 more | 2008-04-17 18:02:47,254 DEBUG [org.jboss.security.auth.login.XMLLoginConfigImpl] Try loading config as Sun format, url=file:/C:/jboss-portal-2.6.4/server/default/conf/login-config.xml | 2008-04-17 18:02:47,269 WARN [org.jboss.security.auth.login.XMLLoginConfigImpl] End loadConfig, failed to load config: file:/C:/jboss-portal-2.6.4/server/default/conf/login-config.xml | org.jboss.security.auth.login.ParseException: Encountered "<?xml" at line 1, column 1. | Was expecting one of: | <EOF> | <IDENTIFIER> ... | | at org.jboss.security.auth.login.SunConfigParser.generateParseException(SunConfigParser.java:395) | at org.jboss.security.auth.login.SunConfigParser.jj_consume_token(SunConfigParser.java:333) | at org.jboss.security.auth.login.SunConfigParser.config(SunConfigParser.java:98) | at org.jboss.security.auth.login.SunConfigParser.parse(SunConfigParser.java:57) | at org.jboss.security.auth.login.SunConfigParser.doParse(SunConfigParser.java:79) | at org.jboss.security.auth.login.XMLLoginConfigImpl.loadSunConfig(XMLLoginConfigImpl.java:310) | at org.jboss.security.auth.login.XMLLoginConfigImpl.loadConfig(XMLLoginConfigImpl.java:294) | at org.jboss.security.auth.login.XMLLoginConfigImpl.loadConfig(XMLLoginConfigImpl.java:268) | at org.jboss.security.auth.login.XMLLoginConfig.startService(XMLLoginConfig.java:176) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) | at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:597) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) | at $Proxy0.start(Unknown Source) | at org.jboss.system.ServiceController.start(ServiceController.java:417) | 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:597) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | 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 $Proxy4.start(Unknown Source) | at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) | 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 org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) | 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:597) | 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 $Proxy5.deploy(Unknown Source) | at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) | at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) | at org.jboss.Main.boot(Main.java:200) | at org.jboss.Main$1.run(Main.java:508) | at java.lang.Thread.run(Thread.java:619) | 2008-04-17 18:02:47,488 DEBUG [org.jboss.security.auth.login.XMLLoginConfig] Started jboss.security:service=XMLLoginConfig | 2008-04-17 18:02:47,488 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.security:service=XMLLoginConfig dependent components: [] | 2008-04-17 18:02:47,488 DEBUG [org.jboss.system.ServiceController] starting service jboss.security:service=JaasSecurityManager | 2008-04-17 18:02:47,488 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] Starting jboss.security:service=JaasSecurityManage | and here is my login-config.xml: | <?xml version='1.0'?> | <!DOCTYPE policy PUBLIC | "-//JBoss//DTD JBOSS Security Config 3.0//EN" | "http://www.jboss.org/j2ee/dtd/security_config.dtd"> | |  | | <policy> |  | <application-policy name = "client-login"> | <authentication> | <login-module code = "org.jboss.security.ClientLoginModule" | flag = "required"> |  | <module-option name="restore-login-identity">true</module-option> | </login-module> | </authentication> | </application-policy> | |  | <application-policy name = "jbossmq"> | <authentication> | <login-module code = "org.jboss.security.auth.spi.DatabaseServerLoginModule" | flag = "required"> | <module-option name = "unauthenticatedIdentity">guest</module-option> | <module-option name = "dsJndiName">java:/DefaultDS</module-option> | <module-option name = "principalsQuery">SELECT PASSWD FROM JMS_USERS WHERE USERID=?</module-option> | <module-option name = "rolesQuery">SELECT ROLEID, 'Roles' FROM JMS_ROLES WHERE USERID=?</module-option> | </login-module> | </authentication> | </application-policy> | |  | |  | <application-policy name = "HsqlDbRealm"> | <authentication> | <login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule" | flag = "required"> | <module-option name = "principal">sa</module-option> | <module-option name = "userName">sa</module-option> | <module-option name = "password"></module-option> | <module-option name = "managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=DefaultDS</module-option> | </login-module> | </authentication> | </application-policy> | | <application-policy name = "JmsXARealm"> | <authentication> | <login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule" | flag = "required"> | <module-option name = "principal">guest</module-option> | <module-option name = "userName">guest</module-option> | <module-option name = "password">guest</module-option> | <module-option name = "managedConnectionFactoryName">jboss.jca:service=TxCM,name=JmsXA</module-option> | </login-module> | </authentication> | </application-policy> | |  | <application-policy name = "jmx-console"> | <authentication> | <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" | flag = "required"> | <module-option name="usersProperties">props/jmx-console-users.properties</module-option> | <module-option name="rolesProperties">props/jmx-console-roles.properties</module-option> | </login-module> | </authentication> | </application-policy> | |  | <application-policy name = "web-console"> | <authentication> | <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" | flag = "required"> | <module-option name="usersProperties">web-console-users.properties</module-option> | <module-option name="rolesProperties">web-console-roles.properties</module-option> | </login-module> | </authentication> | </application-policy> | |  | <application-policy name="JBossWS"> | <authentication> | <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" | flag="required"> | <module-option name="usersProperties">props/jbossws-users.properties</module-option> | <module-option name="rolesProperties">props/jbossws-roles.properties</module-option> | <module-option name="unauthenticatedIdentity">anonymous</module-option> | </login-module> | </authentication> | </application-policy> | |  | <application-policy name = "other"> |  | <authentication> | <login-module code = "org.jboss.security.auth.spi.UsersRolesLoginModule" | flag = "required" /> | </authentication> | </application-policy> | |  | <application-policy name = "SPNEGO"> | <authentication> | <login-module code = "org.jboss.security.auth.NegotiateLoginModule" | flag = "required" /> | <module-option name="loadBalancer">false</module-option> | <module-option name="domainController">192.168.0.1</module-option> | <module-option name="defaultDomain">test.com</module-option> | </login-module> | </authentication> | </application-policy> | | </policy> | May I know what went wrong? Thank you View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144789#4144789 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144789

18 years, 3 months

1
0
0 / 0

[JBoss Portal] - Portlet instances DTD not reachable: 404 Error

by boopet

Hi, our eclipse projects show errors because of a broken DTD reference in the file "portlet-instances.xml". the DTD there can not be resolved because the jboss server shows a 404 error: http://www.jboss.org/portal/dtd/portlet-instances_2_6.dtd Is this issue known or did the URL change? Best regards, Norbert View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144787#4144787 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144787

18 years, 3 months

1
0
0 / 0

[JBoss Getting Started Documentation] - jboss portal server is not opening

by shambhu

after downloading the jboss portal bundle , i unzip that in separate folder.but when i go to bin and click on run.bat .the black screen comes for a a second and then it vanishes.plz.tell me the reason. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144780#4144780 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144780

18 years, 3 months

1
0
0 / 0

[JBossWS] - Re: problem with calling ssl web service

by rapowder

The '1' is not a mistake, it was just an example to tell you that I have different webservices under different paths with the same root: /interfaces/InterfaceBean1 | /interfaces/InterfaceBean2 | etc. I am not sure whether this was clear, but that those are webservices listening to SOAP calls and the problem is that the associated wsdl files are not correctly generated by JBoss. I also have the same configuration in server.xml, and I also have a redirection from http://...:8080 to https://...:8443, which works correctly for my web client. I was actually wondering if the configuration is possible through jws annotations... Let me post you some more code, maybe this will help... Here one of the interface beans: | import javax.ejb.Stateless; | import javax.jws.WebMethod; | import javax.jws.WebParam; | import javax.jws.WebService; | import javax.jws.soap.SOAPBinding; | | @Stateless | @WebService | @SOAPBinding(style = SOAPBinding.Style.RPC) | public class GenericInterfaceAgentBean implements GenericInterfaceAgent { | | @WebMethod | public String sessionLogin( | @WebParam(name = "pUsername")String user, | @WebParam(name = "pPassword")String pass | ) { ... } | | .... | | } | When I restart JBoss, a wsdl file is generated under the path: jboss\server\myconf\data\wsdl\myapp.ear\myapp.jar\GenericInterfaceAgentBeanServiceXXX.wsdl and the wsdl file contains (useful pieces of code) (srv11 is the hostname of my server) | <?xml version="1.0" encoding="UTF-8"?> | <definitions name="GenericInterfaceAgentBeanService" | targetNamespace="http://beans.generic.interfaces.system.myserver.com/" | xmlns:tns="http://beans.generic.interfaces.system.myserver.com/" | xmlns:ns1="http://jaxb.dev.java.net/array" | xmlns:xsd="http://www.w3.org/2001/XMLSchema" | xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" | xmlns="http://schemas.xmlsoap.org/wsdl/"> | | ... | | <service name="GenericInterfaceAgentBeanService"> | <port name="GenericInterfaceAgentBeanPort" binding="tns:GenericInterfaceAgentBeanBinding"> | <soap:address location="http://srv11:8080/interfaces/GenericInterfaceAgentBean"/> | </port> | </service> | | but what I would like is | | ... | | <service name="GenericInterfaceAgentBeanService"> | <port name="GenericInterfaceAgentBeanPort" binding="tns:GenericInterfaceAgentBeanBinding"> | <soap:address location="https://www.myserver.com:8443/interfaces/GenericInterfaceAgentBean"/> | </port> | </service> | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144778#4144778 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144778

18 years, 3 months

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - setting up properties in the run script

by rob_gar_esp

Hi, I modified my run.bat script in order to add environment properties like these: set JAVA_OPTS=%JAVA_OPTS% -Dprogram.name=%PROGNAME% -DSIWO_HOME=C://SIWO-INF -DSCHEMA_BASE_PATH=//schemas when I run the script from a command console works properly, however, I installed the jboss tools plug-in in my eclipse IDE, and when starting the server from eclipse those properties are never setup. Please assist, thanks!!! ///RG View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144774#4144774 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144774

18 years, 3 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 April 2008