August 2007 - jboss-dev-forums - Jboss List Archives

[Design of JBoss Portal] - Re: Starting the detachment of portal common

by bdaw

Which modules do you plan to detach besides common? I see work on test and web. Any others on the list? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4075134#4075134 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4075134

18 years, 7 months

1
0
0 / 0

[Design of JBoss jBPM] - IdentityLoginModule how to inject IdentityService

by jmenendez

I am trying to use integrate the jbpm IdentityLoginModule with the Tomcat JAAS Realm to authenticate users using the jbpm identity schema. Looking at the IdentityLoginModule source code I saw that you need to inject the identityService to the IdentityLoginModule. How can I achieve this using Tomcat JAAS. I guess the other alternative is to write your own IdentityLoginModule to use with the Tomcat JAAS Realm. How well this will work with jbpm? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4075121#4075121 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4075121

18 years, 7 months

1
0
0 / 0

[Design of JBossXB] - Re: Unmarshaller: xsd:choice with minOccurs

by alex.loubyansky＠jboss.com

Here is the testcase I committed for this issue https://svn.jboss.org/repos/common/jbossxb/trunk/src/test/java/org/jboss/... It passes. Are you sure the XSD that is actually used the one you posted and the XML snipped is one that causes the error? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4075110#4075110 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4075110

18 years, 7 months

1
0
0 / 0

[Design of JBossXB] - Re: xsd:attribute ref unsupported in unmarshaller

by alex.loubyansky＠jboss.com

Top level attributes are bound to the schema's target namespace. While local attributes are bound according to the value of their form attribute or schema's attributeFormDefault attribute (which is unqualified by default) http://www.w3.org/TR/xmlschema-1/#declare-attribute And specifically in your schema attributeFormDefault is unqualified and the elementFormDefault is qualified. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4075097#4075097 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4075097

18 years, 7 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Using jdocbook

by steve.ebersole＠jboss.com

"nbhatia" wrote : | 1) I don't see images copied over from src\main\resources\shared\images to target | Why would they be? "nbhatia" wrote : | 2) The URL should probably have file:/// prepended to it. Xalan seems to be forgiving about this but saxon is not. | Nothing to do with SAXON or XALAN. Look at your stack trace. It is FOP. FOP is the one assuming that 'img.src.path' is supposed to be a URL reference instead of a File reference. Unfortunately the docbook folks are not forthcoming about exactly which form is expected... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4075073#4075073 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4075073

18 years, 7 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Using jdocbook

by nbhatia

Revisiting the MalformedURLException... | SEVERE: Error with URL 'D:\ProjectsTest\DocBook\andromda-tutorial-java\target\staging/images/../shared/images/AndromdaArchJava.jpg': | unknown protocol: d | java.net.MalformedURLException: unknown protocol: d | I see two issues with the build: 1) I don't see images copied over from src\main\resources\shared\images to target 2) The URL should probably have file:/// prepended to it. Xalan seems to be forgiving about this but saxon is not. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4075069#4075069 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4075069

18 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Renaming groupId for integration project

by pgier

I'm changing the groupId in the integration poms from jboss to org.jboss (should it be org.jboss.integration instead?). Please let me know if this causes a problem for anyone. I also changed the transaction-spi dependency on jboss-common-core to jboss-common-logging-spi because that is what was being used. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4075040#4075040 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4075040

18 years, 7 months

1
0
0 / 0

[Design of JBoss Build System] - Re: JDK 1.4 Compatibility for Microcontainer and other Proje

by pgier

I ran into some problems when trying to do this using profiles. Using a property value in the artifact Id can cause problems when resolving transitive dependencies. So I am using separate poms for the jdk14 builds. I didn't do this earlier because maven doesn't support using alternate poms in modules. This means that multi-module builds will have to be done one module at a time for the time being. I opened a maven issue http://jira.codehaus.org/browse/MNG-3150 to resolve this and will work on it when I have time. I have created working retro builds with retro tests for the common projects and jboss-test since they are dependencies of microcontainer. So now I'm gradually working my way through the microcontainer modules and their dependencies to get retro builds with working tests. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4075004#4075004 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4075004

18 years, 7 months

1
0
0 / 0

[Design of JBossXB] - Unmarshaller: xsd:choice with minOccurs

by anil.saldhana＠jboss.com

Suppose, I have the following XSD bit: | <xsd:element name="application-policy"> | <xsd:complexType> | <xsd:sequence> | <xsd:choice minOccurs="0"> | <xsd:element ref="jbsx:authentication"/> | <xsd:element ref="jbsx:authentication-jaspi"/> | </xsd:choice> | <xsd:element ref="jbsx:authorization" minOccurs="0"/> | | </xsd:sequence> | </xsd:complexType> | </xsd:element> | I get the following exception: | Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Requested element {urn: | jboss:security-config:5.0}authorization is not allowed in this position in the s | equence. A model group with minOccurs=1 that doesn't contain this element must follow. | at org.jboss.xb.binding.sunday.unmarshalling.SequenceBinding$1.startElem | ent(SequenceBinding.java:271) | at org.jboss.xb.binding.sunday.unmarshalling.ModelGroupBinding$Cursor.st | artElement(ModelGroupBinding.java:185) | at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startE | lement(SundayContentHandler.java:280) | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHan | dler.startElement(SaxJBossXBParser.java:381) | at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Sour | ce) | It seems that XB does not like an xsd:choice with minOccurs/maxOccurs. My xml looks like: | <jbsx:application-policy name="jboss-web-policy"> | <jbsx:authorization> | <jbsx:policy-module code="org.jboss.security.authorization.modules.DelegatingAuthorizationModule" flag="required"/> | </jbsx:authorization> | </jbsx:application-policy> | I am trying to avoid the optional authentication element. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074982#4074982 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4074982

18 years, 7 months

1
0
0 / 0

[Design of JBossXB] - Re: xsd:attribute ref unsupported in unmarshaller

by anil.saldhana＠jboss.com

Is the following an XSD issue? <xsd:attribute ref="jbsx:flag" use="required"/> That was the original issue that I had. You showed me that by namespace prefixing the flag attribute in the xml file, the issue does not exist. Can you please enlighten me? :) Why would the following work without any ns prefix in the xml: <xsd:element ref="jbsx:something" /> but not the attribute ref? I am just curious. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074966#4074966 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4074966

18 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums August 2007