[JBoss JIRA] Created: (JBJMX-101) failed to redeploy MBean dependent web module
by Maxim Gordienko (JIRA)
failed to redeploy MBean dependent web module
---------------------------------------------
Key: JBJMX-101
URL: http://jira.jboss.com/jira/browse/JBJMX-101
Project: JBoss JMX
Issue Type: Bug
Affects Versions: JBossAS-4.0.0
Environment: JBossAS 4.0.4.GA
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_09-b01)
Reporter: Maxim Gordienko
Environment: Sar module containing MBean
content of META-INF/jboss-service.xml
--- CUT ---
<?xml version="1.0" encoding="UTF-8"?>
<server>
<mbean code="dot.com.DummyKPBossService" name="dot.com:service=DummyService">
</mbean>
</server>
--- END CUT ---
War module dependant on MBean from Sar
content of WEB-INF/jboss-web.xml
--- CUT ---
<?xml version="1.0" encoding="UTF-8"?>
<jboss-web>
<depends>dot.com:service=DummyService"</depends>
</jboss-web>
--- END CUT ---
upon redeployment Sar module JBoss tries to redeploy War module but fail with NPE:
java.lang.NullPointerException
at org.jboss.web.WebModule.startModule(WebModule.java:82)
at org.jboss.web.WebModule.startService(WebModule.java:61)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
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: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)
.......
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 4 months
[JBoss JIRA] Created: (JBMESSAGING-627) Create an ant configuration file fragment that would build a Messaging configuration for the AS testing, adding things like securiy roles, etc.
by Ovidiu Feodorov (JIRA)
Create an ant configuration file fragment that would build a Messaging configuration for the AS testing, adding things like securiy roles, etc.
-----------------------------------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-627
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-627
Project: JBoss Messaging
Issue Type: Sub-task
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Fix For: 1.2.0.Beta1
Richard Achmatowicz:
In order not to interfere with your use of the existing Messaging configuration with your tests (functional, stress, etc), it seems as though we need to add a target to release-admin.xml which builds a Messaging configuration for the AS testing. Does this sound reasonable?
Ovidiu Feodorov [26/Oct/06 10:06 PM]:
I would rather keep it separated. I see it more of a function of the testsuite build script. The release admin does need not care of security roles in JBoss AS integration test suite. I can create the ant configuration script fragment for you to use, if you wish, it shouldn't be any big deal. The changes should be applied post-deployment.
Richard Achmatowicz [27/Oct/06 11:22 AM] Yes, please, I would appreciate it if you could create the fragment. Because that fragment will contain rexexp terms, which are messy and should not be present in-line in testsuite/build.xml, i'll create a separate ant script containing your snippet and place it in resources/jbossmessaging.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 4 months
[JBoss JIRA] Created: (JBPORTAL-1043) introduce UserProfile and user metadata (storage mechanism agnostic)
by Boleslaw Dawidowicz (JIRA)
introduce UserProfile and user metadata (storage mechanism agnostic)
--------------------------------------------------------------------
Key: JBPORTAL-1043
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1043
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Portal Identity
Affects Versions: 2.6.Alpha1
Reporter: Boleslaw Dawidowicz
Assigned To: Boleslaw Dawidowicz
Fix For: 2.6.Alpha1
- Each user entry (ldap or database table) can bring different set of user personal information. This makes the user profile
- In portal we have property names like: user.name, user.surname, user.email, user.phone and etc.
- Each UserModule implementation provide a mapping of properties to coresponding values in underlaying database or directory
(table columns or ldat entry attributes for eg.)
- Profile informations are accessed using API like:
user.getMetaData().getProfileMetaData().getProperty(User.NAME_PROPERTY);
.getAllProperties().iterator()
- Currently this is handled by PropertyMap - keept as separate table in DB
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 5 months