I am pleased to announce the jboss identity management 1.0.0.Beta1 is released today.
** Highlights
1. Minimal configuration feature. Developers only need to define the USER in the configuration file, all other types will be lazily created by the hibernate store.
2. Created the ANT based installer. developers can import/drop the schema from the ANT script, also deploy it into JBoss AS or undeploy from it.
3. Used the JBoss AS5 deployer mechanism. It listens on the -jboss-idm.xml suffix file to start the IdentitySessionFactory. The auth-simple example uses this feature.
bug fixes and tasks from the jira, please noted that we also fixed other issues that were not reported in the jira.
** Bug
* [JBID-129] - java.util.ConcurrentModificationException in HibernateIdentityStoreImpl class
** Feature Request
* [JBID-68] - identity component in JBoss5.
* [JBID-71] - Automatic installation of IDM Component for Hudson Runs
* [JBID-73] - Add a DisassociateGroups(User user) API in the relationshipManager
* [JBID-99] - Unique attributes
* [JBID-106] - Javadoc cleanup and update
* [JBID-123] - Use QA databases for sql scripts creation
* [JBID-79] - Write a JBossAS5 deployer for idm config file.
The doc/wiki pages are located at http://www.jboss.org/community/wiki/JBossIdentityIDM.
Any feedback you either can discuss it on our forum: http://www.jboss.org/index.html?module=bb&op=viewforum&f=305
Or report issues on our jira http://jira.jboss.org/jira/browse/JBID if any.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239822#4239822
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239822
I've downloaded the package
jboss-profiler-1.0.CR4
Read the readme file, and the web instruccions but I'm stuck on the LD_LIBRARY_PATH, points to:
echo $LD_LIBRARY_PATH
/home/user/Apps/jboss-profiler-1.0.CR4/jvmpi/linux:/home/user/Apps/jboss-profiler-1.0.CR4/jvmti/native/suse-linux64
But the test:
java -XrunjbossInspector:/tmp Foo
Returns:
Error occurred during initialization of VM
Could not find agent library on the library path or in the local directory: jbossInspector
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239805#4239805
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239805
I'm writing the number of records at where the commit is located.
Example 1:
File1: 5 records
File2: 3 records
File3: 1 records
File4: 4 records and 1 commit
The commit will be:
COMMIT, 4
I won' t need to inform the other files on the summary any more, since I'm guaranteeing they are synced before writing the COMMIT. The only place I could have a hole now is at the current file.
Example 2:
The user took some time to commit, and there are no records at the top:
File1: 5 records
File2: 3 records
File3: 1 records
File4: 4 records
- User takes 2 hours to commit it:
File 10: Commit Record alone
The commit record on that case will be:
COMMIT, 0
what is a valid approach,
And compacting would work fine with this approach also.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239760#4239760
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239760
I'm writing the number of records at where the commit is located.
Example 1:
File1: 5 records
File2: 3 records
File3: 1 records
File4: 1 records and 1 commit
The commit will be:
COMMIT, 4
I won' t need to inform the other files on the summary any more, since I'm guaranteeing they are synced before writing the COMMIT. The only place I could have a hole now is at the current file.
Example 2:
The user took some time to commit, and there are no records at the top:
File1: 5 records
File2: 3 records
File3: 1 records
File4: 1 records
- User takes 2 hours to commit it:
File 10: Commit Record alone
The commit record on that case will be:
COMMIT, 0
what is a valid approach,
And compacting would work fine with this approach also.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239760#4239760
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239760
anonymous wrote : a) don't allow any overrides on the connection factory. The user would have to provide a new ra.xml file for each configuration. This is how 1.4 works and would mean removing cleberts changes, however would still be a problem with lots of MDB;s sharing a CF.
Multiple ras for multiple connections are not acceptable IMO. With 1.4, you had a way to specify another CF JNDI.
You probably just need to have the CF at the ra level created lazily (I thought it already was).
You could have two Beans, or two jms-ds.xml deployed, one overridden, one at the ra level.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239757#4239757
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239757