[Design of JBoss Portal] - Re: WANTED: Input from administrators & developers
by mmontoni
Hi JBoss Team,
first thanks for putting so much effort in improving Jboss portal so fast!
I am evaluating this product along with others like Liferay and Google Portal. I do have some aditional suggestions, if pertinent. A lot was said so far so forgive me if I am being repetitve.
- Layout: It would be interesting to be able
1) to order the tabs in the portal. Right now, if the first letter of the page name is in caps, the order is automatically alphabetical.
2) to choose a layout in a drop down list. For example: 2 collumns (left 40%, right 60%), 2 collumns (left 50%, right 50%) and so on. This would enhance the personalization features of the portal.
3) to upload a company logo whithin the themes offered. By this I mean that I could maintain the theme and layout offered but change the JBoss Portal Logo to my company logo without having to create a new theme and hard core the new reference to the logo. This would even give me flexibilty to create my own theme and re use it within my company.
- Security:
1) I haven't explore that feature yet in Jboss but I didn't notice in the administration page a feature where I can set a group of users to see, edit or configure a portlet. I am suggesting that perhaps the granulatiry of the security could be in pages or portlets too.
2) It would be interesting to add in the documentation, if it doesn't exist, a topic on how to conifigure the portal to SSO.
Thanks for asking us for suggestions!
--Mariella.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978836#3978836
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978836
19 years, 5 months
[Design of JBoss Eclipse IDE (dev)] - PostgreSQL 8.1 JBoss-IDE HQL-Editor does not work
by JDepping
Hi,
i use postgresql version 8.1.3 with jdbc-Driver postgresql-8.1-407jdbc3.jar,
JBoss IDE 2.0.0 for the Hibernate Tools with the jdk1.4. This jdk i have to use!
In my hibernate.cfg.xml i set the
driverclass, password, connectionurl=jdbc:postgresql://localhost/jboss
and the dialect to PostgreSQLDialect.
The Error ist always:
ERROR main org.hibernate.util.JDBCExceptionReporter - ERROR: current transaction is aborted, commands ignored util end of transaction block.
And the console shows the Warning:
WARN main org.hibernate.util.JDBCEceptionReporter - SQL Error:0 SQLState 25P0
The following features are correct:
In the Hibernate Configuration View i see my databasetable.
I can open the Database node with my tables.
I can use the reverse engineering.
But i can't use the hql-Editor or the Hibernate Entity Model.
What is my fault?
- Do i have to add something in my hibernate.cfg.xml?
- Do i have to use another jdbc Driver?
Please help
Jürgen
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978833#3978833
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978833
19 years, 5 months
[Design of JBoss jBPM] - Re: MessageService and JMS
by mteira
Hello.
During my tests, I needed to change some config files, like hibernate.cfg.xml or jbpm.cfg.xml. For example, when I want to use an Oracle database as backend, I need to change the hibernate.cfg.xml file (that eventually gets bundled into the ear file). When I want to use the JMS based message service, I also need to setup the jbpm.cfg.xml file. I think that perhaps a good way to achieve this could be to use properties that can be overriden in the local build.properties file.
But for example, when I want to use the DB based message service, I have to write, in the service tag:
<service name="message"
| factory="org.jbpm.msg.db.DbMessageServiceFactory"/>
and to use the JMS based one:
<service name="message">
| <factory>
| <bean class="org.jbpm.msg.jms.JmsMessageServiceImpl">
| <field name="connectionFactoryJndiName">
| <string value="java:XAConnectionFactory"/>
| </field>
| <field name="destinationJndiName">
| <string value="queue/JbpmJobQueue"/>
| </field>
| </bean>
| </factory>
| </service>
This seems a difficult case to be solved using build properties if we want the ant targets to be not aware of how the services are, or what parameters they need. What I want to mean is that we would need to make the ant target know that a JMS Message service needs those field names, that could be coded using properties. Perhaps we should need a target for every different kind of service.
A better approach could be to have different XML excerpts, one for any kind of service and just assemble all together to generate the jbpm.cfg.xml file in build time, controlled using build properties that could be overriden.
Well, perhaps all this is already solved. I'm not even sure if you understand what I'm trying to say (my english couldn't be worse), but I think that there should be a way to particularize these kind of things without need to change any file under version control.
BTW. Any comment about my previous post and that hypotetic new MDB. Is it actually needed?
Best Regards.
--
Manuel Teira
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978820#3978820
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978820
19 years, 5 months
[Design of JBossCache] - Re: API Issues integrating 2.0.0.DR1 in HEAD
by manik.surtani@jboss.com
anonymous wrote :
| 1) We already have configuration via DOM Elements and Properties of complex types like CacheLoaderManager. We need to add the ability to configure via MC construction of POJOs that represent all the configuration elements. The MC doesn't need to use Element/Properties to build up these POJOs.
|
| 2) Configuration becomes a composite object, with a contained CacheLoaderConfig, (new) BuddyReplicationConfig and (revised) EvictionConfig.
|
+1.
anonymous wrote :
| 3) When the old Element/Properties style of configuration is used, all parsing of DOM elements/reading of Properties to populate the config objects should be done within the config objects themselves. E.g. pass an Element to the constructor of CacheLoaderConfig and let it parse it. CacheLoaderManager constructor gets passed the CacheLoaderConfig, not an Element. BuddyManager gets passed a BuddyReplicationConfig, not an Element.
| 4) The various config objects like CacheLoaderConfig are now exposed to user code via a getter in Configuration. This means their setter methods are also exposed, so if those methods are invoked after the cache is started we need to check if that's allowed. This is already done in Configuration; need to apply the same technique in the other config objects.
|
+1 again. Yes, this does give us a lot of flexibility in how we configure complex structures like cache loaders, eviction policies, etc.
anonymous wrote :
| I've got a good start on this.
|
Cool!
This feedback really does help; I'm looking at cutting an Alpha once these changes are in. Since you already have a start on the config side of things, could I leave this to you?
I'm hoping to tag the alpha later this week, perhaps on Thu. Does this work for you?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978804#3978804
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978804
19 years, 5 months