[JBoss JIRA] (JBIDE-13249) Improve MDB support
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13249?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-13249:
---------------------------------------------
in JBT with Eclipse there are two wizards:
"EJB3 Message Driven Bean"
Wich generates:
public @MessageDriven class test implements MessageListener {
}
and
"Message Driven Bean (EJB-3.x)"
which has some more options and can generate stuff like:
"@MessageDriven(
activationConfig = { @ActivationConfigProperty(
propertyName = "destinationType", propertyValue = "javax.jms.Queue"
) },
mappedName = "herewego")
@TransactionManagement(TransactionManagementType.BEAN)
public class test2 implements MessageListener {"
Seems to me there are a annotations etc.
> Improve MDB support
> -------------------
>
> Key: JBIDE-13249
> URL: https://issues.jboss.org/browse/JBIDE-13249
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: ejb3
> Reporter: Clebert Suconic
> Assignee: Rob Stryker
>
> I have recently tried creating an MDB and it seems out of date.
> It's not adding any annotations and not asking the user for any parameters.
> You could do something like this:
> - Ask what provider is going to be used...
> Ask what's the queue name to be used
> What Resource Adapter's name. (It would be great if you could inspect the server being used here for the RA's names. Each hornetq pooled connection factory will be a resource adapter name BTW).
> What Queue Name
> you could also provide additional activation properties by either selecting a list of providers. Or even better you could inspect the list of available activation properties, so it would be more generic.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-11121) Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-11121:
-------------------------------
Attachment: (was: JBIDE-11121.tweak.txt)
> Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11121
> URL: https://issues.jboss.org/browse/JBIDE-11121
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: SOA Tooling
> Affects Versions: 3.3.0.Beta1-SOA
> Reporter: Nick Boldt
> Assignee: Douglas Palmer
> Priority: Blocker
> Labels: f2f2012
> Fix For: 4.0.0.Alpha1-SOA
>
> Attachments: JBIDE-11121.tweak.txt, ModeShapeToolsBuildLog.txt
>
>
> Generate target platforms for JBT/JBDS SOA Tooling which include:
> 1. JBT Core TP + last stable JBT Core milestone.
> 2. JBDS Core TP + last stable JBDS Core milestone.
> Then, all SOA Component jobs should be rekeyed to use these new TPs when building instead of the JBT/JBDS Core ones.
> This includes Drools, which currently builds against Helios instead of Indigo, and Savara, which has requirements which are not as yet in the JBT/JBDS Core TPs (eg., GMF and Graphiti).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-11121) Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-11121:
-------------------------------
Attachment: JBIDE-11121.tweak.txt
> Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11121
> URL: https://issues.jboss.org/browse/JBIDE-11121
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: SOA Tooling
> Affects Versions: 3.3.0.Beta1-SOA
> Reporter: Nick Boldt
> Assignee: Douglas Palmer
> Priority: Blocker
> Labels: f2f2012
> Fix For: 4.0.0.Alpha1-SOA
>
> Attachments: JBIDE-11121.tweak.txt, ModeShapeToolsBuildLog.txt
>
>
> Generate target platforms for JBT/JBDS SOA Tooling which include:
> 1. JBT Core TP + last stable JBT Core milestone.
> 2. JBDS Core TP + last stable JBDS Core milestone.
> Then, all SOA Component jobs should be rekeyed to use these new TPs when building instead of the JBT/JBDS Core ones.
> This includes Drools, which currently builds against Helios instead of Indigo, and Savara, which has requirements which are not as yet in the JBT/JBDS Core TPs (eg., GMF and Graphiti).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-11121) Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-11121:
-------------------------------
Attachment: JBIDE-11121.tweak.txt
> Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11121
> URL: https://issues.jboss.org/browse/JBIDE-11121
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: SOA Tooling
> Affects Versions: 3.3.0.Beta1-SOA
> Reporter: Nick Boldt
> Assignee: Douglas Palmer
> Priority: Blocker
> Labels: f2f2012
> Fix For: 4.0.0.Alpha1-SOA
>
> Attachments: JBIDE-11121.tweak.txt, ModeShapeToolsBuildLog.txt
>
>
> Generate target platforms for JBT/JBDS SOA Tooling which include:
> 1. JBT Core TP + last stable JBT Core milestone.
> 2. JBDS Core TP + last stable JBDS Core milestone.
> Then, all SOA Component jobs should be rekeyed to use these new TPs when building instead of the JBT/JBDS Core ones.
> This includes Drools, which currently builds against Helios instead of Indigo, and Savara, which has requirements which are not as yet in the JBT/JBDS Core TPs (eg., GMF and Graphiti).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-11121) Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-11121:
-------------------------------
Attachment: JBIDE-11121.tweak.txt
I think this patch might help things, but I still can't resolve the TP, whether it's called soatools-JunoSR1a or soatools, and whether the parent pom is versioned 4.1.0.Alpha1-SNAPSHOT or 4.1.0.JBIDE-11121-SNAPSHOT:
[^JBIDE-11121.tweak.txt]
> Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11121
> URL: https://issues.jboss.org/browse/JBIDE-11121
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: SOA Tooling
> Affects Versions: 3.3.0.Beta1-SOA
> Reporter: Nick Boldt
> Assignee: Douglas Palmer
> Priority: Blocker
> Labels: f2f2012
> Fix For: 4.0.0.Alpha1-SOA
>
> Attachments: ModeShapeToolsBuildLog.txt
>
>
> Generate target platforms for JBT/JBDS SOA Tooling which include:
> 1. JBT Core TP + last stable JBT Core milestone.
> 2. JBDS Core TP + last stable JBDS Core milestone.
> Then, all SOA Component jobs should be rekeyed to use these new TPs when building instead of the JBT/JBDS Core ones.
> This includes Drools, which currently builds against Helios instead of Indigo, and Savara, which has requirements which are not as yet in the JBT/JBDS Core TPs (eg., GMF and Graphiti).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-11121) Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-11121:
-------------------------------
Attachment: (was: JBIDE-11121.tweak.txt)
> Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11121
> URL: https://issues.jboss.org/browse/JBIDE-11121
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: SOA Tooling
> Affects Versions: 3.3.0.Beta1-SOA
> Reporter: Nick Boldt
> Assignee: Douglas Palmer
> Priority: Blocker
> Labels: f2f2012
> Fix For: 4.0.0.Alpha1-SOA
>
> Attachments: ModeShapeToolsBuildLog.txt
>
>
> Generate target platforms for JBT/JBDS SOA Tooling which include:
> 1. JBT Core TP + last stable JBT Core milestone.
> 2. JBDS Core TP + last stable JBDS Core milestone.
> Then, all SOA Component jobs should be rekeyed to use these new TPs when building instead of the JBT/JBDS Core ones.
> This includes Drools, which currently builds against Helios instead of Indigo, and Savara, which has requirements which are not as yet in the JBT/JBDS Core TPs (eg., GMF and Graphiti).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-11121) Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-11121 at 12/13/12 5:10 PM:
--------------------------------------------------------------
I think some steps might be missing. Here's what I did:
{code}
git clone git://github.com/jbosstools/jbosstools-maven-plugins/
pushd jbosstools-maven-plugins/tycho-plugins/; mvn install; popd
git clone git://github.com/mickaelistria/jbosstools-build.git
pushd jbosstools-build; git checkout JBIDE-11121
pushd parent; mvn install; popd
pushd target-platforms/jbosstools-4.2.1.a/; mvn install; popd
pushd target-platforms/soatools-4.2.1.a/; mvn install; popd
git clone git://github.com/jbosstools/jbosstools-bpel.git
pushd jbosstools-bpel
sed -i -e "s/4.1.0.Alpha1-SNAPSHOT/4.1.0.JBIDE-11121-SNAPSHOT/g" pom.xml
mvn clean verify -P soa -Dno.jbosstools.site -Dtycho.localArtifacts=ignore
popd
{code}
Result:
{code}
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ multiple ---
[INFO] Installing /home/nboldt/tru/jbosstools-build/target-platforms/soatools-4.2.1.a/pom.xml to /home/nboldt/.m2/repository/org/jboss/tools/target-platforms/soatools/multiple/4.2.1.a-SNAPSHOT/multiple-4.2.1.a-SNAPSHOT.pom
[INFO] Installing /home/nboldt/tru/jbosstools-build/target-platforms/soatools-4.2.1.a/target/multiple.target to /home/nboldt/.m2/repository/org/jboss/tools/target-platforms/soatools/multiple/4.2.1.a-SNAPSHOT/multiple-4.2.1.a-SNAPSHOT-multiple.target
> mvn clean verify -P soa -Dno.jbosstools.site -Dtycho.localArtifacts=ignore
Could not resolve target platform specification artifact org.jboss.tools.target-platforms.soatools-JunoSR1a:multiple:target:multiple:4.2.1.a-SNAPSHOT
> mvn clean verify -P soa -Dno.jbosstools.site
Could not resolve target platform specification artifact org.jboss.tools.target-platforms.soatools-JunoSR1a:multiple:target:multiple:4.2.1.a-SNAPSHOT
> mvn clean verify -P soa
Could not resolve target platform specification artifact org.jboss.tools.target-platforms.soatools-JunoSR1a:multiple:target:multiple:4.2.1.a-SNAPSHOT
{code}
So... not sure what I'm doing wrong but I can't seem to resolve the new soatools TP definition.
was (Author: nickboldt):
I think some steps might be missing. Here's what I had to do... or at least I *assume* this will work. Had to shut down laptop while jbosstools-4.2.1.a tp build was running:
{code}
git clone git://github.com/jbosstools/jbosstools-maven-plugins/
pushd jbosstools-maven-plugins/tycho-plugins/; mvn install; popd
git clone git://github.com/mickaelistria/jbosstools-build.git
pushd jbosstools-build; git checkout JBIDE-11121
pushd parent; mvn install; popd
pushd target-platforms/jbosstools-4.2.1.a/; mvn install; popd
pushd target-platforms/soatools-4.2.1.a/; mvn install; popd
git clone git://github.com/jbosstools/jbosstools-bpel.git
pushd jbosstools-bpel
sed -i -e "s/4.1.0.Alpha1-SNAPSHOT/4.1.0.JBIDE-11121-SNAPSHOT/g" pom.xml
mvn clean verify -P soa -Dno.jbosstools.site -Dtycho.localArtifacts=ignore
popd
{code}
> Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11121
> URL: https://issues.jboss.org/browse/JBIDE-11121
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: SOA Tooling
> Affects Versions: 3.3.0.Beta1-SOA
> Reporter: Nick Boldt
> Assignee: Douglas Palmer
> Priority: Blocker
> Labels: f2f2012
> Fix For: 4.0.0.Alpha1-SOA
>
> Attachments: ModeShapeToolsBuildLog.txt
>
>
> Generate target platforms for JBT/JBDS SOA Tooling which include:
> 1. JBT Core TP + last stable JBT Core milestone.
> 2. JBDS Core TP + last stable JBDS Core milestone.
> Then, all SOA Component jobs should be rekeyed to use these new TPs when building instead of the JBT/JBDS Core ones.
> This includes Drools, which currently builds against Helios instead of Indigo, and Savara, which has requirements which are not as yet in the JBT/JBDS Core TPs (eg., GMF and Graphiti).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13249) Improve MDB support
by Clebert Suconic (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13249?page=com.atlassian.jira.plugi... ]
Clebert Suconic commented on JBIDE-13249:
-----------------------------------------
I was using the only option I found to create an MDB, which is through new -> other -> EJB -> MDB
Maybe that came from Eclipse.. it would be great if we could extend it..
I didn't find any other option under any of the JBoss Tools for MDBs.
> Improve MDB support
> -------------------
>
> Key: JBIDE-13249
> URL: https://issues.jboss.org/browse/JBIDE-13249
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: ejb3
> Reporter: Clebert Suconic
> Assignee: Rob Stryker
>
> I have recently tried creating an MDB and it seems out of date.
> It's not adding any annotations and not asking the user for any parameters.
> You could do something like this:
> - Ask what provider is going to be used...
> Ask what's the queue name to be used
> What Resource Adapter's name. (It would be great if you could inspect the server being used here for the RA's names. Each hornetq pooled connection factory will be a resource adapter name BTW).
> What Queue Name
> you could also provide additional activation properties by either selecting a list of providers. Or even better you could inspect the list of available activation properties, so it would be more generic.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13286) when kicking a job, generate a comment in JIRAs which match the changes for that job's build
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13286?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13286:
------------------------------------
Additionally, if would be really useful if we could pull the commit hashes from github, query the github rest api, and get data like this:
{code:title=https://api.github.com/repos/jbosstools/jbosstools-base/git/commits/fb35c2ce3d0787946d1cf7ffad7c22b216625ed0}
{
"tree": {
"url": "https://api.github.com/repos/jbosstools/jbosstools-base/git/trees/43da9f4...",
"sha": "43da9f474749a51919ee0b015bd81d69a780d12d"
},
"parents": [
{
"url": "https://api.github.com/repos/jbosstools/jbosstools-base/git/commits/09ffe...",
"sha": "09ffec0da4fbd698f7649cc7b1672af9b18779c8"
}
],
"url": "https://api.github.com/repos/jbosstools/jbosstools-base/git/commits/fb35c...",
"sha": "fb35c2ce3d0787946d1cf7ffad7c22b216625ed0",
"message": "JBIDE-13252 NullPointerException in AnnotationDeclaration.validateNamedValue\n\nTest is added.\n",
"author": {
"date": "2012-12-06T00:47:20Z",
"email": "scabanovich(a)exadel.com",
"name": "Viacheslav Kabanovich"
},
"committer": {
"date": "2012-12-06T01:35:09Z",
"email": "akazakov(a)exadel.com",
"name": "Alexey Kazakov"
}
}
{code}
This could either be dumped into Jenkins (via a plugin?), or perhaps better (to assist w/ non-VPN developers) it could be stuck into a file like this one:
http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.0_trunk....
> when kicking a job, generate a comment in JIRAs which match the changes for that job's build
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-13286
> URL: https://issues.jboss.org/browse/JBIDE-13286
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> Is it possible to pull the git hash value used for a given build, look into github for the matching JIRA #, and drop a comment into the JIRA to the tune of:
> "Spinning in <buildURL> >= BUILD_NUMBER"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months