September 2006 - jboss-user - Jboss List Archives

[Messaging, JMS & JBossMQ] - MDB + durable topic + cluster (failover)

by dooart

Hi there. I've searched the entire forum and couldn't found a way to configure two different clientIDs for a MDB that will be deployed to a two-node cluster. I really don't want to configure this at ejb-jar.xml and create two different EARs every time that I make a change. I've tried to configure it too at uil2-service.xml and put this file at the deploy directory instead of hasingleton, but it didn't work (the second node copied the clientid information and the container raised an exception). Does anybody knows another way to do this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969680#3969680 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969680

19 years, 7 months

1
0
0 / 0

[JBoss jBPM] - jPDL vs. BPEL - I am a bit confused

by rainstar79

Hi jBPM Gurus, I am a bit confused in one thing. Maybe you can help me. I am trying to introduce some students BPM and BPEL. It is just to give them a short overview about tools, methods, standards,... Therefore I wanted to set up a jBPM environment to test some things for a presentation. I thought, when I install jBPM I can use the Eclipse Plugin to model a BPEL file graphically. But I guess that the output is something called jPDL. How could you compare this with BPEL? What is more powerfull - BPEL or jPDL? What are the restrictions of jPDL? Is there a way (or need) of mapping a jPDL after modeling with the graphical tool into BPEL for further processing? Can you recomend me a free modeling tool for generating BPEL which works well with jBPM? Thanks for your help Rainer View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969679#3969679 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969679

19 years, 7 months

1
0
0 / 0

[Tomcat, HTTPD, Servlets & JSP] - Re: Apache workers.properties help please.

by AndrewBoyd

Its still not working but a little bit of sleep has helped me see at least one mistake. I did not have the loadbalancer in my worker.list but I referenced it in my uirworkermap.properties so now my workers.properties looks like: | worker.list=loadbalancer,status | | | # Define Node1 | # modify the host as your host IP or DNS name. | worker.node1.port=8009 | worker.node1.host=node1.howibecameaninternetmillionaire.com | worker.node1.type=ajp13 | worker.node1.lbfactor=1 | # worker.node1.connection_pool_size=10 (1) | | # since inetMillionaire only has one server at this time comment out node2 | # Define Node2 | # modify the host as your host IP or DNS name. | #worker.node2.port=8009 | #worker.node2.host= node2.howibecameaninternetmillionaire.com | #worker.node2.type=ajp13 | #worker.node2.lbfactor=1 | # worker.node1.connection_pool_size=10 (1) | | # Load-balancing behaviour | worker.loadbalancer.type=lb | #worker.loadbalancer.balance_workers=node1,node2 | worker.loadbalancer.balance_workers=node1 | | # Status worker for managing load balancer | worker.status.type=status | Any ideas? Thanks, Andrew View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969678#3969678 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969678

19 years, 7 months

1
0
0 / 0

[JBoss jBPM] - Re: Possible bug in fork-joins

by gmournos

Thx for the fast reply. Well, this coupling of forks and joins puts me off a bit. I would rather that jbpm would be smart enough to figure out that the join is "joining" both parent forks, instead of introducing structural constraints that cannot be automatically validated at design time. Is there an AUTOMATIC way to decouple joins from forks by setting any of the flags (e.g. discriminator and NoutofM)? Or an AUTOMATIC way to achieve behavior similar to introducing a second join. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969675#3969675 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969675

19 years, 7 months

1
0
0 / 0

[JBoss jBPM] - task assignment when using hierarchical user groups

by bert.w

Hi, I am using the identity component to organise the users that use my application. I made a hierarchical order like this: group: all --> group: division1 --> group: division2 --> group: division3 also there are 2 kinds of roles a user can have. "gebruiker" or "hoofdgebruiker" The problem i have is when i use this assignment for a task: <assignment expression="group(all) --> member(hoofdgebruiker)" /> it only assigns the "hoofdgebruiker" users that are a member of the parent group "all", but not the "hoofdgebruiker" users that are in the subgroups. Is there an expression to achieve this? Or is the only solution changing the Group.getUsers() method, to make this return also the users in the subgroups? thanks, BERT View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969673#3969673 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969673

19 years, 7 months

1
0
0 / 0

[Installation, Configuration & Deployment] - Avoid changes in JBoss installation directory using symlinks

by rtm333

Hi, We want to set up JBoss AS in a multi-user Solaris 10 environment in such a way that no modifications are necessary within the JBoss installation itself. I.e. we do not want to place the users' server configurations in $JBOSS_HOME/server. In our opinion there are (at least) three good reasons for this approach: 1) It keeps a clear separation between the JBoss AS installation and our own applications. 2) It avoids granting write permissions for the JBoss installation to the users. 3) It eases the switching between several JBoss releases. Our first solution approach replaced the server configuration directories by symbolic links to the actual directories. E.g.: ln -s $APP1_HOME/server/app1 $JBOSS_HOME/server/ This works and allows starting the application as if it were physically in the $JBOSS_HOME/server directory: $JBOSS_HOME/bin/run.sh -c app1 But it still requires write permissions to create the symlinks. What we would prefer is having the symlinks going in the opposite direction. Let's call the original JBoss installation directory $JBOSS_INSTALL_HOME. ln -s $JBOSS_INSTALL_HOME/bin $APP1_HOME/ | ln -s $JBOSS_INSTALL_HOME/lib $APP1_HOME/ | mkdir $APP1_HOME/server The user's application is placed in $APP1_HOME/server and started with ($JBOSS_HOME is now pointing to $APP1_HOME): $JBOSS_HOME/bin/run.sh -c app1 Unfortunately, this does not work as expected. JBoss aborts with a message that it can't find jboss-service.xml: Failed to boot JBoss: | org.jboss.deployment.DeploymentException: url file:$JBOSS_INSTALL_HOME/server/app1/conf/jboss-service.xml could not be opened, does it exist? Obviously, JBoss is looking for the file in the physical directory structure ($JBOSS_INSTALL_HOME) and not in the logical structure ($JBOSS_HOME aka $APP1_HOME). Does anybody know whether this is a bug or works as designed? It might even be specific to Solaris 10, where there seems to be a similar effect when cd'ing along a symbolic link and then spawning a new ksh. Whereas the parent ksh shows the symlink in the pwd, the child shell shows the physical directory. Any help welcome. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969672#3969672 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969672

19 years, 7 months

1
0
0 / 0

[JBossWS] - Re: Newbie question: Just a first webservice client

by dirkschmitz

Hi! i have a similar problem with my webservice test client using the dynamic invocation interface (DII). When I try to run the client within Eclipse I get the following Exception Exception in thread "main" javax.xml.rpc.ServiceException: Provider com.sun.xml.rpc.client.ServiceFactoryImpl not found at javax.xml.rpc.FactoryFinder.newInstance(FactoryFinder.java:44) at javax.xml.rpc.FactoryFinder.find(FactoryFinder.java:137) at javax.xml.rpc.ServiceFactory.newInstance(ServiceFactory.java:58) at de.mtag.ws.samples.client.WebServiceClient.main(WebServiceClient.java:29) The classpath of the webservice testclient contains the following JBoss-Client-Jars activation.jar commons-logging.jar javaassist.jar jbossall-client.jar jbossws-client.jar log4j.jar mail.jar Web Service Test Client | public class WebServiceClient { | | /** | * @param args | */ | public static void main(String[] args) throws Exception | { | String urlstr = args[0]; | String argument = args[1]; | | System.out.println("Contacting webservice at " + urlstr); | | URL url = new URL(urlstr); | | String ns = "http://xx.xxx.ws.samples.services/simple"; | QName qname = new QName(ns, "SimpleWS"); | QName port = new QName(ns, "SimpleService"); | QName operation = new QName(ns, "echo"); | | ServiceFactory factory = ServiceFactory.newInstance(); | Service service = factory.createService(url, qname); | Call call = service.createCall(port, operation); | | System.out.println("SimpleService.echo(" + argument + ")"); | System.out.println("output:" + call.invoke(new Object[] {argument})); | | } | | } | Service Endpoint Interface | public interface SimpleService { | | public String echo(String echo); | | } | Service Endpoint Implementation | @WebService( | name = "SimpleWS", | targetNamespace = "http://xx.xxx.ws.samples.services/simple", | serviceName = "SimpleWS" | ) | @SOAPBinding(style = SOAPBinding.Style.RPC) | public class SimpleEndpoint implements SimpleService { | | @WebMethod | public String echo(String theEcho) { | return theEcho; | } | | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969671#3969671 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969671

19 years, 7 months

1
0
0 / 0

[JBoss AOP] - Re: Problems getting AOP to work on jboss4.0.4GA

by louberl

I found that an incorrect use of xDoclet can lead to errors being generated in files like web.xml (and other generated files). Which may result in exceptions like this one. check out http://lists.jboss.org/pipermail/jboss-user/2006-July/003506.html for a nice description and a possible solution. Thanks to azhurakousky for solution. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969670#3969670 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969670

19 years, 7 months

1
0
0 / 0

[EJB 3.0] - Re: EJB3 WebServices

by leonell

Yes. But this is Netbeans project, parameters for script are readed from project.properties file: File: project.properties: | application.args= | build.classes.dir=${build.dir}/classes | build.classes.excludes=**/*.java,**/*.form | # This directory is removed when the project is cleaned: | build.dir=build | build.generated.dir=${build.dir}/generated | # Only compile against the classpath explicitly listed here: | build.sysclasspath=ignore | build.test.classes.dir=${build.dir}/test/classes | build.test.results.dir=${build.dir}/test/results | debug.classpath=\ | ${run.classpath} | debug.test.classpath=\ | ${run.test.classpath} | # This directory is removed when the project is cleaned: | dist.dir=dist | dist.jar=${dist.dir}/JbossWS-EJB3Demo-SBI.jar | dist.javadoc.dir=${dist.dir}/javadoc | file.reference.activation.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/activation.jar | file.reference.antlr-2.7.6.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/antlr-2.7.6.jar | file.reference.autonumber-plugin.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/autonumber-plugin.jar | file.reference.avalon-framework.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/avalon-framework.jar | file.reference.bcel.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/bcel.jar | file.reference.bindingservice-plugin.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/bindingservice-plugin.jar | file.reference.bsf.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/bsf.jar | file.reference.bsh-1.3.0.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/bsh-1.3.0.jar | file.reference.bsh-deployer.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/bsh-deployer.jar | file.reference.cglib.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/cglib.jar | file.reference.commons-collections.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/commons-collections.jar | file.reference.commons-httpclient.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/commons-httpclient.jar | file.reference.commons-logging.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/commons-logging.jar | file.reference.ejb3-persistence.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/ejb3-persistence.jar | file.reference.hibernate-annotations.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/hibernate-annotations.jar | file.reference.hibernate-entitymanager.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/hibernate-entitymanager.jar | file.reference.hibernate3.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/hibernate3.jar | file.reference.hsqldb-plugin.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/hsqldb-plugin.jar | file.reference.hsqldb.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/hsqldb.jar | file.reference.jacorb.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jacorb.jar | file.reference.javassist.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/javassist.jar | file.reference.javax.servlet.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/javax.servlet.jar | file.reference.javax.servlet.jsp.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/javax.servlet.jsp.jar | file.reference.jboss-annotations-ejb3.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/deploy/ejb3.deployer/jboss-annotations-ejb3.jar | file.reference.jboss-backport-concurrent.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jboss-backport-concurrent.jar | file.reference.jboss-cache.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jboss-cache.jar | file.reference.jboss-common-jdbc-wrapper.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jboss-common-jdbc-wrapper.jar | file.reference.jboss-ejb3.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/deploy/ejb3.deployer/jboss-ejb3.jar | file.reference.jboss-ejb3x.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/deploy/ejb3.deployer/jboss-ejb3x.jar | file.reference.jboss-hibernate.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jboss-hibernate.jar | file.reference.jboss-iiop.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jboss-iiop.jar | file.reference.jboss-j2ee.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jboss-j2ee.jar | file.reference.jboss-jaxrpc.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jboss-jaxrpc.jar | file.reference.jboss-jca.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jboss-jca.jar | file.reference.jboss-jsr77.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jboss-jsr77.jar | file.reference.jboss-jsr88.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jboss-jsr88.jar | file.reference.jboss-management.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jboss-management.jar | file.reference.jboss-monitoring.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jboss-monitoring.jar | file.reference.jboss-remoting-int.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jboss-remoting-int.jar | file.reference.jboss-remoting.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jboss-remoting.jar | file.reference.jboss-saaj.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jboss-saaj.jar | file.reference.jboss-serialization.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jboss-serialization.jar | file.reference.jboss-srp.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jboss-srp.jar | file.reference.jboss-transaction.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jboss-transaction.jar | file.reference.jboss.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jboss.jar | file.reference.jbossha.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jbossha.jar | file.reference.jbossmq.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jbossmq.jar | file.reference.jbossretro-rt.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jbossretro-rt.jar | file.reference.jbosssx.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jbosssx.jar | file.reference.jbossws14.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/deploy/jbossws14.sar/jbossws14.jar | file.reference.jgroups.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jgroups.jar | file.reference.jmx-adaptor-plugin.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jmx-adaptor-plugin.jar | file.reference.jnpserver.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jnpserver.jar | file.reference.jpl-pattern.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jpl-pattern.jar | file.reference.jpl-util.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jpl-util.jar | file.reference.jstl.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/jstl.jar | file.reference.log4j.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/log4j.jar | file.reference.mail-plugin.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/mail-plugin.jar | file.reference.mail.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/mail.jar | file.reference.mysql-connector-java-3.1.6-bin.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/mysql-connector-java-3.1.6-bin.jar | file.reference.pg74.215.jdbc2ee.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/pg74.215.jdbc2ee.jar | file.reference.properties-plugin.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/properties-plugin.jar | file.reference.quartz-all-1.5.2.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/quartz-all-1.5.2.jar | file.reference.scheduler-plugin-example.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/scheduler-plugin-example.jar | file.reference.scheduler-plugin.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/scheduler-plugin.jar | file.reference.snmp-support.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/snmp-support.jar | file.reference.standard.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/standard.jar | file.reference.wsdl4j.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/deploy/jbossws14.sar/wsdl4j.jar | file.reference.wsdl4j.jar-1=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/wsdl4j.jar | file.reference.xmlentitymgr.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/lib/xmlentitymgr.jar | file.reference.xmlsec.jar=../../../../../var/jboss-4.0.4.GA-ejb3rc8fd/server/all/deploy/jbossws14.sar/xmlsec.jar | jar.compress=false | javac.classpath=\ | ${file.reference.jbossws14.jar}:\ | ${file.reference.wsdl4j.jar}:\ | ${file.reference.xmlsec.jar}:\ | ${file.reference.jboss-annotations-ejb3.jar}:\ | ${file.reference.jboss-ejb3.jar}:\ | ${file.reference.jboss-ejb3x.jar}:\ | ${file.reference.activation.jar}:\ | ${file.reference.antlr-2.7.6.jar}:\ | ${file.reference.autonumber-plugin.jar}:\ | ${file.reference.avalon-framework.jar}:\ | ${file.reference.bcel.jar}:\ | ${file.reference.bindingservice-plugin.jar}:\ | ${file.reference.bsf.jar}:\ | ${file.reference.bsh-1.3.0.jar}:\ | ${file.reference.bsh-deployer.jar}:\ | ${file.reference.cglib.jar}:\ | ${file.reference.commons-collections.jar}:\ | ${file.reference.commons-httpclient.jar}:\ | ${file.reference.commons-logging.jar}:\ | ${file.reference.ejb3-persistence.jar}:\ | ${file.reference.hibernate-annotations.jar}:\ | ${file.reference.hibernate-entitymanager.jar}:\ | ${file.reference.hibernate3.jar}:\ | ${file.reference.hsqldb-plugin.jar}:\ | ${file.reference.hsqldb.jar}:\ | ${file.reference.jacorb.jar}:\ | ${file.reference.javassist.jar}:\ | ${file.reference.javax.servlet.jar}:\ | ${file.reference.javax.servlet.jsp.jar}:\ | ${file.reference.jboss-backport-concurrent.jar}:\ | ${file.reference.jboss-cache.jar}:\ | ${file.reference.jboss-common-jdbc-wrapper.jar}:\ | ${file.reference.jboss-hibernate.jar}:\ | ${file.reference.jboss-iiop.jar}:\ | ${file.reference.jboss-j2ee.jar}:\ | ${file.reference.jboss-jaxrpc.jar}:\ | ${file.reference.jboss-jca.jar}:\ | ${file.reference.jboss-jsr77.jar}:\ | ${file.reference.jboss-jsr88.jar}:\ | ${file.reference.jboss-management.jar}:\ | ${file.reference.jboss-monitoring.jar}:\ | ${file.reference.jboss-remoting-int.jar}:\ | ${file.reference.jboss-remoting.jar}:\ | ${file.reference.jboss-saaj.jar}:\ | ${file.reference.jboss-serialization.jar}:\ | ${file.reference.jboss-srp.jar}:\ | ${file.reference.jboss-transaction.jar}:\ | ${file.reference.jboss.jar}:\ | ${file.reference.jbossha.jar}:\ | ${file.reference.jbossmq.jar}:\ | ${file.reference.jbossretro-rt.jar}:\ | ${file.reference.jbosssx.jar}:\ | ${file.reference.jgroups.jar}:\ | ${file.reference.jmx-adaptor-plugin.jar}:\ | ${file.reference.jnpserver.jar}:\ | ${file.reference.jpl-pattern.jar}:\ | ${file.reference.jpl-util.jar}:\ | ${file.reference.jstl.jar}:\ | ${file.reference.log4j.jar}:\ | ${file.reference.mail-plugin.jar}:\ | ${file.reference.mail.jar}:\ | ${file.reference.mysql-connector-java-3.1.6-bin.jar}:\ | ${file.reference.pg74.215.jdbc2ee.jar}:\ | ${file.reference.properties-plugin.jar}:\ | ${file.reference.quartz-all-1.5.2.jar}:\ | ${file.reference.scheduler-plugin-example.jar}:\ | ${file.reference.scheduler-plugin.jar}:\ | ${file.reference.snmp-support.jar}:\ | ${file.reference.standard.jar}:\ | ${file.reference.wsdl4j.jar-1}:\ | ${file.reference.xmlentitymgr.jar} | # Space-separated list of extra javac options | javac.compilerargs= | javac.deprecation=false | javac.source=1.5 | javac.target=1.5 | javac.test.classpath=\ | ${javac.classpath}:\ | ${build.classes.dir}:\ | ${libs.junit.classpath} | javadoc.additionalparam= | javadoc.author=false | javadoc.encoding= | javadoc.noindex=false | javadoc.nonavbar=false | javadoc.notree=false | javadoc.private=false | javadoc.splitindex=true | javadoc.use=true | javadoc.version=false | javadoc.windowtitle= | meta.inf.dir=${src.dir}/META-INF | platform.active=default_platform | run.classpath=\ | ${javac.classpath}:\ | ${build.classes.dir} | # Space-separated list of JVM arguments used when running the project | # (you may also define separate properties like run-sys-prop.name=value instead of -Dname=value | # or test-sys-prop.name=value to set system properties for unit tests): | run.jvmargs= | run.test.classpath=\ | ${javac.test.classpath}:\ | ${build.test.classes.dir} | src.dir=src | I can send here build.xml and build-impl.xml but they are big and does not contain specification of JAR files. Thanks, Leonell View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969669#3969669 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969669

19 years, 7 months

1
0
0 / 0

[EJB 3.0] - Re: EJB3 WebServices

by Doug.Palmer

Can you post your ant script too? It still looks like you are missing some jars. Did you include the jars from server/all/deploy/jbossws.sar and server/all/deploy/ejb3.deployer? Regards Doug View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969667#3969667 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969667

19 years, 7 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 September 2006