July 2009 - jboss-dev-forums - Jboss List Archives

[Design of JCA on JBoss] - Re: Difference Between Projects

by gurkanerdogdu

OK, understood. Stupid question :) standalone uses new MC booting. Thanks: View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241637#4241637 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241637

16 years, 9 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: Difference Between Projects

by jeff.zhang

Hi Gurkan, We are using it for integration JBossMC project. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241636#4241636 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241636

16 years, 9 months

1
0
0 / 0

[Design of EJB 3.0] - Re: EJBTHREE-1823 - handling of res-type in resource-ref

by jaikiran

"Wolfgang Knauf" wrote : | Is there any check that the object declared through the resource-env-ref/resource-ref element is actually of the correct type? It seems the error message for resource-env-ref is only coming if the declared class is not found at all by the classloader, but if it is just wrong, there is no error message. Is this worth one more JIRA ;-)? | | Wolfgang AFAIK, there isn't any check. Please add the comments to the existing JIRA for the missing validation and if possible attach the same application. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241634#4241634 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241634

16 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - How to use class "LifeCycle" in the JBPM 4.0

by fance317

I found the class "LifeCycle" in the package of the task. but it has never be used inside the code of the JBPM 4.0. Is it ready for the next version? Who tell why, please. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241630#4241630 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241630

16 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: One par file with multiple process definition ??

by chawlaashish26＠gmail.com

Hi kukeltje, Would you be able to provide some more info around that on how to use it and the deployment process if you will? Appreciate you getting back on this. Thanks Ash View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241625#4241625 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241625

16 years, 9 months

1
0
0 / 0

[Design of JBossXB] - Re: JBossXB does not assign schema defined attribute default

by alex.loubyansky＠jboss.com

I've committed the testcase here http://anonsvn.jboss.org/repos/common/jbossxb/trunk/src/test/java/org/jbo... and the xml and xsd are here http://anonsvn.jboss.org/repos/common/jbossxb/trunk/src/test/resources/or... As mentioned above, the problem is the XML parser cannot resolve the XSD. addSchemaLocation(XMLNS_BLUEPRINT, "blueprint.xsd"); won't help. This will configure XsdBinder to resolve schema to class mapping (i.e. this is binding layer) but it has nothing to do with the XML parser. So, here is the testcase I committed UnmarshallerFactory unmarshallerFactory = UnmarshallerFactory.newInstance(); | Unmarshaller unmarshaller = unmarshallerFactory.newUnmarshaller(); | | // this is to make the SAX parser parse the XSD as well and include default attribute values in the startElement | unmarshaller.setSchemaValidation(true); | | // this is EntityResolver that SAX parser (xerces) will use to resolve XSD location for the XML being parsed | JBossEntityResolver xmlResolver = new JBossEntityResolver(); | // Here we map schema location specified in the XML file to the local schema location, | // which is a path relative to the resources directory visible in the classpath. | // Note, we have to specify here and XML the complete URL including the protocol part into the schemaLocation. | // The reason is that if we specify schemaLocation in XML as just a filename, | // the SAX parser will compose its schemaLocation by adding the protocol, baseURI (which will depend on the | // environment the code is run in) and the schemaLocation we specified in the XML and then | // will pass this new schemaLocation to the resolver. | xmlResolver.registerLocalEntity("http://www.hostame.org/SchemaDefaultAttributeValue.xsd", "org/jboss/test/xb/builder/object/attribute/test/SchemaDefaultAttributeValue.xsd"); | unmarshaller.setEntityResolver(xmlResolver); | | // this is to resolve namespace to class mapping and build the SchemaBinding from the class | MultiClassSchemaResolver schemaBindingResolver = new MultiClassSchemaResolver(); | schemaBindingResolver.mapURIToClass("xb:test:default-attribute", DefaultAttribute.class); | // the reason we configured a separate EntityResolver for unmarshaller above instead of | // calling schemaBindingResolver.mapSchemaLocation(nsURI, location) is that | // entity resolution inside schemaBindingResolver is used only for nsURI to class resolution (by XsdBinder) | // and is not related to SAX parser entity resolution and XML validation. | | String xml = findXML("SchemaDefaultAttributeValue.xml"); | Object result = unmarshaller.unmarshal(xml, schemaBindingResolver); XSD <xsd:schema | targetNamespace="xb:test:default-attribute" | xmlns:xsd="http://www.w3.org/2001/XMLSchema" | elementFormDefault="qualified" | attributeFormDefault="unqualified"> | | <xsd:element name="default-attribute"> | <xsd:complexType> | <xsd:attribute name="attribute" type="xsd:int" default="123" /> | </xsd:complexType> | </xsd:element> | </xsd:schema> XML <default-attribute xmlns="xb:test:default-attribute" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | xsi:schemaLocation="xb:test:default-attribute http://www.hostame.org/SchemaDefaultAttributeValue.xsd"/> I agree, XSD resolution and its configuration is confusing. That's something we could work on and make simpler. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241616#4241616 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241616

16 years, 9 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Journal Compacting committed...

by clebert.suconic＠jboss.com

16 years, 9 months

1
0
0 / 0

[Design of JCA on JBoss] - Difference Between Projects

by gurkanerdogdu

There are two differents standalone projects, jboss-jca-sjc and jboss-jca-standalone. IMHO, Main bootstrap class is coming from sjc project. Then standalone project is useless? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241612#4241612 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241612

16 years, 9 months

1
0
0 / 0

[Design of Security on JBoss] - Re: Resolving jacc-api vs. jboss-javaee

by ALRubinger

Done and done. https://jira.jboss.org/jira/browse/JBASPECT-32 S, ALR View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241611#4241611 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241611

16 years, 9 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Consistent handling of HTTP response header across HTTP

by dward

Fixed: $ svn commit services/soap/src/test/java/org/jboss/soa/esb/actions/soap/SOAPClient_Response_UnitTest.java services/soap/src/main/java/org/jboss/soa/esb/actions/soap/SOAPClient.java Sending services/soap/src/main/java/org/jboss/soa/esb/actions/soap/SOAPClient.java Sending services/soap/src/test/java/org/jboss/soa/esb/actions/soap/SOAPClient_Response_UnitTest.java Transmitting file data .. Committed revision 27459. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241609#4241609 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241609

16 years, 9 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 July 2009