[JBoss-user] [Beginners Corner] - Re: Compile Warnings
We are building server components, beans, web services, etc. I thought the client libs were for client applications accessing jboss as opposed to running within (but I might very well be confused... still learning). It works if I use : | | | | | | | | | Guess the jbossall-client does not contain the ejb3.0 stuff yet. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3894464#3894464 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3894464 --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Persistence,JBoss/CMP, Hibernate, Database] - Re: which jar the persistence classes belong to?
You will probably find them in ejb3-persistence.jar. This comes with the EJB 3.0 installation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3893819#3893819 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3893819 --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Beginners Corner] - Re: Compile Warnings
I'm sorry I assumed that others were having this problem as well, and the build code was not needed. I assumed this because the manifest in the lib/commons-logging.jar specifically reference "log4j.jar log4j-core.jar" on the classpath (which do not exist). Yes, we are using Ant. Code below. Thanks for looking. | | | | | | | | | | | | | | | | | | | | | | | | | | | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3893593#3893593 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3893593 --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Beginners Corner] - Compile Warnings
When I compile using the latest JBoss I link against ${jboss.home}/lib and
${jboss.home}/server/all/lib and I get the warnings below. These jar files
certainly do not exist in the directories, and I think they are being generated
from the classpath's defined in some of the manifest files. I'm I just using
jboss wrong or are these warnings expected?
[javac] warning: [path] bad path element
"C:\foo\tools\jboss-4.0.3RC2\lib\log4j.jar": no such file or directory
[javac] warning: [path] bad path element
"C:\foo\tools\jboss-4.0.3RC2\lib\log4j-core.jar": no such file or directory
[javac] warning: [path] bad path element
"C:\foo\tools\jboss-4.0.3RC2\server\all\lib\log4j-core.jar": no such file or
directory
[javac] warning: [path] bad path element
"C:\foo\tools\jboss-4.0.3RC2\server\all\lib\logkit-1.2.jar": no such file or
directory
[javac] warning: [path] bad path element
"C:\foo\tools\jboss-4.0.3RC2\server\all\lib\avalon-framework-4.1.5.jar": no
such file or directory
[javac] warning: [path] bad path element
"C:\foo\tools\jboss-4.0.3RC2\server\all\lib\concurrent-1.3.2.jar": no such file
or directory
[javac] warning: [path] bad path element
"C:\foo\tools\jboss-4.0.3RC2\server\all\lib\antlr-2.7.2.jar": no such file or
directory
[javac] warning: [path] bad path element
"C:\foo\tools\jboss-4.0.3RC2\server\all\deploy\ejb3.deployer\log4j.jar": no
such file or directory
[javac] warning: [path] bad path element
"C:\foo\tools\jboss-4.0.3RC2\server\all\deploy\ejb3.deployer\log4j-core.jar":
no such file or directory
[javac] warning: [path] bad path element
"C:\foo\lib\jaxws-2.0_20050825\lib\jsr173_1.0_api.jar": no such file or
directory
[javac] 10 warnings
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3893291#3893291
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3893291
---
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - HA JNDI Configuration
Currently I have HA JNDI working in a cluster by hardcoding the properties,
i.e.:
| publicstatic InitialContext getHAInitialContext() throws NamingException {
| if (props == null) {
| props = new Properties();
| props.put(InitialContext.PROVIDER_URL, "jnp://localhost:1100");
| }
| return new InitialContext(props);
| }
|
I would like to not have to hardcode this information, but keep it in the
jndi.properties file. If I create a jndi.properties with the content:
| java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
| java.naming.provider.url=localhost:1100
|
And place this property within each of our sar and war files we deploy, several
Jboss services do not start:
[java] --- MBeans waiting for other MBeans ---
| [java] ObjectName: jboss:service=HASessionState
| [java] State: FAILED
| [java] Reason: javax.naming.NameAlreadyBoundException
| [java] I Depend On:
| [java] jboss:service=DefaultPartition
|
| [java] ObjectName:
jboss.jmx:type=adaptor,name=Invoker,protocol=jrmp,service=proxyFactory
| [java] State: FAILED
| [java] Reason: javax.naming.NameAlreadyBoundException
| [java] I Depend On:
| [java] jboss:service=invoker,type=jrmp
| [java] jboss.jmx:type=adaptor,name=Invoker
| [java] Depends On Me:
| [java] jboss.admin:service=PluginManager
|
| [java] --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
| [java] ObjectName: jboss:service=HASessionState
| [java] State: FAILED
| [java] Reason: javax.naming.NameAlreadyBoundException
| [java] I Depend On:
| [java] jboss:service=DefaultPartition
|
| [java] ObjectName:
jboss.jmx:type=adaptor,name=Invoker,protocol=jrmp,service=proxyFactory
| [java] State: FAILED
| [java] Reason: javax.naming.NameAlreadyBoundException
| [java] I Depend On:
| [java] jboss:service=invoker,type=jrmp
| [java] jboss.jmx:type=adaptor,name=Invoker
| [java] Depends On Me:
| [java] jboss.admin:service=PluginManager
I'm sure I'm either doing something wrong, but can someone explain how I can
use the jndi.properties files properly in an HA-JNDI situation?
Thanks in advance.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3885757#3885757
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3885757
---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
