[Design of JBoss Build System] - jboss common maven build
by dimitris＠jboss.org
I need some help here. I have a checkout of jboss common:
build
common-core
common-logging-jdk
common-logging-log4j
common-logging-spi
Made some changes to common-logging-log4j, including the upgrade of log4j from 1.2.8 to 1.2.14.
Going back to the build directory, I'm getting:
X:\cvs\jboss-public\common\build>mvn install
[INFO] Scanning for projects...
Downloading: http://repo1.maven.org/maven2/jboss/jboss-common/2.0.4-beta/jboss-c
ommon-2.0.4-beta.pom
[WARNING] Unable to get resource from repository central (http://repo1.maven.org
/maven2)
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
GroupId: jboss
ArtifactId: jboss-common
Version: 2.0.4-beta
Reason: Unable to download the artifact from any repository
jboss:jboss-common:pom:2.0.4-beta
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Cannot find parent: jboss:jbos
s-common for project: null:jboss-common-core:jar:2.0.4-beta
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent
: jboss:jboss-common for project: null:jboss-common-core:jar:2.0.4-beta
at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(D
efaultMavenProjectBuilder.java:1161)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Def
aultMavenProjectBuilder.java:674)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFi
leInternal(DefaultMavenProjectBuilder.java:416)
at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMave
nProjectBuilder.java:192)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:491)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351)
... 11 more
Caused by: org.apache.maven.project.ProjectBuildingException: POM 'jboss:jboss-c
ommon' not found in repository: Unable to download the artifact from any reposit
ory
jboss:jboss-common:pom:2.0.4-beta
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepo
sitory(DefaultMavenProjectBuilder.java:513)
at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(D
efaultMavenProjectBuilder.java:1157)
... 18 more
Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable
to download the artifact from any repository
jboss:jboss-common:pom:2.0.4-beta
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
faultArtifactResolver.java:136)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
faultArtifactResolver.java:63)
at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepo
sitory(DefaultMavenProjectBuilder.java:467)
... 19 more
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to downl
oad the artifact from any repository
at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(Def
aultWagonManager.java:260)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
faultArtifactResolver.java:124)
... 21 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Thu Mar 29 14:07:51 EEST 2007
[INFO] Final Memory: 1M/2M
[INFO] ------------------------------------------------------------------------
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032704#4032704
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032704
17 years, 2 months
[Design of Security on JBoss] - Flush cache credentials
by adiceglie
I using LDAPExLoginModule on Active Directory to autenticate user and this function correctly. The autenticated user access to a my Web Service integrated in Pentaho throught a Web client application created with Axis in Eclipse. Then, I close and reopen the browser, in the login dialog I insert another user; this user is autenticated on client, but on Web Services the autenticated user is the first user. The first user is never flushed, only if I stop and restart the JBoss Application Server.
Then, I used flushOnSessionInvalidation="true" attribute in Pentaho's jboss-web.xml and call session.invalidate when Webservice finish, but none.
At end I insert before session.invalidate() the following code:
/*
* Flush the cache
*/
String domain = "ldapRealm";
String jaasMgrName = "jboss.security:service=JaasSecurityManager";
String[] params = { domain };
String[] signature = { "java.lang.String" };
MBeanServer server = (MBeanServer) MBeanServerFactory.findMBeanServer(null).get(0);
try {
ObjectName jaasMgr = new ObjectName("jboss.security", "service", "JaasSecurityManager");
server.invoke(jaasMgr, "flushAuthenticationCache", params, signature);
} catch (Exception e){
e.printStackTrace();
}
where ldapRealm is my application domain on LDAP AD.
But also none.
How can I do to solve flush the user credential on Web service?
Thanks in advance
Angela Diceglie
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032696#4032696
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032696
17 years, 2 months
[Design of Security on JBoss] - Flush cache credentials
by adiceglie
I using LDAPExLoginModule on Active Directory to autenticate user and this function correctly. The autenticated user access to a my Web Service integrated in Pentaho throught a Web client application created with Axis in Eclipse. Then, I close and reopen the browser, in the login dialog I insert another user; this user is autenticated on client, but on Web Services the autenticated user is the first user. The first user is never flushed, only if I stop and restart the JBoss Application Server.
Then, I used flushOnSessionInvalidation="true" attribute in Pentaho's jboss-web.xml and call session.invalidate when Webservice finish, but none.
At end I insert before session.invalidate() the following code:
/*
* Flush the cache
*/
String domain = "ldapRealm";
String jaasMgrName = "jboss.security:service=JaasSecurityManager";
String[] params = { domain };
String[] signature = { "java.lang.String" };
MBeanServer server = (MBeanServer) MBeanServerFactory.findMBeanServer(null).get(0);
try {
ObjectName jaasMgr = new ObjectName("jboss.security", "service", "JaasSecurityManager");
server.invoke(jaasMgr, "flushAuthenticationCache", params, signature);
} catch (Exception e){
e.printStackTrace();
}
where ldapRealm is my application domain on LDAP AD.
But also none.
How can I do to solve flush the user credential on Web service?
Thanks in advance
Angela Diceglie
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032695#4032695
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032695
17 years, 2 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: org.jboss.test.jbossmq.test cleanup in jboss5
by scott.stark＠jboss.org
A problem I'm seeing with some test (org.jboss.test.jbossmessaging.test.MessageTypesUnitTestCase) is a failure to deploy the test jms destinations:
| 2007-03-28 22:12:49,448 DEBUG [org.jboss.jms.server.destination.QueueService] Starting jboss.messaging.destination:service=Queue,name=testQueue
| 2007-03-28 22:12:49,462 ERROR [org.jboss.jms.util.ExceptionUtil] Queue[null, name=testQueue] startService
| java.lang.ArrayIndexOutOfBoundsException: 10
| at org.jboss.messaging.util.prioritylinkedlist.BasicPriorityLinkedList.addLast(BasicPriorityLinkedList.java:64)
| at org.jboss.messaging.core.PagingChannelSupport.addFromRefInfo(PagingChannelSupport.java:546)
| at org.jboss.messaging.core.PagingChannelSupport.doLoad(PagingChannelSupport.java:525)
| at org.jboss.messaging.core.PagingChannelSupport.load(PagingChannelSupport.java:211)
| at org.jboss.jms.server.destination.QueueService.startService(QueueService.java:86)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196)
| at sun.reflect.GeneratedMethodAccessor66.invoke(Unknown Source)
| 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.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
| 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:233)
| at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:238)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:724)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:445)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:555)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:489)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:335)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:205)
| 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:142)
| at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:103)
| at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
| at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:56)
| at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52)
| at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:170)
| at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:592)
| at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:603)
| at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:476)
| at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:406)
| 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.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:121)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:110)
| at org.jboss.profileservice.aop.MainDeployerAspect.process(MainDeployerAspect.java:53)
| at org.jboss.aop.advice.org.jboss.profileservice.aop.MainDeployerAspect_z_process_1126829932.invoke(MainDeployerAspect_z_process_1126829932.java)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at AOPContainerProxy$0.process(AOPContainerProxy$0.java)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:795)
| at org.jboss.deployment.MainDeployer.redeploy(MainDeployer.java:570)
| 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 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.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266)
| 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.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140)
| at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
| at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
| 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.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:815)
| at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:416)
| 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 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
| at sun.rmi.transport.Transport$1.run(Transport.java:153)
| at java.security.AccessController.doPrivileged(Native Method)
| at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
| at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
| at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
| at java.lang.Thread.run(Thread.java:595)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032623#4032623
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032623
17 years, 2 months
[Design of JBoss jBPM] - Nonexistant classes referenced by Javadoc?
by zipwow
I cleaned up four or five classes of javadoc errors (nonexistant param tags, variable names changed in code but not doc), but some of the @see and @link tags reference classes I can't find anything about. Do the following classes no longer exist, or are they simply not in the jbpm.3 project? If they're the former, I'll remove or redirect them to their replacements. If they're that latter I'll just ignore them.
>From GraphSession:
org.jbpm.jpdl.par.ProcessArchiveDeployer
>From JbpmSession:
org.jbpm.db.FileSession
org.jbpm.tc.ContextBuilder
org.jbpm.tc.db.JbpmSessionContext
The last two are also referenced from JbpmSessionFactory. The org.jbpm.tc package itself doesn't seem to exist, or I don't know where to look for it.
I checked in the CVS history in the jbpm.2 and jbpm.3 projects, but couldn't find mention of these files.
-Kevin
(enable javadoc processing in Eclipse to see these messages)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032595#4032595
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032595
17 years, 2 months