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

[JBoss ESB Development] - Best practise packaging ESB archives, No. of Services per .esb?

by Kristian Jones

Kristian Jones [http://community.jboss.org/people/kjcooler] created the discussion "Best practise packaging ESB archives, No. of Services per .esb?" To view the discussion, visit: http://community.jboss.org/message/558941#558941 -------------------------------------------------------------- Hi, I've worked through the tutorials and am interested to know on what the best practise for packaging up services into ESB archives is? I'm working on a project that has gone through a prototyping phase and would like to know whether it is preffered to package a single service into a single *.esb archive or whether multiple services per esb archive is acceptable and what the impact of this might be ? My concern is that if we keep adding to a single project and single ESB archive, it will become harder to maintain in the furture, meaning the whole archive will need to be deployed. Packaging multiple services into a single esb archive doesn't feel very service orientated and I was just wondering what other people do? Thanks in advance. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/558941#558941] Start a new discussion in JBoss ESB Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 2 months

1
0
0 / 0

[JBoss AS7 Development] - Hacking on AS7

by Stefano Maestri

Stefano Maestri [http://community.jboss.org/people/maeste] modified the document: "Hacking on AS7" To view the document, visit: http://community.jboss.org/docs/DOC-15596 -------------------------------------------------------------- h4. 1. Create a github account http://github.com http://github.com h4. 2. Fork jboss-as into your account http://github.com/jbossas/jboss-as http://github.com/jbossas/jboss-as h4. 3. Clone your newly forked copy onto your local workspace $ git clone git@github.com:[your user]/jboss-as.git Initialized empty Git repository in /devel/jboss-as/.git/ remote: Counting objects: 2444, done. remote: Compressing objects: 100% (705/705), done. remote: Total 2444 (delta 938), reused 2444 (delta 938) Receiving objects: 100% (2444/2444), 1.71 MiB | 205 KiB/s, done. Resolving deltas: 100% (938/938), done. $ cd jboss-as h4. 4. Add a remote ref to upstream, for pulling future updates git remote add upstream git://github.com/jbossas/jboss-as.git h4. 5. Use maven (make sure you use maven 3) $ mvn install ..... [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] JBoss Application Server: BOM ..................... SUCCESS [1.834s] [INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [0.022s] [INFO] JBoss Application Server: Domain Core ............. SUCCESS [3.051s] [INFO] JBoss Application Server: Server Manager .......... SUCCESS [0.204s] [INFO] JBoss Application Server: Server .................. SUCCESS [0.283s] [INFO] JBoss Application Server: Domain Controller ....... SUCCESS [0.084s] [INFO] JBoss Application Server: Process Manager ......... SUCCESS [0.314s] [INFO] JBoss Application Server: Remoting ................ SUCCESS [0.390s] [INFO] JBoss Application Server: Build ................... SUCCESS [5.696s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ h4. 6. Pulling later updates from upstream $ git pull upstream master >From git://github.com/jbossas/jboss-as * branch master -> FETCH_HEAD Updating 3382570..1fa25df Fast-forward {parent => bom}/pom.xml | 70 ++++---------- build/pom.xml | 13 +-- domain/pom.xml | 10 ++ .../src/main/resources/examples/host-example.xml | 2 +- .../resources/examples/jboss-domain-example.xml | 28 +++--- .../main/resources/schema/jboss-domain-common.xsd | 12 +-- .../main/resources/schema/jboss-domain-host.xsd | 2 +- domain/src/main/resources/schema/jboss-domain.xsd | 17 ++-- pom.xml | 100 ++++++++++++++++++-- process-manager/pom.xml | 3 +- 10 files changed, 156 insertions(+), 101 deletions(-) rename {parent => bom}/pom.xml (85%) h4. 7. Pushing pulled updates or local commits to your private github repo (origin) $ git push Counting objects: 192, done. Delta compression using up to 4 threads. Compressing objects: 100% (44/44), done. Writing objects: 100% (100/100), 10.67 KiB, done. Total 100 (delta 47), reused 100 (delta 47) To git@github.com:[your user]/jboss-as.git 3382570..1fa25df master -> master h4. 8. Discuss your planned changes (if you want feedback) * On the forums - http://community.jboss.org/en/jbossas/dev/jboss_as7_development http://community.jboss.org/en/jbossas/dev/jboss_as7_development * On IRC - irc://irc.freenode.org/jboss-as7 or https://webchat.freenode.net/?channels=jboss-as7 (http://webchat.freenode.net/?channels=jboss-as7) h4. 9. Make sure there is a JIRA somewhere for the enhancement/fix http://jira.jboss.org http://jira.jboss.org h4. 10. Make the changes and commit one or more times (Don't forget to push) git commit -m 'JBAS-XXXX Frunubucate the Fromungulator' git commit -m 'JBAS-YYYY Tripple Performance of Fromungulation' git push h4. 11. Get your changes merged into upstream 1. Make sure your repo is in sync with other unrelated changes in upstream before requesting your changes be merged into upstream 1. git pull upstream master 2. Email a pull request to mailto:jbossas-pull-requests@lists.jboss.org jbossas-pull-requests(a)lists.jboss.org (if I haven't subscribed the list, do it https://lists.jboss.org/mailman/listinfo/jbossas-pull-requests here) with a link to your repo, a description of the changes, and who reviewed (if any) 3. If you have other work going on, consider using a branch to isolate the pull changes from the other work (git branch mychange) 4. After review a maintainer will merge your patch, and reply h4. Appendix A. Adding a new external dependency 1. Edit pom.xml and add a property of the form "version.groupId.artifactId" which contains the version of the dependency. Add your dependency to the <dependencyManagement> section, and use the property for the version. If your new dependency has any transitive dependencies, be sure to <exclude> them (or if possible, update the project so that all its dependencies are of *provided* scope). 2. Add your dependency to any AS modules that require it, but only with group/artifact. 3. Edit build/pom.xml and add your dependency with only group/artifact. 4. Create a directory in build/src/modules corresponding to the *module's* group/artifact name (which may differ from the Maven group/artifact name), with a version of "noversion", like this: "build/src/modules/org/jboss/foo/jboss-foo/noversion". 5. Create a module.xml file inside the "noversion" directory. Use a module.xml from another similar module as a template. 6. Edit build/build.xml and add a <module-def> element. The group/artifact listed in the <module-def> element correspond to the *module* group/artifact name. The group/artifact listed in the nested maven-resource element(s) refer to the *Maven* group/artifact name. 7. *Important:* Make sure you did not introduce any transitive dependencies by using "mvn dependency:tree". If you did, be sure to add <exclusion>s for each of them to your dependency as described above. Please be sure to preserve the alphabetical ordering of all POMs and the build.xml file. h4. Appendix B. Adding a new AS submodule 1. Create the directory corresponding to the submodule and add it to the root pom.xml file. The convention is to leave off the "jboss-as-" portion, so "jboss-as-remoting" becomes "remoting". 2. Create a POM for your submodule (use another submodule as a template). Make sure all dependencies you specify do *not* include a version. The group ID should be "org.jboss.as", and the artifact ID should begin with "jboss-as-" and there should be a proper <name> for the new module. 3. Add the new submodule to the top section of the <dependencyManagement> of bom/pom.xml. The version should be set to "${project.version}". This section is sorted alphabetically by artifact name so please preserve that ordering. 4. Add your submodule dependency to any AS modules that require it, but only with group/artifact. 5. Edit build/pom.xml and add the new submodule with only group/artifact. 6. Create a directory in build/src/modules corresponding to the submodule, with a version of "noversion", like this: "build/src/modules/org/jboss/as/jboss-as-new-subsystem/noversion". 7. Create a module.xml file inside the "noversion" directory. Use a module.xml from another subsystem as a template. 8. Edit build/build.xml and add a <module-def> element for the subsystem. The maven and module group and artifact IDs should match up. Use another submodule as a template. Please be sure to preserve the alphabetical ordering of all POMs and the build.xml file. -------------------------------------------------------------- Comment by going to Community [http://community.jboss.org/docs/DOC-15596] Create a new document in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]

14 years, 2 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS7 Development] - JCA / Datasources in domain.xml

by Stefano Maestri

Stefano Maestri [http://community.jboss.org/people/maeste] replied to the discussion "JCA / Datasources in domain.xml" To view the discussion, visit: http://community.jboss.org/message/558883#558883 -------------------------------------------------------------- > Jesper Pedersen wrote: > > I have been thinking about the configuration for the JCA container - e.g. <jca-container>. > Hi I have completed the xsd design and service implementation for JCA-container (connector subsystem). I have just requested the pull to mantainers, but if someone would have a look it will be found on my git space http://github.com/maeste/jboss-as http://github.com/maeste/jboss-as under connector module. just to keep everyone up to date on work going on in this area, and have some feedbacks too. bye S. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/558883#558883] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 2 months

1
0
0 / 0

[EJB 3.0 Development] - EJBTHREE-2143 EjbReferenceResolver for nointerface view

by jaikiran pai

jaikiran pai [http://community.jboss.org/people/jaikiran] created the discussion "EJBTHREE-2143 EjbReferenceResolver for nointerface view" To view the discussion, visit: http://community.jboss.org/message/558875#558875 -------------------------------------------------------------- I'm going to prioritize https://jira.jboss.org/browse/EJBTHREE-2143 https://jira.jboss.org/browse/EJBTHREE-2143 and start working on it today. The reason I had not touched it this long, was because even though the implementation was easy, it required some careful thought to avoid bringing in JBMETA 2.x dependency into ejb3-common (due to our EAP requirements). After some thought, I have now decided what needs to be done: 1) I am going to create a new jboss-ejb3-ejbref-resolver in git 2) Deprecate the current resolvers (and the spi) from ejb3-common. 3) Move that existing spi and impl code to the new git project created in #1 (and rename their package names) 4) Provide JBMETA 1.x (a.k.a EJB3.0 aware) based impl (for EAP) and JBMETA 2.x (a.k.a EJB3.1 aware) based impl for AS trunk and any other consumers. 5) Once we have this new jboss-ejb3-ejbref-resolver ready, I'm going to make ejb3-core depend on this and +delegate+ the ref resolution to these resolvers (to avoid backward compatibility for EAP). I'm going to start work on this today. If there are any objections, feel free to report here. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/558875#558875] Start a new discussion in EJB 3.0 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 2 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss Tools Development] - can't use jsf 2.0 from jboss tools 3.2 wizard

by Alexey Kazakov

Alexey Kazakov [http://community.jboss.org/people/akazakov] replied to the discussion "can't use jsf 2.0 from jboss tools 3.2 wizard" To view the discussion, visit: http://community.jboss.org/message/558845#558845 -------------------------------------------------------------- Are you trying to create a project using New Dynamic Web Project wizard or New JSF Project wizard? The first one is a wizard of Eclipse Web Tools and should work in Eclipse 3.6/WTP 3.2. The second one is a wizard of JBoss Tools and will support JSF 2 projects in JBT 3.2.0.M2. See https://jira.jboss.org/browse/JBIDE-5219 https://jira.jboss.org/browse/JBIDE-5219 And yes we still bundle RichFaces 3.2 with JBT. See https://jira.jboss.org/browse/JBIDE-6183 https://jira.jboss.org/browse/JBIDE-6183 -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/558845#558845] Start a new discussion in JBoss Tools Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 2 months

1
0
0 / 0

[JBoss Tools Development] - can't use jsf 2.0 from jboss tools 3.2 wizard

by nacer mouzai

nacer mouzai [http://community.jboss.org/people/nmouzai] created the discussion "can't use jsf 2.0 from jboss tools 3.2 wizard" To view the discussion, visit: http://community.jboss.org/message/558827#558827 -------------------------------------------------------------- I installed eclipse 3.6 and jboss tools 3.2. When i try to create dynamic web wizard i can't get jsf 2.0 but only jsf 1.1 0r 1.2. And I noticed that Jboss tools 3.2 use only richfaces 3.2 is it right. thanks -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/558827#558827] Start a new discussion in JBoss Tools Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 2 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss Messaging Development] - How can I specify a message destination reference as my MDB destination?

by Matt Phillips

Matt Phillips [http://community.jboss.org/people/controlfreak123] replied to the discussion "How can I specify a message destination reference as my MDB destination?" To view the discussion, visit: http://community.jboss.org/message/558783#558783 -------------------------------------------------------------- I know this post is old but afaik @ActivationConfigProperty(propertyName="+destination+", propertyValue="queue/MyQueue") is going to try and lookup queue/MyQueue through jndi. If you have a message destination reference that binds queue/MyQueue to a jndi name then it will indeed find it. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/558783#558783] Start a new discussion in JBoss Messaging Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 2 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss Microcontainer Development POJO Server] - Implementing a non-flat deployment for Weld Integration

by Flavia Rainone

Flavia Rainone [http://community.jboss.org/people/flavia.rainone%40jboss.com] replied to the discussion "Implementing a non-flat deployment for Weld Integration" To view the discussion, visit: http://community.jboss.org/message/558761#558761 -------------------------------------------------------------- > Marius Bogoevici wrote: > > I'll add a fix sometime this week. I plan on reviving the unique name JNDI binder for this. > Great! Thanks for the feedback :) -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/558761#558761] Start a new discussion in JBoss Microcontainer Development POJO Server at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 2 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss Microcontainer Development POJO Server] - Implementing a non-flat deployment for Weld Integration

by Marius Bogoevici

Marius Bogoevici [http://community.jboss.org/people/marius.bogoevici] replied to the discussion "Implementing a non-flat deployment for Weld Integration" To view the discussion, visit: http://community.jboss.org/message/558672#558672 -------------------------------------------------------------- I'll add a fix sometime next week. I plan on reviving the unique name JNDI binder for this. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/558672#558672] Start a new discussion in JBoss Microcontainer Development POJO Server at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 2 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss Microcontainer Development POJO Server] - Implementing a non-flat deployment for Weld Integration

by Flavia Rainone

Flavia Rainone [http://community.jboss.org/people/flavia.rainone%40jboss.com] replied to the discussion "Implementing a non-flat deployment for Weld Integration" To view the discussion, visit: http://community.jboss.org/message/558671#558671 -------------------------------------------------------------- > Flavia Rainone wrote: > > > Pete Muir wrote: > > > > Looks like the problem is that the services have got a bit out of control in JBoss AS, and that JBossEjbServices has ended up being dual purposed as an EJB discovery mechanism, and as an impl of EjbInjectionServices. So when you copy it, you end up copying the discovered ejbs as well. > > > > I think the best course of action is to split the two bits of JBossEjbServices into it's two parts - discovery and injection. > That makes a lot of sense and explains why I wasn't able to get rid of the problem. > I'll try that! That worked. :) For now, I'll attach a patch to Jira with everything I did to have WELDINT-1 working in AS trunk. We need a fix for the BeanManager JNDI binding issue before that is committed. Any news on that? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/558671#558671] Start a new discussion in JBoss Microcontainer Development POJO Server at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 2 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 August 2010