A bit too excessive? :-) Running AS_trunk/all config. ---- 14:03:43,671 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:03:43,812 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:03:45,031 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:03:45,718 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:03:45,765 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:03:45,796 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:03:45,828 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:03:46,015 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:03:46,031 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:03:49,265 WARN [HackClassloaderMetaDataDeployer] FIXME Using loader repository config: jboss.console:sar=console-mgr.sar for ding metadata not loader repository config 14:03:59,796 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:03:59,921 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:00,312 INFO [UnifiedInvokerHA] Service name is jboss:service=invoker,type=unifiedha 14:04:00,406 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:01,140 INFO [CorbaNamingService] CORBA Naming Started 14:04:01,140 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:02,562 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:02,656 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:02,703 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:02,718 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:03,031 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:03,031 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:03,046 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:03,468 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:03,750 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:03,750 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:05,015 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxcon 14:04:05,078 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:05,078 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:05,109 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:05,234 INFO [MailService] Mail Service bound to java:/Mail 14:04:05,843 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:06,171 INFO [SnmpAgentService] SNMP agent going active 14:04:06,281 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:07,906 INFO [DefaultPartition] Initializing partition DefaultPartition 14:04:07,937 INFO [STDOUT] ------------------------------------------------------- GMS: address is 127.0.0.1:3903 ------------------------------------------------------- 14:04:08,046 INFO [STDOUT] ------------------------------------------------------- GMS: address is 127.0.0.1:3903 ------------------------------------------------------- 14:04:10,015 INFO [DefaultPartition] Number of cluster members: 1 14:04:10,015 INFO [DefaultPartition] Other members: 0 14:04:10,078 INFO [RPCManagerImpl] Received new cluster view: [127.0.0.1:3903|0] [127.0.0.1:3903] 14:04:10,078 INFO [RPCManagerImpl] Cache local address is 127.0.0.1:3903 14:04:10,125 INFO [ComponentRegistry] JBoss Cache version: JBossCache 'Poblano' 2.2.0.GA 14:04:10,156 INFO [DefaultPartition] Fetching serviceState (will wait for 30000 milliseconds): 14:04:10,156 INFO [DefaultPartition] State could not be retrieved (we are the first member in group) 14:04:11,250 INFO [HANamingService] Started HAJNDI bootstrap; jnpPort=1100, backlog=50, bindAddress=/127.0.0.1 14:04:11,265 INFO [DetachedHANamingService$AutomaticDiscovery] Listening on /127.0.0.1:1102, group=230.0.0.4, HA-JNDI address=12 14:04:11,296 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core 14:04:11,312 INFO [NativeServerConfig] 3.0.4.CR1 14:04:12,109 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker c ease see the JBoss Messaging user guide for instructions on how to do this. 14:04:12,328 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc. 14:04:12,328 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer 14:04:12,671 INFO [TransactionManagerService] Initializing recovery manager 14:04:12,812 INFO [TransactionManagerService] Recovery manager configured 14:04:12,812 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference 14:04:12,843 INFO [TransactionManagerService] Starting transaction recovery manager 14:04:13,453 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environ C Connectivity Solution\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\cvsnt;C:\Program Files\Subversi :\java_lib\apache-ant-1.7.0\bin;C:\java_lib\maven-2.0.9\bin;C:\Program Files\TextPad 4\TextPad.exe 14:04:13,906 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080 14:04:13,921 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009 14:04:13,921 INFO [Catalina] Initialization processed in 741 ms 14:04:13,921 INFO [StandardService] Starting service jboss.web 14:04:13,921 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.1.CR7 14:04:13,984 INFO [Catalina] Server startup in 59 ms 14:04:14,046 INFO [TomcatDeployment] deploy, ctxPath=/web-console, vfsUrl=management/console-mgr.sar/web-console.war 14:04:14,953 INFO [TomcatDeployment] deploy, ctxPath=/juddi, vfsUrl=juddi-service.sar/juddi.war 14:04:15,000 INFO [RegistryServlet] Loading jUDDI configuration. 14:04:15,015 INFO [RegistryServlet] Resources loaded from: /WEB-INF/juddi.properties 14:04:15,015 INFO [RegistryServlet] Initializing jUDDI components. 14:04:15,156 INFO [TomcatDeployment] deploy, ctxPath=/jbossws, vfsUrl=jbossws.sar/jbossws-management.war 14:04:15,203 INFO [TomcatDeployment] deploy, ctxPath=/invoker, vfsUrl=httpha-invoker.sar/invoker.war 14:04:15,421 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:15,421 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:15,500 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.G 14:04:15,500 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:15,515 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:15,515 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.G 14:04:15,515 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:15,546 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:15,546 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.G 14:04:15,546 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:15,562 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported 14:04:15,562 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.G 14:04:15,578 WARN [Ejb3Deployment] EJBTHREE-1508: Quering Ejb3Deployment for persistence unit deployments is no longer supported _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

I uploaded that dependency yesterday because the app server build uses it and it was not in our repository. It is a copy from the maven central repository: http://repo1.maven.org/maven2/javax/xml/ws/jaxws-api/2.1/ If it is incorrect, then you can replace it and the associated checksums with the one from Sun's repository. I'm not sure why they are different, maybe there is a re-distribution restriction in the license of some of the dependencies that prevents them from going into the central maven repository. Alessio Soldano wrote: > Hi, > I've just found that the jaxws-api maven artifact has been > uploaded/re-uploaded to the repository yesterday. I think its pom.xml > is missing some dependencies, as it says: > > <project> > <modelVersion>4.0.0</modelVersion> > <groupId>javax.xml.ws</groupId> > <artifactId>jaxws-api</artifactId> > <version>2.1</version> > <dependencies> > <dependency> > <groupId>javax.xml.bind</groupId> > <artifactId>jaxb-api</artifactId> > <version>2.1</version> > </dependency> > </dependencies> > </project> > > while the one coming from the Sun's repository says: > > <project> > <modelVersion>4.0.0</modelVersion> > <groupId>javax.xml.ws</groupId> > <artifactId>jaxws-api</artifactId> > <version>2.1</version> > <dependencies> > <dependency> > <groupId>javax.xml.bind</groupId> > <artifactId>jaxb-api</artifactId> > <version>2.1</version> > </dependency> > <dependency> > <groupId>javax.xml.soap</groupId> > <artifactId>saaj-api</artifactId> > <version>1.3</version> > </dependency> > <dependency> > <groupId>javax.annotation</groupId> > <artifactId>jsr250-api</artifactId> > <version>1.0</version> > </dependency> > <dependency> > <groupId>javax.jws</groupId> > <artifactId>jsr181-api</artifactId> > <version>1.0-MR1</version> > </dependency> > </dependencies> > </project> > > Is there someone responsible for this kind of stuff? the artifact I'm > referring to and I think is right (as it has the jsr181, ect. > dependencies) lives here: > https://maven-repository.dev.java.net/nonav/repository/javax.xml.ws/ > > Alessio > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development