[JBoss JIRA] (ARTIF-707) Uncaught GWT Error: Cannot read property 'indexOf' of null
by Thomas Heute (JIRA)
Thomas Heute created ARTIF-707:
----------------------------------
Summary: Uncaught GWT Error: Cannot read property 'indexOf' of null
Key: ARTIF-707
URL: https://issues.jboss.org/browse/ARTIF-707
Project: Artificer
Issue Type: Bug
Components: UI
Affects Versions: 1.0.0.Beta1
Reporter: Thomas Heute
Assignee: Brett Meyer
While playing with the UI, I tried to upload some random artifacts (In that case I tried to upload artificer-1.0.0.Beta1.zip itself.
I get an error in the UI:
Uncaught GWT Error!
Exception caught: (TypeError) : Cannot read property 'indexOf' of null
and a message remains forever:
Importing Artifact(s)
Please wait while your import is processed...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months
[JBoss JIRA] (ARTIF-705) Exception when adding properties or classifiers to artifact
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-705?page=com.atlassian.jira.plugin.... ]
Brett Meyer resolved ARTIF-705.
-------------------------------
Resolution: Done
> Exception when adding properties or classifiers to artifact
> -----------------------------------------------------------
>
> Key: ARTIF-705
> URL: https://issues.jboss.org/browse/ARTIF-705
> Project: Artificer
> Issue Type: Bug
> Affects Versions: 1.0.0.Beta1
> Environment: Wildfly 8.2 final, H2
> Reporter: Gary Brown
> Assignee: Brett Meyer
> Fix For: 1.0.0.Beta2
>
> Attachments: ordermgmt.jar, server.log
>
>
> Imported a jar artifact successfully.
> However when I tried to add a property on one of the derived artifacts, representing a SwitchYardComponentService, it resulted in an exception (org.jboss.errai.enterprise.client.jaxrs.api.ResponseException: Internal Server Error). Server log will be attached.
> I then created a simple Ontology called "Test" with top node "Country" and three sub nodes "UK", "France", "Germany". I then tried to 'modify classifiers' on the same artifact, selecting UK and Germany, and it resulted in the same exception.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months
[JBoss JIRA] (ARTIF-706) Create DerivedExtendedArtifactType
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-706?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on ARTIF-706:
-----------------------------------
Note: when this is fixed, search for all instances of "relatedDocument" and see what can be fixed...
> Create DerivedExtendedArtifactType
> ----------------------------------
>
> Key: ARTIF-706
> URL: https://issues.jboss.org/browse/ARTIF-706
> Project: Artificer
> Issue Type: Feature Request
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
> Having "relatedDocument" in an artifact's relationships list requires some stupid logic to deal with (see ArtifactVerifier#verifyNames). Instead, we should rely solely on the real #relatedDocument field. Unfortunately, that's only on DerivedArtifactType. If a derived artifact is an *extended* artifact, there's no access to that field, hence the need to use the general relationship. Re-work that structure to be more useful.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months
[JBoss JIRA] (ARTIF-706) Create DerivedExtendedArtifactType
by Brett Meyer (JIRA)
Brett Meyer created ARTIF-706:
---------------------------------
Summary: Create DerivedExtendedArtifactType
Key: ARTIF-706
URL: https://issues.jboss.org/browse/ARTIF-706
Project: Artificer
Issue Type: Feature Request
Reporter: Brett Meyer
Assignee: Brett Meyer
Having "relatedDocument" in an artifact's relationships list requires some stupid logic to deal with (see ArtifactVerifier#verifyNames). Instead, we should rely solely on the real #relatedDocument field. Unfortunately, that's only on DerivedArtifactType. If a derived artifact is an *extended* artifact, there's no access to that field, hence the need to use the general relationship. Re-work that structure to be more useful.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months
[JBoss JIRA] (ARTIF-705) Exception when adding properties or classifiers to artifact
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-705?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated ARTIF-705:
------------------------------
Fix Version/s: 1.0.0.Beta2
> Exception when adding properties or classifiers to artifact
> -----------------------------------------------------------
>
> Key: ARTIF-705
> URL: https://issues.jboss.org/browse/ARTIF-705
> Project: Artificer
> Issue Type: Bug
> Affects Versions: 1.0.0.Beta1
> Environment: Wildfly 8.2 final, H2
> Reporter: Gary Brown
> Assignee: Brett Meyer
> Fix For: 1.0.0.Beta2
>
> Attachments: ordermgmt.jar, server.log
>
>
> Imported a jar artifact successfully.
> However when I tried to add a property on one of the derived artifacts, representing a SwitchYardComponentService, it resulted in an exception (org.jboss.errai.enterprise.client.jaxrs.api.ResponseException: Internal Server Error). Server log will be attached.
> I then created a simple Ontology called "Test" with top node "Country" and three sub nodes "UK", "France", "Germany". I then tried to 'modify classifiers' on the same artifact, selecting UK and Germany, and it resulted in the same exception.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months
[JBoss JIRA] (ARTIF-705) Exception when adding properties or classifiers to artifact
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/ARTIF-705?page=com.atlassian.jira.plugin.... ]
Gary Brown updated ARTIF-705:
-----------------------------
Attachment: server.log
ordermgmt.jar
Log and imported artifact.
> Exception when adding properties or classifiers to artifact
> -----------------------------------------------------------
>
> Key: ARTIF-705
> URL: https://issues.jboss.org/browse/ARTIF-705
> Project: Artificer
> Issue Type: Bug
> Affects Versions: 1.0.0.Beta1
> Environment: Wildfly 8.2 final, H2
> Reporter: Gary Brown
> Assignee: Brett Meyer
> Attachments: ordermgmt.jar, server.log
>
>
> Imported a jar artifact successfully.
> However when I tried to add a property on one of the derived artifacts, representing a SwitchYardComponentService, it resulted in an exception (org.jboss.errai.enterprise.client.jaxrs.api.ResponseException: Internal Server Error). Server log will be attached.
> I then created a simple Ontology called "Test" with top node "Country" and three sub nodes "UK", "France", "Germany". I then tried to 'modify classifiers' on the same artifact, selecting UK and Germany, and it resulted in the same exception.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months
[JBoss JIRA] (ARTIF-705) Exception when adding properties or classifiers to artifact
by Gary Brown (JIRA)
Gary Brown created ARTIF-705:
--------------------------------
Summary: Exception when adding properties or classifiers to artifact
Key: ARTIF-705
URL: https://issues.jboss.org/browse/ARTIF-705
Project: Artificer
Issue Type: Bug
Affects Versions: 1.0.0.Beta1
Environment: Wildfly 8.2 final, H2
Reporter: Gary Brown
Assignee: Brett Meyer
Imported a jar artifact successfully.
However when I tried to add a property on one of the derived artifacts, representing a SwitchYardComponentService, it resulted in an exception (org.jboss.errai.enterprise.client.jaxrs.api.ResponseException: Internal Server Error). Server log will be attached.
I then created a simple Ontology called "Test" with top node "Country" and three sub nodes "UK", "France", "Germany". I then tried to 'modify classifiers' on the same artifact, selecting UK and Germany, and it resulted in the same exception.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months
[JBoss JIRA] (ARTIF-703) Auto install DDL if the tables don't exist
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-703?page=com.atlassian.jira.plugin.... ]
Brett Meyer resolved ARTIF-703.
-------------------------------
Fix Version/s: 1.0.0.Beta2
Resolution: Done
> Auto install DDL if the tables don't exist
> ------------------------------------------
>
> Key: ARTIF-703
> URL: https://issues.jboss.org/browse/ARTIF-703
> Project: Artificer
> Issue Type: Enhancement
> Affects Versions: 1.0.0.Beta1
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Fix For: 1.0.0.Beta2
>
>
> Since we now build the EMF programmatically, on demand, we should be able to automatically install the DDL on the DB if the tables don't already exist. This is *much* preferred over Hibernate's hbm2ddl, since we can use our real (optimized) DDL SQL. Further, it will allow users to get started even quicker. Even further, we'll need something like this for Docker anyway...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months