[JBoss JIRA] (JBIDE-19536) Infinite job loop when creating project
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19536?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-19536:
---------------------------------------
What maven projects have you imported?
Is this test case always reproducible?
> Infinite job loop when creating project
> ---------------------------------------
>
> Key: JBIDE-19536
> URL: https://issues.jboss.org/browse/JBIDE-19536
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.3.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Snjezana Peco
> Fix For: 4.3.0.CR1
>
> Attachments: building.png, cdi_jstack, jstack.out, threaddump-1440009974151.tdump, threaddump-1440009999047.tdump, threaddump-1440010035476.tdump
>
>
> Sometimes i end up in infinite job loop after creating a CDI project. There's no description of what jobs are running, not exception in log. In progress view I can see only "Building workspace (sleeping)" -see on video https://vimeo.com/123634974
> I was able to reproduce on CDI projects (1.0,1.2) but not on any other (Dynamic Web..)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (JBIDE-19948) Reimplement Eclipse Download plugin to allow dynamic work flow
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19948?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19948:
---------------------------------------------
im still not following why we need this kind of complexity to do a download. If a user does not have access why is it not enough to just send him to a website and then refresh on eclipse side to reauthenticate and get the bits ?
> Reimplement Eclipse Download plugin to allow dynamic work flow
> --------------------------------------------------------------
>
> Key: JBIDE-19948
> URL: https://issues.jboss.org/browse/JBIDE-19948
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection, server
> Affects Versions: 4.3.0.Alpha2
> Reporter: David Hladky
> Assignee: Rob Stryker
> Fix For: 4.3.0.CR1
>
>
> We need to reimplement the plugin to accept new terms and conditions models as well as follow the workflow changes in case of changes to the current ones.
> Under this issue I will create the tasks we need to achieve this goal.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (JBIDE-20100) how to make users aware of fuse and other tooling only being available from earlyaccess?
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-20100:
----------------------------------------
Just had a call with [~maxandersen] and here are the next steps:
* Have "empty" discovery connectors just for advertisement
* About new flow, prevent people to install non-EA versions of connectors when EA is installed (to avoid potential issues with streams crossing, units overlapping,...)
Overall, we agreed that showing into the IDE some parts of UI saying "If you want to use XYZ, please use older version of this tool" is a very bad user experience. It would be much better to have actual content to install.
> how to make users aware of fuse and other tooling only being available from earlyaccess?
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-20100
> URL: https://issues.jboss.org/browse/JBIDE-20100
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.3.0.CR1
>
> Attachments: JBIDE-20100-2.png
>
>
> [~jtyrrell] find it confusing when he cannot see Fuse and other earlyaccess features immediately on the install page.
> Some comments:
> "I install JBDS 8.1 and click on the JBoss Integration and SOA Development, but where is the Fuse tooling in that list."
> "<without earlyaccess> why doesn’t my screen shot tell me to use an older version of JBDS or something."
> Suggestion:
> "when I picked the Integration Stack a greyed out Fuse IDE thingy in the list of choices, and something like (Select early Access) to enable this feature."
> I'm fine exploring options to show early access features more prominently but would prefer we would not need to treat Fuse "special" so maybe we should have a "Early Access" section at the bottom instead of filtered in between everything else ?
> and for any connectors that has additional/different features just add a "Extra features available in Early access " comment ?
> But what to do when Fuse or others dont even have an earlyaccess out yet ? (like is currently the state for devstudio 9)
> [~crobson], [~aileenc] and [~lhein] got any suggestions ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (JBIDE-19536) Infinite job loop when creating project
by Vsevolod Golovanov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19536?page=com.atlassian.jira.plugi... ]
Vsevolod Golovanov edited comment on JBIDE-19536 at 9/1/15 6:45 AM:
--------------------------------------------------------------------
Reproduced it again.
I have a maven project hierarchy. It's imported in JBDS as maven projects with m2e.
I had JBDS open, the workspace was fully built. I did an {{mvn clean install -DskipTests}} from the command line, waited till it finished. Then selected all projects in JBDS and refreshed them. This resulted in an endless "Building workspace" loop.
was (Author: vsevolodgolovanov):
Reproduced it again.
I have a maven project hierarchy.
I had JBDS open, the workspace was fully built. I did an {{mvn clean install -DskipTests}} from the command line, waited till it finished. Then selected all projects in JBDS and refreshed them. This resulted in an endless "Building workspace" loop.
> Infinite job loop when creating project
> ---------------------------------------
>
> Key: JBIDE-19536
> URL: https://issues.jboss.org/browse/JBIDE-19536
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.3.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Snjezana Peco
> Fix For: 4.3.0.CR1
>
> Attachments: building.png, cdi_jstack, jstack.out, threaddump-1440009974151.tdump, threaddump-1440009999047.tdump, threaddump-1440010035476.tdump
>
>
> Sometimes i end up in infinite job loop after creating a CDI project. There's no description of what jobs are running, not exception in log. In progress view I can see only "Building workspace (sleeping)" -see on video https://vimeo.com/123634974
> I was able to reproduce on CDI projects (1.0,1.2) but not on any other (Dynamic Web..)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (JBIDE-19536) Infinite job loop when creating project
by Vsevolod Golovanov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19536?page=com.atlassian.jira.plugi... ]
Vsevolod Golovanov edited comment on JBIDE-19536 at 9/1/15 6:45 AM:
--------------------------------------------------------------------
Reproduced it again.
I have a maven project hierarchy. It's imported in JBDS as maven projects via m2e.
I had JBDS open, the workspace was fully built. I did an {{mvn clean install -DskipTests}} from the command line, waited till it finished. Then selected all projects in JBDS and refreshed them. This resulted in an endless "Building workspace" loop.
was (Author: vsevolodgolovanov):
Reproduced it again.
I have a maven project hierarchy. It's imported in JBDS as maven projects with m2e.
I had JBDS open, the workspace was fully built. I did an {{mvn clean install -DskipTests}} from the command line, waited till it finished. Then selected all projects in JBDS and refreshed them. This resulted in an endless "Building workspace" loop.
> Infinite job loop when creating project
> ---------------------------------------
>
> Key: JBIDE-19536
> URL: https://issues.jboss.org/browse/JBIDE-19536
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.3.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Snjezana Peco
> Fix For: 4.3.0.CR1
>
> Attachments: building.png, cdi_jstack, jstack.out, threaddump-1440009974151.tdump, threaddump-1440009999047.tdump, threaddump-1440010035476.tdump
>
>
> Sometimes i end up in infinite job loop after creating a CDI project. There's no description of what jobs are running, not exception in log. In progress view I can see only "Building workspace (sleeping)" -see on video https://vimeo.com/123634974
> I was able to reproduce on CDI projects (1.0,1.2) but not on any other (Dynamic Web..)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (JBIDE-19536) Infinite job loop when creating project
by Vsevolod Golovanov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19536?page=com.atlassian.jira.plugi... ]
Vsevolod Golovanov commented on JBIDE-19536:
--------------------------------------------
Reproduced it again.
I have a maven project hierarchy.
I had JBDS open, the workspace was fully built. I did an {{mvn clean install -DskipTests}} from the command line, waited till it finished. Then selected all projects in JBDS and refreshed them. This resulted in an endless "Building workspace" loop.
> Infinite job loop when creating project
> ---------------------------------------
>
> Key: JBIDE-19536
> URL: https://issues.jboss.org/browse/JBIDE-19536
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.3.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Snjezana Peco
> Fix For: 4.3.0.CR1
>
> Attachments: building.png, cdi_jstack, jstack.out, threaddump-1440009974151.tdump, threaddump-1440009999047.tdump, threaddump-1440010035476.tdump
>
>
> Sometimes i end up in infinite job loop after creating a CDI project. There's no description of what jobs are running, not exception in log. In progress view I can see only "Building workspace (sleeping)" -see on video https://vimeo.com/123634974
> I was able to reproduce on CDI projects (1.0,1.2) but not on any other (Dynamic Web..)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (JBIDE-20100) how to make users aware of fuse and other tooling only being available from earlyaccess?
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-20100:
---------------------------------------------
d) so now we make it more complicated to disable the earlyaccess repository ? that seems unnecessary to me.
"the fact that you have some Early-Access repositories enabled doesn't guarantee that when installing a connector, you get the Early-Access version of its features/plugins." - some EA repositories ? There are only *one* repository. And how are you avoiding it will not get the earlyaccess versions of angularjs ?
"With our current implementation of Central and the connectors we have, the same feature isn't available in 2 different versions" - the intent of earlyaccess have always been to also be able to allow *earlier* versions of the same thing installed. I do not think we should limit our UX experience here to a world where we will *always* guarantee there are zero overlap between the two.
And this *is* a change compared to the old UI where when earlyaccess was enabled you were not in any way offered to install the GA versions since we know it will install the EA parts once the EA site is added. So this is for sure a consequence/ambiguity this new UI introduces.
"The description doesn't even mention anything about older JBDS. It's more your mind which is focused on that part than the initial user request.". Let me quote from the description which *I* wrote and which Jim provided input to - a user that just commented the exact concern about not being able to guarantee tooling are available for users to use :)
""<without earlyaccess> why doesn’t my screen shot tell me to use an older version of JBDS or something.""
That is the first and foremost issue and still not solved.
"To me, this means that we can put current Fuse IDE as an "Early Access" connector in JBDS 9" - *we* (you and I) do not get to decide when that is available; nor is everything in JBDS-IS currently available for JBDS 9 EA so the issue still remains.
The current PR does not solve the problem raised, and it currently introduces an ambiguity about what will happen wen earlyaccess repositories are added - if we are going to do a change here we need to at least make sure the behavior is not ambiguous.
If we are going to leave out the "tell users when things are not even available in EA" part of this that will only happen because just by luck we have enough IS available .... but this will not help us at 9.1, 10.0, etc.
> how to make users aware of fuse and other tooling only being available from earlyaccess?
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-20100
> URL: https://issues.jboss.org/browse/JBIDE-20100
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.3.0.CR1
>
> Attachments: JBIDE-20100-2.png
>
>
> [~jtyrrell] find it confusing when he cannot see Fuse and other earlyaccess features immediately on the install page.
> Some comments:
> "I install JBDS 8.1 and click on the JBoss Integration and SOA Development, but where is the Fuse tooling in that list."
> "<without earlyaccess> why doesn’t my screen shot tell me to use an older version of JBDS or something."
> Suggestion:
> "when I picked the Integration Stack a greyed out Fuse IDE thingy in the list of choices, and something like (Select early Access) to enable this feature."
> I'm fine exploring options to show early access features more prominently but would prefer we would not need to treat Fuse "special" so maybe we should have a "Early Access" section at the bottom instead of filtered in between everything else ?
> and for any connectors that has additional/different features just add a "Extra features available in Early access " comment ?
> But what to do when Fuse or others dont even have an earlyaccess out yet ? (like is currently the state for devstudio 9)
> [~crobson], [~aileenc] and [~lhein] got any suggestions ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (JBIDE-19948) Reimplement Eclipse Download plugin to allow dynamic work flow
by David Hladky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19948?page=com.atlassian.jira.plugi... ]
David Hladky commented on JBIDE-19948:
--------------------------------------
Hi Max, the current implementation is kinda broken. It was designed to be universal and the relatively easy to use, however the later additions to the communication protocol and the hard coded stuff made it complicated and barely maintainable on both sides. For example name of the file is added as a text field, the xml format is on my side generated manually and therefore it is not suitable for easy parsing using RestEasy and similar frameworks and ohers.....
A) I hoped [~rob.stryker] would have had the layouts prepared by today so the only thing left would have been would have been adding the communication part. I do not know how soon will the code freeze be, if it is this week or next week, I think it makes sense to postpone it to the next development phase. It is pity I was stuck with other critical stuff and blockers so I had time to start working on JBIDE-19948 on last Friday and not earlier as originally planned.
B) I agree completely and we solved it with Rob. The plan was Rob will add version number as a query parameter to the request, which tells DM server part what format to use. No version number = old behaviour. version=1 would allow using the planned layouts and maybe sometime in future versions 2+ would allow more layouts if needed.
C) We really need to make it simple and I think it is possible. Right now I am working on an artifact, that will be deployed to repository.jboss.org. It will contain classes for marshalling and un-marshalling using JAX-RS on both sides, which would simplify the thing quite a lot. Server side the old implementation will need to stay, but in DS the bad implementation should go away completely and the new one should be used instead.
To make the thing easy the original idea of the stateless approach on side of the Eclipse plugin should be used. It is not difficult to have multiple independent components (in this case layouts) and simply pick the one, that matches its identifier. The current implementation has state smuggled into the plugin logic, which makes the whole thing complicated and it caused a lot of problems when I added the new TC model into the system.
----
I will continue the work on the server part. The number 1 priority on my side is to prepare a document, that describes the new approach. When it is done, we can discuss it and possibly do adjustments to it to suite your needs best. I do not know, if we will be able to get the changes to the current DS release, but I now have working capacity for it so I will finish the server side to be ready for DS.
> Reimplement Eclipse Download plugin to allow dynamic work flow
> --------------------------------------------------------------
>
> Key: JBIDE-19948
> URL: https://issues.jboss.org/browse/JBIDE-19948
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection, server
> Affects Versions: 4.3.0.Alpha2
> Reporter: David Hladky
> Assignee: Rob Stryker
> Fix For: 4.3.0.CR1
>
>
> We need to reimplement the plugin to accept new terms and conditions models as well as follow the workflow changes in case of changes to the current ones.
> Under this issue I will create the tasks we need to achieve this goal.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (JBIDE-19536) Infinite job loop when creating project
by Vsevolod Golovanov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19536?page=com.atlassian.jira.plugi... ]
Vsevolod Golovanov edited comment on JBIDE-19536 at 9/1/15 5:37 AM:
--------------------------------------------------------------------
I seem to encounter the same issue with JBDS9.0.0.Beta2 periodically (once in 1-2 work days). I'm not sure how I get to this state, and how to get out of it quick and easy. Just restarting JDBS doesn't help. So far the only thing that helps is cleaning and maven-updating projects.
It's bad, because it completely nullifies hot deploy. Fixing it requires a lengthy full rebuild or two.
!building.png!
I've cropped the buttons on the right of the queued operations. They're the red square "stop" buttons, not the gray X "remove finished" buttons.
I've attached 3 Visuam VM thread dumps. About 30 seconds between takes.
[^threaddump-1440009974151.tdump]
[^threaddump-1440009999047.tdump]
[^threaddump-1440010035476.tdump]
was (Author: vsevolodgolovanov):
I seem to encounter the same issue with JBDS9.0.0.Beta2 periodically (once in 1-2 work days). I'm not sure how I get to this state, and how to get out of it quick and easy. Just restarting JDBS doesn't help. So far the only thing that helps is cleaning and maven-updating projects.
It's bad, because it completely nullifies hot deploy. Fixing it requires a lengthy full rebuild or two.
!building.png!
I've cropped the buttons on the right of the queued operations. They're the reg square "stop" buttons, not the gray X "remove finished" buttons.
I've attached 3 Visuam VM thread dumps. About 30 seconds between takes.
[^threaddump-1440009974151.tdump]
[^threaddump-1440009999047.tdump]
[^threaddump-1440010035476.tdump]
> Infinite job loop when creating project
> ---------------------------------------
>
> Key: JBIDE-19536
> URL: https://issues.jboss.org/browse/JBIDE-19536
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.3.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Snjezana Peco
> Fix For: 4.3.0.CR1
>
> Attachments: building.png, cdi_jstack, jstack.out, threaddump-1440009974151.tdump, threaddump-1440009999047.tdump, threaddump-1440010035476.tdump
>
>
> Sometimes i end up in infinite job loop after creating a CDI project. There's no description of what jobs are running, not exception in log. In progress view I can see only "Building workspace (sleeping)" -see on video https://vimeo.com/123634974
> I was able to reproduce on CDI projects (1.0,1.2) but not on any other (Dynamic Web..)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (JBIDE-20541) wildfly-jts-application-component-2 quickstart fails to validate
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20541?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-20541:
--------------------------------
Description:
See https://issues.jboss.org/browse/WFLY-5250 for followup.
The above quickstart fails to validate in eclipse. It has the following lines in it:
{code}
<jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:iiop="urn:iiop"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd
http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd
urn:iiop jboss-ejb-iiop_1_0.xsd"
version="3.1"
impl-version="2.0">
<assembly-descriptor>
<iiop:iiop>
<ejb-name>InvoiceManagerEJBImpl</ejb-name>
<iiop:binding-name>jts-quickstart/InvoiceManagerEJBImpl</iiop:binding-name>
</iiop:iiop>
</assembly-descriptor>
</jboss:ejb-jar>
{code}
The key line to note is:
{code}
urn:iiop jboss-ejb-iiop_1_0.xsd"
{code}
Using relative paths cannot guarantee the resolution of a dependent schema. I suggest you replace this with:
{code}
urn:iiop http://www.jboss.org/schema/jbossas/jboss-ejb-iiop_1_0.xsd"
{code}
However, even once that is fixed, the quickstart still has other problems. For one example:
{code}
cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:iiop'. One of '{"http://
java.sun.com/xml/ns/javaee":security-role, "http://java.sun.com/xml/ns/javaee":method-
permission, "http://java.sun.com/xml/ns/javaee":container-transaction, "http://java.sun.com/xml/ns/
javaee":interceptor-binding, "http://java.sun.com/xml/ns/javaee":message-destination, "http://
java.sun.com/xml/ns/javaee":exclude-list, "http://java.sun.com/xml/ns/javaee":application-
exception}' is expected.
{code}
I strongly suggest someone test the quickstart in JBossTools and help come up with a descriptor that passes validation.
was:
See https://issues.jboss.org/browse/WFLY-5250 for followup.
The above quickstart fails to validate in eclipse. It has the following lines in it:
{code}
<jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:iiop="urn:iiop"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd
http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd
urn:iiop http://www.jboss.org/schema/jbossas/jboss-ejb-iiop_1_0.xsd"
version="3.1"
impl-version="2.0">
<assembly-descriptor>
<iiop:iiop>
<ejb-name>InvoiceManagerEJBImpl</ejb-name>
<iiop:binding-name>jts-quickstart/InvoiceManagerEJBImpl</iiop:binding-name>
</iiop:iiop>
</assembly-descriptor>
</jboss:ejb-jar>
{code}
The key line to note is:
{code}
urn:iiop http://www.jboss.org/schema/jbossas/jboss-ejb-iiop_1_0.xsd"
{code}
Using relative paths cannot guarantee the resolution of a dependent schema. I suggest you replace this with:
{code}
urn:iiop http://www.jboss.org/schema/jbossas/jboss-ejb-iiop_1_0.xsd"
{code}
However, even once that is fixed, the quickstart still has other problems. For one example:
{code}
cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:iiop'. One of '{"http://
java.sun.com/xml/ns/javaee":security-role, "http://java.sun.com/xml/ns/javaee":method-
permission, "http://java.sun.com/xml/ns/javaee":container-transaction, "http://java.sun.com/xml/ns/
javaee":interceptor-binding, "http://java.sun.com/xml/ns/javaee":message-destination, "http://
java.sun.com/xml/ns/javaee":exclude-list, "http://java.sun.com/xml/ns/javaee":application-
exception}' is expected.
{code}
I strongly suggest someone test the quickstart in JBossTools and help come up with a descriptor that passes validation.
> wildfly-jts-application-component-2 quickstart fails to validate
> -----------------------------------------------------------------
>
> Key: JBIDE-20541
> URL: https://issues.jboss.org/browse/JBIDE-20541
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server
> Affects Versions: 4.3.0.CR1
> Reporter: Rob Stryker
>
> See https://issues.jboss.org/browse/WFLY-5250 for followup.
> The above quickstart fails to validate in eclipse. It has the following lines in it:
> {code}
> <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"
> xmlns="http://java.sun.com/xml/ns/javaee"
> xmlns:iiop="urn:iiop"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd
> http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd
> urn:iiop jboss-ejb-iiop_1_0.xsd"
> version="3.1"
> impl-version="2.0">
> <assembly-descriptor>
> <iiop:iiop>
> <ejb-name>InvoiceManagerEJBImpl</ejb-name>
> <iiop:binding-name>jts-quickstart/InvoiceManagerEJBImpl</iiop:binding-name>
> </iiop:iiop>
> </assembly-descriptor>
> </jboss:ejb-jar>
> {code}
> The key line to note is:
> {code}
> urn:iiop jboss-ejb-iiop_1_0.xsd"
> {code}
> Using relative paths cannot guarantee the resolution of a dependent schema. I suggest you replace this with:
> {code}
> urn:iiop http://www.jboss.org/schema/jbossas/jboss-ejb-iiop_1_0.xsd"
> {code}
> However, even once that is fixed, the quickstart still has other problems. For one example:
> {code}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:iiop'. One of '{"http://
> java.sun.com/xml/ns/javaee":security-role, "http://java.sun.com/xml/ns/javaee":method-
> permission, "http://java.sun.com/xml/ns/javaee":container-transaction, "http://java.sun.com/xml/ns/
> javaee":interceptor-binding, "http://java.sun.com/xml/ns/javaee":message-destination, "http://
> java.sun.com/xml/ns/javaee":exclude-list, "http://java.sun.com/xml/ns/javaee":application-
> exception}' is expected.
> {code}
> I strongly suggest someone test the quickstart in JBossTools and help come up with a descriptor that passes validation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months