March 2008 - jboss-dev-forums - Jboss List Archives

[Design of Security on JBoss] - Re: Security Injection in AS5

by alex.loubyansky＠jboss.com

The XSD cannot be found in the classpath. log wrote : 2008-03-27 15:36:04,375 TRACE [org.jboss.xb.binding.sunday.unmarshalling.DefaultSchemaResolver] (main) Mapped schemaLocation to filename: security-config_5_0.xsd | 2008-03-27 15:36:04,375 TRACE [org.jboss.xb.binding.sunday.unmarshalling.DefaultSchemaResolver] (main) getInputSource, nsURI=urn:jboss:security-config:5.0, baseURI=null, schemaLocation=resource:schema/security-config_5_0.xsd | 2008-03-27 15:36:04,375 TRACE [org.jboss.util.xml.JBossEntityResolver] (main) resolvePublicID, publicId=urn:jboss:security-config:5.0 | 2008-03-27 15:36:04,375 TRACE [org.jboss.util.xml.JBossEntityResolver] (main) Found entity from publicId=urn:jboss:security-config:5.0 fileName=security-config_5_0.xsd | 2008-03-27 15:36:04,375 TRACE [org.jboss.util.xml.JBossEntityResolver] (main) Cannot load publicId from classpath resource: security-config_5_0.xsd The file is in the schema directory of the jboss-metadata.jar Changing the schemaLocation in the XML to include "schema/" doesn't work. I tried changing the mapping in the JBossEntityResolver to include the "schema/". Didn't work. log wrote : 2008-03-27 15:50:25,614 TRACE [org.jboss.util.xml.JBossEntityResolver] (main) Found entity from publicId=urn:jboss:security-config:5.0 fileName=schema/security-config_5_0.xsd | 2008-03-27 15:50:25,614 TRACE [org.jboss.util.xml.JBossEntityResolver] (main) Cannot load publicId from classpath resource: schema/security-config_5_0.xsd View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139325#4139325 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139325

16 years, 3 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Handling contexts in error

by alesj

"adrian(a)jboss.org" wrote : | PROPOSAL | | I've had a seperate thought which is probably more acceptable to both | you and to me, ;-) | | What you really want to do is manage the state of the failed beans. | i.e. you want to takeover the management of the context in error from the MC | and fix it manually. | | So my solution would be to allow something like: | | xml pseudo code as always ;-) | | | <bean ... error-handling="manual"/> | | | | If for example the bean threw an error in start() then we no longer just discard | this bean. Instead we would effectively change its controller mode to "manual" | (if it isn't already) and just then revert it to the previous state. i.e. Created in this case | or back to Instantiated if the property configuration failed. | | You can then pick up the management of the bean from there. | When you decide to move the bean, we would just clear the error in the | controller context and try again (reverting back to automatic if the bean | was previously in that mode). | | We would never try to move a context in such a state without an | explicit request on the controller to do so. | | I don't think this would require a major change in the Controller, | most of the work would be in the IncompleteDeploymentException | where we would now have to check all contexts at all states | to see whether it has an error set (previously we just retrieved those | in the **ERROR** state). | | We may want to only allow this for checked exceptions. i.e. if start throws | a RuntimeException or Error, we would still discard the bean | or perhaps make it configurable? | | This semantic would deal with my objections above and give you the | ability to manage the failing beans/contexts without having to re-install them. Are there any other hooks (api changes), apart ErrorHandlingMode enum, you've had in mind? Picking up bean in the Controller can be done with Controller::change. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139322#4139322 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139322

16 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: New jBPM Console

by kukeltje

anonymous wrote : alternatively, we'll provide the identity component implementation that fits in the portal identity interface. i see that as more feasible, but also that is not concrete yet. Sound interesting. I'll file at least a jira issue for this View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139318#4139318 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139318

16 years, 3 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Pluggable Instrumentors in AS5

by kabir.khan＠jboss.com

Galder raised this question internally for a support case a few days ago, and it has now been added. http://jira.jboss.com/jira/browse/JBAS-5331 http://jira.jboss.com/jira/browse/JBPAPP-709 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139316#4139316 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139316

16 years, 3 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Pluggable Instrumentors in AS5

by jason.greene＠jboss.com

Is there a reason why the pluggable instrumentors are not included in the AS build? Requiring users to download AOP and then manually install them is not only a PITA, people often end up using the wrong version. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139315#4139315 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139315

16 years, 3 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Deployment ClassPath and AOP

by kabir.khan＠jboss.com

Cool :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139314#4139314 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139314

16 years, 3 months

1
0
0 / 0

[Design of JBoss Build System] - aop pom for CR8

by adrian＠jboss.org

Paul why are you breaking people's builds? http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139298#4139298 Since the MC projects rely on jboss-aop to specify which versions of javassist, trove, qdox to use (instead of us having to change them every time we update AOP) they no longer build. This includes the tagged betas I did last weekend http://repository.jboss.com/maven2/org/jboss/microcontainer/jboss-microco... Those builds are no longer reproducable!!!!!! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139313#4139313 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139313

16 years, 3 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Concurrent deployments

by alesj

"adrian(a)jboss.org" wrote : | The important thing is that we don't change the api after 2.0.0.CR1 | we can implement missing features without changing the api if the api already exists. We can probably add methods, but not modify the existing? Or plain nothing should be modified, except impl details? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139308#4139308 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139308

16 years, 3 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Deployment ClassPath and AOP

by adrian＠jboss.org

I see what the problem is, it's my misunderstanding. You expect the GUID to be a host name in the url. I've changed it to this and now it works. ;-) | // protocol, host, file | URL dynamicClassRoot = new URL("vfsmemory", new GUID().toString(), ""); | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139307#4139307 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139307

16 years, 3 months

1
0
0 / 0

[Design of Security on JBoss] - Re: Security Injection in AS5

by alex.loubyansky＠jboss.com

Yes, by "fixing it" I meant the logging :) I am still figuring out why it can't find the schema. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139300#4139300 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139300

16 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums March 2008