[Design of JBoss Collaboration Server] - Feature Request - I'll do the work!
by sappenin
Sorry if this has been addressed. If so, please point me in the right direction.
I would like to be able to lock down the JMS queues that JBCS uses (like localmail, remotemail, etc). I don't want a random application to be able to place messages into those queues without authenticating.
Currently, the JMSMailListener doesn't authenticate when it connects to the JMS queues to "put" messages on them (i.e., the "unauthenticated user" identity is used). In JMSMailListener.putMessage(...), there should be an option to authenticate as a given user (i.e., a "system" or "admin" user, for example).
I would be willing to add the code necessary to get the "putMessage" function to authenticate as some pre-specified user, but I'm wondering what is the best way to do get userid/password information for such a "system" user.
Does it make sense to have "system"/"admin" userid and password attributes in the jboss-service.xml Listener definitions (and tweak the Mbean code as well)? That way, a given listener would be able to query what the "system" userid/password is.
Unfortunately, If it were designed this way, then every listener would need to define an authentication userid/password, which isn't exactly pretty.
Is there a better way to accomplish this?
Thanks!
David
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3961646#3961646
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3961646
17 years, 9 months
[Design of JBoss jBPM] - Re: next steps for the console webapp
by kukeltje
"svetzal" wrote :
| For sure, it's all a matter of how interactive you want it to be.
Not much, certainly not initially
"svetzal" wrote :
| And if we're not adding much more value than a single-tag analog of a JSF dataTable, I'm not sure why we'd want to make the effort.
Correct, for the form elements that is true. Now you'd have to pass it some thing to make it read-only or not, pass the label, the formelement etc.... That could all be hidden, but the advantage is imo to little.
For the 'transition buttons' it would hide some things, but there to I'm looking for a different implementation instead of using javascript to set another field. I'm no supporter of hiding complexity, removing complexity is imo always better.
"svetzal" wrote :
| It would be very interesting to split these out into a separate package in hopes that it could be used with other JSF implementations.
Please explain a little more, I do not exactely get what you mean.
"svetzal" wrote :
| I have an interactive JSF component written by one of our guys here (with much cursing and swearing) that does LDAP browsing and object selection. Our next step is to refactor it so that it is simpler.
Would things like combining dojo/myfaces solve anything here?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3961598#3961598
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3961598
17 years, 9 months
[Design of JBoss jBPM] - Re: next steps for the console webapp
by svetzal
"tom.baeyens(a)jboss.com" wrote :
| sure a task list and a task form JSF component should be possible, no ?
|
For sure, it's all a matter of how interactive you want it to be. Event propogation and state coordination between sub-components we've found tricky due to the way the components are instantiated throughout the JSF request lifecycle.
And if we're not adding much more value than a single-tag analog of a JSF dataTable, I'm not sure why we'd want to make the effort.
"tom.baeyens(a)jboss.com" wrote :
| i don't see why an explicit ty to myfaces would be required. also i don't get what you mean with external resource binding.
|
In order for a component to be highly interactive, and visually interesting, we will require some client-side JavaScript, CSS styles, possibly iconography/images... In order to make this easy for JSF app developers to use we would want to package the components in a JAR along with their own resources.
Serving out these resources is not difficult, but seems "hackish" as you need to settle on your own URL convention, build a phase listener to implement that convention, and broker requests to these private resources. And you need to build it flexibly so you can grow this library in the future.
MyFaces has some interesting efforts underway to make this flexible and elegant, but the classes are buried in recent implementations. You can see if you check out HEAD and look through the Tomahawk implementations.
It would be very interesting to split these out into a separate package in hopes that it could be used with other JSF implementations.
I have an interactive JSF component written by one of our guys here (with much cursing and swearing) that does LDAP browsing and object selection. Our next step is to refactor it so that it is simpler.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3961570#3961570
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3961570
17 years, 9 months