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

[Design of EJB 3.0] - org.jboss.jbossas_jboss-as-naming dependencies

by scott.stark＠jboss.org

Looking at the naming dependencies, they are in the core project, and include: org.jboss.naming.ENCFactory - java:comp management org.jboss.naming.JavaCompInitializer org.jboss.naming.NamingContextFactory - uses lastInitialContextEnv ThreadLocal org.jnp.interfaces.NamingContext org.jnp.interfaces.MarshalledValuePair org.jnp.server.SingletonNamingServer - testing org.jboss.naming.Util - should be using org.jboss.util.naming.Util from jboss-common-core. I have replace this. The naming server has already been pulled into https://svn.jboss.org/repos/jbossas/projects/naming/trunk/jnpserver by Anil, so we should just be able to switch to that, and so can jbossas. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132049#4132049 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132049

18 years, 1 month

1
0
0 / 0

[Design of OSGi Integration] - Re: Facade Questions

by johnbailey

"alesj" wrote : | The new CLMD with Requirements/Capabilities has everything we need. | Along with Module and Domain they have been rewritten to have all the OSGi notions. | | For OSGiMetaData, there should just be deployers that transform Manifest.MF --> OSGiMetaData --> ClassLoaderMetaData. | It seems like the ClassLoadingMetaData is the correct choice. It has the Requirements and Capabilities representing the imports/exports. I will develop against that, as the ClassloaderMetaData only contains the ClassLoader. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132027#4132027 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132027

18 years, 1 month

1
0
0 / 0

[Design of EJB 3.0] - Re: Eclipse project settings in the ejb3 trunk

by scott.stark＠jboss.org

That won't work as its jca 1.5. I just uploaded the 1.0 jar from http://java.sun.com/j2ee/connector/index.jsp View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132018#4132018 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132018

18 years, 1 month

1
0
0 / 0

[Design of EJB 3.0] - Re: Eclipse project settings in the ejb3 trunk

by scott.stark＠jboss.org

The sandbox/ and socket-inflow/ project still don't have any classpath entries. After generating these with the eclipse plugin, I'm still seeing a missing dependency on the jca api being pulled in from jotm for the test target: | [starksm@succubus sandbox]$ mvn test | [INFO] Scanning for projects... | WAGON_VERSION: 1.0-beta-2 | [INFO] ---------------------------------------------------------------------------- | [INFO] Building JBoss EJB 3 Sandbox | [INFO] task-segment: [test] | [INFO] ---------------------------------------------------------------------------- | [INFO] [resources:resources] | [INFO] Using default encoding to copy filtered resources. | [INFO] [compiler:compile] | [INFO] Nothing to compile - all classes are up to date | [INFO] [resources:testResources] | [INFO] Using default encoding to copy filtered resources. | Downloading: http://snapshots.jboss.org/maven2/javax/resource/connector/1.0/connector-... | Downloading: http://repository.jboss.org/maven2/javax/resource/connector/1.0/connector... | Downloading: http://repository.jboss.org/maven2/javax/resource/connector/1.0/connector... | Downloading: http://repo1.maven.org/maven2/javax/resource/connector/1.0/connector-1.0.jar | [INFO] ------------------------------------------------------------------------ | [ERROR] BUILD ERROR | [INFO] ------------------------------------------------------------------------ | [INFO] Failed to resolve artifact. | | Missing: | ---------- | 1) javax.resource:connector:jar:1.0 | | Try downloading the file manually from: | http://java.sun.com/j2ee/connector/download.html | | Then, install it using the command: | mvn install:install-file -DgroupId=javax.resource -DartifactId=connector \ -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file | Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=javax.resource -DartifactId=connector \ | -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file \ | -Durl=[url] -DrepositoryId=[id] | | Path to dependency: | 1) org.jboss.ejb3:jboss-ejb3-sandbox:jar:0.12.0-SNAPSHOT | 2) jotm:jotm:jar:2.0.10 | 3) javax.resource:connector:jar:1.0 | We should not be needing jotm. I'm going to deploy the org.jboss.javaee:jboss-jca-api as javax.resource:connector for now. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132016#4132016 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132016

18 years, 1 month

1
0
0 / 0

[Design of JBossXB] - How to force strict validation?

by rob.stryker＠jboss.com

I've been trying this out for a while... no success. Schema: <xsd:schema xmlns:jbxb="http://www.jboss.org/xml/ns/jbxb" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <xsd:element name="garbageRoot" type="root-type"/> <xsd:complexType name="root-type"> <xsd:annotation> <xsd:appinfo> <jbxb:class impl="garbage.XbGarbageRoot"/> </xsd:appinfo> </xsd:annotation> <xsd:attribute name="name" type="xsd:string" use="required" /> </xsd:complexType> </xsd:schema> XbGarbageRoot (POJO): public class XbGarbageRoot { private String name; public XbGarbageRoot() { } public String getName() { return name; } public void setName(String name) { this.name = name; } } Test case: public class ParseTest extends TestCase { private static final String SCHEMA = "/home/rob/apps/eclipse/workspaces/work/garbage/src/schema.xsd"; private static final String DATA = "/home/rob/apps/eclipse/workspaces/work/garbage/data/test.xml"; public void testABC() { try { File f = new File(SCHEMA); InputStream stream = new FileInputStream(f); SchemaBinding binding = XsdBinder.bind(stream, "UTF-8", null); stream.close(); Unmarshaller unmarshaller = UnmarshallerFactory.newInstance().newUnmarshaller(); binding.setStrictSchema(true); FileInputStream dataStream = new FileInputStream(new File(DATA)); Object xmlObject = unmarshaller.unmarshal(dataStream, binding); System.out.println("object is " + xmlObject); } catch( Exception e ) { // GOOD! I want XB to fail! return; } fail("data file should not have validated!"); } } Clearly, i'm setting that it should use a strict schema... but it's not throwing an exception. Any ideas? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132014#4132014 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132014

18 years, 1 month

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Implementing JAXB style parsing for aop-mc-int

by adrian＠jboss.org

The builder stuff doesn't use the schema, it "generates it" from the annotations. Turn on trace logging for org.jboss.xb. It will tell you what it is doing. There's also a simple "SchemaPrinter" class you can use to look at what it thinks the schema should be. Or alternatively, commit the code and Alex or me can look at it. I can only guess what the problem is since I can't see your code. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132008#4132008 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132008

18 years, 1 month

1
0
0 / 0

[Design of JBoss Build System] - Re: JBossAS CR1 build plan

by scott.stark＠jboss.org

These are the jbossas related dependencies I see: <version.org.jboss.jbossas_jboss-as-aspects>5.0.0.Beta4</version.org.jboss.jbossas_jboss-as-aspects> <version.org.jboss.jbossas_jboss-as-connector>5.0.0.Beta4</version.org.jboss.jbossas_jboss-as-connector> <version.org.jboss.jbossas_jboss-as-iiop>5.0.0.Beta4</version.org.jboss.jbossas_jboss-as-iiop> <version.org.jboss.jbossas_jboss-as-naming>5.0.0.Beta4</version.org.jboss.jbossas_jboss-as-naming> <version.org.jboss_jnpserver>5.0.0.Beta4</version.org.jboss_jnpserver> The last two should essentially be the same thing, and even then I'm not sure why there is a dependency on the implementation vs the javax.naming apis. I'm going through the ejb3 dependencies to see what type of additions to the integration project are needed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131999#4131999 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131999

18 years, 1 month

1
0
0 / 0

[Design of EJB 3.0] - Re: Eclipse project settings in the ejb3 trunk

by ALRubinger

I'd done a two-step update of the .classpath files in order to more easily track revisions in SVN. Looks like you got caught inbetween, update again? >From Core .classpath, for example: http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/trunk/core/.classpath All you should have to set is variable M2_REPO to point to your local Maven repository. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131998#4131998 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131998

18 years, 1 month

1
0
0 / 0

[Design of EJB 3.0] - Eclipse project settings in the ejb3 trunk

by scott.stark＠jboss.org

I just updated the ejb3 trunk projects, and all of the eclipse classpaths are empty. Why is that? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131996#4131996 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131996

18 years, 1 month

1
0
0 / 0

[Design of OSGi Integration] - Re: Facade Questions

by alesj

"johnbailey" wrote : Sounds good. I will drop the reference to the OSGIMetaData attachment and pull it from the CLMD. | The new CLMD with Requirements/Capabilities has everything we need. Along with Module and Domain they have been rewritten to have all the OSGi notions. For OSGiMetaData, there should just be deployers that transform Manifest.MF --> OSGiMetaData --> ClassLoaderMetaData. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131994#4131994 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131994

18 years, 1 month

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 February 2008