[JBoss Seam] - DataModel and DataModelSelection
by wschwendt
One thing that I don't understand is why a @DataModelSelection annotation can ONLY be used in a component when there is also a @DataModel annotation placed on a field or getter method of this component ( Component.getDataModelSelectionName() enforces this).
What are the reasons for this requirement?
I think it would be very useful if @DataModelSelection could also be placed on a component even if this component doesn't expose a DataModel via the @DataModel annotation.
Of course, if @DataModelSelection was used in a component without an accompanying @DataModel annotation used in this component, it would be necessary to set the value attribute of @DataModelSelection to explicitly provide the context variable name the DataModel is bound to.
Any chances that the requirement could be lifted that @DataModelSelection needs an accompanying @DataModel annotation in the same component?
If not, we cannot really leverage the org.jboss.seam.framework package, if DataModel selection should be handled.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080461#4080461
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080461
18 years, 7 months
[Microcontainer] - Re: How do I programmatically declare a JNDI name dependency
by wolfc
Doh!
13:12:36,630 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
|
| *** CONTEXTS IN ERROR: Name -> Error
|
| HASessionState -> java.lang.IllegalArgumentException: Wrong arguments. setHAPartition for target AOPContainerProxy$4@bb0257 expected=[org.jboss.ha.framework.interfaces.HAPartition] actual=[org.jnp.interfaces.NamingContext]
|
| JGCacheInvalidationBridge -> java.lang.IllegalArgumentException: Wrong arguments. setHAPartition for target AOPContainerProxy$9@536500 expected=[org.jboss.ha.framework.interfaces.HAPartition] actual=[org.jnp.interfaces.NamingContext]
|
| HASingletonDeployer -> java.lang.IllegalArgumentException: Wrong arguments. setHAPartition for target AOPContainerProxy$11@1f84d01 expected=[org.jboss.ha.framework.interfaces.HAPartition] actual=[org.jnp.interfaces.NamingContext]
|
| HAJNDI -> java.lang.IllegalArgumentException: Wrong arguments. setHAPartition for target AOPContainerProxy$5@e6f8d7 expected=[org.jboss.ha.framework.interfaces.HAPartition] actual=[org.jnp.interfaces.NamingContext]
We could have predicated this one. For the moment I'll prefix "jndi:" to the dependencies.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080451#4080451
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080451
18 years, 7 months
[Tomcat, HTTPD, Servlets & JSP] - Obtaining Servlet Container Instance
by kumar.vi
We have AJP13 protocal for comm. between JK and JBoss server. Request generated by JK are handled by AJP Connector running in JBoss.
My understanding of code is this:
Client Request ---> mod_JK ---> AJP Connector ---> AJP Processor ---
---> Final Request is sent to container(Code is something like this connector.getContainer().invoke(request, response));
Question:
Who is setting up "container"? In "Ajp13Connector.java" there are setter and getter for container. But, who is setting these container?
What I am trying to do:
I have a bean which is loaded by some(like spring) framwork. This bean act like a server( handles the requests). It is similer to AJP Connector but, in my case this bean is loaded by my framwork which is loaded by JBoss.
This bean works perfect, problem is to forward final request to servlet container.
So, what my server want to do is to simply accepting the socket connection, removing all the custom details and pass on the request to normal request handling procedure (Which I think is passing request to container).
Question:
>From where to get container instance to which I can pass on the request.
Or
I will have to make connector similer to AJP13 activated by JBoss(or Tomcat)
Or you can see it in these way also
Can a bean use JBoss normal request handling machanise, working as a source of request?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080447#4080447
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080447
18 years, 7 months
[Security & JAAS/JBoss] - problem creating a new tomcat authentication method
by antoniofer
Hello,
I'm trying to create a new web authentication method following the next procedure:
- based on FormAuthenticator.java i've coded a new class (well, i've just copied FormAuthenticator but with different name in order to prevent errors)
- added the line CUSTOM=<<my custom class>> in Authentication.properties
- in web.xml, added the line <auth-method>CUSTOM</auth-method> (and all the necessary ones to protect the web resources)
I'm using a simple application based on JSP pages to test my configuration but get a HTTP/403 Configuration error.
This is the error page I get:
type Status report
message Configuration error: Cannot perform access control without an authenticated principal
description Access to the specified resource (Configuration error: Cannot perform access control without an authenticated principal) has been forbidden.
I've tried to "cheat" JBoss to test my class:
- changed in authentication.properties the line FORM=org.jboss.etc... with FORM=<<my custom class>>
- now the application's web.xml has the next line: <auth-method>FORM</auth-method>
Everything goes fine in this case, but I would like to add this new authentication method instead of modifying the FORM method.
Somebody knows what is happening?
Thanks in advance,
Antonio
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080446#4080446
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080446
18 years, 7 months