Menu
▾
▴
jboss-dev-forums
|
From: <wes...@jb...> - 2006-06-28 06:52:29
|
And for some reason...as if literally on cue...we get 2 questions about this in the user forum, and the JIRA task itself... One thing we could do is add a new element to the *-ds.xml file specifically naming RA level properties. Something like: <ra-config-property> Or, add a 'scope' attribute to the existing element. I am inclined to the former just because it is more clear. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953895#3953895 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3953895 |
|
From: <wes...@jb...> - 2006-06-28 06:55:53
|
One more time...;-) This is where the MBean repository, or exposure of the ResourceAdapter itself would help. Right now, the only way 'in' to the adapter is via the ManagedConnectionFactory MBean which is starting to sort of look like Swiss cheese. This is in large part due to the fact that there is no other place to 'put' stuff as it relates to a RAR deployment as a whole. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953896#3953896 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3953896 |
|
From: <wes...@jb...> - 2006-06-28 07:07:04
|
Sigh...sorry, I can't resist. This also came up in another discussion I had today via email (Sorry Adrian, I didn't start the thread so yell at the EJB3 guys for this :-) ) In JBoss 4.0.x we had standardjboss.xml allowing for container configurations that would be universally applied across EJB deployments unless overridden by jboss.xml. With the advent of EJB3, this mechanism has essentially dissapeared and again, as if on cue, we had a client asking how can they configure an inflow deployment without having to replicate properties in the ActivationConfig for every MDB. This is really where RA level properties would come into play in for an ActivationSpec. In fact, the spec basically calls for this capability so we may have to end up doing something for this anyway. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953898#3953898 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3953898 |
|
From: <ad...@jb...> - 2006-06-29 11:36:10
|
"wes...@jb..." wrote : | We definitely don't do the first one, hence the JIRA task, but we also don't allow for the second condition at all. Typical case would be an RA with the following properties: | | RA | ServerName = "localhost" | Port = "8080" | | | MCF | ServerName = "" | Port = "" | | (Yes, yes, stupid example I know) | What are you talking about? We apply the rar properties from the ra.xml to the ResourceAdapter We also apply the rar properties onto the MCF, there are tests for this. Your example is stupid. In this case, if they specify ServerName="" on the MCF then that is the ServerName. If they want the rar value then they shouldn't specify it on the MCF. The jira issue is about modifying the ResourceAdapter properties without having to modify the ra.xml, e.g. using an alt-dd or jboss-ra.xml, etc. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954329#3954329 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954329 |
|
From: <ad...@jb...> - 2006-06-29 11:37:48
|
"wes...@jb..." wrote : And for some reason...as if literally on cue...we get 2 questions about this in the user forum, and the JIRA task itself... | | One thing we could do is add a new element to the *-ds.xml file specifically naming RA level properties. Something like: | | <ra-config-property> | | Or, add a 'scope' attribute to the existing element. I am inclined to the former just because it is more clear. | | You can't specify rar properties in the -ds.xml (managed connection factory) It is too late. The rar is already initialized and start() invoked. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954330#3954330 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954330 |
|
From: <wes...@jb...> - 2006-06-29 11:41:53
|
Where in RAR deployment do we apply the properties for a ResourceAdapter? We definitely do it for the ManagedConnectionFactory, but not for the adapter. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954332#3954332 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954332 |
|
From: <wes...@jb...> - 2006-06-29 11:42:46
|
Sigh...ok...now I am a complete idiot... I see it....Damnit... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954333#3954333 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954333 |
|
From: <wes...@jb...> - 2006-06-29 11:44:27
|
Ok, so I propose the following: *-ds.xml is modified Adding <ra-config-property> </ra-config-property> <config-property scope="ra"/> This will give us enough to set the property on the adatper. Agreed? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954334#3954334 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954334 |
|
From: <wes...@jb...> - 2006-06-29 11:50:57
|
Sigh...ok...this morning sucks... Now that I have proven beyond a shadow of a doubt how utterly f*(@*$ stupid I really am...is there anything wrong with overriding the ResourceAdapter with *-ds.xml properties when we start the deployment? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954335#3954335 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954335 |
|
From: <ad...@jb...> - 2006-06-29 11:55:05
|
No. See my earlier comments. The order is: ResourceAdapter deployer 1) Create rar 2) Apply properties (ra.xml) 3) Apply overrides (THIS IS MISSING AND IS JBAS-3343) 4) rar.start() ManagedConnectionFactory deployer 11) Create MCF (waits for rar to full start) 12) Apply properties from rar (ra.xml) 13) Apply properties from mcf (ra.xml) 14) Apply overrides (-ds.xml) The simplest solution is to allow a jboss-ra.xml inside the rar. Another would be to have an alternate dds with the rar not getting directly deployed, e.g. | <rar> | <rar-file>/some/path/to/rar</rar-file> | <ra-config-property> | etc. | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954336#3954336 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954336 |
|
From: <wes...@jb...> - 2006-06-29 12:01:40
|
Right, right...I got it...after I hear something about 50 times I usually understand... I was already working on a jboss-ra.xml, this would seem to be the best case to introduce it. Could you talk about the second case a bit more. This would seem to be the most interesting. Adding jboss-ra.xml is fine but I just want to understand what you thoughts on the alternative approach would be. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954337#3954337 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954337 |
|
From: <ad...@jb...> - 2006-06-29 14:03:49
|
The second approach is a way to do what JSR88 does. i.e. You have the original jar + an appserver specific desriptor This avoids having to modify somebody else's archive e.g. opening the jar add META-INF/jboss-ra.xml and then rejaring You have an alternate descriptor + deployer, e.g. jboss-rar.xml that points at the rar (not in the deploy directory) and add overriding configuration in the same descriptor. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954381#3954381 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954381 |
|
From: <sco...@jb...> - 2006-06-29 14:19:31
|
This second way is what you should look at because its the way deployers/components need to operate in jboss5 with the profile service. Given a rar to deploy/add to a profile, there has to be a management view that externalizes the settings that can be set by management tools. This info needs to be stored in the associated server profile outside of the rar. I'm working on merging the current profile service work with the virtual deployment framework in the system2 module to tie this together. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954386#3954386 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954386 |
|
From: <wes...@jb...> - 2006-06-29 14:19:50
|
Ok. But using this approach would require that the RAR not be in the deploy directory (as you said) and they use the alternateDD/jar to point to the RAR and then override. At least from what I am hearing. I guess I am not clear on what the Deployer actually gets in the DeploymentInfo. Just the alternateDD, or is it actually packed in a RAR that just provides the 'wrapping'? I will take a look at JSR88. No reason why we couldn't support both approaches. Do the jboss-ra.xml stuff first and then add the alternate DD support. Man, I am wicked sorry about the idiocy on this one. I have no clue what I was thinking. You can shoot me when you come to Westford...you sort of already did in making me get up and talk in front of people..;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954387#3954387 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954387 |
|
From: <ad...@jb...> - 2006-06-29 14:33:12
|
The deployer creates the DeploymentInfo (and classloader) like the old rar deployer, Except now the rar metadata is from ra.xml and the xxx-rar.xml overrides. There is just an additional source of metadata from the xxx-ra.xml it would also be that one that is watched for hotdeployment purposes. I'm not saying you should do it this way. It is one possible way to achieve the externalization of the overrides. Another would be an even more generic deployer that has something like: | <deploy> | <file>xxx.Xar</file> | <alt-dd-file>/some/location</alt-dd-file> | or | <alt-dd> | <!--inline stuff--> | </alt-dd> | </deploy> | But that has problems with the current way we use extensions to derive the deployment ordering. Again not an insurmountable problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954389#3954389 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954389 |
|
From: <sco...@jb...> - 2006-06-29 14:38:18
|
The existence of the rar in/not in the deploy directory is a separate issue that relates to how the hot deployment service has to behave in the presence of a profile service that dictates what deployments are part of a server configuration. Certainly a rar can have jboss specific deployment descriptors. A deployer will ultimately have to support an external metadata configuration based on the management view it exposes to effectively integrate with the profile service though, because the profile service is not going to be writing out deployer specific descriptors. It will have an object representation it stores however, and this will be passed in as additional metadata at deployment time. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954392#3954392 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954392 |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X